incident.io
Administrative and Support Services
incident.io is an all-in-one incident management platform unifying on-call scheduling, real-time incident response, and integrated status pages – helping teams resolve issues faster and reduce downtime.
Is incident.io hiring?
Yes. As of November 14, 2026, incident.io has 5 open roles on Metaintro.
Open roles
Newest first. Pay shown when the posting lists it.
- Staff Software EngineerDeveloperLondon, UK · RemoteLondon, UKRemote—Jan 1, 2026
- Account Executive, CommercialSalesNew York, NY · RemoteNew York, NYRemote—Jan 1, 2026
- Business Development RepresentativeBusiness DevelopmentNew York, NY · HybridNew York, NYHybrid—Jan 1, 2026
- Enterprise Sales ManagerSalesSan Francisco, CA · HybridSan Francisco, CAHybrid—Dec 17, 2025
- Enterprise Account ExecutiveSalesNew York, NY · RemoteNew York, NYRemote—Oct 24, 2025
Customers
All 37 companies incident.io names as customers.
Customers hiring now27
- Netflix417 open roles

- SSumUp295 open roles
- ZZendesk126 open roles
- PPicnic113 open roles
- IIntercom103 open roles
- EEtsy90 open roles
- Vanta79 open roles

- RRho49 open roles
- Contentful46 open roles
- TTrainline35 open roles
- Pleo33 open roles
- Groq32 open roles

- TTorq31 open roles
- WorkOS27 open roles

- Kaizen Gaming24 open roles

- Motorway19 open roles

- Accurx14 open roles

- TrueLayer8 open roles

- Future7 open roles

- Buffer6 open roles

- Isometric6 open roles

- turbopuffer6 open roles

- RRD Station4 open roles
- AudioStack3 open roles
- Built1 open role

- BBud1 open role
- FFavor1 open role
Show 17 more customersShow fewer
Case studies7
- CClari
- TThrive Learning
- Bold Commerce

- SSublime Security
- Giant Swarm
- Skyscanner
- Flagstone
Other customers3
- CCloud Platform Team, Built
- BBud Financial
- EEngineering Productivity & Product Reliability
What their customers say
Quotes from people at incident.io's customers.
“[incident.io] allowed us to broaden the definition of what an incident is. Now, with incident.io, the overhead during incidents is gone, leaving response teams feeling more confident throughout the process.”
“It allows for incidents to get funneled into a process that's well defined. More focused communication and a clearer beginning and end to incidents are a huge benefit. Tracking when something started. Keeping tabs on the status of it. Fewer of these things are left open. Now we have more consistent, reliable tracking.”
“The consistency and common touch points across all incidents make it really easy for someone to know what an incident Slack channel is. It allows different people with varying degrees of technical comfort to dig in deeper, which I think is really valuable at our stage.”
“This feature has been really helpful. The transition from them into the postmortem process has helped us be consistent in tracking post-incident workloads.”
“We had specific requirements. The UX needed to be relatively intuitive. The more intuitive it was, the better it scored for the product. And we wanted support getting communications out to all the relevant parties that needed to be kept in the loop on what was going on with incidents,”
Show 25 more quotesShow fewer
“There's one way you do your process, and then you can do the same for any other. So that's what I see as the critical value that incident.io brings.”
“We started as a global incident management program for customer-facing incidents. But we've also incorporated security incidents into it. I think the critical thing is that we have a blueprint to replicate for different problems,”
“I think the biggest thing I see is when I comment in our Slack channel, it gets added to your product board. And then someone comes back and says, ‘Hey, by the way, this is fixed.’ And it’s not weeks or months for turnaround and fixes. It's days, which is super, super impressive.”
“The support team has been excellent. Herbert and George—when you were rolling out the AI assistant —were accommodating. I'm still impressed at the speed with which fixes are turned around,”
“We recently had a product manager fire up an incident for the first time. He had never done one before but knew enough to kick it off. And then I could come in and guide him and say, ‘Okay, great. You’re off to a good start,’”
“The biggest advantage we have right now is that there’s only one way to declare an incident. There’s only one way to track an incident and one way to track an incident evaluation. That in itself is a big win for us,”
“We wanted to roll out the same process to every team. Ultimately, you want to ensure a unified view if you have different products under your portfolio like we do. So I believe having a standardized tool and practice and removing some of the manual cognitive load helped.”
“When I joined in March of last year, I was happy that Balaji was already convinced of the importance of this,”
“There would be lots of ad hoc Zoom calls and very little documentation in the Slack channel,”
“It was not just bespoke, but it was very much at the whim of the individual incident commander. They weren't necessarily being pulled in effectively or quickly.”
“We had an incident command rotation with a primary, secondary, and third-level fallback. But it was, I'd say, very tribal knowledge and isolated as to what people knew and how they did things,”
“We had a very manual and bespoke process. We did have certain guidelines on how to start incidents, how to run them, and how to do follow-ups, but we were basically following instructions from Confluence or Google Docs,”
“When you’re in an incident, your focus should be on recovery. After you have recovered, you should focus on learning. We were struggling to run the process correctly. So we couldn’t focus on the right things,”
“We're focused on solving problems before they happen: agentic remediation, removing the human from the loop, keeping our processes and systems running.”
“You need a full incident management suite, not just an on-call and escalation tool. That makes a whole world of difference, being able to build your process around the tool versus just adopting something that manages one part of the lifecycle.”
“Almost all of it used to be a manual process: the timelines, the follow-ups, all of it. The platform changed that. Every time a new feature lands, it gets harder to imagine running incidents any other way.”
“I don't have to join every call to understand what's going on when the team's working it. The reporting gives me visibility into what happened, who was involved, how long it ran.”
“As an incident manager, I can focus on the incident and not the paperwork. I can focus on the problem. I don't have to worry about documenting the steps that we did; I can have it auto-generated. That has been just night and day.”
“Before, we were managing all of our incident management responses in Confluence, pretty manual and hard to follow. Now we've been able to codify that with incident.io, centralize it, and automate what actually happens.”
“Incident managers don't need to know every step. The system prompts them and drives them through it.”
“We essentially just cut over. Whatever the first incident was, we just started using the tool. It wasn't perfectly configured; we had to tinker and figure things out as we went, but we started immediately handling incidents with incident.io.”
“There were a couple of things that stood out about incident.io compared to the competitors: the licensing model and how Slack-native the process was. We were okay with leaving PagerDuty. It wasn't really special to us.”
“We loved how it managed incidents through Slack, meeting us where we already are.”
“We brought in incident.io for roughly what we were paying for PagerDuty. Except now we had the full incident management lifecycle. That was the big ROI.”
“We had Slack automations that would create a Jira ticket, spin up the incident room, and page the people through PagerDuty who were on call. We built that whole orchestration through Slack.”
AI launches and partners
What incident.io has launched and who it works with on AI.
- LaunchAI handles the adminAI handles the admin while you focus on the fix.
- LaunchAI call transcriptionAI transcribes calls and handles the admin while users focus on the fix.
- LaunchAI filters on-call alertsAI filters the noise and escalates what matters for on-call.
- LaunchAI SRE agentThe AI SRE agent collaborates across the investigation, answers questions, runs parallel analysis, and surfaces things the team may not have thought to look for.
Skills they ask for
Most frequent across open postings.
Tech stack
- Analytics
- Google Analytics 4
- Google Tag Manager
- CMS
- Sanity
- Frameworks
- Next.js
- Libraries
- Tailwind CSS
- Swiper
Company facts
- Founded
- 2021
- Industry
- Administrative and Support Services
- Sector (NAICS)
- Information
- Peer
- Desort
- Website
- incident.io
- Careers
- incident.io/careers
Roles by location
Where incident.io is hiring. Pick a city to see its roles.
Similar companies
Companies in the same industry as incident.io that are hiring now.
Questions about incident.io
- Is incident.io hiring?
- Yes. As of November 14, 2026, incident.io has 5 open roles on Metaintro. The most are in Sales (3), Business Development (1), and Developer (1).
- Where is incident.io hiring?
- incident.io is hiring in New York, London, and San Francisco, with the most open roles in New York.
- Who are incident.io's customers?
- incident.io names 37 customers, including Netflix, SumUp, Zendesk, Picnic, and Intercom.
Work at incident.io? Claim this page