Team structure

Last updated:

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

Core Analytics


Core Experience


Platform


Growth


Marketing

People & culture

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.
  • 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.