Covers design and operational practices for building and running reliable software systems and for achieving operational maturity. Topics include defining, measuring, and using Service Level Objectives, Service Level Indicators, and Service Level Agreements; establishing error budget policies and reliability governance; measuring incident impact and using error budgets to prioritize work. Also includes architectural and operational techniques such as redundancy, failover, graceful degradation, disaster recovery, capacity planning, resilience patterns, and technical debt management to improve availability at scale. Operational practices covered include observability, monitoring, alerting, runbooks, incident response and post incident analysis, release gating, and reliability driven prioritization. Proactive resilience practices such as fault injection and chaos engineering, as well as trade offs between reliability, cost, and development velocity and scaling reliability practices across teams and organizations, are included to capture both hands on and senior level discussions.
MediumSystem Design
0 practiced
Create a runbook template for an on-call responder handling a payment gateway outage. The template must include triage checklist, health checks/commands, mitigation steps (circuit-breakers, fallback payments), rollback criteria, stakeholder communication templates, and post-incident follow-ups.
HardSystem Design
0 practiced
Design a distributed rate limiting solution using token bucket semantics across an API gateway cluster to ensure fair usage without introducing a single global bottleneck. Discuss local token buckets, global quotas, synchronization strategies (consistent hashing, sharding, central token service), failure modes, and latency implications.
HardTechnical
0 practiced
Propose a decision framework that teams can use to prioritize remediation of reliability issues versus building new features. Include a formula or rubric that factors error budget consumption, customer impact (e.g., dollars/minute), remediation effort, and downstream risk. Show a worked example comparing two tickets.
HardSystem Design
0 practiced
Architect an automated release gating system that integrates SLO analysis, synthetic tests, real-user telemetry, and ML-based anomaly detection to automatically block or slow rollouts. Describe data flows, decision logic, tooling choices, failure modes, and how teams can request manual overrides with auditability.
MediumTechnical
0 practiced
Design a synthetic monitoring strategy for a global SaaS product: decide what checks to run (availability, auth, checkout flow), where to run them (global locations), frequency, script complexity, cost trade-offs, and how to use synthetic results alongside real-user metrics to detect regressions earlier.
Unlock Full Question Bank
Get access to hundreds of Reliability and Operational Excellence interview questions and detailed answers.
