A little about us

incident.io is the leading AI incident response platform, relied on by some of the best engineering teams in the world when things go wrong.

Since launching in 2021, we've helped over 2,000 companies, including OpenAI, Netflix, and Airbnb, run more than 1 million incidents.

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

We've raised $96 million from Index Ventures, Insight Partners, and Point Nine, and we're growing fast. There's never been a better time to join.

The role in one line

Being the PMM for AI and Platform at incident.io means explaining something that didn't exist eighteen months ago to engineers who'll spot a hollow claim in a heartbeat — and getting it right anyway.

What that looks like day to day

You'll own positioning and messaging for AI and Platform — turning fast-moving, technically deep capability into narratives that land with engineers and the people who buy for them. You're the one who decides what we claim, what we don't, and how we prove it.

That starts with the product. You'll use it, break it, and build a real mental model of how it works, because your credibility with a technical audience depends on it. The same goes for how you work: standing up a tool to analyse a few hundred Gong calls, shipping a working demo instead of describing one. We'd rather you spent an afternoon building the thing than a week writing the doc about it.

You'll drive launches end to end — narrative and naming through to launch assets, docs, enablement and post-launch adoption — working with Product and Engineering from well before the ship date, not the week of. And you'll arm the whole GTM team for technical conversations with battle cards, objection handling, demo narratives and proof points that hold up when the customer's staff engineer is in the room.

Underneath all of it is knowing the market properly. Customer and prospect research, Gong calls, community, competitive mapping — enough that you know where the AI incident-management category is actually going, not just where vendors say it is. Then you make that story show up everywhere: website, docs, campaigns, content, conference talks, in partnership with product engineering and the wider marketing team.

Who you are

• You've marketed an AI product or feature already. Not adjacent to one — you've owned the positioning, launch or narrative for AI capability and lived through what that's actually like: the proof problem, the sceptics, the moving roadmap, the claims you had to walk back.

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

• You're technical enough to be dangerous. You can read API docs, hold your own with engineers, and explain a system without hand-waving — because you've been one, or because you've marketed to them for years.

• You've positioned complicated things for technical buyers before. Dev tools, infrastructure, platform, security — somewhere the audience knows more than you'd like and the story has to survive contact with them.

• You have a point of view on positioning, not just a process for it. You've probably read Obviously Awesome more than once, and you've disagreed with bits of it.

• You can write. Really write — the kind that makes something complex simple without quietly making it wrong.

• You're sceptical about AI in the right way. You follow the space closely enough to know what's genuinely new and what's been rebranded, and you'd rather describe what the product does than reach for the category buzzword.

• The brief will often be one sentence, and that suits you. You'd rather build the thing than ask what shape it should be, and increasingly the fastest route there runs through AI.

Bonus points

• You've shipped something with AI that other people actually use — an internal tool, a side project, a prototype that made it to production.

• You've written developer documentation, or worked shoulder-to-shoulder with the people who do.

• You've spoken at, or written for, a technical audience under your own name — especially about AI, where a public point of view is worth a lot.

• You've built AI into how a marketing team works, not just into your own workflow.

Supporting you

We work hard and we think life outside work matters just as much. Our benefits pack is built to support both.

• Private medical insurance. Seriously good cover - we want you and the people you love to be looked after.

• Competitive annual leave. Showing up at your best requires switching off, and we make sure you have time to do that.

• First Friday of every month off. Yes, seriously.

• Enhanced pension. We put real money in, because future-you deserves better than an afterthought.

• Meaningful equity. We're rapidly scaling, and everyone who helps shape the outcome should share in it.

• Unlimited AI spend. For everyone, not just engineers. We're all-in on AI across the company, and we expect you to be too.

• Generous parental leave. The early days with a new baby matter more than anything we're doing here, and we want you to be present for them.

• Two budgets that have your back. £1000 to invest in your setup, £500 a year to invest in yourself.