Data Engineer Skills and Job Description (September 2026)
SQL is asked for by 66% of Data Engineer employers, the most common requirement across 300 live postings read in September 2026. Then Python, AWS, Azure.
Median posted pay is $147,250, most postings between $113,086 and $180,000 — from 204 postings that disclosed it, across 99 companies.
Posted pay is up 8.3% since 2026-09-08 ($136,000 → $147,250).
These are ranges employers published in their own job postings — not salaries people typed into a form years ago.
What Data Engineer postings actually ask for
Ranked by how many of the 300 posting descriptions mention them.
SQL66%
Python59%
AWS36%
Azure31%
Data Pipelines31%
Data Modeling30%
Snowflake27%
Spark24%
Git24%
Databricks23%
ETL22%
Data Quality20%
Java20%
DBT19%
Airflow19%
Agile18%
CI/CD18%
Oracle17%
PostgreSQL16%
Terraform16%
GCP14%
Data Science14%
Data Governance14%
Information Systems13%
Kubernetes13%
Would your background clear the bar?
These are the requirements Data 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 Data Engineer postings open right now.
Median of remote-eligible postings against the rest.
Remote-eligible
$151,000
Onsite
$147,250
61 remote-eligible postings against 145 onsite. Remote pays 2.5% more in this sample.
Pay by experience level
Level is taken from the posting title, so only postings that state one are counted.
Mid
$105,95016
Senior
$154,98070
Lead / Manager
$188,02514
Principal / Staff
$200,00013
Pay by location
Metros with at least three salaried postings.
New York, NY
$177,50015
US
$161,20011
Austin, TX
$184,95011
Remote, US
$145,00010
Chicago, IL
$120,7506
Seattle, WA
$155,4506
McLean, VA
$202,2505
Ashburn, VA
$157,5005
Dallas, TX
$160,0005
Richmond, VA
$156,0005
Cupertino, CA
$178,3005
San Francisco, CA
$206,8754
Where this data comes from
300 live postings analysed
204 (68%) published a salary range
82 (27%) were remote-eligible
148 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.