The AI Layoff Lie: Only 4.5% of 2025 US Cuts Were Actually About AI

Thu, 30 Apr 2026 07:34:28 +0000

Oxford Economics published the receipt: AI-related job cuts accounted for only 4.5% of US layoffs in the first 11 months of 2025. The remaining 245,000 layoffs in the same period were driven by ordinary market and economic conditions — nearly four times higher.

The story we've been told about engineers being replaced by software is mostly accounting in a costume.

The hiring manager survey

In December 2025, Resume.org surveyed 1,000 US hiring managers. Two numbers worth writing down:

59% admitted that AI framing in layoff announcements lands better with stakeholders than the actual reasons
Only 9% said AI had actually replaced roles entirely

That is the gap between the layoffs that happened and the layoffs that were marketed.

The CEO disclosures

The most interesting receipts come from the people with the most to lose by speaking honestly.

Sam Altman, CEO of OpenAI, at the India AI Impact Summit (February 2026):

"I don't know what the exact percentage is, but there's some AI washing where people are blaming AI for layoffs that they would otherwise do."

The man whose company sells the technology being blamed for the layoffs. Calling it AI washing. In public.

Babak Hodjat, Chief AI Officer at Cognizant — a 100,000-person AI consulting firm — to Nikkei Asia (Q1 2026):

"AI becomes the scapegoat from a financial perspective, like when a company hired too many."

Two senior AI executives, separately, in separate venues, naming the same dynamic. Companies hired too many during the pandemic. The correction was due. AI is the story being told to explain it.

The actual mechanics

So if it isn't AI, what is it? Three drivers, none of them new.

1. The pandemic over-hiring correction never finished.

Big tech roughly doubled headcount between 2020 and 2022, on the assumption that remote-work demand would compound forever. It did not. The first wave of cuts came in late 2022. The second in 2023. The current wave is the third — and the cleanup still isn't done.

2. AI infrastructure capex is consuming the income statement.

The combined 2026 AI infrastructure spend across Alphabet, Microsoft, Meta, and Amazon is approaching $650 billion. That money has to come from somewhere. Payroll is one of the largest controllable costs in a software company. If you need to fund a data center the size of a small city, the math points to one place.

The companies aren't exactly lying when they say AI is the reason. The spend on AI is the reason. Not the model output.

3. Operating margin expansion is its own incentive.

A layoff framed as "strategic AI repositioning" gets a friendlier market reaction than the same layoff framed as "we missed a quarter." The framing isn't free. It moves the stock. That is its own incentive — the boring, mechanical kind that drives quarter after quarter of corporate communication.

What this changes for engineers

If your role was cut and you have spent the last few weeks assuming AI made you obsolete — the data says it almost certainly did not.

Oxford Economics gave the systemic number: 4.5% of layoffs were AI-related. 95.5% had other reasons. You did not lose your job to a machine. You lost your job to a financial decision wearing a machine costume.

The skill that got you hired is still the skill that gets you hired.

The harder truth: the hiring slowdown is real even where layoffs aren't dramatic. Roles aren't being backfilled. Open requisitions are being quietly closed. The job market for mid and senior engineers in 2026 is harder than it was in 2021. The reason is macro — capex is going into AI buildout, not headcount. Interest rates haven't come back down.

None of that is about your skill becoming obsolete. All of it is about the cost of capital in a different economy.

How to actually use this

Three concrete actions:

1. Read your company's earnings call, not its AI strategy post. The earnings call tells you what's actually driving cost decisions. The AI strategy post tells you what they want investors to believe.

2. Stop pre-discounting yourself in interviews. The companies cutting headcount are not cutting because AI got better at your job. They are cutting because the capital math changed. When the capital math shifts again, hiring will return — and the skill set will not have to be rebuilt from scratch.

3. Negotiate from a calmer position. If you internalize the AI replacement story, you panic and pivot into a defensive posture that doesn't match the actual threat. If you internalize the financial restructuring story, you negotiate with people, not with a fictional robot.

The data supports the second story. The CEO of OpenAI supports the second story. The Chief AI Officer of Cognizant supports the second story. Even Oxford Economics supports the second story.

4.5%. Not 99. The next time someone tells you AI took your job, ask them which study they read.

What is your team using to communicate AI-driven changes — actual data, or stakeholder optics?

Microsoft Just Officially Called "10x AI Coding Productivity" a Myth. Real: 26%

Mon, 27 Apr 2026 22:17:16 +0000

On April 9, 2026, Microsoft Research published the New Future of Work Report. Buried inside is a section titled "myths" — three of them, named directly:

Counting AI-generated lines of code is a meaningful productivity metric
Current tools will instantly turn every developer into a "10× engineer"
Adoption primarily depends on model capability

The company that owns GitHub Copilot just officially called the entire AI coding marketing playbook from the last two years a myth.

The real number

The same report links to a randomized controlled trial published in Management Science (2026):

4,867 developers across Microsoft, Accenture, and an anonymous Fortune 100 company
Random subset got access to an AI coding assistant; the rest didn't
Outcome measured at the developer level on real production work

The result: 26.08% more completed tasks (standard error: 10.3%).

Not 10x. Not 5x. Twenty-six percent.

A note on timing: the experiments themselves ran in 2022–2023, on the GPT-3.5 generation of Copilot. Peer-reviewed final results came out in February 2026. The April 2026 Microsoft Research report cites this study as the best evidence available — meaning when they list "10x" as a myth, this is the number they're pointing at.

The hidden finding

Read the second sentence of the abstract: "Less experienced developers had higher adoption rates and greater productivity gains."

Translation: juniors got more out of the assistant than seniors. The benefit is concentrated where the existing skill is lowest.

The mechanism is obvious to anyone who's watched both kinds of engineer use these tools. A junior asks the assistant to write a function and ships what comes back. A senior asks the assistant to write a function and then spends as long reviewing it as it would have taken to write from scratch.

Reviewing is more cognitively expensive than writing. The senior pays that cost. The junior either doesn't pay it, or doesn't yet know they're supposed to.

Same tool. Two different jobs. Two different productivity numbers.

Stack the second study

The METR randomized trial (2025) measured experienced open-source developers working on their own repositories with Cursor + Claude 3.5/3.7 Sonnet:

Predicted before the trial: +24% speed-up
Felt after the trial: +20% faster
Measured: −19% slower

A 40-point gap between perception and reality.

Stack the two studies:

Microsoft (RCT, 4,867 devs, code completion, GPT-3.5 era): +26%
METR (RCT, 16 experienced devs, agent tools, modern Sonnet): −19%

The honest range is somewhere between +26% up and −19% down, depending on the task, the seniority of the user, and the discipline of the prompt.

How to actually use this

1. Stop using "lines of code" as an AI productivity metric. Microsoft Research just officially flagged it as a myth.

2. Budget against ~25%, not 10x. A quarter is the right size of number to plan around. License renewals, hiring forecasts, quarterly capacity. 26% is the kind of gain you can actually budget against.

3. Expect inverse seniority gains. If your senior devs feel like AI isn't helping them as much as your juniors — they're probably right, and the data confirms it.

If you've been quietly suspecting the hype was off — you now have a citation. Use it the next time someone asks why your AI-assisted output doesn't look like a launch keynote.

The full breakdown is in the video above.

What's your team using as an AI productivity metric right now?

Coder Legion - Recent posts tagged microsoft-research

The AI Layoff Lie: Only 4.5% of 2025 US Cuts Were Actually About AI

The hiring manager survey

The CEO disclosures

The actual mechanics

What this changes for engineers

How to actually use this

Microsoft Just Officially Called "10x AI Coding Productivity" a Myth. Real: 26%

The real number

The hidden finding

Stack the second study

How to actually use this