Team structure

Last updated:

|Edit this page

Small teams

We've organized the team into small teams that are multi-disciplinary and as self-sufficient as possible. You can read about why we've done it this way, or browse the small teams.

Our small teams are:

Reporting lines

We maintain our full org chart in Deel, which you can access here.

Team leads do not necessarily = managers - read more about how we think about management here.

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 at the small teams level. 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 relevant Small Team page.
    • Update the Org Chart in Deel.
  • Let everyone else in the company know in the next all hands 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.

Questions?

Was this page useful?

Next article

Overview

Our primary focus is on making our paying customers successful, not forcing sales through. We follow a 100% inbound sales model - our approach to product-led growth means that we do not do cold outreach. Our plan is to put this off for as long as possible - ideally to $50m+ ARR. While this means working with a smaller number of users than typical B2B SaaS companies, we know that the people we talk to are mostly already pre-qualified and genuinely interested in potentially using PostHog. The…

Read next article