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