Cloud engineer career path
Cloud engineering overlaps so much with DevOps and SRE that hiring managers read your platform and scale before your title. From here most people go one of three ways. Architecture means cloud architect, then principal or enterprise. Platform engineering means building internal tools other engineers use. Or you specialize in cloud security or cost. Infrastructure management exists, but most senior cloud engineers who stay hands-on end up with architect in their title.
Updated Pay and job counts from live US job listings
What comes after cloud engineer?
A common next step for a cloud engineer is cloud architect, usually after 5 to 7 years. Other routes are a sideways move to platform engineer, cloud security engineer, or site reliability engineer and a career change to solutions architect.
Cloud engineer jobs in the US
- Advertised pay
- $122K-$147K
- Open jobs
- 6,436
- Median
- $126K
Jobs are counted by title on US job boards. Pay is the middle half of the 8 listings that state a salary.
Where cloud engineers go next
5 moves people make from this role. The job counts and pay are for each destination role, so you can see what the market wants right now.
| Move to | Type | Usually when | Open US jobs | Advertised pay |
|---|---|---|---|---|
| Cloud architect | Step up | After 5 to 7 years | 2,951 | $41K-$163K |
| Platform engineer | Sideways move | Year 3 or 4 | 11,713 | $123K-$145K |
| Cloud security engineer | Sideways move | After 3 to 5 years | 1,140 | $119K-$148K |
| Site reliability engineer | Sideways move | Year 2 to 4 | 2,648 | $120K-$161K |
| Solutions architectIts career path: solutions architect | Career change | After 4 to 6 years | 9,656 | $108K-$156K |
Job counts and pay from US listings, September 29, 2026. Pay shows only where at least five listings state it.
What each move takes
Why each move fits, the skills hiring managers look for, and the proof to have on your resume before you apply.
Cloud architect
Step up2,951 open US jobs$41K-$163K advertised
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.
Platform engineer
Sideways move11,713 open US jobs$123K-$145K advertised
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.
Cloud security engineer
Sideways move1,140 open US jobs$119K-$148K advertised
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 engineer
Sideways move2,648 open US jobs$120K-$161K advertised
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.
Solutions architect
Career change9,656 open US jobs$108K-$156K advertised
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.
Now check your own resume
Your own resume will give you a sharper answer than this page. Your years, tools and wins change which move fits.
The suggested roles and fit scores come from AI. The job counts and pay come from live listings.
Questions cloud engineers ask
Can a system administrator become a cloud engineer?
Yes, it's one of the most common routes in. Linux, networking and troubleshooting carry over directly. Pick one cloud, earn its associate-level certification, learn Terraform, and rebuild something you run today as code.
What comes after cloud engineer?
Senior cloud engineer, then cloud architect, is the most common path. Others move into platform engineering, SRE or cloud security. A smaller group goes into solutions architecture or infrastructure management.
Is FinOps a real career path for cloud engineers?
Yes, at companies with large cloud bills, where FinOps engineers and analysts sit between engineering and finance. The FinOps Certified Practitioner cert is the usual starting point. Cost cuts you can put numbers on are what get you hired.