What is Error Budget?
An error budget is the amount of unreliability a service is allowed over a window, the gap between its Service Level Objective and 100%. A 99.9% availability SLO yields a 0.1% error budget (about 43 minutes of downtime per month).
No account needed · Scored in under a minute against a senior rubric
What does Error Budget mean in practice?
Error budgets turn reliability into a currency teams can spend. If your SLO is 99.9%, you are explicitly allowed to be unavailable 0.1% of the time. That budget can be spent on shipping risky features, doing migrations, or absorbing the occasional incident. The point is to make the trade-off between reliability and velocity explicit and data-driven instead of an argument between developers who want to ship and operators who want stability.
The mechanism is an error budget policy. When there is budget left, the team ships freely and can take risks. When the budget is exhausted (too many incidents this month), the policy kicks in: feature work pauses, and the team focuses on reliability, fixing the causes, adding tests, hardening, until the service is back within budget. Burn rate (how fast you are consuming the budget) drives alerting.
For QA and SDET, error budgets connect testing to business decisions. A spent budget is often a signal of insufficient testing or fragile releases; testing, canaries, and good rollback are how teams protect the budget. Speaking this language shows you understand reliability as a managed resource.
Why do interviewers ask about Error Budget?
Error budgets are an advanced, high-signal interview topic for SDET, platform, and lead roles. Explaining how a budget balances velocity against reliability, and how testing protects it, shows SRE-influenced maturity.
What does Error Budget look like in a real project?
A team with a 99.9% SLO burns most of its monthly error budget through two incidents by mid-month. Their error budget policy freezes new feature launches and redirects the team to add the missing tests and rollback automation that would have prevented the incidents, until reliability recovers.
How should you talk about Error Budget in an interview?
Define an error budget as the allowed unreliability (the gap between the SLO and 100%) and explain the policy: ship freely when budget remains, pause features and focus on reliability when it is spent. Tie it to how testing and safe releases protect the budget.
Go Deeper on Error Budget
Know the term. These are the courses that turn the concept into something you can demonstrate.
Common questions about Error Budget
How is an error budget calculated?
It is 100% minus the SLO, applied over a window. A 99.9% availability SLO gives a 0.1% error budget, roughly 43 minutes of allowed downtime per 30-day month.
What happens when the error budget runs out?
An error budget policy typically pauses new feature launches and redirects the team to reliability work, fixing causes, adding tests, hardening, until the service is back within its SLO and the budget recovers.
Which terms relate to Error Budget?
Explore related glossary terms to deepen your understanding.
Related Resources
Dive deeper with these related interview prep pages.
Free QA career tools, no account needed
Instant and private, everything runs in your browser. Try them before you sign up.
QA Resume Checker
Instant 0-100 score on automation keywords, impact, and ATS formatting.
QA Cover Letter Generator
A tailored 3-paragraph QA cover letter from your resume and a job post.
QA Application Tracker
Drag-and-drop kanban to track every QA application from Applied to Offer.
QA Take-Home Test Generator
A realistic take-home assignment with a scenario, tasks, and a rubric.
QA LinkedIn Headline Generator
A recruiter-searchable headline, About section, and skills list.
QA STAR Story Builder
Structure a QA behavioral answer with the STAR method and instant checks.
QA Bug Report Generator
Build a clean, reproducible bug report for Markdown, Jira, or plain text.
Boundary Value Analysis Generator
Generate boundary value and equivalence partitioning test cases from a range.
QA Metrics Calculator
Calculate DRE, defect leakage, defect density, and pass rate with interpretation.
QA Test Plan Generator
Build a structured test plan (scope, approach, criteria, risks) in Markdown.
QA Salary Calculator
Estimate QA, SDET, and automation tester pay by level, market, and skills.
QA Offer Evaluator
See total comp, a counter range, and a ready-to-send negotiation message.
Ready to Ace Your QA Interview?
Practice explaining error budget and other key concepts with our AI interviewer.
Join 500+ QA engineers already practicing with AssertHired.
A test passes locally but fails in CI about one run in five. Walk me through what you check first, and why.
Scored on the same four dimensions as the real thing: Technical accuracy · Coverage · Clarity · Best practices.
Rather skip ahead? Create a free account