The AI Salary Premium That Dissolved
Correction, 2026-08-29. This post originally reported a 9% AI salary premium, $168,000 against $154,000. That was correct for the dataset as it stood on 12 June 2026. On 16 July 2026 every US salary here was re-anchored to its federal occupation wage curve, and the premium did not survive: the same two role sets now compute $133,000 and $156,000. The post has been rewritten around why the comparison is not measurable at title level, rather than around either number.
Data
A dataset or measurement series published as the primary artifact, with its definitions and its limits.
We published a number. Then we made the data honest and the number went away.
On June 12, 2026 this post opened with two figures. The 687 AI-classified roles in our dataset carried a $168,000 median base. The other 2,758 carried $154,000. A $14,000 gap. A 9% premium.
Those numbers were correct. Run our method against the dataset as it stood that day and you get $168,000 and $154,000 to the dollar.
They are also gone.
On July 16 we re-anchored every US base salary in the dataset to its own federal occupation wage curve, placed by seniority tier, reproducible from the Bureau of Labor Statistics OEWS file. That was an improvement. Before it, a role's number came from our model of what the role pays. After it, the number traces to a federal wage survey.
The premium did not survive the improvement. Today the same 687 AI roles carry a $133,000 median and the same 2,758 non-AI roles carry $156,000.
The honest reading is not that AI roles started paying less. It is that our old numbers were measuring our own assumptions about AI titles, and the moment they stopped, the signal went with them.
Why the premium was never measurable at title level.
Here is the structural fact that explains it, and it is the thing worth taking away from this post.
Our 687 AI-classified roles map to 59 federal occupation codes. Fifty three of those 59 are also used by roles we do not classify as AI. 679 of the 687 AI roles, 99% of them, share an occupation code with a non-AI role.
So once every salary is anchored to an occupation code, comparing AI titles to non-AI titles compares two overlapping samples drawn from mostly the same wage curves. Whatever gap you compute is telling you which occupation codes each group happens to draw from, and in what seniority mix. It is not telling you what AI pays.
The compression is visible in the numbers. Our 687 AI titles are served by 79 distinct medians. All 3,445 roles are served by 202. Rank the 13 AI hubs by median pay today and you get 6 distinct values across 13 rows. Rank the top AI titles and four different vice president titles tie at exactly $303,000.
A ranking where a third of the rows are ties is not a ranking. It is a wage curve with job titles written next to it.
What we got wrong, and what to do about it.
I published the 9% figure and I would publish it again with the data I had. That is not a defence. A number computed correctly from a modelled dataset inherits the model, and I described it as a measurement of the market when it was a measurement of our own estimates. The dataset told me what I had told it.
If you are quoting an AI salary premium from anyone, including us, ask one question. Is the underlying number anchored to something outside the vendor, and if it is, do the AI and non-AI groups share the anchor? If they share it, the premium is an artifact of grouping.
What still holds: location, and it is the biggest lever in the data.
One finding survived the re-anchoring unchanged, because it never depended on the modelled layer.
San Jose, CA carries the highest cost-of-labor multiplier across all 81 cities in our data: 1.38. Charleston, WV carries the lowest: 0.78. San Jose pays 77% more than Charleston for the same role.
Worked example. A role with a $150,000 national median prices at $207,000 in San Jose and $117,000 in Charleston. Same title, same band, $90,000 apart.
The distribution matters more than the extremes. Of the 81 cities, 34 sit above the 1.0 national baseline, 1 sits exactly at it, and 46 sit below. Most tracked cities pay below the national number, so a national median quoted without a city is an overestimate for most of the map.
Location is the single biggest lever in this dataset that has nothing to do with your skills.
To price any of the 3,445 roles against any of the 81 cities, run the salary calculator.
AI does not own the top bracket, and now it is under-represented in it.
743 of the 3,445 roles, 22%, carry a median of $200,000 or more. Of those 743, 88 are AI-classified. That is 12% of the top bracket against AI's 19.9% share of the dataset.
Under-represented, not over. The June version of this post ran the same calculation on the modelled data and found AI mildly over-represented at 22%. The direction flipped for the same reason everything else did.
The reason underneath is unchanged and boring. The non-AI tail includes medicine, law, and executive roles, and those clear $200,000 on their own occupation curves.
The current distribution, for anyone who needs it: median $136,000, 10th percentile $101,000, 90th percentile $219,000, range $34,000 to $333,000, mean $156,139. The mean sits above the median, so the distribution is right-skewed. Quote medians.
Where these numbers come from.
Every figure here comes from our published salary dataset: 3,445 roles across 81 US cities, each role's base median anchored to its federal occupation wage curve by seniority tier and reproducible from the BLS OEWS file. The AI classification comes from our open role taxonomy, 687 roles across 13 hubs, CC BY 4.0.
The June figures are quoted from the dataset as it stood on June 12, 2026, which is why they no longer reproduce against today's data. The current figures were computed on August 29, 2026.
The limitations, and this post is mostly about one of them:
- Base salary only. No equity, bonus, or signing.
- US only.
- Medians, not individual offers.
- Titles collapse onto occupation codes. 3,445 roles resolve to 202 distinct medians, so many titles share a number with a title that is not much like them. Any comparison between groups of titles is affected by this, which is the finding above.
- AI classification is structural: taxonomy hub assignment, not job-description text.
- City figures are multiplier-based, and live role-by-city pages apply a deterministic per-page variance of up to plus or minus 4%.
If you cite this, cite the correction along with the number. The taxonomy is CC BY 4.0. Attribution is the whole ask.
Common questions
How much do AI engineers make in 2026?
In our data the AI Engineer median is $133,000, with a band of $99,000 to $174,000. Software Engineer carries the same $133,000, because both titles resolve to the same federal occupation code. That identity is the point rather than a glitch: our figures are anchored to occupation wage curves, so distinct titles often share a number.
What is the highest paying AI job in 2026?
By our current figures SVP of AI Innovation tops the AI roles at a $324,000 median, with Chief AI Officer at $310,000. Read the ranking carefully. Four different vice president titles tie at exactly $303,000, because those roles resolve to shared occupation codes, so the order below the top few carries no real signal.
Do AI jobs pay more than software engineering jobs?
Not in our data, and the comparison does not survive scrutiny. AI Engineer and Software Engineer both carry a $133,000 median because they share a federal occupation code. 679 of our 687 AI-classified roles share a code with a role we do not call AI, so a title-level premium measures grouping rather than pay.
Which US cities pay AI engineers the most?
San Jose, CA leads at 1.38 times the national baseline, the highest multiplier across all 81 cities in Orbyt's 2026 data. That's 77% above the lowest, Charleston, WV, at 0.78. Only 34 of 81 tracked cities sit above the national baseline; 46 sit below it.
Do AI skills pay more?
Our own role-level data no longer shows one. After anchoring to federal occupation wage curves, AI-classified roles compute below the rest, and 679 of 687 share an occupation code with a non-AI role. PwC's 2025 AI Jobs Barometer separately reports a 56% wage premium for AI-skilled workers within occupations, which measures skills rather than titles.
How much more do AI jobs pay than other tech jobs in 2026?
We reported a 9% premium in June 2026 and withdrew it in August. After every salary was anchored to federal occupation wage curves, AI-classified roles compute a $133,000 median against $156,000 for the rest. That gap is not a finding either, because the two groups draw on mostly the same occupation codes.
Does the city you work in really change an AI salary that much?
Yes. San Jose, CA carries the highest cost of labor multiplier among the 81 tracked cities at 1.38, while Charleston, WV carries the lowest at 0.78, meaning San Jose pays 77% more for the same role. A role with a $150,000 national median would price at $207,000 in San Jose versus $117,000 in Charleston, a $90,000 difference from location alone.
Related research
- How Much Does an AI Engineer Make in San Francisco? (2026 Data) Data, Jul 2026.
- What Recruiters Are Actually Doing With AI Right Now Research, Aug 2026.
- Is an Algorithm Silently Rejecting Your Resume? What the Research Actually Shows Research, Aug 2026.




