---
title: 'Product Engineer - GTM at incident.io'
canonical: 'https://feeny.ai/job/product-engineer-gtm-incident-io-london-s82q918zk5dd'
type: 'job'
last_seen: '2026-10-14'
---

# Product Engineer - GTM at incident.io

- **Company:** incident.io
- **Location:** London, United Kingdom
- **Employment:** full-time
- **Posted:** 2026-08-13
- **Last confirmed live:** 2026-10-14
- **Apply:** https://jobs.ashbyhq.com/incident/e4e272c4-95a3-43df-a414-a4c1c5f1279d

## Job description

A little about us [incident.io](http://incident.io) is the AI software reliability platform trusted by engineering teams at Netflix, Etsy, and 2,000+ companies who can't afford downtime. 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 $100+ 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

You’ll build and run the software and systems our revenue team relies on, working directly with the people using them to find the right problems, build the right solutions, and own them end to end.

What that looks like day to day You’ll work closely with BDRs, AEs, Customer Success, Marketing and GTM leadership to understand how work actually gets done: where people are spending time on repetitive tasks, where data or context gets lost between systems, and where the tools we have are getting in the way. From there, you’ll work out what the right solution is. Sometimes that will be an automation or integration. Sometimes it’ll be an internal tool, an AI workflow, or a piece of software you build yourself. Sometimes the right answer will be simplifying a process or getting rid of a tool entirely. You’ll spend plenty of time building, but this isn’t a role where requirements arrive neatly packaged. You’ll talk directly to the people using what you make, understand the underlying problem, ship something, and follow up to see whether it actually helped. You’ll also take a broader view of our GTM systems. You’ll understand how data and workflows move between tools, make decisions about where logic should live, and help us evolve the stack as the company changes. We want systems that are understandable and dependable, rather than a collection of one-off automations that happen to work today. And you’ll own what you build in production. If an integration breaks or a workflow behaves strangely, you’ll debug it, fix the underlying problem, and improve the system around it. Supporting the revenue team is part of the feedback loop, not a separate ticket queue. AI is already a normal part of how we work, and there’s a lot of opportunity to use it here. We’re interested in where agents and models can genuinely improve a workflow, as well as where conventional software is still the better answer. You’ll have room to experiment, measure what works, and turn the useful parts into things people can depend on.

## Who you are

- You’re a software builder who enjoys working on messy, real-world problems. You’ve built things that people rely on and you care about how they behave once they’re in use.
- You’re product minded. You want to understand the problem before reaching for a solution, and you’re comfortable talking directly to users to get there.
- You understand how modern go-to-market teams work. You’re familiar with the workflows and systems behind sales, outbound, customer success and marketing, and you can get up to speed quickly in an unfamiliar stack.
- You think in systems. APIs, integrations, data models, automation and reliability are interesting to you, and you notice when a local fix is creating a bigger problem elsewhere.
- You’re pragmatic about technology. You’re as happy configuring an existing tool when that’s the sensible answer as you are writing code when it isn’t.
- You use AI seriously in your own work. You’ve experimented enough to have a feel for what it’s good at, what needs careful evaluation, and where simpler approaches work better.
- You’re comfortable with ambiguity and ownership. Problems here won’t always come with a specification or an obvious owner, and you’re happy turning something fuzzy into something useful.
- You communicate clearly. A big part of the job is making technical systems understandable to the people who depend on them, and making their problems understandable to the people building them.
- You have taken ownership of software procurement in the past, and know how to get a new tool bought, configured and rolled-out.

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.

## About incident.io

## Company Overview
- **One-liner**: incident.io provides an all-in-one AI-powered incident management platform that helps fast-moving teams respond to outages, coordinate on-call, and keep customers informed.
- **Entity Type**: Private (Series B, raised $62M at ~$400M valuation)
- **Headquarters**: London, UK (with offices in San Francisco and New York)
- **Founded**: 2021
- **Founders**: Stephen Whitworth (CEO), Pete Hamilton (CTO), Chris Evans (CPO)

## Core Business
- **Primary industry**: Incident management / IT operations / DevOps
- **Target customers**: B2B, primarily mid-market to enterprise (organisations of 200+ users), including engineering, product, support, and increasingly security teams
- **Mission**: “Move fast when you break things” — empower teams to respond quickly, coordinate clearly, and get better each time something breaks

## Products & Services
- **Response**: End-to-end incident lifecycle management, deeply integrated with Slack and Microsoft Teams, with AI-powered workflows to accelerate resolution
- **On-call**: Modern on-call scheduling with noise reduction, designed for humans — competes directly with PagerDuty (used by 70% of customers)
- **Status Pages**: Automated, transparent status updates to keep customers informed during incidents
- **Investigations**: AI-driven root cause analysis that surfaces failing PRs and suggests fixes, often before the responder has opened their laptop
- **AI Copilot**: Summarises incident calls, queries monitoring tools like Datadog, and generates action items

## Market Standing
- **Valuation**: ~$400 million (Series B, April 2025) — [TechCrunch](https://techcrunch.com/2025/04/10/incident-io-raises-62m-at-a-400m-valuation-to-help-it-teams-move-fast-when-things-break/)
- **Key Metric**: Total funding $96M; annual revenue not disclosed, but customer base tripled in the last 12 months
- **Notable Investors/Partners**: Insight Partners (Series B lead), Index Ventures, Point Nine Capital
- **Growth Signals**: 190 employees across London, SF, and NY; over 1,000 customers including Netflix, Airbnb, Block, Linear, Ramp, and Etsy; 250,000 incidents managed since founding; 75% of new customers are U.S.-based — [incident.io/careers](https://incident.io/careers), [TechCrunch](https://techcrunch.com/2025/04/10/incident-io-raises-62m-at-a-400m-valuation-to-help-it-teams-move-fast-when-things-break/)

## Competitive Advantages
- **All-in-one platform**: Combines on-call, response, status pages, and AI investigation — reducing tool fragmentation that plagues incident management
- **AI-first, pragmatically**: Uses AI where it genuinely adds value (investigation, summarisation, root cause analysis) rather than for hype — [incident.io/blog/incident-io-behind-the-curtain](https://incident.io/blog/incident-io-behind-the-curtain)
- **Office-first culture**: High-bandwidth collaboration and pace, attracting talent who thrive in an in-person environment
- **PagerDuty Rescue Program**: Aggressive migration offering (white-glove migration, contract buyout) to capture market share — [incident.io](https://incident.io/)
- **Strong product-led growth**: Engineers love the product, driving organic adoption

## Strategic Focus
- Deepen AI capabilities for incident investigation and remediation (moving toward autonomous fixes)
- Expand into security incident response (already seeing adoption from security teams)
- Grow U.S. market presence through sales and marketing
- Continue to build out the platform to cover the full incident lifecycle

## Why Work Here
- **Culture**: High trust, high standards, fast execution. Values: *Make it magic*, *Find a way*, *Raise the pace*, *Trust by default*, *Win together* — [incident.io/careers](https://incident.io/careers)
- **Work environment**: Office-first in London (4–5 days/week expected, with occasional remote weeks); offices in SF and NY. Not a remote-first company — [incident.io/blog/incident-io-behind-the-curtain](https://incident.io/blog/incident-io-behind-the-curtain)
- **Engineering culture**: 1–3 week projects, broad product surface area, written alignment (scopes, design docs, thorough commit messages), AI used where it genuinely helps
- **Growth**: Well-funded, fast-growing, strong market position — career-defining problems and a wildly talented team
- **Perks**: Not explicitly listed, but emphasis on sane work-life balance, autonomy, and working on a product customers genuinely love

## Sources
1. [incident.io/careers](https://incident.io/careers)
2. [incident.io](https://incident.io/)
3. [LinkedIn](https://www.linkedin.com/company/incident-io)
4. [incident.io/blog/incident-io-behind-the-curtain](https://incident.io/blog/incident-io-behind-the-curtain)
5. [TechCrunch](https://techcrunch.com/2025/04/10/incident-io-raises-62m-at-a-400m-valuation-to-help-it-teams-move-fast-when-things-break/)

## Other roles at incident.io

- [GTM Talent Partner](https://feeny.ai/job/gtm-talent-partner-incident-io-london-sn8gmv7sgykb) — London, United Kingdom
- [Account Executive](https://feeny.ai/job/account-executive-incident-io-new-york-6tnwfsz7cr2y) — New York, NY
- [Account Executive](https://feeny.ai/job/account-executive-incident-io-san-francisco-a762xtjkmeqy) — San Francisco, CA
- [Customer Success Engineer](https://feeny.ai/job/customer-success-engineer-incident-io-london-6kj1w1f72ezs) — London, United Kingdom
- [Technical Support Engineer](https://feeny.ai/job/technical-support-engineer-incident-io-london-kfc1bgjex9k3) — London, United Kingdom
- [Technical Support Engineer](https://feeny.ai/job/technical-support-engineer-incident-io-new-york-7277zz6mzvnc) — New York, NY
- [VP of Sales, EMEA](https://feeny.ai/job/vp-of-sales-emea-incident-io-london-2eghnw2eanwk) — London, United Kingdom
- [Entry-Level Business Development Representative (BDR) 2027 Cohort](https://feeny.ai/job/entry-level-business-development-representative-bdr-2027-cohort-incident-io-san-5evq0jcd4002) — San Francisco, CA
- [Enterprise Customer Success Manager](https://feeny.ai/job/enterprise-customer-success-manager-incident-io-london-s0ejpjwnhw7n) — London, United Kingdom
- [Commercial Customer Success Manager](https://feeny.ai/job/commercial-customer-success-manager-incident-io-london-dk5n2we14h6x) — London, United Kingdom