Database Administrator → Site Reliability Engineer
A realistic transition from Database Administrator to Site Reliability Engineer: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 19%. Difficulty: Hard.
Difficulty: Hard7 stepsDuration: 16 to 20 monthsOverlap: 19%
Transition from Database Administrator to Site Reliability Engineer.
Skills to learn
- Observability & tracing
- Kubernetes
- Programming (Go/Python)
- SLO & error budgets
- Terraform
- Distributed systems
Step-by-step learning plan
1. Build on your Database Administrator experience
2–4 weeks
Leverage
Map transferable skills — Performance engineering — against what a Site Reliability Engineer needs.
2. Close the partial gaps toward Site Reliability Engineer
3–6 weeks
Improve
Raise Linux internals to the level a Site Reliability Engineer relies on.
3. Learn the core of the Site Reliability Engineer role
6–10 weeks
Learn
- Observability & tracing
- SLO & error budgets
- Kubernetes
- Incident command
Technologies
KubernetesGoOpenTelemetry
Cover the biggest gaps first: Observability & tracing, SLO & error budgets, Kubernetes.
4. Master advanced Site Reliability Engineer skills
6–10 weeks
Learn
- Programming (Go/Python)
- Distributed systems
- Terraform
Technologies
LokiTempoTerraform
Handle the advanced topics: Programming (Go/Python), Distributed systems, Terraform.
5. Get productive with the Site Reliability Engineer toolchain
4–8 weeks
Technologies
KubernetesGoOpenTelemetryLokiTempoTerraformArgoCDAWS
Be hands-on with Kubernetes, Go, OpenTelemetry and the rest of the target stack.
6. Practise Site Reliability Engineer work in real conditions
4–8 weeks
Ship a portfolio project or take on Site Reliability Engineer tasks at work.
7. 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.