Cloud Engineer
Cloud engineers build and maintain the infrastructure that runs apps on AWS, Azure, or Google Cloud. It's invisible work — when it goes well, no one notices; when it breaks, everyone does.
What Tuesday looks like
You wake up to a Slack ping at 7:15 — a deployment from last night is throwing errors in one region. You spend 40 minutes in your pajamas reading CloudWatch logs before figuring out it's a misconfigured IAM role. You fix it, push the change, drink coffee. Standup at 10. Then you go back to the actual project you're supposed to be working on: migrating a service from EC2 to containers. You write Terraform, run a plan, get a confusing error about state files, ask a coworker, fix it. Lunch at your desk while reading a postmortem from another team. Afternoon is a meeting with developers who want to know why their build is slow (it isn't your fault, but you help anyway), then more Terraform. At 4:30 you get paged about high latency. You stay until 6 confirming it's resolved. The work is satisfying when it clicks. The on-call rotation isn't.
Career profile
Career shape
Tap or hover each point to explore a dimension
In the landscape
Tap or hover any dot to identify a career
Salary range
$95K
Entry
$126K
Median
$162K
Senior
$75K floor
$205K ceiling
10-yr growth
+17%
8/10 exposure
Reward profile
3 quick questions to see how this career fits the way you work.
What school costs — and when it pays off
Bachelor's degree · Four years at a public university. Costs here use the cheaper in-state rate.
The chart shows your annual salary over time alongside the annual loan repayment. The shaded band at the bottom is what goes to the loan each year — when it disappears, your full salary is yours.
School cost fully covered by year 8, with strong earnings well beyond that.
Entry-level salary
$95K
25th percentile — what most people start at
Experienced salary
$162K
75th percentile — after ~10 years in the field
School & training cost
$80K
+ $29K interest over 10 yrs
Loan paid off
Year 14
$910/mo for 10 years
First year of work
After loan's paid (yr 14)
Salary range reflects 25th–75th percentile nationally, growing from entry-level to experienced over 10 working years. School costs are national averages — yours will vary. Loan assumes you borrow the full amount at 6.54% interest, repaid over 10 years. Monthly figures are pre-tax.
The first years
Year 1–2: Junior Cloud Engineer or DevOps Associate
You're making $75-95K and spending most of your time learning how things actually work in production, which is nothing like your bootcamp or college labs. You'll get assigned 'small' tickets that take you three days because you don't know the codebase, the deployment pipeline, or why the staging environment is broken (it's been broken for months, apparently). Expect to feel dumb a lot — senior engineers casually reference tools, acronyms, and internal systems you've never heard of. You're not on-call yet, or if you are, someone shadows you.
Year 2–4: Cloud Engineer (the grind years)
Pay jumps to $100-130K and you're now expected to own things. You write Terraform without copy-pasting from Stack Overflow as much, you understand IAM well enough to debug it half-asleep, and you're in the on-call rotation for real. This is when you find out if you can handle being woken up at 3 AM to fix something that turns out to be DNS. You'll probably get one or two AWS or GCP certifications, mostly because your company pays for them. The work is interesting maybe 60% of the time; the rest is meetings, YAML, and explaining to developers why their thing is slow.
Year 4–5: The Fork
You've got real skills now and recruiters are in your DMs weekly. You're making $130-160K and you have to decide what kind of engineer you want to be. The job is changing fast — AI tools now write a lot of the Terraform and config you used to write by hand, and the people getting ahead are either going deeper into specialized areas (security, platform engineering, ML infrastructure) or going wider into architecture and leadership.
Decision point
Specialize or broaden? Going deep into something like cloud security, Kubernetes/platform engineering, or ML infrastructure means higher pay ($170K+) and more job security against AI automation, but you become 'that person' and your options narrow. Going broader toward Staff Engineer or Cloud Architect means more meetings, more design docs, less hands-on building, and managing opinions instead of systems. Some people also jump to a startup here for equity and chaos, or go independent consulting once they have a network. There's no wrong answer, but staying a generalist mid-level cloud engineer forever is the one path that gets squeezed as AI takes over routine infrastructure work.
Year 5–7: Senior Cloud Engineer or Specialist
You're at $150-200K depending on company and location, and you're the person other engineers ask when something is genuinely broken. You spend less time writing code and more time reviewing it, designing systems, and writing documents nobody reads until production breaks. On-call is easier because you've seen most of the failure modes before, but the responsibility is heavier — if you screw up an architecture decision, it costs the company real money. You'll mentor juniors, sit in more meetings than you'd like, and occasionally miss the days when your only job was closing tickets.
The path in
Computer Science · Information Technology · Computer Engineering · Cloud Computing
The standard route — most cloud engineers have a CS or IT degree, then stack AWS/Azure/GCP certifications on top. The degree gets you the first interview; the certs get you the job.
Cloud Computing · Network Administration · Information Technology
A real path if you pair it with serious certifications (AWS Solutions Architect, Azure Administrator). You'll likely start in IT support or junior sysadmin roles and work up — slower than the degree route but far cheaper.
AWS Certified Solutions Architect · Microsoft Azure Administrator · Google Cloud Professional
Cloud is one of the few tech fields where certifications carry real weight without a degree — but you'll need a portfolio of personal projects and likely some IT experience first. Hardest part is getting that first job without a degree filter blocking you.
Cloud Engineering · DevOps · Site Reliability Engineering
Bootcamps can compress the learning curve, but job placement is tougher than it was a few years ago. Best for career-changers with some tech background — straight from high school it's a tough sell to employers.
Known for this field
One of the top CS programs in the country, with deep coursework in distributed systems — the foundation of cloud computing.
Strong CS program with an affordable in-state option and a respected online master's. Heavy focus on systems and networks.
Top-tier CS program with strong recruiting pipelines to AWS, Microsoft, and Google for cloud roles.
Competency-based and affordable (~$4K/term, finish faster to pay less). Built around real AWS and Azure certifications you earn as part of the degree.
One of the few schools offering a dedicated cloud computing track at the undergrad level, available online or in person.
Affordable two-year path with industry certifications built in. Good launchpad to transfer to a state university or jump into IT support roles.
Located in the heart of the AWS/data center corridor — strong local employer connections and AWS Academy partnership.
Not a degree — but the most respected self-paced platform for AWS, Azure, and GCP certification prep. Often used alongside any of the above paths.
Related paths
Cybersecurity Analyst
Cloud and security work overlap heavily since securing cloud environments is a top concern at most companies. Many cloud engineers specialize into cloud security.
DevOps Engineer
Both roles manage infrastructure and deployment pipelines, and their day-to-day work overlaps a lot. Many cloud engineers and DevOps engineers can do each other's jobs.