01
Failure scenarios
Make this concrete enough that another engineer can understand what you built and why.
CAREER PROJECT · Intermediate · 1 weekend
Reliability Game Day
Inject controlled failures, measure detection/recovery and improve a service runbook.
ReliabilityIncident responseMonitoringRunbooksPostmortems
DEFINITION OF DONE
Leave artifacts a reviewer can inspect.
02
Timeline
Make this concrete enough that another engineer can understand what you built and why.
03
Metrics
Make this concrete enough that another engineer can understand what you built and why.
04
Postmortem
Make this concrete enough that another engineer can understand what you built and why.
05
Updated runbook
Make this concrete enough that another engineer can understand what you built and why.
RESUME / PORTFOLIO FRAMING
Describe what you actually did.
Ran a controlled reliability game day, measured recovery behavior and converted findings into operational improvements.
Use this as a starting structure, then replace it with your real implementation details, metrics and constraints. Do not claim outcomes you did not measure.
STRETCH GOALS
Go deeper if the core is already solid.
Chaos automation
Add only if it strengthens the engineering story instead of delaying a finished, deployable core.
SLO impact
Add only if it strengthens the engineering story instead of delaying a finished, deployable core.
Multi-service scenario
Add only if it strengthens the engineering story instead of delaying a finished, deployable core.