The Debrief by incident.io

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.

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 atincident.io. In this episode, we chat with Product Engineer Leo about her time building On-call, our favorite engineering tooling, and what makes our engineering culture as good as cinnamon buns.

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, Norberto Lopes and Rory Malcolm discuss Rory's journey as a product engineer at incident.io, focusing on his experiences in the AI team and the challenges of developing the AI investigations product. They explore the engineering culture at incident.io and the impact of AI on incident management. The discussion also touches on the future of incident management and the evolving role of AI in a tech environment.

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, Alicia chats with Kelsey, a long-time product engineer on the Response team. They dive into Kelsey’s journey from lab automation to building core incident features, the magic (and madness) behind Scribe, and what it’s like working on a high-performing team. Expect stories about AI, workarounds, and why versioning folders manually isn’t a scalable solution.

Join us for a deep dive into how incident.io is leveraging AI to build an intelligent incident investigator. Our guests, Ed and Lawrence, share insights on building AI-powered investigations that help teams to leverage huge amounts of data and signals to respond faster and more effectively.

In this episode, Stephen, Pete and Chris take a look back at 2024 at incident.io — reflecting on the year’s personal milestones, company-wide changes, and how the product has evolved along the way. And as is customary, there's plenty of the usual good-natured humor along the way too.

In this episode, hosts Norberto and Lawrence discuss the recent CrowdStrike incident that began on July 19th. You won't find any backseat commentary on the technical specifics, but instead a deep dive into the things we care about incident.io, like communication, their over response and proactive problem-solving during crises.

This week, we're talking to Sabin Roman, engineering manager at Linear, to talk about processes that sit behind building their product. We cover how they build teams around planned work, how their "goalie" role works to protect teams from unplanned work, the zero bugs policy they've introduced and how they ensure everyone at Linear sweats the details on their product.

This week we sit down with Hank Jacobs, Staff Site Reliability Engineer at Netflix to discuss their deployment of incident.io across their organization. Among other things, we discuss how great UX has allowed them to roll out to hundreds of teams in months, how they have more entries in their Catalog than any other incident.io customer, and how their partnership with incident.io has been an overall game changer.

During a recent episode of The Debrief, we spoke with Jeff Forde, Architect on the Platform Engineering team at Collectors, about building an incident management program at various stages of growth.  In that episode, we called it growth from zero to one, one to two, and two to three.  But what happens once you’ve scaled beyond three and answers to question you may have become that much harder to find.  To get to the bottom of this, we chatted with Oliver Tappin, Director of SRE at Eagle Eye, about what to do once your company has reached a point where there’s no precedent or roadmap, and you can’t necessarily look to others for answers.