Platform Engineer → Site Reliability Engineer
A realistic transition from Platform Engineer to Site Reliability Engineer: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 32%. Difficulty: Medium.
Difficulty: Medium6 stepsDuration: 9 to 13 monthsOverlap: 32%
Transition from Platform Engineer to Site Reliability Engineer.
Transferable skills
- Kubernetes
- Programming (Go/Python)
- Terraform
Skills to learn
- Observability & tracing
- Linux internals
- SLO & error budgets
- Performance engineering
- Distributed systems
- Incident command
Step-by-step learning plan
1. Build on your Platform Engineer experience
2–4 weeks
Leverage
- Kubernetes
- Programming (Go/Python)
- Terraform
Map transferable skills — Kubernetes, Programming (Go/Python), Terraform — against what a Site Reliability Engineer needs.
2. Learn the core of the Site Reliability Engineer role
6–10 weeks
Learn
- Observability & tracing
- SLO & error budgets
- Linux internals
Technologies
LinuxOpenTelemetryLoki
Cover the biggest gaps first: Observability & tracing, SLO & error budgets, Linux internals.
3. Master advanced Site Reliability Engineer skills
6–10 weeks
Learn
- Incident command
- Performance engineering
- Distributed systems
Technologies
TempoKafkaPostgreSQL
Handle the advanced topics: Incident command, Performance engineering, Distributed systems.
4. Get productive with the Site Reliability Engineer toolchain
4–8 weeks
Technologies
LinuxOpenTelemetryLokiTempoKafkaPostgreSQLEnvoyIstio
Be hands-on with Linux, OpenTelemetry, Loki and the rest of the target stack.
5. Practise Site Reliability Engineer work in real conditions
4–8 weeks
Ship a portfolio project or take on Site Reliability Engineer tasks at work.
6. Get certified and position yourself as a Site Reliability Engineer
4–8 weeks
Technologies
CKA / CKADGoogle Professional Cloud DevOps EngineerAWS Solutions Architect
Update your CV and LinkedIn around Site Reliability Engineer, then apply to target roles.