Team structure

Last updated:

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.

Our small teams are:

Reporting lines

We maintain our full org chart in Roots, 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.
  • 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.

Questions?

Was this page useful?

Next article

Customer Success Team

People Mission Responsibilities Own initial inbound contact requests from the website Deliver compelling product demonstrations Assist users in getting up and running with the product, introducing the right PostHog people at the right time Make it easy to become a paying customer Ensure long term success with PostHog Q1 2023 Goals Customer Primarily brand new and existing users of our self-serve product Output metrics Revenue through conversion of high quality free sign-ups to paid Existing…

Read next article