Infrastructure Engineer → DevOps Engineer
A realistic transition from Infrastructure Engineer to DevOps Engineer: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 19%. Difficulty: Medium.
Difficulty: Medium6 stepsDuration: 9 to 13 monthsOverlap: 19%
Transition from Infrastructure Engineer to DevOps Engineer.
Transferable skills
- Linux
- Cloud (AWS/Azure/GCP)
Skills to learn
- CI/CD pipelines
- Docker
- Kubernetes
- Terraform
- Python / Go scripting
- Observability
Step-by-step learning plan
1. Build on your Infrastructure Engineer experience
2–4 weeks
Leverage
- Linux
- Cloud (AWS/Azure/GCP)
Map transferable skills — Linux, Cloud (AWS/Azure/GCP) — against what a DevOps Engineer needs.
2. Learn the core of the DevOps Engineer role
6–10 weeks
Learn
- CI/CD pipelines
- Docker
- Git & branching strategies
- Terraform
Technologies
DockerGitLab CIGitHub Actions
Cover the biggest gaps first: CI/CD pipelines, Docker, Git & branching strategies.
3. Master advanced DevOps Engineer skills
6–10 weeks
Learn
- Kubernetes
- Observability
- Python / Go scripting
- Security in pipelines
Technologies
JenkinsArgoCDHelm
Handle the advanced topics: Kubernetes, Observability, Python / Go scripting.
4. Get productive with the DevOps Engineer toolchain
4–8 weeks
Technologies
DockerGitLab CIGitHub ActionsJenkinsArgoCDHelmGCPPrometheus
Be hands-on with Docker, GitLab CI, GitHub Actions and the rest of the target stack.
5. Practise DevOps Engineer work in real conditions
4–8 weeks
Ship a portfolio project or take on DevOps Engineer tasks at work.
6. Get certified and position yourself as a DevOps Engineer
4–8 weeks
Technologies
CKAHashiCorp Terraform AssociateAWS DevOps Engineer Professional
Update your CV and LinkedIn around DevOps Engineer, then apply to target roles.