aceModerate evidence
Published recordLaborGood Space
More
Artificial intelligence exposure and occupational wages: Evidence from the United States
- Truvace record
- TRV-2026-2561raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Observational study
- Sources
- 1 sourcePeer-reviewed
- sha256
- 46516936d479…check it
Purpose This paper investigates the relationship between occupational exposure to artificial intelligence (AI) and wage structures in the United States. While much of the literature focuses on the displacement effects of AI, less attention has been given to its implications for wage outcomes across occupations. Design/methodology/approach The study uses occupation-level data for 671 occupations, combining wage information with an AI exposure index that captures the extent to which occupations are affected by AI…
The gain
In a study of 671 US occupations, those with higher AI exposure had higher wage levels, an association that held across the wage distribution and was stronger in cognitively demanding jobs.
What this doesn’t fix
The study uses occupation-level rather than individual-level data, so it cannot capture wage differences within occupations, and its AI exposure index reflects potential exposure rather than actual firm-level adoption.
Sources
1 on file- Journal of Economic Studiesdoi:10.1108/jes-03-2026-0281
Cite this record
v1Truvace Impact Record TRV-2026-2561, v1: “Artificial intelligence exposure and occupational wages: Evidence from the United States.” Truvace, 2026-11-12. /record/TRV-2026-2561 (accessed on the day you copy it). sha256 46516936d479711e…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2561 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.