Product Marketing Manager AI & Platform

is the AI software reliability platform trusted by engineering teams at Netflix Etsy and 2000 companies who cant afford downtime.

The stakes are real the talent is insane and somehow its a genuinely lovely place to work. We all pull our weight go the extra mile and put in the bit of magic most companies dont have time for all while having fun and never taking ourselves too seriously.

Weve raised $96 million from Index Ventures Insight Partners and Point Nine and were growing fast. Theres never been a better time to join.

Own positioning messaging and the funnel for Investigations our newest AI product and work cross-functionally with product and sales to be the bridge between them.

The Team

The small but mighty Marketing team at is responsible for accelerating revenue growth. We define product marketing as communicating how the world hears about understands and buys our product from sales collateral and pitch narratives to website creative and product launch materials.

This role is different from a generalist PMM seat. Youll own the two areas where our product is changing fastest and where the story is hardest to tell: AI and the platform underneath it. That means investigations Nexus our AI capabilities integrations APIs extensibility and the developer-facing surfaces. These are the things technical buyers push hardest on and the things a vague message gets punished for.

Youll be collaborating with the AI team and product engineering to define the future of how we positiong and package our AI features. Youll create messaging and campaigns that make the technical genuinely legible to engineers to platform teams to the sceptics in the room whove heard AI-powered too many times.

One thing we should be upfront about: this role is for someone who is already deep in AI not someone whos interested in getting there. Youve marketed an AI product or feature. You build things with AI at work or on weekends in Claude Code or Cursor or Lovable or whatever youve landed on. You have opinions about what these tools are actually good at because youve hit their limits yourself.

If the last time you used an LLM was to tidy up a draft this likely isnt the seat.

• Owning positioning and messaging for AI & Platform turning fast-moving technically deep capability into narratives that land with engineers and the people who buy for them. Youll be the one who decides what we claim what we dont and how we prove it.

• Getting hands-on with the product & demos. Youll use it break it and build a real mental model of how it works. Your credibility with a technical audience depends on this.

• Building with AI as part of how you work. Standing up a tool to analyse a few hundred Gong calls. Shipping a working demo instead of describing it. Wed rather you spent an afternoon building the thing than a week writing the doc about it.

• Driving launches for AI and platform capability from narrative and naming through to launch assets docs collaboration enablement and post-launch adoption. Working closely with Product and Engineering from well before the ship date.

• Arming all of GTM for technical conversations with battle cards objection handling demo narratives and proof points that hold up when the customers staff engineer is in the room.

• Understanding the market and the buyer through customer and prospect research Gong calls community and competitive mapping. Youll know where the AI incident-management category is actually going not just where vendors say it is.

• Making the technical story show up everywhere website docs campaigns content conference talks in partnership product engineering and the wider marketing team.

• Youve marketed an AI product or feature already. Not adjacent to one youve owned the positioning launch or narrative for AI capability and lived through what thats actually like: the proof problem the sceptics the moving roadmap the claims you had to walk back.

• You build with AI yourself. Youve spent real time with Claude Code Cursor Lovable v0 or similar at work or on your own time and you can describe a recent project you built what it does where the tools fell over and what youd do differently. Well ask about this and a vague answer will be obvious.

• Genuine technical fluency. You can read API docs hold your own with engineers and explain a system without hand-waving. You might have your own Git Hub account have worked as an engineer or have marketed developer-facing products for…