Site Reliability Engineering interview question · Most asked
What is chaos engineering, and how do you start safely?
Summary
Chaos engineering runs controlled experiments that inject failures (instance loss, latency, dependency errors, zone outages) to verify that the system behaves as expected, uncovering weaknesses before real incidents do.
Longer Answer
Method from the Principles of Chaos Engineering: define steady state with metrics (an SLI), form a hypothesis ("losing one cache node does not change the error rate"), inject a realistic failure, minimise blast radius, and compare. Start in staging or with a tiny production scope during working hours, with a stop button and on-call aware; expand as confidence grows. Tools: AWS Fault Injection Service, Chaos Mesh, LitmusChaos, Gremlin. Game days apply the same idea to people and processes.
Key Points
- Hypothesis-driven failure experiments.
- Measure steady state via SLIs.
- Small blast radius and a stop button.
- Start small; expand with confidence.
More most-asked Site Reliability Engineering questions
- What is Site Reliability Engineering, and how does it relate to DevOps?
- What makes a good alert? Explain symptom-based alerting and alert fatigue.
- What is an error budget, and how should it be used?
- Define SLI, SLO and SLA, and explain how they relate.
- What is burn-rate alerting, and why is it better than alerting on raw error rates?
- How do you choose good SLIs for a service?
- What are the four golden signals?
- What is the difference between monitoring and observability? Explain metrics, logs and traces.