Windows System Administrator → Infrastructure Engineer
A realistic transition from Windows System Administrator to Infrastructure Engineer: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 20%. Difficulty: Medium.
Difficulty: Medium7 stepsDuration: 9 to 13 monthsOverlap: 20%
Transition from Windows System Administrator to Infrastructure Engineer.
Skills to learn
- Networking
- Infrastructure as Code
- Linux
- Cloud (hybrid)
- Disaster recovery
- Automation
Step-by-step learning plan
1. Build on your Windows System Administrator experience
2–4 weeks
Map your current strengths against the Infrastructure Engineer role.
2. Close the partial gaps toward Infrastructure Engineer
3–6 weeks
Improve
- Virtualisation & compute
- Storage & backup
Raise Virtualisation & compute, Storage & backup to the level an Infrastructure Engineer relies on.
3. Learn the core of the Infrastructure Engineer role
6–10 weeks
Learn
- Disaster recovery
- Linux
- Networking
Technologies
ProxmoxLinuxTerraform
Cover the biggest gaps first: Disaster recovery, Linux, Networking.
4. Master advanced Infrastructure Engineer skills
6–10 weeks
Learn
- Infrastructure as Code
- Cloud (hybrid)
- Automation
Technologies
AnsibleNetAppAWS
Handle the advanced topics: Infrastructure as Code, Cloud (hybrid), Automation.
5. Get productive with the Infrastructure Engineer toolchain
4–8 weeks
Technologies
ProxmoxLinuxTerraformAnsibleNetAppAWSKubernetesCisco
Be hands-on with Proxmox, Linux, Terraform 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.