Originally posted at ashby · Apply on the company's site for the best experience.
Originally posted at ashby · Apply on the company's site for the best experience.
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 (existing text is fine) We are: Product-led . More than 500K organizations have installed PostHog, mostly driven by word-of-mouth. We have intensely strong product-market fit. Default alive . 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. 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 . 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 . 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. 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. Other companies would call this being a Product Marketer, but we're looking for someone with devtool experience, so: Developer Marketer. As a Developer Marketer for Sales, your job is to distil the sometimes chaotic happenings within PostHog into sales enablement. You'll be taking positioning and messaging from across PostHog and turning it into something Sales can actually use to win deals. You'll use a mix of strong communication and engineering skills to do it. You'll collaborate closely with our sales team, our other PMMs, engineers, and users to strengthen our position as the default all-in-one devtool. The work spans positioning, competitive intelligence, objection handling, customer storytelling, and the operating cadence that keeps it all current. PostHog ships fast and our product surface area is broad -- staying ahead of that, and making sure Sales doesn't fall behind it, is the core of the job. You'll also create positioning and messaging for platform features and areas without a dedicated PMM. Marketers at PostHog are hands-on, T-shaped people who take on a lot of varied responsibilities to support users and other teams. You'll be one of the key voices for our company and comfortable being visible to customers, partners, and the sales team, often translating between them. What you will be doing Owning sales enablement end-to-end . You'll be the person Sales goes to for positioning, competitive material, objection handling, and customer stories. You'll build and maintain the playbooks in the public handbook so Sales can find what they need in the moment they need it. Translating PMM work into Sales-ready material . Our PMMs own product-level positioning and messaging for some products. You'll take that work and turn it into battlecards, talk tracks, discovery questions, and enablement sessions that Sales can actually use. Filling positioning gaps . Some platform features and product areas don't have a dedicated PMM today. You'll own positioning for those areas so Sales has a clear story everywhere. Surfacing insight from real customer conversations . Use cases, objections, and pain points are currently buried in Gong recordings and Slack threads. You'll pull signal out of those and feed it back into messaging, content, and product. Shipping. A lot. This is not a job where you write a strategy deck and wait. You'll be shipping enablement every week -- battlecards, FAQs, training sessions, launch enablement -- and iterating fast based on what Sales actually finds useful. Example public issues/projects: Product Launch: Launch Plan: LLM Observability requests-for-comments-public#348 Price Cut Comms: RFC: Data warehouse pricing update Q3 2025 requests-for-comments-internal#818 What you won't be doing ❌ Writing whitepapers, mission statements, or sales decks nobody reads. ❌ Running formal certification programs or quarterly readiness training. ❌ Owning the CRM, sales ops, or pipeline metrics. That's Sales' job. ❌ Spending multiple quarters planning big projects which don't have immediate impact. ❌ Running yawn-worthy webinars and bombarding users with invitations to attend. Requirements Excellent writing, researching, and communication skills Development experience, though not necessarily in a formal role -- vibecoded side projects still count Experience targeting developers as customers or writing for technical audiences Experience building and maintaining sales enablement content that's actually used Comfort working closely with Sales as your primary internal customer Nice to have Experience surfacing insights from call recordings (Gong, Granola, etc.) Experience working with handbook-style documentation as the source of truth Familiarity or experience working with devtool products Experience working as a product marketer, growth marketer, or content marketer 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