Automation Engineer → Infrastructure Automation Engineer
A realistic transition from Automation Engineer to Infrastructure Automation Engineer: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 62%. Difficulty: Easy.
Difficulty: Easy6 stepsDuration: 4 to 8 monthsOverlap: 62%
Transition from Automation Engineer to Infrastructure Automation Engineer.
Transferable skills
- Terraform
- Ansible
- Linux
- Python / Bash
- CI/CD
Skills to learn
- Cloud provisioning
- Networking
- GitOps basics
Step-by-step learning plan
1. Build on your Automation Engineer experience
2–4 weeks
Leverage
- Terraform
- Ansible
- Linux
- Python / Bash
Map transferable skills — Terraform, Ansible, Linux — against what an Infrastructure Automation Engineer needs.
2. Learn the core of the Infrastructure Automation Engineer role
6–10 weeks
Learn
- Cloud provisioning
- GitOps basics
Technologies
PulumiGitHub ActionsGCP
Cover the biggest gaps first: Cloud provisioning, GitOps basics.
3. Master advanced Infrastructure Automation Engineer skills
6–10 weeks
Learn
Technologies
PackerCloudFormation
Handle the advanced topics: Networking.
4. Get productive with the Infrastructure Automation Engineer toolchain
4–8 weeks
Technologies
PulumiGitHub ActionsGCPPackerCloudFormation
Be hands-on with Pulumi, GitHub Actions, GCP 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.