How to become a Site Reliability Engineer (SRE)
Keep systems fast, available and debuggable - with software, not heroics.
Before you start this one
Around 1-3 years in development or operations. SRE is rarely a first job because it assumes you have already run something in production.
Best for
Engineers who enjoy diagnosing failure, automating away toil, and reasoning about systems under stress.
Maybe not for you if
Freshers with no production exposure yet. Start in backend or DevOps, get a year of real incidents, then come back - the role assumes scar tissue.
The 4 phases
What each phase gets you to. The steps, resources and checkpoint inside each one open with a free account.
Phase 1 - Systems depth
7-10 weeksGoal: Diagnose a slow or failing system from first principles rather than by guesswork.
3 steps · ends in a scored checkpoint (70% to clear) · assumes some production exposure, you can read and write code in at least one language
Phase 2 - Observability and SLOs
6-9 weeksGoal: Instrument a service so that its health is a measurement rather than an opinion.
4 steps · ends in a build deliverable
Phase 3 - Incidents and resilience
5-8 weeksGoal: Run an incident calmly and turn it into a lasting fix.
3 steps · ends in a build deliverable
Phase 4 - Automation and scale
6-9 weeksGoal: Run the platform from code, and remove a recurring manual task permanently.
3 steps · ends in a scored checkpoint (65% to clear)
Open the full Site Reliability Engineer (SRE) roadmap
Free account, no card. It takes about a minute and you do not need to verify your email to start.
- All 13 steps, in order, with why each one is there
- 14 hand-picked free resources, no paid course upsells
- The specific mistake people make at each stage
- 2 scored checkpoint tests, so progress is earned not ticked
- Progress saved per step, so a break does not cost you the thread
- Adaptive start, phases your test history already clears are skipped
What hiring actually looks like here
SRE typically expects strong coding plus deep systems knowledge, and is commonly reached after development or operations experience. Hybrid profiles such as SRE with security or platform skills are increasingly valued.
We claim no placement outcome, salary or success rate. This describes what is commonly reported about the role, nothing more. Linked resources are credited to their authors.