Infrastructure Automation Engineer → Infrastructure Architect
A realistic transition from Infrastructure Automation Engineer to Infrastructure Architect: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 23%. Difficulty: Hard.
Difficulty: Hard6 stepsDuration: 16 to 20 monthsOverlap: 23%
Transition from Infrastructure Automation Engineer to Infrastructure Architect.
Skills to learn
- Infrastructure architecture
- Storage & compute
- DR & HA
- Vendor strategy
- Cost modelling
- Security
Step-by-step learning plan
1. Build on your Infrastructure Automation Engineer experience
2–4 weeks
Leverage
Map transferable skills — Hybrid cloud, Networking — against what an Infrastructure Architect needs.
2. Learn the core of the Infrastructure Architect role
6–10 weeks
Learn
- Infrastructure architecture
- DR & HA
- Storage & compute
Technologies
VMwareWindows ServerNetApp
Cover the biggest gaps first: Infrastructure architecture, DR & HA, Storage & compute.
3. Master advanced Infrastructure Architect skills
6–10 weeks
Learn
- Vendor strategy
- Cost modelling
- Security
Technologies
CiscoF5NSX
Handle the advanced topics: Vendor strategy, Cost modelling, Security.
4. Get productive with the Infrastructure Architect toolchain
4–8 weeks
Technologies
VMwareWindows ServerNetAppCiscoF5NSXTOGAF
Be hands-on with VMware, Windows Server, NetApp and the rest of the target stack.
5. Practise Infrastructure Architect work in real conditions
4–8 weeks
Ship a portfolio project or take on Infrastructure Architect tasks at work.
6. Get certified and position yourself as a Infrastructure Architect
4–8 weeks
Technologies
TOGAFAWS Solutions Architect ProfessionalVMware VCAP-DCV
Update your CV and LinkedIn around Infrastructure Architect, then apply to target roles.