Case study · Causal inference · Econometrics

Is AI taking jobs? Testing the claim on 722 occupations

We linked how much AI is actually used in each occupation to US employment before and after ChatGPT, then ran the test most analyses skip: the same model on years when generative AI did not exist.

Causal inferenceRegressionPlacebo testData linkageLabour market
Independent project on public dataCode and data publishedUpdated 1 November 2026
722
occupations linked, covering 92% of US employment
r = 0.01
correlation between AI exposure and employment change, 2019–2025
−0.20
the same slope in 2015–2019, before ChatGPT existed: the “effect” predates the cause
7
occupations where displacement does show up, from customer service to translation

01The question

Headlines about AI and jobs usually rest on one of two things: studies of which tasks AI could do, or companies mentioning AI in a layoff announcement. Neither counts jobs.

We asked the question directly: did occupations where AI is actually being used lose employment after generative AI arrived, compared with occupations where it is not? And we committed in advance to publishing the answer whichever way it came out.

02The approach

  1. Measure real use, not potential

    We used the Anthropic Economic Index, which maps millions of real AI conversations to the roughly 18,000 tasks in the US occupational database, and kept a pre-ChatGPT theoretical index as a cross-check.

  2. Link three datasets that do not line up

    Occupation codes changed between 2015, 2019 and 2025. We built a crosswalk that merges codes only where they split or combined, keeping 722 occupations and 92% of employment.

  3. Control for the obvious confounders

    Pay level, how much of a job can be done from home, and fixed effects for 22 occupation families, with employment weights and robust standard errors.

  4. Run the placebo

    The identical models on 2015–2019, before generative AI. If exposure “predicts” job change then too, the post-2019 relationship cannot be caused by AI.

  5. Look where the effect could hide

    A change-in-growth design (did growth slow compared with each occupation's own trend?), unweighted versions, and the individual occupations most exposed to AI.

03What we found

Scatter plot of AI exposure against employment change for 722 occupations, 2019 to 2025, with a nearly flat fitted line. Pearson r = 0.01.
Figure 1. Exposure to AI barely predicts what happened to employment. It explains under 1% of the variation in job change across 722 occupations.
Coefficient plot of the AI exposure effect across model specifications for 2019 to 2025 and the 2015 to 2019 placebo period. Effects are small in every specification and the placebo reproduces the raw slope.
Figure 2. The one “significant” result (−0.48 points a year with pay and remote-work controls) shrinks to −0.16 and loses significance once occupation families are compared like with like. The pre-ChatGPT placebo gives −0.20 against −0.23 after: the tilt was already there.
Chart of the 30 most AI-exposed occupations comparing employment growth before and after 2019: 21 shrank after 2019 and 9 kept growing.
Figure 3. Where displacement is real, it is specific: customer service representatives, office clerks, receptionists, medical transcriptionists, technical writers, interpreters and graphic designers. Computer programmers fell 54%, but had already fallen 31% before ChatGPT; software developers grew 33%.

A naive analysis finds an “AI effect”. A careful one shows most of it is something else, and points to the handful of jobs where the effect is real.

04Why this matters

Workforce planning

Which of your roles are actually being reshaped, and which are only theoretically exposed? The difference changes hiring and training budgets.

Marketing and pricing

Did the campaign or the price change cause the uplift, or was the trend already there? The placebo test answers that in one model run.

Policy and investment

Before backing a programme or a sector thesis, check whether the relationship survives controls and a pre-period.

Messy data linkage

Codes that change over time, partial coverage and mismatched units are the normal state of real data. Getting the joins right is most of the work.

05Limits

What this can and cannot show

  • It counts wage-and-salary jobs, not hours, hiring or the self-employed, so a freeze on graduate hiring would show up only slowly.
  • The data ends in May 2025, two and a half years after ChatGPT's launch. Effects may still be building.
  • The exposure measure reflects use of one AI system. Occupation-level data cannot show what happens inside firms.

06How we would do this for you

Week 1

State the claim

Write down the causal question, the comparison group and the placebo before looking at results.

Weeks 2–3

Link and model

Join your data to the external sources it needs, then run the main models, controls and pre-period tests.

Week 4

Report the answer

A plain-English report that says what the data supports, what it does not, and what to watch next.

07Reproduce it

Python 3RstatsmodelspandasmatplotlibHC3 robust errors

Data: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics; Anthropic Economic Index; Felten, Raj and Seamans (2021) AI Occupational Exposure; Dingel and Neiman (2020) teleworkability.

This is an independent project built on public data to show how we work. It is not client work, and no client data was used. Figures are reproducible from the published code.

About to act on a correlation?

Before you change prices, budgets or headcount because two numbers move together, let us test whether one actually causes the other.

More case studies

Experimentation · Monte Carlo
24.6%of no-difference tests call a winner when checked daily

Your A/B test “winner” may be noise: what 100,000 simulated tests show

A Monte Carlo study of the most common A/B testing mistake, and a sequential stopping rule that lets you look every day without fooling yourself.

ExperimentationA/B testingMonte Carlo simulationSequential testingStatistics
Read the case study
Machine learning · NLP
1%of today's AI reviews caught by a detector trained on 2019's fakes

Can a model spot an AI-written review?

A detector that catches 86% of AI reviews while wrongly flagging 1% of genuine ones, the blind spot that makes older detectors useless, and a live demo you can try.

Machine learningNLPTrust and safetyModel evaluationExplainable AI
Read the case study