Operations | Monitoring | ITSM | DevOps | Cloud

At incident.io, we’ve spent the past year shifting how we work to incorporate the AI into both how we build and what we build. The result? AI has become a fundamental pillar of our company. This is the story of how we built reliable AI for reliability itself — reshaping how teams manage and resolve incidents. From early experiments to a company-wide culture of building with AI, this is how we’re redefining incident response for the future.

Pete Hamilton, CTO, Lawrence Jones, AI Engineer, and Ed Dean, AI Product Manager runs through our new AI SRE product. AI SRE shortens time to resolution by automating investigation, root cause analysis, and a fix, all before you’ve even opened your laptop.

From 3 people in 2020 to 93 in 2025—incident.io has come a long way, and we’re just getting started. Whether you’ve been here since the early days or just joined, this is what it looks like to build something great *together*. If you're after:️️ Great people Real impact (across the globe, not just in Greece) A place where growth is the default And teammates who’ll always be there for you... We’re hiring! (And we're going to need a bigger couch…)

Molly Struve (Netflix) goes beyond the purely technical post-incident analysis, diving into the human element of system failure.

Michael Tweed (Skyscanner) shares the story of an incident that quietly broke data emission for days, and why none of their alerts (or AI) caught it.

No matter how hard you try to prevent it, your product will break. And sometimes, it breaks in the middle of the night. Getting paged at 3 a.m. is rough. Getting paged again two hours later because of a follow-up issue you missed the first time is even worse. So how can a manager stay aware when their team is having a tough night or a tough week on call, without relying solely on direct reports?

In this episode, CTO Pete and Product Engineer Rory B. discuss how we’re using Claude Code and Git Worktrees to allow engineers to build multiple features in parallel.

We’re running a short mini-series on The Debrief podcast called Beyond the code, where we interview our engineers about what it’s really like to build at incident.io. In this episode, we chat with Product Engineer Leo about how we’re using AI tools like Claude Code to ship more product, more quickly.

Let's be honest - observability can suck. Ever feel like you're swimming in dashboard soup? You know the feeling: tons of single-use dashboards, building new ones during every incident only to lose them in the chaos, and spending ages creating visualizations that no one ever looks at again. Even with all the right tools, something still feels off.