PostHog is the open-source product-analytics platform — combines analytics, feature flags, A/B tests, session replay, and a data warehouse in one tool. Y Combinator alum. Series D in 2025. The interview emphasizes ClickHouse-backed analytics at scale, async written-first culture, and the unique tradeoffs of an OSS-first commercial product.
Process
Recruiter screen → take-home (build a small feature; usually 4–6 hours) → 90-minute take-home review → 1:1 with potential team mates → final founder/leadership chat. Cycle: 2–4 weeks.
What they actually ask
- Design an event-ingestion pipeline (Kafka → ClickHouse) at billions of events/day. This is a core system-design round — interviewers probe how you batch writes into ClickHouse (async inserts or a buffer table rather than row-by-row), partition the events table by time, and handle backpressure, retries, and duplicate events with an idempotency key. Be ready to sketch the events schema and explain why you denormalize for read-heavy analytical queries.
- Design a session-replay storage and playback system. Focus on capturing rrweb-style DOM snapshots plus incremental mutations, chunking and compressing them, and storing the payloads cheaply in blob storage (S3) with a small metadata index for lookup. Expect follow-ups on streaming playback, retention windows, and the storage-cost tradeoffs of keeping full recordings.
- Design a feature-flag service with low-latency decisioning at the edge. The key idea is local evaluation — ship flag definitions down to the SDK or edge so a decision is computed in-process without a network round trip. Talk through consistent hashing for percentage rollouts, how config changes propagate, and how you bound staleness when a flag is flipped.
- Coding: practical, real-world (the take-home is the main signal). Expect to build a small feature end to end — a Django endpoint plus a React component — with tests and a clear PR description rather than algorithm puzzles. They weight readable, shippable code and how well you explain your choices over raw problem-solving speed.
- Behavioral: written communication, autonomy, OSS instincts. They probe how you operate async and make decisions without a manager in the room, so bring examples of work you drove to completion on your own and any public or open-source contributions. Much of the signal comes from your written artifacts, so write clearly in the take-home review.
Levels and comp (2026)
- Engineer: $170K–$230K total (transparent published bands)
- Senior Engineer: $230K–$310K total
- Staff Engineer: $310K–$420K total
- Principal Engineer: $420K–$550K total
(All bands are public on the PostHog handbook — same comp regardless of location, with cost-of-living adjustment.)
Prep priorities
- Be fluent in Python (Django backend) and TypeScript (React frontend). The take-home spans both — a Django model or view on the backend and a React component on the frontend — so show idiomatic code on each side rather than leaning on one.
- Understand ClickHouse query patterns and event-stream design. Know why columnar storage makes large aggregations fast, when materialized views help, and how to model events so analytical queries stay cheap at scale.
- Brush up on async/written communication — that is the dominant collaboration mode. Practice writing tight issue and PR descriptions and short design docs, because decisions here get made and reviewed in writing rather than in meetings.
Frequently Asked Questions
Is PostHog remote-friendly?
Fully distributed since founding. No offices. Engineers across 30+ countries. Quarterly in-person offsites.
How does PostHog compare to Mixpanel or Amplitude?
Mixpanel and Amplitude are mature SaaS. PostHog is OSS-first with a self-host option and a much broader product surface (replay, flags, warehouse). Comp is transparent and competitive — same band for everyone in a level.
What is the engineering culture?
Async, written-first (everything in GitHub issues/PRs), high autonomy, ship-focused. Strong fit for engineers who prefer writing over meetings.
Similar company guides
Prepping for PostHog? Put it to work:
