Cloud Support Engineer → Cloud Engineer
A realistic transition from Cloud Support Engineer to Cloud Engineer: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 53%. Difficulty: Medium.
Difficulty: Medium7 stepsDuration: 9 to 13 monthsOverlap: 53%
Transition from Cloud Support Engineer to Cloud Engineer.
Transferable skills
- AWS / Azure / GCP
- Cloud networking
- Linux
- Scripting (Python)
Skills to learn
- Terraform
- Identity & access management
- Containers
Step-by-step learning plan
1. Build on your Cloud Support Engineer experience
2–4 weeks
Leverage
- AWS / Azure / GCP
- Cloud networking
- Linux
- Scripting (Python)
Map transferable skills — AWS / Azure / GCP, Cloud networking, Linux — against what a Cloud Engineer needs.
2. Close the partial gaps toward Cloud Engineer
3–6 weeks
Improve
Raise Cost optimisation to the level a Cloud Engineer relies on.
3. Learn the core of the Cloud Engineer role
6–10 weeks
Learn
- Terraform
- Identity & access management
Technologies
CloudFormationAnsibleEKS
Cover the biggest gaps first: Terraform, Identity & access management.
4. Master advanced Cloud Engineer skills
6–10 weeks
Learn
Technologies
LambdaGitLab CIVault
Handle the advanced topics: Containers.
5. Get productive with the Cloud Engineer toolchain
4–8 weeks
Technologies
CloudFormationAnsibleEKSLambdaGitLab CIVaultPrometheus
Be hands-on with CloudFormation, Ansible, EKS and the rest of the target stack.
6. Practise Cloud Engineer work in real conditions
4–8 weeks
Ship a portfolio project or take on Cloud Engineer tasks at work.
7. Get certified and position yourself as a Cloud Engineer
4–8 weeks
Technologies
AWS Solutions Architect AssociateAZ-104Terraform Associate
Update your CV and LinkedIn around Cloud Engineer, then apply to target roles.