120,000 Tech Workers Laid Off in 2026 — AI Is the Blame

Tech layoffs in 2026 have reached 120,000 roles, according to Layoffs.fyi. AI is the most-cited reason, per outplacement firm Challenger, Gray & Christmas. The cuts span Microsoft, Google, Meta, Oracle, and dozens of others — many reporting record revenues while culling staff.

The Numbers Behind the Cuts

What This Means for Developers

If you're a developer in 2026, the job market is brutal but not random. Companies are cutting middle management, support, and non-core roles while hiring for AI infrastructure, security, and platform engineering. GitLab's restructuring is instructive: it's exiting 22 countries, flattening management, and rebuilding its platform for "agent-scale workloads." That means fewer managers, more individual contributors who can work with AI tooling.

The cuts at Google's Cloud division — even as Cloud revenue grows 63% — suggest that even profitable units are not safe. The trend of "quiet layoffs" via performance reviews (Google) or buyouts (Microsoft) means you may not see a headline but the impact is real.

The AI Rationale: Real or Cover?

Several companies explicitly say AI is not replacing the cut roles. Microsoft stated its 4,800 cuts are "not being replaced by AI." Yet the same companies cite AI as a reason for restructuring. The contradiction is hard to ignore. Many of these companies hired aggressively during the pandemic — perhaps the AI narrative is convenient cover for correcting overhiring.

Jack Dorsey's prediction that "most companies are late" and will make similar structural changes within a year suggests this wave is just beginning. For developers, the takeaway is clear: focus on skills that complement AI, not compete with it. Learn to build with AI agents, understand infrastructure scaling, and stay lean.

Next Steps

If you're affected by layoffs, consider roles at companies investing in AI infrastructure (Dell, GitLab) or those with explicit AI hiring plans (IBM's tripling of entry-level AI roles). If you're still employed, audit your team's exposure — are you a "measurer" or a builder? The latter is safer.

For more details, see the original TechCrunch article.