AI Momentum
← Back to the day · June 29, 2026

'AI Did It' Is the New Layoff Script — and It's Doing Two Jobs at Once

A report argues that Meta, Amazon and Salesforce are using AI as the public rationale for layoffs. The provocative question: how much is real automation, and how much is a convenient story?

The argument is pointed: "AI" has become the headline explanation for job cuts at Meta, Amazon and Salesforce. The report's contention — and we attribute it as such — is that AI is serving partly as a cover story, a more palatable narrative than over-hiring, slowing growth, or ordinary cost discipline.

There's a reason this framing is attractive to companies. "We're restructuring because AI made roles redundant" signals forward-looking strength to investors, while "we hired too aggressively and need to trim" signals a mistake. Both can be true at once, and that ambiguity is exactly the point: the AI label can describe genuine productivity gains and launder unrelated belt-tightening in the same breath.

The impact lands on workers and on the public conversation. If every layoff is attributed to automation, we lose the ability to measure what AI is actually doing to labor — and we risk a fatalism that treats job loss as technological destiny rather than a choice executives are making and should be accountable for.

Our reading: resist both extremes. The catastrophist version — "the robots are taking everything" — is not supported by a corporate press release, and the naive version — "it's all just spin" — ignores that AI genuinely is reshaping some work. The honest position is that we're in a turbulent transition where automation, macroeconomics and management decisions are tangled together, and clear attribution is a public good. The long-term promise of this technology is that it frees people from drudgery to do work they find meaningful — but that future isn't automatic. It depends on naming what's really happening, investing in transition and retraining, and refusing to let "AI did it" end the conversation when it should start one.

Sources & references