Cloud engineering is one of the best-paid and most portable technical careers in the United States, and it is also one of the hardest to research honestly, because the job did not exist as a category long enough to be counted properly. Everything you read about what it pays is an aggregate of self-reported numbers. This guide starts by working out which occupations the work is actually counted under, which turns out to answer more than a salary question — including where the people doing these jobs came from, and where the next wave will come from.
Which Occupation Is This, Actually?
The Bureau of Labor Statistics has no "cloud engineer" occupation. That is not an oversight to work around; it is genuinely useful information, because it means the work is being counted somewhere else, and which somewhere tells you what a given role really is.
Three occupations absorb almost all of it:
- Network and computer systems administrators — a $99,130 median as of May 2025, the lowest tenth under $62,640 and the highest tenth above $155,050. Running the estate.
- Computer network architects — a $134,050 median, the lowest tenth under $79,900 and the highest tenth above $202,680. Designing it. BLS notes this typically needs a bachelor's degree and five years or more in a related occupation.
- Software developers — a $135,980 median, the highest tenth above $214,670. Building platform tooling as software.
So the practical question at offer stage is not "what do cloud engineers earn". It is which of those three the role actually is. A job that provisions and maintains environments pays like administration. A job that designs them pays like architecture. A job that builds internal platform software pays like development. The word "cloud" in the title moves the number far less than which of those three verbs the work is.
Read the requirements with that in mind and the pay band usually predicts itself.
The Declining Occupation That Feeds This One
Here is the number nobody puts in a cloud careers article. BLS projects employment of network and computer systems administrators to decline 4 per cent from 2025 to 2035, with about 13,400 openings a year — almost all of them replacements rather than growth.
Read carelessly, that looks like bad news adjacent to a good career. Read properly, it is the single most useful fact on this page, and it says two things.
First, the work is not disappearing — it is being re-titled. Servers still need provisioning, patching, monitoring and recovering. What changed is that the server is now an API call, the configuration is now code, and the job title on the advertisement is now "cloud engineer". The decline in one occupation and the growth of these postings are largely the same phenomenon seen from two sides.
Second, if you are administering systems today, that projection is addressed to you. A declining occupation with 13,400 mostly-replacement openings a year is not somewhere to spend a decade. And the migration is unusually achievable, because you already have the thing that is genuinely hard to acquire: operational experience of systems under load. What you are missing — Terraform, a cloud platform, pipelines — is learnable, and demonstrably so.
By contrast, computer network architects are projected to grow 8 per cent on 9,600 openings a year. The direction of travel inside this field is from running things towards designing them, and the pay gap between those two BLS medians — $34,920 — is what that journey is worth.
Why "Learning Terraform" Is Not the Entry Requirement
Postings for junior cloud engineers do exist, and the draft this page was built from is right that some welcome people still learning infrastructure as code. But the framing is backwards. Terraform is the easy part. It is well documented, free to practise, and a determined person can be productive in it inside a month.
What cannot be learned from documentation is the judgement that comes from having run something in production: what fails first under load, why the obvious fix makes the outage worse, how a change looks at three in the morning. That is why cloud engineering is usually a second job rather than a first, reached from systems administration, networking, support or development.
If you are starting out, the honest route is to take a role that gives you operational responsibility for something real, and do the cloud learning alongside it. If you are already in one, you are much closer than the job descriptions make you feel.
Cost Is the Skill That Gets You Promoted
Every listing puts cost optimisation near the bottom of the requirements. In practice it is the fastest route to seniority in this field, for a reason that has nothing to do with engineering: it is the only part of the job with a dollar figure attached.
An engineer who improves reliability has to explain the value of an outage that did not happen. An engineer who takes 30 per cent off a monthly cloud bill has a number their manager can take to a finance meeting. Both matter; only one is legible outside the team.
Practically, that means learning where the money actually goes — idle compute, over-provisioned instances, storage tiers nobody reviewed, egress, forgotten environments — and being able to talk about commitments and rightsizing with the people who sign the invoice. It is unglamorous and it is the difference between "runs our infrastructure" and "runs our infrastructure and saved us $400,000 last year" on a promotion case.
What Certifications Do and Do Not Do
Cloud certifications are more useful in this field than in most, because the platforms change fast enough that a current certificate genuinely signals current knowledge. Two honest limits.
They get your application read; they do not substitute for having run anything. An associate-level AWS or Azure certification alongside a real project you can describe in detail beats a professional-level certificate with nothing behind it, because the interview will go straight to what you actually did.
And pick the platform your target employers run, not the one with the best course. If the postings you want say Azure, an AWS certification is evidence of general aptitude rather than a match. If you are heading towards Kubernetes security specifically, note the ordering trap covered in our cybersecurity engineer guide: the security exam requires the administrator one first.
GovCloud, Clearance and the Federal Market
A meaningful share of US cloud postings — particularly around Washington DC and Northern Virginia — are federal or defence work, and ask for AWS GovCloud experience alongside an active security clearance. A clearance requires US citizenship and an employer to sponsor it, and cannot be obtained independently.
If you are not a US citizen, read for that line before investing time in the application; the commercial market is large, better paid at the top end, and considerably more remote-friendly. Our cybersecurity analyst guide covers the clearance rules in full.
The Roles You Will Actually Meet
- Cloud Engineer. The general title: provisioning, automation and maintenance of cloud environments.
- Cloud Infrastructure or Systems Engineer. Compute, storage and networking design. Closest to the architect band.
- Cloud DevOps Engineer. Infrastructure plus the delivery pipeline. Expect to own both.
- Site Reliability Engineer. Uptime, scaling and incident response, usually with a software engineering bar and pay to match.
- Cloud Security Engineer. Identity, guardrails and compliance — the strongest premium of the specialisms and covered in our security engineering guide.
- Platform Engineer. Building the internal tooling other engineers deploy through. The most software-like of these, and paid accordingly.
Skills That Keep Recurring in Listings
- Infrastructure as code — Terraform above CloudFormation in most postings, and treated as code that gets reviewed.
- One cloud platform in depth, AWS or Azure, rather than three at surface level.
- Containers and Kubernetes, including what they cost to run.
- CI/CD — GitHub Actions, GitLab CI or Jenkins — and the discipline to keep pipelines boring.
- Identity and access management, the most common root cause in cloud incidents and the least advertised skill.
- Python for automation, and enough software practice to write code others maintain.
- Cost management and capacity planning — last on their list, first on your promotion case.
Frequently Asked Questions
How much do cloud engineers make in the USA?
There is no federal figure for the title. The work is counted under network and computer systems administrators at a $99,130 median, computer network architects at $134,050 and software developers at $135,980. Which the role resembles matters more than the word "cloud" in it.
Is cloud engineering a good career given sysadmin roles are declining?
The decline is the reason to move, not a reason to worry. BLS projects network and computer systems administrators to fall 4 per cent from 2025 to 2035 while network architects grow 8 per cent. The work is being re-titled rather than removed, and operational experience is the hard part you already have.
Can I become a cloud engineer with no experience?
Rarely straight away. Terraform and the platforms are learnable in months; judgement about systems under load is not. This is usually a second job, reached from support, systems administration, networking or development.
Which cloud certification should I take?
An associate-level certification on the platform your target employers actually run, backed by a project you can describe in detail. A current certificate signals current knowledge in a fast-moving field, but it does not substitute for having run something.
AWS or Azure?
Whichever appears in the postings you want. AWS dominates overall US listings; Azure is stronger in enterprises already committed to Microsoft, and in a great deal of government-adjacent work.
What actually gets a cloud engineer promoted?
Cost. It is the only part of the job with a dollar figure attached, so it is the part a manager can take to a finance meeting. Reliability matters as much and argues for itself far less.
Do cloud engineer jobs require a security clearance?
Federal and GovCloud roles usually do, which means US citizenship and an employer sponsor. The commercial market does not, and is larger and more remote-friendly.
Are these roles remote?
A large share are, particularly at mid and senior level with commercial employers. Expect an on-call rotation on most platform teams regardless of where you sit.
People Also Search For
AWS cloud engineer jobs USA
The largest share of US cloud postings, and the deepest applicant pool with it. Covered in full in our AWS cloud engineer guide, including the difference between GovCloud eligibility and a security clearance.
Azure cloud engineer jobs
Strong in Microsoft-committed enterprises and government-adjacent work. Our Azure cloud engineer guide covers the certification order Microsoft enforces and the Microsoft 365 work bundled into many of those postings.
Remote cloud engineer jobs
Common at commercial employers and rare in cleared work. Ask about the on-call rotation before the offer stage.
Entry level cloud engineer jobs
Scarce as a first job. The realistic entry is a role with operational responsibility, learning the cloud stack alongside it.
Cloud engineer salary USA
Depends which of three occupations the role belongs to: $99,130, $134,050 or $135,980 at the median. Read the requirements to find out which.
Terraform jobs USA
The most requested infrastructure-as-code tool in these listings, and the easiest part of the job to learn.
FinOps and cloud cost optimisation jobs
A growing specialism, and the most legible value a cloud engineer can produce.
GovCloud cloud engineer jobs
Federal work requiring US citizenship and a sponsored clearance. Check for that line before applying.
More Job Guides
Comparing the infrastructure routes? These cover them:
- AWS Cloud Engineer Jobs in USA — the largest platform market, and why GovCloud and a clearance are two different bars.
- Azure Cloud Engineer Jobs in USA — the enterprise platform, its gated exam path, and the M365 work hidden in the job title.
- Cybersecurity Engineer Jobs in USA — the security specialisation of this work, and the Kubernetes certification ordering trap.
- Cybersecurity Analyst Jobs in USA — the clearance rules in full, and the shorter door into security.
- Software Developer Jobs in USA — the best-paid of the three occupations this work is counted under.
- Python Developer Jobs in USA — the automation language that carries most of this job.
- Mobile App Developer Jobs in USA — the application side, and the store gate in front of a portfolio.
- Full Stack Developer Jobs in USA — which of two very different pay bands that title is hiding.
- Network Engineer Jobs in USA — the occupation the operations work moved out of, and the $34,920 between running a network and designing one.
- DevOps Engineer Jobs in USA — the delivery half of platform work, and the four measures senior interviews run on.
- Data Scientist Jobs in USA — the workloads these platforms increasingly exist to run.
- DevOps Engineer Jobs in Germany — cloud and pipeline work in Europe, with official German pay figures.
- Database Administrator Jobs in USA — where database work sits as it moves into the cloud.
- How to Apply for Telkom Indonesia IT Jobs — and the national ID requirement that closes the door first.
- How to Apply for Google Data Center Jobs in the USA — technician work Google prices openly, with no sponsorship on any US posting.
This article is for general informational purposes and is not legal, immigration or careers advice. Wage data, employment projections, certification requirements and clearance policy change, and posting counts on any job board are a moving figure rather than a statistic. Confirm the current position with the Bureau of Labor Statistics, your target cloud provider and the employer's own advertisement before applying or paying for any course.
