DevOps Engineer → Cloud Architect
A realistic transition from DevOps Engineer to Cloud Architect: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 31%. Difficulty: Hard.
Difficulty: Hard7 stepsDuration: 16 to 20 monthsOverlap: 31%
Transition from DevOps Engineer to Cloud Architect.
Skills to learn
- Landing zones
- Cost & FinOps
- Migration
- Governance
- Stakeholder mgmt
Step-by-step learning plan
1. Build on your DevOps Engineer experience
2–4 weeks
Leverage
Map transferable skills — Hybrid cloud — against what a Cloud Architect needs.
2. Close the partial gaps toward Cloud Architect
3–6 weeks
Improve
- Cloud architecture
- Security
Raise Cloud architecture, Security to the level a Cloud Architect relies on.
3. Learn the core of the Cloud Architect role
6–10 weeks
Learn
- Landing zones
- Migration
- Cost & FinOps
Technologies
GoIAMS3
Cover the biggest gaps first: Landing zones, Migration, Cost & FinOps.
4. Master advanced Cloud Architect skills
6–10 weeks
Learn
- Governance
- Stakeholder mgmt
Technologies
EKSLambda
Handle the advanced topics: Governance, Stakeholder mgmt.
5. Get productive with the Cloud Architect toolchain
4–8 weeks
Technologies
GoIAMS3EKSLambda
Be hands-on with Go, IAM, S3 and the rest of the target stack.
6. Practise Cloud Architect work in real conditions
4–8 weeks
Ship a portfolio project or take on Cloud Architect tasks at work.
7. Get certified and position yourself as a Cloud Architect
4–8 weeks
Technologies
AWS Solutions Architect ProfessionalAzure AZ-305Google Professional Cloud Architect
Update your CV and LinkedIn around Cloud Architect, then apply to target roles.