Introduction
PostHog is one of the most unusual places to be a product manager. Founded in 2020 by James Hawkins and Tim Glaser through Y Combinator (W20), it has grown from an open-source product analytics tool into an all-in-one platform for product engineers: product and web analytics, session replay, feature flags and experiments, surveys, error tracking, a data warehouse, LLM analytics, logs, and AI products such as PostHog AI, Replay Vision, Inbox and PostHog Desktop. It raised a $70M Series D at a $920M valuation in June 2025 and a $75M Series E at a $1.4B valuation, led by Peak XV, in September 2025.
What makes PostHog different for PM candidates is that it has very few PMs. Engineers own most product decisions, and PMs are usually added to a team only after its product has launched and started earning revenue. PostHog writes all of this down in a public handbook, so candidates can read exactly what the company expects before they apply. This guide explains the role, requirements, interview process, pay and how to prepare, with honest notes for students and early-career candidates.
| Hiring Metric | Value |
|---|---|
| PM openings at any time | Typically 1–3 (estimate) |
| APM / new-grad PM program | None |
| Interview stages | 4, ending in a paid SuperDay |
| SuperDay payment | $1,000 flat |
| Typical time to offer | 2–4 weeks (estimate) |
| Work model | Fully remote, async-first |
Candidates who read PostHog's handbook pages on the PM role and PM hiring before applying consistently do better. The company tests for the exact traits it describes there: user obsession, SQL-level metrics ownership and product sense, with respect for engineers who own the roadmap.
PM Role
A PostHog product manager brings context and clarity to one or more small engineering teams. The PM does not own the roadmap; the team lead does. The PM owns user discovery systems, the team's metrics and pricing, and shares ownership of user understanding and competitive research.
According to PostHog's handbook, PMs own:
- Systems for user discovery: regular user calls for PMs and engineers, a retrievable store of feedback, interviews, metrics reviews and replay watch parties.
- Team metrics: always knowing how the product performs in usage and revenue, and forming hypotheses when metrics move. Products follow a standard per-product growth review format.
- Pricing: checking whether pricing matches value, spotting friction, designing pricing changes with billing and marketing, and tracking the impact.
PMs share user understanding (personas, jobs to be done) and competitive monitoring with engineers. They support launches, decisions on what to build next and UX feedback.
The role changes with the product's stage:
In stages one and two, most teams have no PM; product engineers decide what to build, when to launch and how to charge. PMs typically join at stage three, when opportunities multiply and someone needs to connect feedback with metrics. In mature products, PMs help sustain an ambitious growth rate (the handbook cites a 9% month-over-month revenue target) through segment research, pricing and "conviction sprints". Handbook examples of PM work include pricing for PostHog AI, renaming Max AI to PostHog AI, a Surveys pricing change, and research into data engineers' needs after the Data Warehouse was repositioned.
| Aspect | PostHog PM | Typical Big Tech PM | Typical SaaS PM |
|---|---|---|---|
| Owns roadmap | No (team lead does) | Yes | Yes |
| Writes SQL | Expected, daily | Sometimes | Sometimes |
| Owns pricing | Yes | Rarely | Sometimes |
| Ratio to engineers | Very low | 1:6–10 | 1:5–8 |
| Ships code | Optional, valued | Rare | Rare |
| Work style | Remote, written, async | Meetings, docs | Mixed |
Job Requirements
PostHog's job posts avoid years-of-experience requirements and keep "must-haves" short. Recent titles include Product Manager (ex-founder or ex-product engineer) and Product Manager, Observability (ex-founder or ex-product engineer), which tells you the profile it wants.
Experience:
- Owning a product's metrics over months or years, not just a one-off project
- Examples like defining and validating an activation metric, breaking down retention by segment, iterating on churn fixes, or building a churn or cross-sell analysis
- Background as a founder, product engineer, user researcher or another deeply user-facing role
Technical skills:
- Fluent SQL and comfort investigating data directly in a warehouse
- Data modelling, analytics engineering or dashboard building is a plus
- Coding is optional, but PMs who can navigate a codebase or ship a small PR are valued
Product and soft skills:
- Obsession with talking to users
- Product sense: spotting friction, wrong defaults, incoherent language and one-way-door decisions
- Strong opinions on metrics, pricing, users and positioning, combined with "disagree and commit"
- Excellent written communication for an async, remote company
| Requirement | Essential | Preferred |
|---|---|---|
| Metrics ownership | Lived experience with retention, churn, activation | Built churn or cross-sell models |
| SQL | Fluent | Data modelling, dbt-style work |
| User research | Regular user conversations | Ran a discovery system |
| Coding | Not required | Shipped PRs or side projects |
| Background | PM, founder or product engineer | Developer tools or B2B SaaS |
Candidates who present themselves as roadmap owners or "CEO of the product" struggle here. PostHog wants PMs who lead with context and trust engineers to make the build decisions.
For students: PostHog rarely hires junior people. A realistic path is to build product skills as a product engineer, founder or PM elsewhere, ideally with a developer-tools product, and apply once you can show metrics you owned for a long period.
Interview Process Breakdown
PostHog publishes its hiring process. For PM roles it usually looks like this:
| Stage | Format | Duration | Focus Areas |
|---|---|---|---|
| Application | Online via Ashby | N/A | Relevant experience, written clarity |
| Talent interview | Video | ~30 mins | Motivation, background, what you want |
| Technical interview | Video with hiring manager | 45–60 mins | Metrics depth, SQL comfort, product sense, past ownership |
| Small Team / culture interview | Video with a Blitzscale (exec) member | ~20–30 mins | Culture fit, autonomy, motivation |
| SuperDay | Paid full day of real work | 1 day (can be split) | Real PM task, communication, judgement |
Detailed breakdown:
A conversation about your experience, what you are looking for and how PostHog works. Expect questions about why PostHog and why remote async work suits you.
For PMs this is a deep dive into metrics you owned: how you defined activation, how you diagnosed churn, what SQL you wrote and what you changed. Interviewers probe for depth, so be ready to go three levels down on one example.
A short conversation with an exec to test values: autonomy, directness, written communication and comfort without a traditional hierarchy.
A full day of paid work (a flat $1,000). You get a private Slack channel, a kickoff with the hiring manager and a realistic task, for example analysing a product's usage data, proposing a pricing change or synthesising user feedback into recommendations. You also meet one or two future colleagues for ~30-minute peer chats. The hiring manager and team lead review your output.
Timeline expectations:
- Application to offer: usually 2–4 weeks (estimate based on reports)
- Rejected candidates face a 12-month cooling period before reapplying
Product Manager Compensation & Levels at PostHog
PostHog uses a public compensation calculator: salary = San Francisco benchmark × location factor × level modifier × step modifier, plus "significant equity". A recent PM posting showed a $250,000 SF benchmark, giving $237,500–$260,000 at level modifier 1 with step modifiers of 0.95–1.04.
Levels: Junior (rarely hired), Intermediate, Senior, Staff, Director/Principal. Steps within a level: Learning, Established (default for new hires), Thriving, Expert.
| Level | Base salary, San Francisco (USD) |
|---|---|
| Intermediate PM | ~$195,000 – $215,000 (estimate) |
| Senior PM | $237,500 – $260,000 |
| Staff PM | ~$285,000 – $315,000 (estimate) |
| Director / Principal | ~$330,000 – $380,000 (estimate) |
Location factors follow GitLab's approach (cost of market, not cost of living), with a floor of 0.85 in the US and 0.6 elsewhere. Pay is reviewed two to three times a year, equity refreshes are 18–25% of a new grant each year, and PostHog offers four months' severance if it ends a contract after the first three months. See the salary guide for details.
How to Prepare
Core values to show:
- User obsession: bring stories of user conversations that changed your thinking.
- Metrics ownership: prepare two or three deep examples with real numbers.
- Context, not control: show how you influenced engineers with data rather than authority.
- Bias to action and written clarity: PostHog runs on written, async communication.
Tailor your resume: Lead with outcomes you owned over time ("raised 90-day retention from 31% to 38% over three quarters") and mention SQL, analytics tools and any code you shipped. Keep it short; PostHog values clarity. For feedback, NextSprints' Resume Review service can help.
Practice product cases: Use PostHog's own products. Install it on a side project, explore the free tier, and form opinions about onboarding, pricing and cross-product links. Practise questions on activation, retention diagnostics, pricing changes and AI features. NextSprints' Product Manager Interview Questions include PostHog-specific cases.
Practise SQL and analysis: Be able to write cohort retention, funnel and churn queries from scratch, and explain trade-offs in metric definitions.
Mock interviews: Do mocks with PMs from developer-tools or B2B SaaS companies, and rehearse explaining a metric deep-dive in under five minutes. NextSprints PM Coaching can connect you with experienced PMs.
FAQs
Does PostHog hire associate or new-grad product managers?
No formal APM program exists, and PostHog says it rarely hires at Junior level. Students are better off joining as product engineers elsewhere, founding something, or gaining PM experience with clear metrics ownership, then applying later.
How technical do PostHog PMs need to be?
SQL fluency is essential, because PMs do their own analysis in PostHog's data warehouse. Coding is not required, but PMs who can read code or ship small PRs build stronger relationships with engineers and understand developer users better.
What happens on the PostHog SuperDay?
It is a paid day of real work ($1,000 flat) with a task relevant to the role, a private Slack channel, a kickoff with the hiring manager and short peer interviews. It can be split across sessions if needed. The hiring manager and team lead review the output.
Who owns the roadmap if not the PM?
The team lead, usually an engineer, owns the product and its roadmap. The PM provides user and metric context, owns pricing and discovery systems, and acts as the informed decision-maker in those areas.
Is the process fully remote?
Yes. PostHog is a fully remote, async-first company, and every stage, including the SuperDay, is done remotely.
Related Guides Section
📖 PostHog Product Strategy Guide – How PostHog is moving from analytics to self-driving products.
📖 PostHog Product Manager Salary Guide – The transparent pay calculator explained by level.
📖 PostHog Product Teardown Guide – Analysis of PostHog's all-in-one product platform.
Disclaimer: This guide is created for product management interview preparation purposes only. The analysis is based on PostHog's public handbook, job postings and candidate reports, and is not affiliated with or endorsed by PostHog.
