Working at PostHog: Culture, Pace and Who Thrives

How Work Gets Done at PostHog

Most companies say they value autonomy. PostHog removes the guardrails that make autonomy feel safe (no deadlines, no sprint ceremonies, no product managers assigning tickets) and watches what happens when engineers decide what to build and when to ship it.

The company runs on a written-first, async-by-default rhythm across 30-plus countries. Tuesdays and Thursdays are protected maker-schedule days: no meetings allowed, just long blocks for coding, writing, or thinking. The handbook lives in public. Compensation bands are published. The product roadmap is a GitHub issue anyone can read. Decisions move through PRs and RFCs, not Slack huddles or steering committees. "Submit PRs, not issues" is the operating mantra — if you see a problem, you're expected to fix it, not file a ticket and wait.

PostHog organizes around small teams of two to six people, each functioning like a mini-startup with end-to-end ownership of a product slice. Roughly 16 to 17 products are in development or maintenance at any time, spanning analytics, session replay, feature flags, A/B testing, a data warehouse, and newer coding tools that auto-generate fixes from detected product issues. Teams choose their own stack within the shared foundation (Python, Django, TypeScript, React, ClickHouse, PostgreSQL, Kafka, Kubernetes) and ship without asking permission. The "Why not now?" principle means anyone can push a change today if they believe it serves the customer; consensus is explicitly not required.

We hire people that are really great at their jobs, and get out of their way. There are no deadlines, very minimal coordination and you won't have us breathing down your neck.

—James Hawkins, co-founder

That trust comes with a counterpart: extraordinarily high ownership. You decide what to work on. You write the spec. You build it. You watch the metrics. You iterate. The feedback loop is direct and public — your PRs, your commits, your reasoning are visible to the whole company and, because the codebase is open source, to the world. For some engineers that visibility is motivating; for others, especially those earlier in their careers, it feels like performing on a stage.

Communication defaults to writing. Meetings exist but are rare and intentional — mostly the quarterly offsites that bring the full team together for the spontaneous conversation Slack can't replicate. Day to day, context lives in GitHub issues, pull requests, and the public handbook. The "Make it public" norm pushes decisions out of private channels and into searchable artifacts, which reduces politics but also means there's nowhere to hide a half-baked idea.

The pace is deliberate. Founders James Hawkins and Tim Glaser have described the strategy as a series of simplistic bets: build a second product, then a tenth, then aim for hundreds, each shipped fast to learn faster. They killed a paid self-hosted tier that was generating revenue because the cloud product grew faster; they admit they should have done it a year sooner. That bias for action, combined with lean teams and no middle management, creates velocity but also a sustained workload that can push people toward exhaustion. The freedom to structure your day around exercise or family is real. So is the isolation of a fully remote, low-meeting culture where your closest collaborator might be eight time zones away.

Values and Operating Principles

PostHog's operating system is its public handbook — a living document that began as a maturity signal and became the company's central nervous system. James Hawkins and Tim Glaser, the founders, started writing it in 2020 after realizing that "big, boring companies" all had extensive footer links; they needed content to fill theirs. The answer was to "write up how we want to work." Once published, the handbook transformed the organization: "Every team member, and even strangers on the internet, could suggest changes. If you're doing something in public, you're going to think it through better. Ultimately, it made us treat the company as our product."

That philosophy — the company as product — anchors every principle that follows.

Written-first, async by default. Collaboration happens in GitHub issues and pull requests, not meetings. The handbook states it plainly: "Async, written-first (everything in GitHub issues/PRs), high autonomy, ship-focused. Strong fit for engineers who prefer writing over meetings." This isn't a preference; it's a filter. Candidates are explicitly told to "brush up on async/written communication: that is the dominant collaboration mode." The marketing team, led by engineers and journalists rather than career marketers, applies the same standard: "We concluded that we think our ability to write really well is important. Like we're not going to churn out thousands of terrible articles on the internet or whatever. We're just going to write things that we're proud of."

Radical transparency as operational discipline. Inspired by GitLab's model, PostHog publishes compensation bands, strategy, and decision rationale. All salary bands are public in the handbook: "same comp regardless of location, with cost-of-living adjustment." This transparency extends to product direction: the vision "to make your product self-driving" and the multi-product roadmap (warehouse, ETL, surveys, feature flags, experimentation, CDP, notebooks, web analytics) are documented openly.

High autonomy, low process. Fully distributed since founding with no offices, engineers span 30+ countries and convene only for quarterly offsites. The hiring rubric selects for "scrappiness, low ego, ambition, able to write code, optimist", traits that survive without managerial oversight. Interviewers are instructed to "go deep" on these themes rather than cover breadth shallowly: "It's more important to validate a few things well... than it is for you to do a shallow interview across everything." The take-home assignment (4–6 hours building a real feature) is the primary signal; the 90-minute review and founder chat confirm alignment.

Velocity over perfection in engineering; quality over volume in marketing. "The top thing we prioritize in marketing is writing. In engineering, it is velocity." This dual standard reflects the product-led growth engine: inbound demand from developers recommending PostHog to developers. "We're inbound-led, and most customers buy from us without ever talking to sales." The unit economics prove it — CAC payback has hovered around two to three months for the company's life, recently compressing to five days.

Pull-based growth, not push. "We're not against taking the top of the market but we're against doing it in a rush. We want to do it on a pull basis rather than a push basis." This shows in the 2023 decision to drop paid self-hosted support and double down on open source and cloud, sacrificing immediate enterprise revenue for mass adoption among high-potential startups. "Simply, this will better help us increase the number of successful products in the world." The same logic drives pricing: an 80% cut on the two most popular products in July 2024, jobsbyculture.com found.

Each product team operates like a startup. Growth reviews run through "each product's metrics (revenue/usage/support/performance) and feedback / reasons for any churn that has happened, so we can truly treat each small team like a startup." This mirrors the multi-product playbook of Atlassian and AWS, companies PostHog explicitly studies, while maintaining a developer-first, bottom-up motion closer to Sentry or GitHub.

Frugality as strategic leverage. "We've just always been really well capitalized as a result because we just will default to not spending much money at all whilst also scaling quite quickly." The company reached cashflow positive in December 2024 with ~80 people, then ~140 by October 2025, and ~200 by early 2026, after raising ~$194M across Series D and Series E. Revenue quadrupled in 2023 while net headcount grew by three.

Hiring for signal, not pedigree. "Candidates who've worked at places with strong product market fit will have had an easier time achieving results. Some of our best people have come from a string of very average startups." Interviewers are warned against "getting seduced by companies rather than people" and told to "imagine any perceived issue being magnified 10x when the candidate starts." A mild concern in the interview becomes a structural problem at scale.

Marketing by makers, not marketers. "The marketing team has very little marketing experience... it's a group of like engineers, journalists... illustrators, designers, so it's a quite creative group of people." The goal is standing out: "if we hire a bunch of marketing people, you've done tons of marketing before. I think it's going to feel the same as other people's marketing teams work." A commissioned puppet joined the mix in January 2025.

These principles compound. Written-first communication enables async autonomy. Transparency builds trust that replaces management overhead. Velocity and frugality fund the multi-product bet. Pull-based growth keeps the product honest. The handbook isn't culture documentation — it's the mechanism that keeps the system coherent as PostHog scales toward its stated path to a $100B+ company.

What the Hiring Bar Selects For

PostHog's hiring funnel is built to filter for the same traits its culture rewards: written clarity, autonomous execution, and a bias toward shipping. The company runs 100 percent inbound by default, effectively a word-of-mouth strategy that mirrors its marketing model, and supplements only with targeted sourcing when the pipeline needs more diverse candidates. All recruiting stays in-house; no external agencies touch any role. The handbook notes this approach "has resulted in the highest number of qualified and motivated candidates reaching final stages with us compared to other methods, such as more generic sourcing."

The interview sequence is deliberate: recruiter screen, a take-home build (usually four to six hours), a 90-minute take-home review, 1:1 conversations with potential teammates, and a final chat with a founder or leadership. The cycle runs two to four weeks. At every stage the rubric is binary: "if it is not a definite yes, then it's a no", and interviewers are told to ask whether the candidate raises the bar. Feedback is due by end of day after each interview; waiting longer "can kill the momentum and leave the candidate with a bad experience."

The take-home is intentionally scoped to exceed what one person can finish in a day. That design tests prioritization, not just coding speed. Candidates are told to spend at least 80 percent of their time on the task and less than 20 percent meeting people, because the decision rests on the output. The follow-up review digs into the written artifact, examining how the candidate structures a PR, explains tradeoffs, and responds to critique, because decisions at PostHog get made and reviewed in writing, not in meetings.

Behavioral signal centers on three dimensions the handbook names explicitly: written communication, autonomy, and open-source instincts. Interviewers probe how you operate async and make decisions without a manager in the room. They want examples of work you drove to completion on your own and any public or open-source contributions. The techinterview guide for PostHog emphasizes the same trio, asking candidates to bring such examples and noting that much of the signal comes from written artifacts, so write clearly in the take-home review.

Technical fluency expectations are specific. The backend runs on Python and Django; the frontend is TypeScript and React. The take-home spans both a Django model or view on one side and a React component on the other, so candidates need idiomatic code on each rather than leaning on one stack. ClickHouse knowledge is a differentiator: columnar storage rationale, materialized-view tradeoffs, event-stream modeling that keeps analytical queries cheap at scale. The interview guide lists these as prep priorities one through three.

Geographic and visa constraints shape the pool before a resume arrives. Hiring is limited to candidates physically based in GMT+2 through GMT-8 (with a daylight-savings exception for countries that shift from GMT+2 to GMT+3). US visa sponsorship, including H-1B transfers, is off the table; the company can only sponsor in the UK. US hires go through E-Verify. A handful of European and South American countries are excluded from employment due to employer-cost thresholds, though contractor arrangements have worked in Brazil and Uruguay. These boundaries are published in the handbook, not discovered late in the process.

Compensation bands are public and location-agnostic (with a cost-of-living adjustment).

Transparency acts as a self-selection filter — candidates who need opacity to negotiate opt out early.

The SuperDay, a paid full-day work simulation ($1,000 flat, $500 if the role fills before the day runs), is the final gate. It can be split across sessions or timezone-adjusted; a candidate never loses out for scheduling constraints. The decision target is 48 hours post-SuperDay. Rejected candidates receive a short personalized email with specific improvement points and an open door to reapply in 12–18 months. When a hire doesn't work out in probation, the talent partner runs a post-mortem not to assign blame but to extract one or two high-leverage changes to the process, and publishes findings in #team-talent and #tell-posthog-anything.

Current openings on the Zero G Talent board reflect the same profile: Product Engineer, AI Research Engineer, ClickHouse Operations Engineer, Security Engineer, Site Reliability Engineer (US - Pacific time), Product Manager (ex-founder or ex-product engineer), Developer Marketer - Sales, Animator & Motion Graphics Designer, and Finance Manager, Revenue Accounting. The company plans to grow from roughly 96 people to 185 by end of 2025, with hiring forecasts updated monthly: three months out for exact titles, six months for role counts, 12–24 months for headcount totals.

Internships don't exist; the handbook says the team is "a bit too scrappy to do them well right now." Students are pointed to campus events or community incubator grants instead. The bar, in short, selects for builders who write well, ship without supervision, and treat open-source contribution as a default mode of work — not a side project.

Who Thrives, Who Struggles: The Evidence

PostHog's overall Glassdoor rating sits at 4.3 out of 5.0 as of early 2026 — a strong score that carries an asterisk: only six reviews underpin it. With that sample size, a handful of new entries could swing the rating materially. The 75 percent recommendation rate aligns with the high marks, but the same caveat applies. What the reviews do reveal, in aggregate, is a pattern consistent with the company's public handbook and the operational norms documented elsewhere in this piece.

The standout metric is compensation and benefits at 4.8 out of 5. Reviewers consistently cite the quarterly review cycle, public salary bands benchmarked to San Francisco rates, and meaningful equity at a $1.4B Series E valuation as differentiators. One theme recurs: pay feels fair and transparent because the formula is visible. The 4.5 work-life balance score maps directly to the no-meeting Tuesdays and Thursdays, the output-only culture, and the absence of hour tracking. Multiple reviewers describe structuring days around exercise, family, and personal interests without guilt, a practical benefit of the async-first design.

Transparency draws praise not as an abstract value but as a daily friction reducer. Reviewers note that public decision logs, open compensation calculators, and an entirely open-source codebase (70,000+ stars on GitHub as of early 2026) eliminate the information asymmetry that fuels politics in larger organizations. "You spend your energy on the work rather than navigating internal dynamics" captures the sentiment across several accounts. The flat structure and small teams give engineers end-to-end ownership (design, development, testing, deployment, user support) without a product management layer dictating priorities. The "submit PRs, not issues" mantra appears in multiple reviews as cultural shorthand for the autonomy expected and rewarded.

The criticism clusters around the predictable trade-offs of that same model. Limited career progression paths surface repeatedly: at roughly 200 people across 30-plus countries, the flat hierarchy means fewer management rungs and fewer formal promotion cycles. Reviewers who value structured mentorship, pair programming, or daily synchronous collaboration describe the environment as isolating. The trade-off is isolation — if you thrive on daily social interaction, PostHog can feel lonely. The company mitigates this with multiple offsites per year, but the day-to-day rhythm remains async and solitary by design.

Top-down decision-making occasionally overrides team input despite the transparency ethos, a tension several reviewers flag. The founders retain ultimate authority on strategic bets, and the public handbook doesn't change that dynamic. DEI investment is cited as an area where the company still needs to progress, a gap acknowledged in the company's own public communications. For engineers earlier in their careers, the visibility of every commit and PR on a public repository can feel like a stage performance rather than learning in a safe container.

The data is thin. Six Glassdoor reviews and a handful of public blog posts from team members constitute the attributable record. No named current or former employees with dated quotes appear in the available sources. What emerges from the aggregate is internally consistent: the people who praise PostHog value autonomy, transparency, and output-based evaluation; the people who struggle cite isolation, limited structure, and the pressure of public work. The culture selects for the former.

That selection is visible in the daily rhythm. Engineers who see a problem, open a branch, and ship a fix without waiting for a ticket or a green light from a product manager thrive here. Small teams own their product area end-to-end, covering design, development, testing, deployment, and user support, as previously noted. Engineers talk directly to users, read support tickets, and decide what to build based on usage data from their own platform. If you need detailed specs and close oversight, the environment will feel uncomfortable. If you're self-directed and opinionated about product, it's one of the best engineering environments in the industry.

Open-source contributors fit naturally. The entire codebase is public on GitHub, which means every engineer's work is visible not just to colleagues but to thousands of developers worldwide. For some, that exposure is motivating; for others, particularly those earlier in their careers, the experience feels like a stage performance. Strong async communicators also gain an edge. Clear, concise writing is essential because verbal charisma matters far less than the ability to articulate thinking in PRs, handbook updates, and GitHub discussions. The culture is allergic to bureaucracy: no timesheets, no mandatory meetings on focus days, no performance theater. People who want to be judged purely on what they build get exactly that.

Generalists outpace specialists. At roughly 200 employees across 30+ countries, roles are genuinely cross-functional. An engineer might write backend Python/Django code in the morning, hop on a user call in the afternoon, and update documentation before end of day. Specialization is a luxury PostHog can't always afford. The same tech stack demands breadth, and the open-source model means contributions span the full product suite previously listed.

The flip side is equally distinct. PostHog is not ideal for people who need daily social interaction with colleagues. The culture is heads-down and solo between offsites; reviewers note lower priority on relationship-building. Tuesdays and Thursdays are designated no-meeting days, the "maker's schedule", and the output-based culture means no one tracks hours. But between offsites, isolation is real. If you thrive on daily collaboration, pair programming, or spontaneous hallway conversations, the environment can feel isolating. The company handles this through its quarterly offsites for in-person collaboration and the spontaneous conversation that doesn't happen over Slack, yet the daily rhythm remains solitary.

Career progression through titles is another friction point. The flat structure means fewer management layers but also fewer rungs to climb. At ~200 people, there simply aren't many levels between an individual contributor and the founding duo. Reviewers cite limited career progression paths as a common criticism. If career progression through defined ladders matters, companies like HubSpot or Databricks offer more structured frameworks. DEI efforts are also cited as an area needing investment, which compounds the challenge for employees who don't see themselves reflected in the existing team.

Such top-down overrides of team input persist despite the transparency ethos — a tension the research previously flagged without resolution. Growing pains typical of a company founded in 2020 persist. The compensation rigor (public bands, SF-benchmarked pay with location adjustments, quarterly reviews, meaningful equity at a $1.4B Series E valuation) and 4.5/5 work-life balance rating attract talent, but they don't erase the structural realities.

The filter isn't subtle. It's built into the daily rhythm.

Working in AI? Zero G Talent tracks the openings: see every open PostHog role, browse AI jobs, the companies hiring, and the people building the field.