When OpenAI CEO Sam Altman told an audience in February 2026 that AI washing is real — “there’s some AI washing where people are blaming AI for layoffs that they would otherwise do” — he wasn’t theorising. He was describing what the data had already confirmed. In the year following New York’s first-of-its-kind AI disclosure requirement, not one of 162 companies that filed mass termination notices attributed a single job loss to AI.
This article is part of our series on AI-washing and the corporate fiction it enables. Here we move from the macro evidence to the company-level specifics: seven named organisations, placed on a single spectrum with explicit verdicts and the evidence behind each verdict.
So here’s what we’ve done. We’ve taken seven companies — Duolingo, Amazon, Klarna, Salesforce, Hewlett-Packard, Goldman Sachs, and Morgan Stanley — and ranked them on a single spectrum from clear fiction to documented legitimate displacement. No one else has put them all together with explicit verdicts and evidence. That’s what this article does.
If you want to understand why AI-washing is structurally rational in the first place, we’ve covered why this behaviour is structurally rational elsewhere. And for the macro picture that sits behind these company-level decisions, the data behind these company decisions gives you the baseline.
How do you place a company on the AI-washing to genuine displacement spectrum?
AI washing is the practice of attributing layoffs, hiring freezes, or restructuring to AI adoption when the actual driver is financial, structural, or operational. The spectrum has six positions:
- Clear fiction — AI language applied to a decision with no AI displacement mechanism for the stated workforce (Duolingo)
- Contested — contradictory internal statements; legal filings do not support the AI claim (Amazon)
- Mixed — AI contribution is real but inseparable from structural correction; causation genuinely unclear (Klarna)
- Disclosure gap — internal sources claim AI; legal filings say otherwise without a public executive contradiction (Goldman Sachs, Morgan Stanley)
- Forward-tense — AI cited for planned future cuts with no current evidence (Hewlett-Packard)
- Documented legitimate — specific named mechanism, specific function, specific numbers, confirmed plausible by independent economists (Salesforce)
The key grading tool is what we call the WARN attestation test. NY WARN filings carry legal liability — someone at the company signed them knowing what misrepresentation means. When a company is telling investors it’s achieving AI efficiencies while simultaneously filing WARN notices with “economic” cause codes, that gap is itself an evidential signal. What a company is willing to legally sign carries more weight than whatever its PR team put in a press release.
Here is the full spectrum summary:
- Duolingo — Clear Fiction — No full-time layoffs; only contractor phase-out; no WARN filings; company grew headcount
- Amazon — Contested — Galetti (AI) vs. Jassy (culture) contradiction; 660 NY WARN filings all “economic”
- Klarna — Mixed — AI hiring-freeze claim plausible; pandemic overhiring correction inseparable; partial rehiring
- Goldman Sachs — Disclosure Gap — IR communications cited AI savings; 4,100+ NY WARN notices all “economic”
- Morgan Stanley — Disclosure Gap — Internal sources cited automation; 260 NY WARN filings with no AI attribution
- Hewlett-Packard — Forward-Tense — Future cuts not yet taken; no mechanism to evaluate
- Salesforce — Documented Legitimate — Named mechanism (Agentforce); specific function (customer support); 9,000→5,000; economist-confirmed plausible
What does a textbook AI-washing announcement look like? The Duolingo case
Duolingo represents the clearest AI-washing case in this analysis because no full-time employees were laid off — only contractor relationships were ended — and the company was actively growing headcount while the AI displacement narrative circulated.
In April 2025, CEO Luis von Ahn published an “AI first” all-hands memo on LinkedIn announcing that Duolingo would “gradually stop using contractors to do work that AI can handle.” The coverage was immediate — here was a company replacing workers with AI. Five months later, von Ahn told CNBC that Duolingo had not laid off a single full-time employee. The company had been gradually phasing out contractors, yes, but it had also been adding headcount, not cutting it, since April.
Contractor phase-outs aren’t subject to WARN Act notification. That means a company can wrap AI-displacement language around what is really a procurement decision — ending contingent-workforce contracts — without any legal attestation requirement. No WARN filings exist for Duolingo full-time employees because no full-time employees lost their jobs. The absence of filings isn’t a disclosure gap. It’s confirmation that the workforce displacement story was fictional.
Verdict: Clear AI-Washing (Fiction end of spectrum).
Why is the Galetti-Jassy contradiction the most data-rich contested case? The Amazon analysis
Amazon’s October 2025 reduction is the most evidence-rich contested case because the contradiction between Beth Galetti’s AI attribution and Andy Jassy’s public walkback is on the public record, and the NY WARN filings are retrievable and unambiguous.
In October 2025, Amazon SVP Beth Galetti wrote in an all-hands memo attributing the 14,000-job reduction at least in part to AI efficiency. Hours later, a spokesperson issued a statement: “AI is not the reason behind the vast majority of reductions… Last year, we set out to strengthen our culture and teams by reducing layers.” Then CEO Andy Jassy went further still. The cuts were “not really financially driven, and it’s not even really AI-driven, not right now. It really is culture” — directly contradicting his own VP’s framing.
Amazon reported 660 affected workers in New York for the October 2025 reduction. Every single filing came back “economic.” Amazon’s legal team attested economic causation while the PR layer was still cycling through contradictory AI narratives. A former Amazon principal program manager laid off in October put it plainly: she described herself as a “heavy user of AI” but said “I was laid off to save the cost of human labour.”
Verdict: Contested (likely AI-washing). If you want to understand why this pattern of non-disclosure keeps repeating, why none of these companies disclosed AI in WARN filings covers the regulatory dynamics.
What does it mean when a CEO says “zero layoffs due to AI” but credits AI for not hiring? The Klarna case
Klarna presents the most genuinely ambiguous case on the spectrum: the CEO’s “zero layoffs due to AI” statement is technically accurate, AI’s contribution to the hiring freeze is plausible, but the full headcount reduction cannot be attributed to AI when pandemic overhiring correction and attrition are the dominant mechanisms.
Sebastian Siemiatkowski publicly stated “zero layoffs due to AI” — and simultaneously credited AI as the primary reason Klarna did not replace departing employees. Klarna’s headcount fell from approximately 5,500 at its 2022 peak to approximately 3,000, a 45% reduction achieved primarily through attrition. Revenue per employee grew from $300,000 to $1.3 million over the same period.
But there are two things you can’t separate from the AI narrative here. First, pandemic overhiring: Klarna, like many fintechs, significantly overhired in 2020–2022. A meaningful chunk of that headcount reduction is a correction of that structural error, nothing more. Second, the AI experiment itself backfired. Klarna deployed an AI agent for customer support that the company claimed handled work equivalent to 700–853 customer service agents. Customer satisfaction declined. Klarna reversed course and started rehiring human support staff. Siemiatkowski acknowledged: “People were very angry with me for saying that.”
Unlike Amazon’s contested case, Klarna has an actual deployed AI product handling customer service volume — so the ambiguity is genuine rather than simply unsupported.
Verdict: Mixed (genuine ambiguity).
Why are economists treating Agentforce as the legitimate benchmark? The Salesforce case
Salesforce is the only case in this analysis that passes all four criteria for documented legitimate AI displacement: a named AI mechanism, a specific function affected, specific before-and-after numbers, and no contradicting internal executive statement.
Marc Benioff stated that Salesforce reduced customer support headcount from 9,000 to 5,000 specifically because of Agentforce deployment. That’s 4,000 people, a 44% reduction in a single defined function. Agentforce is not a generic AI efficiency claim. It’s a named AI agent platform deployed in a specific bounded function. Oxford Internet Institute economist Fabian Stephany confirmed the case is plausible: “The work that has been described — particularly online and customer support — is, in terms of tasks and required skills, relatively close to what current AI systems can perform.”
What makes Salesforce the legitimate benchmark is that four-criteria combination: a named mechanism (Agentforce), a specific function (customer support), verified numbers (9,000 to 5,000), and no internal contradiction.
That said, it’s not beyond dispute. SalesforceBen analysis notes Salesforce “later stated it had ‘redeployed hundreds,’ leaving thousands unaccounted for.” A counter-view exists that Salesforce used AI as cover for financially-driven cuts. These complications bring the rating down from “verified” to “credibly genuine” — still the highest legitimacy position on this spectrum.
Verdict: Documented Legitimate. Worth noting: this legitimacy applies specifically to the 4,000-person customer support reduction attributed to Agentforce. It doesn’t mean every Salesforce layoff across every period was AI-driven.
What does the WARN Act disclosure gap reveal? The Goldman Sachs and Morgan Stanley cases
Goldman Sachs and Morgan Stanley demonstrate a distinct spectrum category: companies willing to communicate AI causation through unaccountable channels while simultaneously filing legal documents that make no AI attribution whatsoever.
Goldman Sachs filed NY WARN notices for over 4,100 workers in 2025. AI cost savings were cited internally. Every single WARN filing came back “economic.” When contacted, Goldman Sachs told Bloomberg Law that its NY WARN notices were “triggered” by the company’s annual talent review exercise — no mention of AI. Morgan Stanley cut 260 New York positions; an unnamed source told Bloomberg that a portion reflected automation; the WARN filings made no AI attribution.
Both firms communicated AI causation through IR channels — analyst calls, internal memos, unnamed sources — while filing legal documents with “economic” cause codes. The incentive structure here is pretty clear. Attributing layoffs to AI in WARN filings could invite labour regulatory attention and bias claims. As Cornell labour economist Erica Groshen noted, the binary yes-no structure of WARN AI disclosure creates perverse incentives: firms have every reason to avoid the AI checkbox regardless of actual causation.
Verdict: Disclosure Gap (Goldman Sachs and Morgan Stanley). For the full regulatory picture, why AI layoff disclosure laws are not working covers what the NY WARN data reveals.
What about Hewlett-Packard’s forward-tense claim?
HP CEO Enrique Lores stated in a November 2025 earnings call that AI would allow HP to cut approximately 6,000 people “in the next years.” That’s a future-tense claim. The reduction hasn’t happened yet. There’s no mechanism to evaluate. Come back and apply the eight questions once the cuts actually occur.
Verdict: Forward-Tense (Unverifiable at this stage).
What eight questions should you ask to evaluate any AI layoff announcement?
These questions are ordered from most to least reliable evidence. A company that answers well on questions 1, 2, and 7 is provisionally legitimate. A company that fails questions 1, 2, and 4 is provisionally AI-washing.
1. Has the company filed WARN notices, and what cause code is used? This is your single highest-reliability signal. WARN filings carry legal liability. Amazon (660 filings, all “economic”), Goldman Sachs (4,100+ filings, all “economic”), and Morgan Stanley (260 filings, no AI attribution) all fail this test.
2. Is there a named AI mechanism? You need a specific product, platform, or tool. “Agentforce” passes. “AI efficiency” fails. No name, no claim.
3. Which workforce category was affected — full-time employees or contractors? Contractor phase-outs aren’t subject to WARN notification and aren’t workforce displacement in the conventional sense. The entire Duolingo case turns on this distinction.
4. Do internal executive statements agree? A CEO contradicting a VP’s AI claim is a strong signal of AI-washing. The Galetti-Jassy contradiction at Amazon is the clearest example.
5. Is the AI claim in the same communication channel as the legal filing? If a company claims AI causation on an earnings call but its WARN filings say “economic,” the channel gap is evidence.
6. Can the reduction be explained by non-AI factors? Pandemic overhiring correction, rate-environment cost cuts, and structural reorganisation all reduce AI attribution confidence.
7. Have independent economists or auditors verified the AI mechanism? Third-party verification is your highest legitimacy marker. Salesforce is the only case in this analysis with external economist confirmation.
8. Is the claim past-tense or future-tense? Future-tense claims like HP’s aren’t necessarily AI-washing, but they have zero current evidence and belong in a separate category from claims about completed reductions.
FAQ
What is AI washing in the context of workforce reductions?
AI washing is the practice of attributing layoffs, hiring freezes, or restructuring to AI adoption when the actual driver is financial, structural, or operational. Not all AI washing is deliberate — some cases are just opportunistic framing of genuine but minor AI contributions. The important thing to understand is that AI washing exists on a spectrum from clear fiction (Duolingo) to disclosure gaps (Goldman Sachs). Where a company sits on that spectrum determines how you should respond to its announcement.
What is the WARN Act and why does it matter for evaluating AI layoffs?
The federal WARN Act requires companies with over 100 workers to give 60 days’ notice of mass layoffs. New York’s WARN Act adds a requirement to disclose whether AI, robotics, or software modernisation drove the cuts. Because WARN filings carry legal liability, they’re more reliable indicators than press releases or earnings call statements. In the year following the AI checkbox’s introduction, zero of 162 NY filers attributed cuts to AI — including Amazon, Goldman Sachs, and Morgan Stanley, all of which made AI claims through other channels.
What is the difference between an AI layoff and an AI-driven hiring freeze?
An AI layoff involves actively terminating existing employees and attributing that to AI displacement. An AI-driven hiring freeze involves not replacing employees who leave, attributing that decision to AI capability. Klarna is the hiring-freeze case. Only the first is direct AI displacement — WARN filings capture active terminations, not attrition decisions, so the audit checklist applies differently to each.
This article places AI-washing and the corporate fiction it enables in operational context by assessing specific companies against available evidence. The companion analysis what the layoff data actually shows establishes the macro baseline these company-level cases sit against. To apply this spectrum to your own planning decisions, the CTO decision framework translates case study pattern recognition into professional action. For the full picture of what the layoff data actually shows across all six analytical layers, see the series overview.
