guide
  • Introduction
  • Guiding Principles
    • Mission Statement
    • Conflict Resolution Process
  • Operating Model
    • Working Together
    • Holacracy
      • Meetings
      • Specific Roles
      • Terms and Definitions
      • Finer Points
      • Holacracy-Asana Key
    • Getting Things Done
      • Daily, Weekly, Monthly, and Annual Reviews
      • GTD-Asana Key
    • Transparency
    • Language
    • Budgeting
    • By Department
      • Engineering Operations
  • General Guidelines
  • Employment Policies
    • Equal Opportunity Employment
    • At-Will Employment
    • Code of Conduct in the Community
    • Complaint Policy
    • Drug and Alcohol Policy
    • Vacation, Holiday, and Paid Time Off (PTO) Policy
    • Supplemental Policies for Remote Employees and Contractors
    • Supplemental Policy for Bonus, Commissions, and other Performance-based Payments
    • Supplemental Policies for Hourly International Contractors or Workers
    • Supplemental Policies for Hourly International Contractors or Workers
    • Disputes and Arbitration
  • Benefits and Perks
    • Health Care
    • Vacation, Holiday and Paid Time Off (PTO) Policy
    • Holiday List
  • Hiring Documents
    • Acknowledgement of Receipt
    • Partner Proprietary Information and Inventions Agreement
  • Engineering Wiki
    • Code Snippets
      • Front End Code Snippets
    • Setup
      • 1: Overview of development using Audienti
      • 2: How to setup your dev environment on Docker
      • 2a: Setting up on our cloud your dev server
      • 3: Connect to Production using the VPN
      • 4: Import data into your development environment
    • Deployment
      • Docker based deployment of back end (manual)
    • Culture
      • How our development team works
      • Code Best Practices
    • Tips
      • Setting up a new development machine
      • Importing data to Development environment
      • GIT workflow and work tracking
      • Using Slack
      • Using Rubocop
      • Our Code Standards
      • General suggested best practices
      • Tracking your time
      • Naming Iterations
    • Migrations
      • Postgres
      • ElasticSearch
      • Redis
    • Database and System Maintenance
      • Redis Howtos
      • Elasticsearch HowTos
      • Postgres HowTos
      • Administration recipes
      • App maintenance crash course notes
    • Front End
      • 2016 Plan
      • Deploy
      • Assets
      • SearchLogic
      • How to create UI components
      • OMA Standard Tables
    • Monitoring and Alerting
      • Monitoring Systems
      • Monitoring individual controller actions
      • Get notified when a metric reaches a certain threshold
      • Instrumenting your models using Oma Stats
      • Configuring Graphite Charts
      • Tracking your results with StatsD
      • Logging Fields
      • Updating Kibana Filtering
    • Testing
      • Coverage
      • Elasticsearch mapping config synchronization
      • Testing Gotchas
      • Rspec Preloader
      • Test Best Practices
    • Models
      • Backlinks
    • Queueing and Worker System
      • Queueing and Job Overview
    • Processors
      • Rebuilding Spot Instances
      • Deploying processors
      • Running processors in development
      • Reverting to the previous build on a failed deployment
    • Processors / Opportunity Pipeline
      • Opportunity Pipeline
      • Diagram
    • Processors / Enrichment Pipeline
      • Diagram
      • Clustering
    • Processors / Backlink Pipeline
      • Diagram
      • Backlink Pipeline external APIs
      • Backlink pipeline logic
    • Processors / Automation Pipeline
      • Diagram
      • Automation Pipeline Overview
      • Agents
      • Running in development
    • Messaging and Social Accounts
      • Overview
    • API
      • Audienti API
    • Algorithms
    • Troubleshooting
      • Elasticsearch
    • Big Data Pipeline Stuff
      • Spark
    • Our Product
      • Feature synopsis of our product
    • Research
      • Backend framework comparison
      • Internet marketing Saas companies
    • Code snippets
      • Commonly Used
      • Not Used
    • Miscellaneous
      • Proxies and Bax
    • Legacy & Deprecated
      • Search criteria component
      • Classes list
      • Target Timeline
      • Twitter processor
      • Asset compilation
      • Test related information
      • Interface to EMR Hadoop jobs
      • Mongo Dex Indexes to be Built
      • Mongodb errors
      • Opportunity pipeline scoring
      • Graph Page
      • Lead scoring
      • Insights
      • Shard keys
      • Setting up OMA on local
      • Clone project to local machine
      • Getting around our servers in AWS
  • Acknowledgements
  • Documents That Receiving Your First Payment Triggers Acknowledgement and Acceptanace
Powered by GitBook
On this page
  • Vacation, Holiday, and Paid Time Off (PTO) Policy
  • Our Policy
  • Your Responsibilities
  • Details
  1. Benefits and Perks

Vacation, Holiday and Paid Time Off (PTO) Policy

EARLY DRAFT: This section still needs a lot more work before it is ready. Most things here will probably change before it reaches a publishable state.

Vacation, Holiday, and Paid Time Off (PTO) Policy

Here at OMAlab, we’re working hard on creating a culture of personal responsibility and mutual trust, and we wanted our vacation and time off policy to reflect that. After some reflection, we decided to adopt an Open PTO Policy which allows our employees the flexibility to take time off when they need it. Netflix and other large employers have shown that this can work on a large scale, and it matches our culture perfectly.

We strongly feel that we’ll have better employee productivity and retention with this policy, but it’s not for everyone. It requires a strong peer review process and a lot of trust in your employees.

Here at OMAlab, we recognize the need for employees to take time away from the office to creatively recharge, and that not everyone works the best during traditional 9 to 5 office hours. We also believe in taking personal responsibility for managing our own time, workload and results. To that end, we’ve adopted an Open PTO (Paid Time Off) policy, in which each employee is afforded the flexibility to take vacation, take time off for illness and shift schedules as necessary.

Our Policy

We do not track or limit vacation times or sick days – take the time you need to operate at peak performance.

You are welcome to shift your schedules to match your work style, as long as it does not impact the productivity of your colleagues.

Your Responsibilities

Keep your coworkers informed. Let your colleagues know at least 2 weeks ahead of schedule when you’ll be on vacation, and report in on days you need to be out unexpectedly.

Be available when you’re needed. Customer calls, staff meetings and other time sensitive responsibilities must be covered regardless of your personal work schedule. If you have planned time off, make sure to coordinate with your coworkers to have coverage for any of your responsibilities during that time off.

Be productive. You are engaged by OMAlab with a role that has expectations and responsibilities, and are expected to maintain them. Let your colleagues know when you will be taking time off for your country's schedule. For example, Independence Day, etc. at least 2 weeks in advance.

Details

  1. The OMAlab Open PTO plan is only available to full-time, exempt (salaried) OMAlab employees.

  2. You do not “accrue” PTO days as in traditional plans, and so will not be compensated for “unused” PTO time when you leave the company.

PreviousHealth CareNextHoliday List

Last updated 7 years ago