Cloud Engineer → Cloud Database Engineer
A realistic transition from Cloud Engineer to Cloud Database Engineer: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 34%. Difficulty: Medium.
Difficulty: Medium7 stepsDuration: 9 to 13 monthsOverlap: 34%
Transition from Cloud Engineer to Cloud Database Engineer.
Transferable skills
- Terraform
- Cost optimisation
Skills to learn
- NoSQL (DynamoDB/Cosmos)
- SQL tuning
- HA & replication
- Backup & DR
- Data modelling
Step-by-step learning plan
1. Build on your Cloud Engineer experience
2–4 weeks
Leverage
- Terraform
- Cost optimisation
Map transferable skills — Terraform, Cost optimisation — against what a Cloud Database Engineer needs.
2. Close the partial gaps toward Cloud Database Engineer
3–6 weeks
Improve
- Cloud databases (RDS/Aurora)
Raise Cloud databases (RDS/Aurora) to the level a Cloud Database Engineer relies on.
3. Learn the core of the Cloud Database Engineer role
6–10 weeks
Learn
- Backup & DR
- SQL tuning
- HA & replication
Technologies
AWS RDSAuroraDynamoDB
Cover the biggest gaps first: Backup & DR, SQL tuning, HA & replication.
4. Master advanced Cloud Database Engineer skills
6–10 weeks
Learn
- NoSQL (DynamoDB/Cosmos)
- Data modelling
Technologies
Azure SQLCosmos DBSpanner
Handle the advanced topics: NoSQL (DynamoDB/Cosmos), Data modelling.
5. Get productive with the Cloud Database Engineer toolchain
4–8 weeks
Technologies
AWS RDSAuroraDynamoDBAzure SQLCosmos DBSpannerPostgreSQLMongoDB
Be hands-on with AWS RDS, Aurora, DynamoDB and the rest of the target stack.
6. Practise Cloud Database Engineer work in real conditions
4–8 weeks
Ship a portfolio project or take on Cloud Database Engineer tasks at work.
7. Get certified and position yourself as a Cloud Database Engineer
4–8 weeks
Technologies
AWS Certified Database – SpecialtyGoogle Professional Cloud Database EngineerAzure DP-300
Update your CV and LinkedIn around Cloud Database Engineer, then apply to target roles.