DevOps interview prep: recover with evidence

Restore service. Show the evidence.

Open the incident

Practice interviews

03 Make the release condition explicit

“Set the evaluation window, failure criteria, and maximum failure count.” (opens the source)

CircleCI, Product changelog · CircleCI Changelog, Sep 2, 2026

Set a failure condition and an observation window before the change.

“Protect customers from repeated SLO misses” (opens the source)

Steven Thurgood, Author, example error-budget policy · Google SRE Workbook, Feb 19, 2018

Apply the service's written policy to its own error budget.

Enter the incident roomTake the on-call seat

Sources

  1. Matthew Prince, Author, Cloudflare incident report, at the time. Cloudflare Blog, “Cloudflare outage on November 18, 2025”, Nov 18, 2025. Open the source. Checked against the published text.
  2. CircleCI, Incident report, at the time. CircleCI Discuss, “Post Incident Report: June 23, 2026 - Delays starting Docker jobs”, Jun 27, 2026. Open the source. Checked against the published text.
  3. CircleCI, Product changelog, at the time. CircleCI Changelog, “Smart Deployments: continuous release validation with automatic rollback”, Sep 2, 2026. Open the source. Checked against the published text.
  4. Steven Thurgood, Author, example error-budget policy, at the time. Google SRE Workbook, “Example Error Budget Policy”, Feb 19, 2018. Open the source. Checked against the published text.
  5. Stevan Malesevic and Christopher Heiser, Distinguished Software Engineer and Distinguished Site Reliability Engineer, at the time. Google Cloud Blog, “AI in SRE: Where and how Google is deploying agentic AI to improve operations”, May 28, 2026. Open the source. Checked against the published text.
  6. Daniel Chatfield and Andrew Lawson, Distinguished Engineer and Senior Staff Engineer, at the time. Monzo Technology, “Tolerating full cloud outages with Monzo Stand-in”, Feb 13, 2025. Open the source. Checked against the published text.

Last reviewed Nov 10, 2026