Team structure

Reporting structure

• James Hawkins, CEO & Co-founder
  • Tim Glaser, CTO & Co-founder
    • Marius Andra, Full Stack Engineer
      • Emanuele Capparelli, Growth Engineer
      • Michael Matloka, Full Stack Engineer
      • Paul D'Ambra, Full Stack Engineer
    • Ben White, Full Stack Engineer
      • Alex Kim, Full Stack Engineer
    • James Greenhill, Data/Infra engineer
      • Tiina Turban, Full Stack Engineer
      • Yakko Majuri, Full Stack Engineer
      • Zack Elan, Software Engineer
    • Ellie Huxtable, Full Stack Engineer
      • Guido Iaquinti, Site Reliability Engineer
      • Daniel Jaramillo, Site Reliability Engineer
    • Eric Duong, Full Stack Engineer
      • Li Yi Yu, Full Stack Engineer
      • Neil Kakkar, Full Stack Engineer
    • Luke Harries, Head of Product
      • Annika Schmid, Product Manager
      • Joe Martin, Product Marketer
    • Karl-Aksel Puulmann, Full Stack Engineer
    • Harry Waye, Full Stack Engineer
  • Charles Cook, VP of Operations & Marketing
    • Andy Vandervell, Content Marketer
    • Grace McKenzie, Operations Manager
    • Coua Phang, Tech Talent Partner
    • Ian Vanagas, Technical Content Marketer
  • Cory Watilo, Lead Designer
    • Lottie Coxon, Graphic Designer
    • Eli Kinsey, Front End Engineer
    • Paul Hultgren, Developer Advocate
  • Simon Fisher, Customer Success Lead
    • Cameron DeLeone, Customer Success Manager

Small teams

We've organised the team into small teams that are multi-disciplinary. You can read about why we've done it this way.

Engineering

Engineering is spread out into three small teams. Team Platform is a scope-specific team which focuses on deployments and ingestion (see Team Platform for more details). App teams East and West work on the PostHog product in general and they're split based on timezones for optimal collaboration. We mostly hire full-stack engineers and each team has expertise across the stack of the entire product. To learn what each team is working on you can take a look at feature ownership.

Product Analytics

• Marius Andra (Team lead, Full Stack Engineer)
• Michael Matloka (Full Stack Engineer)
• Paul D'Ambra (Full Stack Engineer)
• Product: Supported by Annika Schmid
• Product design: Supported by Cory Watilo
• Hiring for a full stack engineer
• Hiring for a full stack engineer

Experimentation

• Eric Duong (Team lead, Full Stack Engineer)
• Neil Kakkar (Full Stack Engineer)
• Li Yi Yu (Full Stack Engineer)
• Hiring for a full stack engineer
• Product: Supported by Luke Harries
• Product design: Supported by Cory Watilo

Session Recording

• Ben White (Team lead, Full Stack Engineer)
• Alex Kim (Full Stack Engineer)
• Emanuele Capparelli (Growth Engineer)
• Hiring for a full stack engineer
• Product: Supported by Annika Schmid
• Product design: Supported by Cory Watilo

Infrastructure

• Ellie Huxtable (Site Reliability Engineer)
• Guido Iaquinti (Site Reliability Engineer)
• Daniel Jaramillo (Site Reliability Engineer)
• Hiring for an Site Reliability Engineer
• Product: Supported by Luke Harries

Pipeline

• Yakko Majuri (Full Stack Engineer)
• James Greenhill (Data/Infra Engineer)
• Karl-Aksel Puulmann (Full Stack Engineer)
• Harry Waye (Full Stack Engineer)
• Tiina Turban (Full Stack Engineer)
• Zack Elan (Software Engineer)
• Incoming Senior Data Engineer
• Hiring for a full stack engineer
• Product: Supported by Luke Harries
• Product design: Supported by Cory Watilo

Marketing

• Charles Cook (Team lead, VP Ops & Marketing)
• Joe Martin (Product Marketer)
• Andy Vandervell, Content Marketer (Content Marketer)
• Ian Vanagas, Technical Content Marketer

Website and Docs

• Cory Watilo (Lead Designer)
• Eli Kinsey (Frontend Engineer)
• Lottie Coxon (Graphic Designer)

People & Operations

• Charles Cook (Team lead, VP Ops & Marketing)
• Grace McKenzie (Operations Manager)
• Coua Phang (Tech Talent Partner)

Customer Success

• Simon Fisher (Team lead, Customer Success)
• Cameron DeLeone (Customer Success Manager)

Exec Team

• James Hawkins (Team lead, CEO)
• Tim Glaser (CTO)
• Luke Harries (Head of Product)
• Charles Cook (VP Ops & Marketing)
• Kendal Hall (Executive Assistant)

Organization changes

We’re still an early stage company, and so is our product. We strongly value moving and shipping fast (see core values) and we constantly iterate not only our product but our organization too. As this happens, it may be quite possible that organizational changes occur. This mostly happens on the small teams plane. To make the changes smoother for everyone, here’s the checklist we use:

• Discuss with relevant team leads (and/or managers if applicable).
• Discuss with relevant team member(s).
• Open a PR on posthog.com documenting the change on the handbook.
  • Update the Team structure page.
• Let everyone else in the company know in the next PostHog News session.
• Add/remove from relevant Sentry teams.
• Add/remove from relevant GitHub teams.
• Add/remove from Slack @ groups / team mentions (e.g. @core-experience).

Team Lead checklist

• Onboarding 1:1 with new team member.
• Add to stand-ups, planning sessions, and any other team rituals.
• Update Slack channel description, and invite to Slack channel if needed.