## About PostHog
Product development used to mean manually writing code, running analysis, diagnosing bugs, and rolling out changes using dozens of tools.
PostHog makes products [self-driving](https://posthog.com/self-driving). It's 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](https://posthog.com/handbook/story). We've since shipped [more than a dozen products](https://posthog.com/products), including:
- [PostHog Desktop](https://posthog.com/desktop), the only AI devtool that understands your product, not just your codebase.
- [A built-in data warehouse](https://posthog.com/docs/data-warehouse), so users can query product and customer data together using custom SQL insights.
- [PostHog AI](https://posthog.com/ai), an AI-powered analyst that answers product questions, helps users find useful session recordings, and writes custom SQL queries.
We are:
1. **Product-led**. More than 450,000 organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit.
2. [**Default alive**](https://paulgraham.com/aord.html). Revenue is growing incredibly quickly, and we're very efficient. We raise money to push ambition and grow faster, not to keep the lights on.
3. **Well-funded.** We've raised more than $180m from some of the world's top investors. We're set up for a long, ambitious journey.
We're focused on building an awesome product for end users, hiring exceptional teammates, shipping fast, and [being as weird as possible](https://posthog.com/deskhog).
## Things we care about
- **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](https://posthog.com/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](https://posthog.com/handbook/wide-company) and [make product decisions](https://posthog.com/handbook/which-products). Teams are flexible and easy to change when needed.
- **Shipping fast:** [Why not now?](https://posthog.com/handbook/values#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](https://posthog.com/founders/cracked-manifesto) 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](https://posthog.com/handbook/company/culture#were-on-the-makers-schedule), 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](https://posthog.com/deskhog) with dubious shareholder value. Doing weird stuff is a competitive advantage. And it's fun.
## **Who we're looking for**
We're hiring for a range of roles here. What you end up working on will depend on your exact skillset and preferences, so choose your own adventure.
In general we seek Product Engineers who are:
- **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](https://posthog.com/blog/what-is-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](https://posthog.com/handbook/company/grown-ups), 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.
## **What you'll be doing**
- **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](https://posthog.com/handbook/engineering/product-engineering), owning pricing, and ensuring the ongoing success of your work.
- **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](https://storybook.dev.posthog.dev) **.** From there, it's up to you to decide when to [collaborate with our design team](https://posthog.com/handbook/engineering/product-design) to iterate and polish the experience.
- **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.
- **Doing support.** Every week, one person in each engineering team is designated the [Support hero](https://posthog.com/handbook/engineering/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](https://posthog.com/handbook/engineering/on-call-rotation), too.
- **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**
- 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](https://posthog.com/handbook/engineering/stack) – 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](https://posthog.com/handbook/company/culture#we-write-everything-down), most of it publicly. The ability to communicate your ideas and make persuasive arguments is essential.
## **Nice to have**
- Have worked at a high-growth SaaS company before.
- Extensive knowledge of Django and/or TypeScript-based React.
- Experience building AI-native products, or integrating AI into existing software.
_We are committed to ensuring a fair and accessible interview process. If you need any accommodations or adjustments, please let us know_
_#LI-DNI_
Visa sponsorship is not available for this role.
