SLIs, SLOs, SLAs, and Error Budgets Questions
Defining and operating reliability targets. Covers choosing service level indicators, setting service level objectives and agreements, computing and spending error budgets, and using them to drive engineering decisions. Includes negotiating reliability targets with stakeholders.
Describe the key success metrics and SLOs you defined for a production data service you built. Include quantitative thresholds (throughput, p95/p99 latency, data freshness, error rate), how you chose the thresholds based on business needs, and how you validated those SLOs during launch and operation.
How would you measure release velocity for a team and correlate it with error budget consumption to detect unhealthy trade-offs? Propose metrics, how to collect them, visualization approach, and at least one alert or policy you might derive from the correlation.
Implement a Python function compute_error_budget_consumption(slo_percent: float, window_minutes: int, good_minute_flags: List[int]) that returns the percentage of the error budget consumed in the window. good_minute_flags is a list with 1 for a 'good' minute and 0 for a 'bad' minute. Assume the list length equals window_minutes. Show examples and complexity.
Define Service Level Indicators (SLIs) and Service Level Objectives (SLOs) for a support ticketing system focused on response and resolution. Propose three alerting thresholds that would escalate from an on-call page to a stakeholder email, and explain how to set each threshold to minimize alert fatigue.
Design SLOs for a background batch job pipeline (daily ETL ingest) that is allowed to run for several hours. Which SLIs would you choose (e.g., completion rate, freshness, correctness), how do you measure them, and how do you reflect them as SLOs given inherently asynchronous behavior?
Unlock Full Question Bank
Get access to all SLIs, SLOs, SLAs, and Error Budgets interview questions and detailed answers.
Sign in to ContinueJoin thousands of developers preparing for their dream job.