Product Manager (ex-founder or ex-product engineer)
We're shipping every product that companies need to run their business from their first day, to the day they IPO, and beyond. The operating system for folks who build software.
We started with open-source product analytics, launched out of Y Combinator's W20 cohort. We've since shipped more than a dozen products, including:
Next on the roadmap are CRM, workflow, revenue analytics, and support products. When we say every product that companies need to run their business, we really mean it!
We are:
We're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and being as weird as possible.
Product management plays a slightly different role at PostHog than at most other companies and is incredibly important. Instead of micro-managing engineers, PMs are responsible for research, data, and setting high-level context across the organization. They work across multiple products to determine how products are being used, what the competitive landscape is like, and how users are feeling about PostHog. Using the usual PM jargon we could say PMs at PostHog are very discovery-focused and don’t engage in delivery almost at all.
Among other things, they:
If you want to know more about our philosophy of building products, read our article “Product Management is broken. Engineers can fix it.”
You will be joining PostHog as a Product Manager, working with one of our small engineering teams (with the potential to cover more than one team/product after your onboarding period), with a heavy emphasis on analyzing data, talking to users and owning the commercial aspects of your product(s):
Across our 10+ products (and counting!), we have thousands of paying customers and many more on the free tier. That’s a lot of users and a lot of data. Finding actionable patterns in this data is one of the key ingredients to reaching $100M ARR. Example questions you might be answering:
How does revenue/usage churn for your product compare across different segments?
❌ Backlog grooming (it always sounded gross anyway)
❌ Deciding or approving what we build (though you’ll help surface the context needed to make good decisions)
❌ Shielding developers from users (instead, you should aim to invite an engineer for every user interview you do)
❌ Project management / writing gazillions of tickets, RFCs, or PRDs
❌ Coding and shipping new features yourself (small PRs and hackathon contributions are of course encouraged!)
Nice-to-haves (We don’t expect you to tick all of these boxes, but 2-3 are a big plus):
If this sounds like you, we should talk.
We are committed to ensuring a fair and accessible interview process. If you need any accommodations or adjustments, please let us know.
Now that we've told you what you'll be building with us, let's talk about what we'll be building for you.
Health Insurance
Dental Insurance
Vision Insurance
Mental Health Benefits
401(k) Match
401(k) / Retirement Plan
Pay Transparency
Stock Options
Unlimited PTO
Minimum PTO Requirement
Unlimited Sick Days
Home Office Stipend
Learning & Development Budget
Book Stipend
Company Offsites / Retreats
Coworking Allowance
Company Equipment
Work From Anywhere
Paid Trial
Flexible Hours
Parental Leave
Entrepreneurship Encouraged