• Product
  • Pricing
  • Docs
  • Using PostHog
  • Community
  • Company
  • Login
  • Table of contents

  • Handbook
    • Start here
    • Meetings
    • Story
    • Team
    • Investors
    • Strategy overview
    • Ideal Customer Persona
    • Business model
    • Objectives
    • Roadmap
    • Brand
    • Culture
    • Values
    • Small teams
    • Goal setting
    • Diversity and inclusion
    • Communication
    • Management
    • Sprints
    • Offsites
    • Security
    • Brand assets
    • Team structure
    • Customer Success
    • Exec
    • Experimentation
    • Growth
    • Infrastructure
    • Marketing
    • People & Ops
    • Pipeline
    • Product Analytics
    • Session Recording
    • Website & Docs
    • Compensation
    • Share options
    • Benefits
    • Time off
    • Spending money
    • Progression
    • Training
    • Side gigs
    • Feedback
    • Onboarding
    • Offboarding
      • Product Manager ramp up
    • Merch store
      • Overview
      • How to interview
      • Engineering hiring
      • Marketing hiring
      • Operations hiring
      • Design hiring
      • Exec hiring
      • Developing locally
      • Tech stack
      • Project structure
      • How we review PRs
      • Frontend coding
      • Backend coding
      • Support hero
      • Feature ownership
      • Working with product design
      • Releasing a new version
      • Handling incidents
      • Bug prioritization
      • Event ingestion explained
      • Making schema changes safely
      • How to optimize queries
      • How to write an async migration
      • How to run migrations on PostHog Cloud
      • Working with ClickHouse materialized columns
      • Deployments support
      • Working with cloud providers
      • How-to access PostHog Cloud infra
      • Developing the website
      • MDX setup
      • Markdown
      • Jobs
      • Overview
      • Data storage or what is a MergeTree
      • Data replication
      • Data ingestion
      • Working with JSON
      • Query performance
      • Operations
        • Overview
        • sharded_events
        • app_metrics
        • person_distinct_id
    • Shipping things, step by step
    • Feature flags specification
    • Setting up SSL locally
    • Tech talks
    • Overview
    • Product metrics
    • User feedback
    • Paid features
    • Releasing as beta
    • Our philosophy
    • Product design process
    • Designing posthog.com
    • Overview
    • Personas
    • Testimonials
    • Value propositions
      • Content & SEO
      • Sponsorship
      • Paid ads
      • Email
      • Press
      • YouTube
    • Growth strategy
    • Customer support
    • Inbound sales model
    • Sales operations
      • Managing our CRM
      • YC onboarding
      • Demos
      • Billing
      • Who we do business with
    • Growth reviews
  • Table of contents

  • Handbook
    • Start here
    • Meetings
    • Story
    • Team
    • Investors
    • Strategy overview
    • Ideal Customer Persona
    • Business model
    • Objectives
    • Roadmap
    • Brand
    • Culture
    • Values
    • Small teams
    • Goal setting
    • Diversity and inclusion
    • Communication
    • Management
    • Sprints
    • Offsites
    • Security
    • Brand assets
    • Team structure
    • Customer Success
    • Exec
    • Experimentation
    • Growth
    • Infrastructure
    • Marketing
    • People & Ops
    • Pipeline
    • Product Analytics
    • Session Recording
    • Website & Docs
    • Compensation
    • Share options
    • Benefits
    • Time off
    • Spending money
    • Progression
    • Training
    • Side gigs
    • Feedback
    • Onboarding
    • Offboarding
      • Product Manager ramp up
    • Merch store
      • Overview
      • How to interview
      • Engineering hiring
      • Marketing hiring
      • Operations hiring
      • Design hiring
      • Exec hiring
      • Developing locally
      • Tech stack
      • Project structure
      • How we review PRs
      • Frontend coding
      • Backend coding
      • Support hero
      • Feature ownership
      • Working with product design
      • Releasing a new version
      • Handling incidents
      • Bug prioritization
      • Event ingestion explained
      • Making schema changes safely
      • How to optimize queries
      • How to write an async migration
      • How to run migrations on PostHog Cloud
      • Working with ClickHouse materialized columns
      • Deployments support
      • Working with cloud providers
      • How-to access PostHog Cloud infra
      • Developing the website
      • MDX setup
      • Markdown
      • Jobs
      • Overview
      • Data storage or what is a MergeTree
      • Data replication
      • Data ingestion
      • Working with JSON
      • Query performance
      • Operations
        • Overview
        • sharded_events
        • app_metrics
        • person_distinct_id
    • Shipping things, step by step
    • Feature flags specification
    • Setting up SSL locally
    • Tech talks
    • Overview
    • Product metrics
    • User feedback
    • Paid features
    • Releasing as beta
    • Our philosophy
    • Product design process
    • Designing posthog.com
    • Overview
    • Personas
    • Testimonials
    • Value propositions
      • Content & SEO
      • Sponsorship
      • Paid ads
      • Email
      • Press
      • YouTube
    • Growth strategy
    • Customer support
    • Inbound sales model
    • Sales operations
      • Managing our CRM
      • YC onboarding
      • Demos
      • Billing
      • Who we do business with
    • Growth reviews
  • Handbook
  • Small teams
  • People & Ops

People & Ops Team

Last updated: Dec 12, 2022

On this page

  • People & Ops
  • Mission
  • Responsibilities
  • Customer
  • Objectives & key results
  • Q1 2023
  • Team 121s
  • Slack channels
  • Tools
  • Hiring
  • Contracts & Offer Letters
  • HR, Recruiting, and Payroll
  • Finance and Banking
  • Everything Else
  • What we're building

People & Ops

Team members

  • Charles Cook

    Team lead

    Operations & Marketing

  • Grace McKenzie

    Operations Manager

  • Coua Phang

    Tech Talent Partner

  • Kendal Hall

    Executive Assistant

Mission

Our primary goal is to build and retain our world-class team. We will accomplish this by making PostHog the most transparent company in the world, and the best place for people to work. Once on board, our goal is to enable our team to:

  1. Maximize their impact and performance
  2. Grow personally and professionally
  3. Have a strong sense of purpose and belonging

Responsibilities

Our people team works across talent, people, operations, and culture. This is what we care about:

  • Setting a very high bar for bringing people on board. We are always looking for the best people in their field, or people on their way to becoming exceptional at their jobs. This is so important to us, it's enshrined in our values.
  • Supporting our team throughout the entire employee lifecycle - from making an offer, to onboarding and career development, parental leave, and eventually parting ways.
  • We create light-touch initiatives, systems, and processes that allow PostHog to act fast and scale iteratively
  • Building a diverse and inclusive culture with a strong sense of belonging is at the heart of everything we do. It's so important to us, we have a dedicated handbook page.

We use the RACI model to manage the various areas of focus within the team:

  • R = Responsible ie who is in charge of getting the work done
  • A = Accountable ie who ensures that the work gets done
  • C = Consulted ie who needs to be brought in on decisions
  • I = Informed ie who needs to be told when decisions are made
CharlesGraceCoua
People Ops
UK payrollIR,AC,I
UK pensionIR,AC,I
UK benefitsIR,AC,I
US payrollIR,AC,I
US 401(k)IR,AC,I
US benefitsIR,AC,I
Offer lettersCIR,A
Onboarding - legalIR,AC,I
Onboarding - companyC,IC,IR,A
State registrationsIR,AC,I
Compensation reviewsC,IRC,I
Conduct managementR,AIC,I
Termination decisionsR,AIC,I
Offboarding processAR,AC,I
Recruiting
SourcingC,IR,A
Pipeline managementC,IR,A
Interview schedulingR,A
Offer decisionsCIR,A
Referral bonusesCIR,A
Culture
Team celebrationsIC,IR,A
OffsitesC,IR,AI
Team surveys.C,IC,IR,A
DE&I initiativesR,ARR
Team 121sRR,AR
Passion Talks/Life StoriesIIR,A
Finance
Accounting - USC,IR,A
Accounting - UKC,IR,A
Financial planningR,ARI
Board reportingR,AR
InsurancesC,IR,A
Legal
Commercial agreementsR,AR
FundraisingR,A
IP & Confidentiality.R,AC,I
New agreementsR,AC,I
Privacy & ComplianceR,AR
UK options schemeRR,AC
US options schemeRR,AC
Systems
Customer supportC,IR,A
Equipment managementCR,A
Accounts managementAR
Mail monitoringC,IR,A

Customer

Every PostHog team member, as well as current, future and past candidates.

Objectives & key results

Q1 2023

  • Objective:
    • Make PostHog the best place anybody has ever worked.
  • Key Results:
    • Hiring: Hire a Full Stack Engineer (Experimentation) and Product Designer
    • Hiring: Start reporting diversity of pipeline on a monthly basis
    • Culture: Run a whole team offsite that at least 80% of the team rate as 4/5
    • Culture: Set up regular team surveys and ensure at least 90% responsiveness
    • Finance: Ensure we stay within 5% of forecast cash burn
    • Finance: 100% of monthly reports are shared with the team before the end of the following month
    • Ops: Complete our SOC 2 audit and get certified.
  • Rationale:
    • Our ops run smoothly already, so it doesn’t make sense to invest more time for marginal gains here.
    • We should focus on making the experience of working at PostHog as pleasant and enjoyable as possible.

Team 121s

On a monthly basis, People & Ops offer every team member an optional, informal check-in about life, work, and as an opportunity to provide any feedback on how the company runs as a whole.

The breakdown of assignments is:

Charles:

  • Marius
  • Karl
  • Michal
  • Cory
  • Paul D'A.
  • Tim
  • Guido
  • Tiina
  • Eric
  • Em
  • Thomas

Grace:

  • James G.
  • Li
  • Alex
  • Eli
  • Cameron
  • Yakko
  • James H.
  • Joe
  • Ellie
  • Lottie
  • Luke
  • Raquel

Coua:

  • Simon
  • Harry
  • Andy
  • Ian
  • Paul H.
  • Neil
  • Daniel
  • Annika
  • Ben
  • Kendal
  • Xavier

Slack channels

#team-people-and-ops - internally public, default for ops & people discussions #private-people-ops - internally confidential, for minority of issues, e.g. salaries, candidate offers

Tools

An operations team is never complete without a robust toolkit to allow us to automate processes and multiply our impact. Here is a summary of some of the tools we've found most effective for getting the job done. You can read more about why we chose them here.

Hiring

Contracts & Offer Letters

  • All templates are stored in the Legal Docs [CONFIDENTIAL] shared Google Drive, in the Team folder.
  • To avoid emailing PDFs back and forth forever, we use the e-signature platform HelloSign.

HR, Recruiting, and Payroll

  • Gusto - platform for managing all permanent US employees, including contracts, healthcare and payroll.
    • We use Middesk to manage all our state registrations and filings on our behalf.
    • For managing our US 401(k) we use Pentegra, which requires a manual monthly reporting process. However, we will be exploring more self-serve options in the future as we now have Operations team members in the US who can act as company fiduciaries.
  • Deel - platform for managing all employees outside the US and UK (using their EOR service), and all contractors globally.
  • UK contracts are currently done manually in Google Drive, with payroll also being run manually.
  • CharlieHR - used to store all team personal details, documents, pay and for booking any type of leave.
  • Ashby - our ATS for managing all recruitment (you can find their full documentation here.

Finance and Banking

  • Accounting:
    • For the US, we use Fondo. We have a shared Slack channel with them.
    • For the UK, we use DRG. Everything is managed by email.
  • Banking:
    • Brex is our main account, which we also use for team credit cards and expense management.
    • We have backup savings accounts with Mercury and SVB.
  • Pry (recently acquired by Brex) is our main financial planning tool.
  • LTSE Equity is where we manage our cap table.
  • Anrok helps us stay on top of any state and local tax obligations triggered by employee presence or sales volume, and connects seamlessly and imports sales data from Stripe. They also provide automated support for registering with local tax authorities to automate the remittance process (though we don't use this part of their service yet).

Everything Else

  • For those pesky externalities, we use Embroker for all of our insurance coverage.
  • A bit unusual for an operations team, we track everything in GitHub from maintaining this handbook to sprint planning. You can find the People & Ops project board here.

What we're building

Check out the company roadmap to see what we're working on next!

Questions?

Was this page useful?

Next article

Pipeline Team

People Mission Responsibilities Team Ingestion owns our ingestion pipeline end-to-end. That means we own the Django server ingestion API, the ingestion (plugin) server, as well as our client libraries, Kafka and ClickHouse setup, where it pertains to event ingestion. Our work generally falls into one of three categories: Scaffolding to support core PostHog features In order to achieve company goals or introduce new features (often owned by other teams), changes to our ingestion pipeline may be…

Read next article

Authors

  • Charles Cook
    Charles Cook
  • Grace McKenzie
    Grace McKenzie
  • Eli Kinsey
    Eli Kinsey

Share

Jump to:

  • People & Ops
  • Mission
  • Responsibilities
  • Customer
  • Objectives & key results
  • Q1 2023
  • Team 121s
  • Slack channels
  • Tools
  • Hiring
  • What we're building
  • Questions?
  • Edit this page
  • Raise an issue
  • Toggle content width
  • Toggle dark mode
  • Product

  • Overview
  • Pricing
  • Product analytics
  • Session recording
  • A/B testing
  • Feature flags
  • Apps
  • Customer stories
  • PostHog vs...
  • Docs

  • Quickstart guide
  • Self-hosting
  • Installing PostHog
  • Building an app
  • API
  • Webhooks
  • How PostHog works
  • Data privacy
  • Using PostHog

  • Product manual
  • Apps manuals
  • Tutorials
  • Community

  • Questions?
  • Product roadmap
  • Contributors
  • Partners
  • Newsletter
  • Merch
  • PostHog FM
  • PostHog on GitHub
  • Handbook

  • Getting started
  • Company
  • Strategy
  • How we work
  • Small teams
  • People & Ops
  • Engineering
  • Product
  • Design
  • Marketing
  • Customer success
  • Company

  • About
  • Team
  • Investors
  • Press
  • Blog
  • FAQ
  • Support
  • Careers
© 2022 PostHog, Inc.
  • Code of conduct
  • Privacy policy
  • Terms