AI Research Engineer Skills and Job Description (October 2026)
Python is asked for by 45% of AI Research Engineer employers, the most common requirement across 300 live postings read in October 2026. Then Software Engineering, LLM, Machine Learning.
Median posted pay is $175,000, most postings between $129,000 and $215,000 — from 236 postings that disclosed it, across 84 companies.
Posted pay is up 3.4% since 2026-09-27 ($169,233 → $175,000).
These are ranges employers published in their own job postings — not salaries people typed into a form years ago.
What AI Research Engineer postings actually ask for
Ranked by how many of the 300 posting descriptions mention them.
Python45%
Software Engineering24%
LLM20%
Machine Learning18%
AWS16%
PyTorch15%
Version Control15%
Electrical Engineering14%
Java14%
Azure14%
Data Science14%
SQL13%
Docker11%
CI/CD11%
Kubernetes11%
Distributed Systems10%
Cloud Platforms10%
AI Tools10%
Go9%
Data Models9%
Data Pipelines9%
Artificial Intelligence9%
Data Analysis8%
Infrastructure As Code8%
Would your background clear the bar?
These are the requirements AI Research 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 AI Research Engineer postings open right now.
Median of remote-eligible postings against the rest.
Remote-eligible
$159,803
Onsite
$213,600
56 remote-eligible postings against 181 onsite. Onsite pays 25.2% more in this sample.
Pay by experience level
Level is taken from the posting title, so only postings that state one are counted.
Senior
$241,80084
Lead / Manager
$216,30043
Principal / Staff
$225,00022
Pay by location
Metros with at least three salaried postings.
New York, NY
$220,24920
San Francisco, CA
$225,00019
Remote, US
$150,00013
Menlo Park, CA
$220,4989
US
$155,0007
San Diego, CA
$232,5007
Santa Clara, CA
$235,7507
Atlanta, GA
$162,5056
Mountain View, CA
$195,7506
Cupertino, CA
$214,0006
Los Angeles, CA
$160,5005
Seattle, WA
$186,3754
Where this data comes from
300 live postings analysed
236 (79%) published a salary range
71 (24%) were remote-eligible
123 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.