Linux System Administrator → Infrastructure Engineer
A realistic transition from Linux System Administrator to Infrastructure Engineer: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 34%. Difficulty: Medium.
Difficulty: Medium6 stepsDuration: 9 to 13 monthsOverlap: 34%
Transition from Linux System Administrator to Infrastructure Engineer.
Transferable skills
- Storage & backup
- Networking
- Linux
Skills to learn
- Virtualisation & compute
- Infrastructure as Code
- Cloud (hybrid)
- Disaster recovery
- Automation
Step-by-step learning plan
1. Build on your Linux System Administrator experience
2–4 weeks
Leverage
- Storage & backup
- Networking
- Linux
Map transferable skills — Storage & backup, Networking, Linux — against what an Infrastructure Engineer needs.
2. Learn the core of the Infrastructure Engineer role
6–10 weeks
Learn
- Virtualisation & compute
- Disaster recovery
- Infrastructure as Code
Technologies
VMwareProxmoxWindows Server
Cover the biggest gaps first: Virtualisation & compute, Disaster recovery, Infrastructure as Code.
3. Master advanced Infrastructure Engineer skills
6–10 weeks
Learn
Technologies
TerraformNetAppVeeam
Handle the advanced topics: Cloud (hybrid), Automation.
4. Get productive with the Infrastructure Engineer toolchain
4–8 weeks
Technologies
VMwareProxmoxWindows ServerTerraformNetAppVeeamAWSAzure
Be hands-on with VMware, Proxmox, Windows Server and the rest of the target stack.
5. Practise Infrastructure Engineer work in real conditions
4–8 weeks
Ship a portfolio project or take on Infrastructure Engineer tasks at work.
6. 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.