Cloud Engineer

You build and run the infrastructure everything else lives on — the AWS, Azure, and GCP estates behind nearly every product you use. It's the natural promotion path out of IT support, the certs genuinely move salaries, and demand has outrun supply for a decade.

Median pay (US)

~$120k / yr

Typical range

$90k–$165k+

Degree required?

No — skills + certs + projects

What the job actually is

Cloud engineers design, build, and operate infrastructure on AWS, Azure, or GCP: networks, compute, storage, identity, and increasingly everything-as-code — Terraform definitions instead of hand-built servers. The role spans a spectrum: closer to sysadmin work on one end (migrations, operations, cost control), closer to DevOps and platform engineering on the other (CI/CD, Kubernetes, developer tooling). Companies of every size need it, because every company became a cloud company and most of their bills prove nobody's watching the meter.

Is it actually you?

You'll probably love it if

You're in IT support or sysadmin work and want the ceiling raised
Building systems that other engineers stand on appeals to you
You like automating yourself out of repetitive work — clicking the console twice means it's time to script it
Studying for certs suits you — this is the rare field where they genuinely pay
Cost, reliability, and security tradeoffs feel like engineering, not overhead

Maybe not, if

You want to build user-facing products — you'll be the stage crew, not the cast
On-call rotations are a dealbreaker (infrastructure carries pagers)
Vendor ecosystems annoy you — this job is deep inside one or two of them
You'd rather not code: modern cloud work is Terraform, Python, and YAML, not console clicks

The real day-to-day (no hype)

It's the best-paying exit from the IT help desk. Support → sysadmin → cloud engineer is the most-walked path, and each step is learnable nights-and-weekends: certs, a home lab, then automating things at your current job until your title catches up to your work.
Certs open doors here like almost nowhere else in tech. AWS Solutions Architect Associate or the Azure equivalent gets recruiters calling; the professional-level and specialty certs move real salary. But a cert without hands-on proof stalls in interviews — pair every cert with something you actually built and can explain.
Infrastructure-as-code is the actual job now. Terraform, CloudFormation, or Bicep plus a scripting language is the modern baseline. Engineers who can only navigate the console are the previous era; the ones who treat infrastructure like a codebase — versioned, reviewed, tested — are the hires.
Cost engineering is the quiet superpower. Cloud bills are many companies' second-biggest expense and most of it is waste. An engineer who can cut 30% off a seven-figure AWS bill pays their own salary several times over — and has one of the easiest-to-tell interview stories in tech.

How people break in — or switch in

Pick one cloud (AWS has the most jobs; Azure dominates enterprises that run Microsoft) and get the associate-level architect cert. Build in public while you study: a home-lab project deployed with Terraform, documented on GitHub, beats the cert alone. If you're in IT already, volunteer for anything touching the cloud estate — migrations, backups, identity — and let your résumé say what you did, not what your title was. Entry titles to hunt: cloud support, junior cloud engineer, cloud operations.

IT operations experience is the head start, not the baggage — you already understand networks, identity, and what breaks at 2am. The upgrade is expressing all of it as code.

Your application, already half-written

Here's a question every Cloud Engineer application asks, answered the way pirch would — in a real voice, grounded in real experience:

“Tell us about an infrastructure improvement you drove end to end.”

At my last company, every new environment was built by hand from a wiki page — it took two days, and no two environments matched, which meant 'works in staging' proved nothing. I proposed moving to Terraform, and rather than asking for a big migration project, I started with the piece that hurt most: the QA environments. I modularized the network, compute, and IAM setup, put it through code review like any other repo, and got environment spin-up down to twenty minutes with drift detection catching manual changes. Then the pattern spread — production followed within two quarters because the QA modules had proven themselves. The part I'm proudest of isn't the tooling; it's that our postmortems stopped containing the phrase 'configuration difference,' and new engineers could read the infrastructure like documentation, because it was.

pirch's co-pilot writes answers like this for your background and the exact job — try it free →

pirch finds the cloud roles that are actually you

Tell pirch who you are — your platform, your certs, ops-leaning or platform-leaning — and it hunts down real, verified-open cloud engineering jobs that fit the whole you, with a tailored cover letter already written.

start your free hunt

first hunt free · we never auto-apply · you stay in control

Common questions

How much do cloud engineers make?

US median around $120k, typically $90k–$165k+. Platform and DevOps-flavored roles at product companies pay toward the top; cloud-operations roles at traditional enterprises start lower but promote steadily.

Which cloud certification should I get first?

AWS Certified Solutions Architect – Associate is the highest-liquidity single cert in the job market. If your target employers are Microsoft shops, the Azure Administrator (AZ-104) is the equivalent door-opener. One cert plus a demonstrable project beats three certs and no proof.

Can I become a cloud engineer without a degree?

Yes — this is one of tech's most cert-and-skills-driven specialties, full of people who came up through help desks and server rooms. Employers hire on certification, hands-on projects, and operational judgment; a degree helps at some large enterprises but is rarely the gate.

Is cloud engineering still in demand with AI automating things?

Yes — AI workloads run on cloud infrastructure and have made the estates bigger and costlier, not smaller. The routine console work is automating away, but that's been the direction for years: the demand is for engineers who codify, secure, and cost-optimize infrastructure, and it's growing.