The tech industry cut nearly 80,000 jobs in the first quarter of 2026. That's the largest quarterly total since early 2023. Almost 50% of those positions cited AI as a contributing factor. Freshworks and Coinbase both cut more than 10% of their workforces and named AI explicitly in their press releases.
The narrative was ready before the ink dried. AI is replacing workers. The reckoning is here. Etc.
The reality is messier, more important, and in some ways more uncomfortable than either side of that story wants to admit.
AI as Cause, AI as Cover
Let me say the thing that most coverage either glosses over or ignores entirely: both things are true at the same time, in different proportions, at different companies.
At some companies, AI is genuinely doing work that humans used to do. Junior and mid-level developers handling repetitive feature work, bug fixes, and code review prep are finding that AI tools now handle large portions of those tasks faster and cheaper. New software engineering job postings dropped 15% in the first two months of 2026 compared to the same period a year earlier. That's a structural signal, not noise. A team of 10 developers with good AI tooling can produce what 15 used to produce. The math eventually hits headcount.
At other companies, "AI efficiency" is the most socially acceptable excuse the corporate world has had in years. Andy Challenger from outplacement firm Challenger, Gray & Christmas put it plainly: companies are shifting budgets toward AI investments at the expense of jobs. That's subtly different from AI literally doing the job. It means someone in finance decided to reallocate the payroll dollars, and the AI narrative gave that decision a technology story instead of a cost-cutting one.
Both things are happening. The hard part — the part that actually matters for your career or your team — is figuring out which is which.
The 15% Drop That Should Worry You More Than the Headlines
The layoff numbers get the headlines because they're large and immediate. The number I'd watch more carefully: a 15% drop in new software engineering job postings in January and February 2026 versus the same period a year ago.
Layoffs are loud. Job posting declines are quiet. But job posting declines tell you more about the structural direction of the market than any single round of cuts. Companies that are cutting via AI don't just shrink headcount — they shrink the pipeline. If the work is being absorbed by AI and the remaining engineers are more productive, you need fewer of them over time. That shows up first in hiring freezes and posting declines, not just in headline layoff numbers.
Employment among software developers aged 22–25 has dropped nearly 20% since 2024. That's not a rounding error. That's an entry-level pipeline in serious trouble, and the implications for who learns to build software over the next decade are significant in ways we're not really talking about.
The Question You Actually Need to Answer
Here's the uncomfortable split test. Is your company:
A) Actually deploying AI to absorb work that humans were doing, with measurable changes in what gets shipped with fewer people?
B) Using "AI transformation" to justify cuts that were driven by capital reallocation, market conditions, or investor pressure — with the actual AI deployment still mostly theoretical?
The response to A is: understand which parts of your role are most legible to AI, get ahead of that transition, and build skills in the parts that aren't. Architecture, system design, complex debugging, knowing your domain deeply — these remain genuinely human work for now.
The response to B is: be skeptical of the narrative, don't make career-altering decisions based on AI hype you can't verify, and watch whether the "AI efficiency" gains actually show up in the product.
The dangerous mistake is treating B like A — panicking about displacement that isn't actually happening yet at your company — or treating A like B — dismissing a real structural shift because the PR language around it is often cynical.
What the Next Wave Actually Looks Like
The developers most at risk are not necessarily the worst ones. They're the ones whose work is most legible to AI — meaning predictable, well-specified, well-exemplified in training data. A lot of entry-level and mid-level development work fits that description.
The developers with the best long-term positions are the ones whose value is in judgment that requires context AI doesn't have: knowing the org's history, understanding why the current architecture is the way it is, being the person who can translate between what business stakeholders want and what engineering can actually deliver. That's not coding skill. That's institutional knowledge and communication under ambiguity — things that take years to build and don't compress into a prompt.
If your current job description could be completed by a very well-specified ticket and a capable agent, that's the conversation to have with yourself. Not in panic. In honest evaluation.
80,000 jobs gone in a quarter, half blamed on AI. Some of that is real. Some of that is convenient. The trick is knowing which half you're in.
Sources: Tom's Hardware — Tech industry lays off nearly 80,000 in Q1 2026 · TechRadar — Freshworks and Coinbase layoffs · The Hill — AI tied to tech layoffs · Rest of World — Tech jobs in 2026