Infrastructure Engineer → Infrastructure Architect
A realistic transition from Infrastructure Engineer to Infrastructure Architect: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 45%. Difficulty: Hard.
Difficulty: Hard7 stepsDuration: 16 to 20 monthsOverlap: 45%
Transition from Infrastructure Engineer to Infrastructure Architect.
Transferable skills
- Networking
- Storage & compute
Skills to learn
- DR & HA
- Vendor strategy
- Cost modelling
- Security
Step-by-step learning plan
1. Build on your Infrastructure Engineer experience
2–4 weeks
Leverage
- Networking
- Storage & compute
Map transferable skills — Networking, Storage & compute — against what an Infrastructure Architect needs.
2. Close the partial gaps toward Infrastructure Architect
3–6 weeks
Improve
- Infrastructure architecture
- Hybrid cloud
Raise Infrastructure architecture, Hybrid cloud to the level an Infrastructure Architect relies on.
3. Learn the core of the Infrastructure Architect role
6–10 weeks
Learn
Technologies
PrometheusF5NSX
Cover the biggest gaps first: DR & HA, Vendor strategy.
4. Master advanced Infrastructure Architect skills
6–10 weeks
Learn
Technologies
TOGAF
Handle the advanced topics: Cost modelling, Security.
5. Get productive with the Infrastructure Architect toolchain
4–8 weeks
Technologies
PrometheusF5NSXTOGAF
Be hands-on with Prometheus, F5, NSX and the rest of the target stack.
6. Practise Infrastructure Architect work in real conditions
4–8 weeks
Ship a portfolio project or take on Infrastructure Architect tasks at work.
7. 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.