Why AI is racing ahead while U.S. unemployment hasn't budged—Anthropic's head of economics has answers
- 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.
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?
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.
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.
- Labor productivity: 1.6% a year
- AI not yet at scale
- 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.
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.
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:
- AI learns a task and replaces a person
- Tasks automated → jobs erased
- Result: unemployment rises
- AI takes some work; people do harder work
- Tasks automated → remaining human work worth more
- Result: human output is amplified
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.
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.
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.
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.
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:
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.
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.
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.
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.
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.
- Youth hiring softens in AI-exposed roles
- People in exposed roles also worry more about job loss
- 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.
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.
- Models keep improving; innovation may be automated
- In theory, an "economic singularity"
- 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.
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
Peter McCrory (Head of Economics, Anthropic)·Long post on X·2026-07-22
Killing tasks ≠ killing jobs: why AI hasn't pushed up unemployment
Anthropic head of economics Peter McCrory, 18 months of research, one illustrated page.
↓ One page · one animated figure
Everyone fears AI will take their jobs. In the U.S., three things stack at once: firms already use AI widely, the job market is healthy, and unemployment hasn't climbed. Anthropic's head of economics, Peter McCrory, folds 18 months of company research into a framework that explains why.
His logic: the base is large enough that if AI were stealing jobs at scale, unemployment should already show it. The signal is real—and it shows up under output per hour. Figures above follow Peter McCrory and his team's cited numbers.
Why did efficiency rise while unemployment stayed quiet? His call: so far AI is skill-biased and labor-augmenting—whoever can use it gains value. It takes some work; people still set direction, judge, and hold the hardest pieces. One person's feasible boundary widens.
- AI learns a task and replaces a person
- Tasks automated → jobs erased
- Result: unemployment rises
- AI takes some work; people do harder work
- Tasks automated → remaining human work worth more
- Result: human output is amplified
Supporting evidence points the same way: complex outputs usually have a skilled human directing; the model struggles most on the hardest work and needs human cover; longer use turns it into a thinking partner; in coding, skilled users succeed more and recover better when AI fails—pure coding falls in value, planning and recovery rise.
Automating a pile of tasks doesn't erase the job, because a job is a bundle of tasks. AI peels off a few blocks; as long as human-only work remains, the job stays—and may be worth more because people fill the gaps. Jobs were never fixed packs either: new tech reshuffles tasks and creates new work.
Take XiaoHu's day job: entry and layout can go to AI; judgment, people work, and failure recovery stay human. While those blocks remain, the job isn't gone—and human value can rise.
He doesn't dodge contrary signs: youth hiring softened in AI-exposed roles (same direction as Stanford's "Canaries in the Coal Mine"). But the macro mess of recent years—the largest non-recession employment slowdown on record, with low hire and low fire—already hits new entrants hardest. The worry is real; pinning it all on AI still doesn't stand up.
- Models keep improving; innovation itself may be automated
- May show first in recursive self-improvement (RSI)
- In theory, an "economic singularity": unbounded growth in finite time
- Growth sticks on links that are critical and hard to improve
- Coding agents: code ×10–20, releases only +30%, app usage flat
- One link sped up; the chain still moves at the slowest step
Why are people still hired?
Firms use AI widely.
Unemployment hasn't climbed.
June unemployment
Full-employment level
/40%
All industries / IT
using AI in ops
job theft should show…
Signal is real—under
output per hour.
AI learns a task
→ replaces a person
→ unemployment up
AI takes some work
→ people do harder work
→ output amplified
I still call the shots.
Skill with AI raises pay.
AI widens what one person can do.
The job still stands.
Occupations with
every task fully
taken by AI
Jobs not erased!
What only humans do: judge, deal with people, catch failures—caps throughput and lifts pay.
Code volume up
Releases only +30%
App usage flat
Productivity faster.
won't jump due to AI.
Figures and judgment from Peter McCrory and team; in-house AI-company research, leans optimistic; future still uncertain.
XiaoHu Explains · best.xiaohu.ai
FIN