Infrastructure Engineer → Infrastructure Automation Engineer
A realistic transition from Infrastructure Engineer to Infrastructure Automation Engineer: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 33%. Difficulty: Medium.
Difficulty: Medium6 stepsDuration: 9 to 13 monthsOverlap: 33%
Transition from Infrastructure Engineer to Infrastructure Automation Engineer.
Transferable skills
- Linux
- Cloud provisioning
- Networking
Skills to learn
- Terraform
- Ansible
- Python / Bash
- CI/CD
- GitOps basics
Step-by-step learning plan
1. Build on your Infrastructure Engineer experience
2–4 weeks
Leverage
- Linux
- Cloud provisioning
- Networking
Map transferable skills — Linux, Cloud provisioning, Networking — against what an Infrastructure Automation Engineer needs.
2. Learn the core of the Infrastructure Automation Engineer role
6–10 weeks
Learn
- Terraform
- Ansible
- Python / Bash
Technologies
PulumiBashGitLab CI
Cover the biggest gaps first: Terraform, Ansible, Python / Bash.
3. Master advanced Infrastructure Automation Engineer skills
6–10 weeks
Learn
Technologies
GitHub ActionsGCPDocker
Handle the advanced topics: CI/CD, GitOps basics.
4. Get productive with the Infrastructure Automation Engineer toolchain
4–8 weeks
Technologies
PulumiBashGitLab CIGitHub ActionsGCPDockerVaultPrometheus
Be hands-on with Pulumi, Bash, GitLab CI and the rest of the target stack.
5. Practise Infrastructure Automation Engineer work in real conditions
4–8 weeks
Ship a portfolio project or take on Infrastructure Automation Engineer tasks at work.
6. Get certified and position yourself as a Infrastructure Automation Engineer
4–8 weeks
Technologies
Terraform AssociateRed Hat Certified EngineerAWS SysOps Administrator
Update your CV and LinkedIn around Infrastructure Automation Engineer, then apply to target roles.