Writing the full English HTML translation, preserving structure and localizing all visible copy.Polishing a few tight SVG labels, then emitting the full HTML.
Deep dive · XiaoHu Explains

Why AI is racing ahead while U.S. unemployment hasn't budged—Anthropic's head of economics has answers

His take: so far AI amplifies people rather than replaces them. Killing tasks is not the same as killing jobs.
One-minute takeaway
  • AI is already widespread, yet jobs haven't vanished at scale. Anthropic's head of economics, Peter McCrory, wrote a long piece on why AI still hasn't driven up unemployment.
  • His thesis in brief: so far, AI amplifies people rather than replaces them. It automates some tasks, but the work only humans can do—judgment, quality control, catching failures—gets more valuable.
  • "The task is not the job": in the U.S. Department of Labor's occupation database, no occupation has every task systematically taken over by AI. Jobs get reshuffled, not erased.
  • He doesn't dodge the worry: youth hiring has weakened in AI-exposed roles. But the macro mess of recent years—the largest non-recession employment slowdown on record—may not be AI's fault.
  • The picture flips if AI starts automating innovation itself. For now, weak links still bottleneck the system. His bet: a year from now, unemployment won't be markedly higher because of AI.
⚑ Personal analysis by Anthropic's head of economics, drawing on in-house research. Arguing that "AI hasn't hit jobs" leans optimistic by nature; most figures come from him and his team, not independent third-party verification. He stresses the future is highly uncertain—this isn't blind bullishness. Calibrate the conclusions yourself.
1 What this is

AI is everywhere. Why hasn't unemployment moved?

Everyone worries AI will take their jobs. Reality has been stranger: AI is already in use across industries, yet U.S. unemployment has barely budged. Machines took on so much work that someone should have been pushed out. That hasn't happened. Why?

The person offering an answer is Peter McCrory, Anthropic's head of economics. Pulling together 18 months of the company's economic research, he lays out a framework for the question almost everyone is asking: is AI actually taking jobs?

💼
Why this piece is worth your time: An AI company's own head of economics, using real Claude usage data, faces the question head-on: will AI put me out of work? He delivers a serious analysis—numbers, counterexamples, and an honest label that the future is still highly uncertain.
2 Context

The job market is solid

Before asking whether AI has hit employment, rule out one possibility: maybe the labor market itself is worsening and masking AI's effect. It isn't. U.S. job metrics look healthy. Unemployment sits near 4.2%—full employment in the Fed's eyes. Weekly initial jobless claims are low. Job openings roughly match people looking for work; supply and demand are about balanced.

Over the same stretch, AI adoption is substantial: about 20% of firms already use AI in operations, rising to 40% in information technology. His inference: the base is large enough that if AI were really stealing jobs, it should already show up in the macro data.

4.2%
Unemployment at full-employment levels; layoffs and jobless claims also low
20% / 40%
Firms using AI in operations: all industries / IT
3 Where the signal is

AI's fingerprint shows up in productivity

There is a signal—just not in unemployment. It shows up under productivity. Labor productivity (output per hour) has grown faster in recent years than before the pandemic.

Four years pre-pandemic
  • Labor productivity: 1.6% a year
  • AI not yet at scale
2022–2026
  • Labor productivity: 2.0% a year
  • Sectors using more AI grew faster

One honest caveat: there are two yardsticks for "efficiency," and they don't fully agree.

Up ✓
Labor productivity: output per hour. 2.0%, above the pre-pandemic pace
Milder
Total factor productivity: growth left after capital and labor inputs are stripped out—pure "working smarter"

One ruler says AI is speeding things up; the stricter one is less bullish. His read: the clash itself may mean an acceleration is just starting and hasn't fully registered in the data. Either way, this section's point holds: AI's macro effect is visible in output efficiency, not unemployment.

4 Core framework

So far, AI is amplifying human capability

So why did efficiency rise while unemployment didn't? That's the essay's central claim. On how AI reshapes work, two worldviews sit in opposition:

Displacement (what people fear)
  • AI learns a task and replaces a person
  • Tasks automated → jobs erased
  • Result: unemployment rises
Augmentation (what he sees)
  • AI takes some work; people do harder work
  • Tasks automated → remaining human work worth more
  • Result: human output is amplified
Core claim

So far, AI is a skill-biased, labor-augmenting technology. It rewards people who can use it and amplifies what they can finish—humans still steer, judge, and hold the hardest parts. It widens what one person can do, so the returns to working with AI have gone up, not down.

An analogy

It's more like being handed a super-capable assistant: you finish a week's work in a day, so the boss needs you more—not a reason to let you go.

5 Why

Killing tasks is not killing jobs

How can AI automate so many tasks without wiping out whole jobs? One sentence holds the answer—he calls it "the task is not the job." A job is a bundle of tasks. Automating a few of them is not the same as automating the job.

A "job" = a stack of tasks Data entryAI takes FormattingAI takes Judgment & direction People work Catch failures AI kills a few tasks, but no occupation has every task taken over by AI end-to-end. What only humans can do caps throughput—and raises human value ↑

This isn't hand-waving. In O*NET—the U.S. Department of Labor's catalog that breaks each occupation into typical tasks—no occupation has every task systematically taken over by Claude. What remains usually needs human coordination, face-to-face interaction, or dealing with the physical world. Only people can do that work for now.

There's a deeper layer: a job was never a fixed task pack. Every major technology reshuffles tasks inside a role—kills some, strengthens others, and creates entirely new work. The net effect: human marginal product rises, not falls.

A classic (illustrative) example: after ATMs spread, many expected bank tellers to vanish. They didn't. Tellers shifted into sales and advising that need a human touch. Each branch needed fewer people and got cheaper to run, so banks opened more branches—and total teller employment rose. Machines took the "count cash" task; people moved into higher-value "serve the customer" work.

6 Evidence

Why call it "amplification"? The evidence

This isn't a gut call. Behind it sit several findings from Anthropic's economics team, based on real Claude usage data:

01
Hard work still has a skilled human behind it

Data show that more sophisticated user inputs line up with more complex Claude outputs. When Claude builds a complex economic model, someone is usually in the loop giving expert direction.

02
On the hardest tasks, Claude fails more often

Average model performance looks fine, but it struggles most on the hardest work—consistent with METR's "task duration" findings. Raising complexity still needs a human in the loop watching and covering failures.

03
The more people use it, the more it becomes a thinking partner

Even after half a year of use, people lean toward treating Claude as a thinking partner—and success rates rise. If the model were good enough alone, that pattern shouldn't show up.

04
Even coding agents reward domain skill

Seven months of Claude Code tracking: people plan, AI implements. More skilled users succeed more often and recover better when the AI fails. Pure coding drops in value; planning and failure recovery rise.

7 The caveat

The one soft spot is young workers—don't rush to blame AI

He doesn't duck contrary evidence. Weaker signs show youth hiring softening over the past year in AI-exposed roles—same direction as the Stanford Digital Economy Lab's "Canaries in the Coal Mine." He immediately adds: don't pin the whole bill on AI.

Looks like AI's fault
  • Youth hiring softens in AI-exposed roles
  • People in exposed roles also worry more about job loss
More likely a macro story
  • A messy few years: post-pandemic scars, rate hikes, commodity swings, trade conflict
  • Hiring is an investment; uncertainty suppresses it
  • Largest non-recession slowdown on record—low hire, low fire hurts new entrants most

So the struggle young people face finding work may be macro, not AI. The worry is real. Treating it as proof that AI has already caused unemployment doesn't hold yet.

8 Variables and judgment

What would break the case

"Amplify, don't replace" is a so-far conclusion. He admits that as models strengthen, it can break: the jagged frontier—AI that's uneven and hard to predict—may fill in, and the payoff to human expertise may shrink. The biggest variable: AI may start automating innovation itself.

Past general-purpose technologies couldn't do that: a stronger internal combustion engine doesn't invent new forms of transport on its own. Bolt general intelligence onto machines, and you have an engine for the next wave of invention. In standard models, once innovation itself is automated—first, perhaps, via recursive self-improvement (RSI)—you can get an "economic singularity": unbounded growth in finite time.

The accelerator
  • Models keep improving; innovation may be automated
  • In theory, an "economic singularity"
The brake: weak links
  • Growth sticks on links that are critical and hard to improve
  • Any work that stays un-automatable is a ceiling
  • And keeps labor's income share from collapsing for long

Those weak links are already biting. Example: coding agents lifted generated code volume 10–20×, yet software releases rose only ~30%, and app usage didn't rise at all.

Writing got an order of magnitude faster; delivery barely kept up. Where's the jam? Coding was only ever one step in software production. Upstream you still have to decide what to build; downstream sit testing, review, integration, shipping, and actual user adoption—steps AI has barely sped up. Code flies, then slams into everything that didn't accelerate. That's a weak link: a chain moves only as fast as its slowest ring, not its fastest.

Decide what to build
No faster
Write code
AI ×10–20
Test & review
No faster
Integrate & ship
No faster
Reach users
No faster

Result: code volume 10–20×, software releases only +30%, app usage flat. One link sped up; the whole chain still crawls at the slowest step.

Scaling laws are hard to argue with. Models will get better—much better. I expect faster productivity growth, and clearer signs of self-improvement. I don't think unemployment will be markedly higher a year from now, at least not because of AI.Peter McCrory
Source
Why hasn't AI increased unemployment?
Peter McCrory (Head of Economics, Anthropic)·Long post on X·2026-07-22
Note
All figures in the piece follow the author and his team's cited numbers, not independently verified by this site. Charts are illustrative diagrams drawn here for clarity. Author title (Head of Economics, Anthropic) independently verified.