Cloud Engineer Skills and Job Description (September 2026)
Python is asked for by 37% of Cloud Engineer employers, the most common requirement across 300 live postings read in September 2026. Then AWS, Azure, Software Engineering.
Median posted pay is $166,364, most postings between $133,500 and $192,000 — from 208 postings that disclosed it, across 71 companies.
Posted pay is up 8.4% since 2026-09-07 ($153,500 → $166,364).
These are ranges employers published in their own job postings — not salaries people typed into a form years ago.
What Cloud Engineer postings actually ask for
Ranked by how many of the 300 posting descriptions mention them.
Python37%
AWS22%
Azure21%
Software Engineering20%
Kubernetes17%
Terraform17%
Electrical Engineering15%
SQL15%
Configuration Management15%
Git15%
Security Clearance13%
U.S. Citizenship12%
Cloud Platforms12%
JavaScript11%
CI/CD11%
Agile10%
Project Management10%
Java10%
Systems Engineering10%
LLM9%
Information Systems8%
TypeScript8%
PowerShell8%
Distributed Systems8%
GCP8%
Would your background clear the bar?
These are the requirements Cloud Engineer postings list. Paste one of those postings and your résumé — FitToHire checks you against every requirement and shows the evidence behind each verdict.
15 companies in this sample have Cloud Engineer postings open right now.
Median of remote-eligible postings against the rest.
Remote-eligible
$136,000
Onsite
$168,500
73 remote-eligible postings against 135 onsite. Onsite pays 19.3% more in this sample.
Pay by experience level
Level is taken from the posting title, so only postings that state one are counted.
Senior
$158,717158
Principal / Staff
$206,00023
Pay by location
Metros with at least three salaried postings.
Remote, US
$150,00010
San Diego, CA
$205,00010
Austin, TX
$184,9507
New York, NY
$177,5006
Wright-Patterson AFB, OH
$166,3646
Boulder, CO
$161,2076
San Francisco, CA
$234,0005
Cupertino, CA
$214,0005
Santa Clara, CA
$223,0004
Los Angeles, CA
$192,7744
Calabasas, CA
$138,0004
US
$183,0504
Where this data comes from
300 live postings analysed
208 (69%) published a salary range
103 (34%) were remote-eligible
117 distinct employers
Requirements read from 300 full posting descriptions
Each employer gets one vote in the median, so a company running a large hiring campaign cannot move it
Ranges are converted to annual figures; hourly and contract postings are normalised before comparison
How the requirements were read
Requirements are not keyword counts. Each posting is read by our extraction engine, which works out what the employer is actually asking for and separates a requirement from a section heading or a line of boilerplate. Two postings asking for the same thing in different words are counted once, because our skills graph knows which phrasings mean the same thing and which imply others.
The share beside each requirement is the percentage of distinct EMPLOYERS in that sample who asked for it, counted one vote per company so a firm posting the same role many times cannot inflate its own requirements. Measured, not estimated, and read from the posting text rather than counted as keywords.
Because every reading is dated, the movement figures above are real month-over-month change. Sites built on self-reported salaries cannot produce that number: their data has no posting date.