Virtualization Engineer → Infrastructure Engineer
A realistic transition from Virtualization Engineer to Infrastructure Engineer: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 43%. Difficulty: Medium.
Difficulty: Medium7 stepsDuration: 9 to 13 monthsOverlap: 43%
Transition from Virtualization Engineer to Infrastructure Engineer.
Transferable skills
- Storage & backup
- Networking
- Automation
Skills to learn
- Virtualisation & compute
- Infrastructure as Code
- Linux
- Disaster recovery
Step-by-step learning plan
1. Build on your Virtualization Engineer experience
2–4 weeks
Leverage
- Storage & backup
- Networking
- Automation
Map transferable skills — Storage & backup, Networking, Automation — against what an Infrastructure Engineer needs.
2. Close the partial gaps toward Infrastructure Engineer
3–6 weeks
Improve
Raise Cloud (hybrid) to the level an Infrastructure Engineer relies on.
3. Learn the core of the Infrastructure Engineer role
6–10 weeks
Learn
- Virtualisation & compute
- Disaster recovery
Technologies
AWSAzureKubernetes
Cover the biggest gaps first: Virtualisation & compute, Disaster recovery.
4. Master advanced Infrastructure Engineer skills
6–10 weeks
Learn
- Linux
- Infrastructure as Code
Technologies
Cisco
Handle the advanced topics: Linux, Infrastructure as Code.
5. Get productive with the Infrastructure Engineer toolchain
4–8 weeks
Technologies
AWSAzureKubernetesCisco
Be hands-on with AWS, Azure, Kubernetes and the rest of the target stack.
6. Practise Infrastructure Engineer work in real conditions
4–8 weeks
Ship a portfolio project or take on Infrastructure Engineer tasks at work.
7. Get certified and position yourself as a Infrastructure Engineer
4–8 weeks
Technologies
VMware VCP-DCVAZ-104AWS Solutions Architect Associate
Update your CV and LinkedIn around Infrastructure Engineer, then apply to target roles.