Product Engineer

posthog· 16 open roles

Remote RemoteFullTime5 months ago

Salaryest.

$120,000 - $200,000

Experience

Mid

Job Type

FullTime

Posted

5 months ago

Apply Now

Get more other jobs in your inbox

Verified daily — no ghost listings.

About This RoleAI processing…

About PostHog Product development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools. PostHog is the only platform that acts like a co-pilot for you (and your AI agents) to do it all – autonomously. 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: PostHog Code , the only AI devtool that understands your product, not just your codebase. A built-in data warehouse , so users can query product and customer data together using custom

Key Responsibilities

1
Owning products and features from beginning to end. This means originating ideas based on your intuition, talking to users, and understanding our strategy and goals. It means testing MVPs in production with real users. It means iterating on their feedback , owning pricing, and ensuring the ongoing success of your work.
2
Collaborating with design (when necessary). Product engineers at PostHog are full stack, so we expect you to ship and own the basic UX of your work using our design system . From there, it's up to you to decide when to collaborate with our design team to iterate and polish the experience.
3
Talking to users. Good product engineers read feedback from users and iterate quickly. Great product engineers have users they're friendly with, talk with them frequently, bounce ideas off them, and iterate with them when they ship new things.
4
Doing support. Every week, one person in each engineering team is designated the Support hero . Their job is to investigate and resolve issues reported by customers for their product. Giving users support from real engineers, and shipping fixes and improvements in real-time, is one of the best ways to spark joy in users. This role will also include some on-call time , too.
5
Writing docs. We have a content team that will collaborate with you on reviewing, polishing, and improving your documentation, but the best person to document a new feature is the person who built it.

Requirements

Enthusiastic drivers. We need proactive people that can fully own projects and get them done, and know to get help when needed. This is what being a product engineer is all about. "Are we there yet?" is the wrong question.
Optimistic problem solvers. Things get hard here sometimes – whether it's scaling, shipping complex products, handling a stream of support requests, or trying to ship something that touches multiple teams. We need people who won't get disheartened, and will collaborate, iterate, and ship their way out of anything.
Grown ups. We’re an international bunch of weirdos, but one thing unites us: everyone is kind, considerate, and professional towards each other. This isn't about age or experience , it's about being low-ego, flexible, and respectful.
Genuine builders. PostHog is full of people who just love building stuff, people who would still be building software even if there wasn't a paycheck at the end. If this sounds like you, we should talk.
You've built things agents actually use. More and more of what we ship is used by agents, not people, and building for them is genuinely different. We want someone who's done it and has the scars: an API an agent can drive, an MCP server, evals, docs written for a machine. Side projects count.
Full-stack experience with relevant technologies – e.g. Python or similar, React or similar, something to do with big data is a bonus.
Experience taking a project from 0 to 1. You might have led a project, been a founder previously, or built an impressive side project.
Strong writing skills. We document everything , most of it publicly. The ability to communicate your ideas and make persuasive arguments is essential.

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.