Cloud engineer career path

Account structure, networking, identity and cost belong to the architect. If you built a landing zone or led a migration, you've made those calls at a smaller scale.

Usually when

After 5 to 7 years, once you've designed an environment instead of building from someone else's diagram

Skills to add

• Multi-account and landing zone design
• Well-Architected reviews
• Hybrid connectivity and DR design
• AWS Certified Solutions Architect Professional or Azure Solutions Architect Expert

Have this on your resume first

An environment or migration you designed, with its scale in accounts or workloads and what happened to reliability and cost.

Your reusable modules and account vending are the start of an internal platform. Platform teams turn that into a self-service product and treat developers as the customers.

Usually when

Year 3 or 4, especially if other people already reuse your Terraform modules

Skills to add

• Kubernetes and CKA
• Internal developer portals (Backstage)
• GitOps with Argo CD or Flux
• Golden-path templates and developer experience metrics

Have this on your resume first

Infrastructure you packaged so other teams could use it without asking you, and how many teams did.

Most cloud security is configuration. You've been setting IAM, network exposure, encryption and logging for years, and you know which defaults are unsafe.

Usually when

After 3 to 5 years, often after owning IAM or network design across many accounts

Skills to add

• Policy as code (OPA, AWS SCPs, Azure Policy)
• CSPM and CNAPP tools such as Wiz or Prisma Cloud
• Cloud logging and detection (CloudTrail, GuardDuty, Microsoft Defender for Cloud)
• AWS Certified Security Specialty or CCSP

Have this on your resume first

Guardrails or security controls you rolled out across accounts, with findings reduced or coverage gained.

Site reliability engineering cares less about standing infrastructure up and more about keeping services healthy on it. Knowing failure domains, autoscaling and managed-service quirks is the groundwork.

Usually when

Year 2 to 4, particularly if you already carry the pager for production

Skills to add

• SLOs and error budgets
• Observability (Prometheus, Grafana, OpenTelemetry)
• Incident command and blameless postmortems
• Go or Python for reliability tooling

Have this on your resume first

Incidents you handled and one reliability fix you made, with uptime or latency numbers.

Cloud providers, consultancies and SaaS vendors need architects who've run real workloads. You'll whiteboard more and carry the pager less.

Usually when

After 4 to 6 years, usually engineers who like explaining a design as much as building it

Skills to add

• Customer discovery and requirements elicitation
• Presenting architecture to non-technical buyers
• Proof-of-concept delivery
• Cost estimation and business case writing

Have this on your resume first

Designs you explained to people outside engineering, and migrations or builds with a clear business outcome attached.