SevyDevy

Design a chaos engineering platform

PremiumCloud infrastructureMedium

  • Chaos engineering
  • Fault injection
  • Blast radius

Quick answer

This cloud infrastructure interview question asks you to design a chaos engineering platform. Aim for a design that runs reliably and securely in the cloud at a sensible cost, then explain the services, regions, deployment and trade-offs. Interviewers want to see how you balance reliability, security and cost.

The problem

Design a chaos engineering platform like the fault-injection tools large companies run: teams kill instances, add latency or cut network paths in staging and production to learn whether systems really recover. The hard parts are keeping the blast radius small, stopping fast when customers are hurt, and never leaving a fault switched on.

Each experiment states a steady-state hypothesis, for example: checkout success rate stays above 99.5% while 5% of payment pods are killed.

What must a chaos engineering platform do?

  • Experiments: Define the target (service, zone, share of pods), the fault (kill, CPU stress, latency, packet loss, dependency errors, zone blackhole), duration, steady-state metric and abort rules.
  • Fault injection: Agents on hosts and sidecars in pods apply faults and remove them.
4 more requirementsUnlock to see all

How well must it do it?

  • Faults always end: Every fault has a deadline enforced by the agent itself, so it ends even if the control plane is unreachable.
  • Fast abort: Under 30 s from a metric breach to all faults removed.
3 more requirementsUnlock to see all

What scale should you design for?

Use these numbers in your estimates.

The scale numbers unlock with this questionUnlock

Key concepts

  • Chaos engineering
  • Fault injection
  • Blast radius
  • Abort conditions
  • Steady state hypothesis
  • SLO guardrails

How you’ll practise

6 short steps · save and come back any time
  1. Requirements
  2. Environments and topology
  3. Deployment pipeline
  4. Reliability and disaster recovery
  5. Observability and cost
  6. Wrap-up

Lala, personalized to you, gives a hint when you ask and reviews your design when you are ready.

What do interviewers look for?

In any cloud infrastructure design round.

  • Clarifies availability, security and cost targets
  • Chooses managed services with reasons
  • Plans regions, zones and failover
  • Covers identity, secrets and network boundaries
  • Explains deployment, rollback and observability
  • Keeps an eye on cost as usage grows

Questions people ask about this interview question

Which design type is this question?
It is a cloud infrastructure question. You design a chaos engineering platform and explain your choices the way you would in an interview.
Is this question asked at entry level?
It is marked Medium. Entry-level engineers can practise it, but it expects you to reason about requirements and trade-offs, not only list components.
What should I cover first?
Start with the workloads, the availability target and the security and cost limits. Agree on scope with the interviewer before you design anything.
Can I practise it for free?
It is a premium question. Sign up and unlock it once for 10 credits; it then stays unlocked. When you finish, Lala, your personalized AI mentor, can review your design for 30 credits.

Related questions

Updated · Written by the SevyDevy team

Premium questionSign up free, then unlock it