Incident Management & Resilience Lead

Incidents get resolved, but the fixes that would stop them recurring slip down the backlog — and a few weeks later, a version of the same failure comes back. Most teams live with that. On a platform as critical as Buildkite's, we've decided not to, which is why we're creating a role whose whole remit is to own how we respond to incidents and design them out for good.

🔧 The problem worth solving

Buildkite runs production builds for teams like OpenAI, Anthropic, Uber, Shopify, Airbnb, Canva and Pinterest — software delivery in the critical path for over a billion daily users. When something breaks here, it breaks loudly, for people who can't afford it to.

Until now, Incident response has been carried by whoever was closest, in the gaps between everything else they own. It's held up. But "held up" is no longer the bar for a platform this critical. We'll be asking you to set the standard for how the whole engineering org detects, responds to, learns from, and designs out the incidents that matter — end to end.

🚀 What you'll own

You'd own incident management across engineering — the definition, process, tooling, and adherence — and make it stick.

In the moment, you're in the room on the high-impact incidents, driving clarity, coordination and a clean resolution. Between incidents — where the real work lives — you're running postmortems that go somewhere, making sure the followups get done every time, and turning what each one taught us into the changes that make the next incident smaller.

You'd work across every product team plus Security and Support, holding one consistent resilience bar and bringing engineering managers with you. And you'd coach engineers on how to run an incident, communicate through it, and own the outcome.

🎨 The person we're picturing

You've built or materially lifted incident management capability somewhere before, and you've got a clear, earned point of view on what good looks like.

…