Product Manager, Observability (ex-founder or ex-product engineer)

posthog· 10 open roles

Remote RemoteFullTime2 weeks ago

Salary

Undisclosed

Experience

Mid

Job Type

FullTime

Posted

2 weeks ago

Apply Now

Boost your chances at posthog

Tailor your resume to this exact job and generate a matching cover letter in about 60 seconds with JobEase — our AI application assistant.

ATS-optimized resume
Personalized cover letter
Match score & keyword gaps

Tailor my application

Free to start · no card required

Get more other jobs in your inbox

Verified daily — no ghost listings.

About This RoleAI processing…

About PostHog PostHog is your product’s context layer. It ingests and stores your analytics, errors, replays, and business data so you and your agents can query and act on it. We launched out of Y Combinator's W20 cohort . We've since shipped more than a dozen products, including: A suite of analytics and observability tools, including product analytics , replay vision , AI observability , and error tracking PostHog MCP for users and their agents to query and act on their product and business data Data warehouse so users can query product and customer data together using custom SQL insights. W

Key Responsibilities

1
We have a growth review with every product every month. As the PM, you ensure we have the right metrics, dig into things that have changed, understand what users are doing, why they're churning, etc. You use the findings to figure out if we need to dig deeper into a trend or reprioritize what we're building.
2
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?
3
Which behaviours lead to long-term retention for your product?

Requirements

You’ve been a technical founder or product engineer in a startup: We are explicitly looking for someone who has written code before and now wants to focus on the product and commercial side
You have strong product sense - meaning you can identify a product’s biggest selling points and weaknesses (both user experience and commercial) and turn them into actionable insights that inform your team’s product decisions
You’re familiar with business and product metrics (e.g. activation, retention, churn) and defining and tracking key product metrics. You don’t hesitate to write SQL (or another query language) to answer data questions
You have hands-on experience using observability products and understand how engineers use them to investigate, debug, and diagnose issues in production.
You have additional data modelling experience on top of writing queries.
If you have a disability, please let us know if there's any way we can make the interview process better for you - we're happy to accommodate! #LI-DNI

Perks & Benefits

Transparency: Everyone can read about our roadmap, how we pay (or even let go of) people, our strategy, and how we work, in our public company handbook . Internally, we share revenue, notes and slides from board meetings, and fundraising plans, so everyone has the context they need to make good decisions.

Autonomy: We don’t tell anyone what to do. Everyone chooses what to work on next based on what's going to have the biggest impact on our customers, and what they find interesting and motivating to work on. Engineers lead product teams and make product decisions . Teams are flexible and easy to change when needed.

Shipping fast: Why not now? We want to build a lot of products; we can't do that shipping at a normal pace. We've built the company around small teams – autonomous, highly-efficient groups of cracked engineers who can outship much larger companies because they own their products end-to-end.

Time for building: Nothing gets shipped in a meeting. We're a natively remote company. We default to async communication – PRs > Issues > Slack. Tuesdays and Thursdays are meeting-free days , and we prioritize heads down building time over perfect coordination. This will be the most productive job you've ever had.

Ambition: We want to solve big problems. We strongly believe that aiming for the best possible upside, and sometimes missing, is better than never trying. We're optimistic about what's possible and our ability to get there.

Being weird: Weird means redesigning an already world-class website for the 5th time. It means shipping literally every product that relates to customer data. It means building an objectively unnecessary developer toy with dubious shareholder value. Doing weird stuff is a competitive advantage. And it's fun.