Snap CEO Evan Spiegel this week told employees the company would lay off approximately 1,000 people and close more than 300 open roles — a reduction of roughly a quarter of Snap's planned 2026 headcount. The memo, which Spiegel posted to the entire company Slack, was unusually direct about the cause.
'AI is producing more than 65% of our new code,' Spiegel wrote. 'Teams that used to need twenty engineers to ship a feature are now shipping faster with twelve. We owe the company an honest recalibration.'
That recalibration is happening everywhere; most tech CEOs are just being less frank about it. Google, Meta, Salesforce, and Amazon have all trimmed middle-management and junior-engineering layers in the last six months, typically with language about 'efficiency' and 'organizational flattening.' Spiegel's memo is the first time a public-company CEO has explicitly attributed a four-digit cut to AI code generation.
Key facts
- 01Snap. A key thread of reporting in this story.
- 02Layoffs. A key thread of reporting in this story.
- 03AI adoption. A key thread of reporting in this story.
The investor reaction has been mixed but leaning positive. SNAP closed up 6.4% on the day of the announcement; analysts at Evercore raised the name from hold to outperform, citing 'structural margin expansion.'
The harder question is what happens to the people. Snap's severance package is generous by tech standards — six months of salary plus extended healthcare — and the company is partnering with a retraining fund to place affected engineers into AI-adjacent roles. But at industry scale, the retraining math does not work. If Snap's 65% code-generation number becomes the baseline across software, the net headcount destruction over the next three years will be counted in hundreds of thousands.
Working on something we should cover, or seeing a story we missed? Send leads, documents, or feedback to hello@aichatdaily.com. For sensitive tips, see our secure tips page for Signal and PGP options.
Spotted an error? Email hello@aichatdaily.com with the URL and the issue, or read our full corrections policy.
