In January 2023, Google laid off 12,000 people. Microsoft cut 10,000. Amazon eliminated 18,000. Meta removed 11,000. By the end of that wave, more than 260,000 tech workers had lost their jobs in a span of months.
That was 2023. The cuts kept coming. In 2024, nearly 150,000 more tech workers were laid off. In 2025 and into 2026, the pace has slowed but the pattern has not changed: companies are still trimming, still questioning how many engineers they actually need, and still pointing at AI as the reason.
If you're an engineer who survived the waves — or if you didn't, and you're trying to figure out what happened and what's next — this piece is for you.
This isn't an editorial about whether AI is good or bad. It's an honest accounting of what's changing in the industry, who's being affected and why, and what you can actually do about it.
What the data actually shows
Layoffs.fyi, which tracks tech industry cuts, reported over 260,000 layoffs in 2023 alone. In 2024, the total crossed 147,000. These aren't startups failing — these are some of the most valuable companies in the world cutting tens of thousands of roles simultaneously.
The commonly cited narrative: Companies over-hired during COVID and are now correcting.
The less-discussed reality: The correction happened. The hiring hasn't come back. And AI is now being used to justify workforce sizes that would have employed half as many people even three years ago.
The 2023 layoffs were initially framed as a correction. "We hired too fast during the pandemic boom," the CEOs said. "Now we're right-sizing for a new reality." The new reality, it turns out, keeps requiring fewer people.
By 2025, a new framing had emerged: companies weren't just correcting COVID-era over-hiring. They were permanently re-baselining what "enough engineers" means — and AI coding tools were doing the heavy lifting of that argument.
A 2024 MIT study found that AI coding assistants increased individual engineer productivity by approximately 35-50% on certain tasks. A McKinsey report estimated that generative AI could automate up to 30% of work tasks for software developers. Neither number tells the full story, but both point in the same direction: the work is becoming more concentrated in fewer hands.
Why AI is changing the math
Before AI coding tools, engineering velocity was bottlenecked by human cognition. A senior engineer could ship a feature in a day that a junior needed a week to produce. But the ratio was maybe 3:1 or 5:1. AI tools have changed that ratio to something like 10:1 or 20:1 for certain categories of work — and companies know it.
The mechanism is simple: if one engineer with AI tools can do the work of two, then a company has two options. Option A: keep both engineers and ship twice as fast. Option B: keep one engineer and cut costs by half.
In a growth-at-all-costs environment, companies chose Option A. In a profitability-focused environment — which is what 2023-2026 has been — they increasingly choose Option B.
The uncomfortable truth is that the engineers most at risk aren't necessarily the least capable. They're often the most expensive. A senior engineer at $250,000/year is a tempting target when a mid-level engineer with AI tools can produce comparable code velocity. The seniority premium has to be justified by things that don't show up in sprint velocity — architecture, judgment, mentorship, cross-functional leadership.
The framing that helps: AI isn't replacing engineers. It's changing which engineer roles are scarce and which are plentiful. The scarce engineers are the ones who can use AI as a lever while providing the judgment, creativity, and accountability AI cannot.
The engineers thriving right now aren't necessarily the ones writing the most code. They're the ones who can define what code needs to be written, evaluate whether it's correct, integrate it into larger systems, and communicate what they've built to non-technical stakeholders.
Who's actually getting laid off
The laid-off engineers don't fit a single profile. Based on reports from those who've been through layoffs at major tech companies, a few patterns emerge:
- Entire teams eliminated, not individual poor performers. When Stripe eliminated a percentage of its workforce across the board, it wasn't targeting the lowest performers. It was reducing capacity in certain areas. Entire teams working on adjacent products were cut regardless of individual performance ratings.
- Mid-level engineers in areas AI is touching hardest. Testing, QA, routine frontend development, data pipeline maintenance — these are areas where AI tools have made the most immediate impact on individual productivity. Engineers in these roles have been disproportionately affected.
- Entire layers of management. Companies are using layoffs as an opportunity to flatten hierarchies. Director-level roles, management layers that existed to coordinate between teams, and Program Manager roles have been significantly reduced.
- Engineers who can't articulate their value beyond code. This is the uncomfortable one. Engineers who can only describe their work as "I shipped features" are more vulnerable than those who can connect their work to business outcomes, team capability, or architectural decisions that affected company trajectory.
The last point is not a judgment. It's a market signal. If your job search isn't going well, it may not be your skills — it may be that you're applying for roles that the market is valuing differently right now.
A recovery framework that actually works
Recovery from a layoff isn't linear, and it isn't fast. But there is a path through it that doesn't require you to pretend you're fine or to catastrophize about the future.
Week 1–2: Stabilize
File for unemployment immediately. Don't wait. In most states, the filing takes 2-3 weeks to process and benefits are not retroactive.
Check your insurance. You have 60 days after separation to elect COBRA (expensive but immediate) or sign up for the marketplace. Don't let a gap in coverage become another stressor.
Tell people. Not the world — but the people who matter. Friends, family, former colleagues. You don't need to announce it, but you do need support.
Don't make big decisions. You have time. The urgency you feel to "figure out what's next" is mostly anxiety. You don't need to decide anything for 2-4 weeks.
Week 3–4: Process and Reorient
Name what you've lost. Not just the job — the routine, the colleagues, the sense of direction. Write it down. Grieve it.
Take stock honestly. What do you actually want? Not what the market wants, not what your parents expect, not what you thought you'd be doing at this point in your career. What do you want?
Audit your skills and preferences. Are there parts of your job you actively disliked? This might be the moment to let those go. Are there parts you loved? Double down on those.
Rest. This sounds trivial but it's not. The job search grind is real. If you start it exhausted, you'll make worse decisions and burn relationships faster.
Month 2–3: Position and Act
Reframe your story. "I was laid off" is a fact. How you talk about it matters. "My team was eliminated as part of a company-wide restructuring" is accurate and doesn't invite sympathy.
Activate your network first. Most jobs never get posted. They're filled through referrals. Reach out to former colleagues, managers, friends-of-friends. Tell them what you're looking for specifically.
Be strategic about where you apply. Early-stage startups with funding are still hiring. Companies that "got AI right" (whatever that means to you) may have growth capacity. Smaller companies outside the tech industry are often overlooked by engineers but can offer real stability and different problems.
Consider the counter-offer carefully. If you're in final stages somewhere and get a counter from your former employer: the reasons you were on the job market probably still exist. Tread carefully.
The longer view: this is a reorientation, not a catastrophe
History offers perspective. Every major technology shift has created disruption cycles: the PC revolution, the internet, mobile, cloud. Each one eliminated some categories of work while creating enormous new categories. Software engineers aren't going away — the work is shifting.
The engineers who navigated the shifts successfully weren't necessarily the most technically brilliant. They were the ones who could read the market, adapt their skills, and position themselves where value was accumulating. That requires emotional stability to make clear-headed decisions — which is why taking care of your mental health during a job search isn't self-care indulgence. It's strategy.
The specific skills that are compounding right now: systems thinking (understanding how complex systems interact), product judgment (knowing what to build and why), AI collaboration literacy (knowing how to use AI as a lever rather than a crutch), and communication (the ability to work across functions and translate between technical and non-technical contexts).
These aren't soft skills versus hard skills. They're the skills that let one excellent engineer leverage AI tools to produce what previously required a team. The leverage is in combining technical depth with these cross-cutting capabilities.
If you're still employed but worried
Reading this from inside a company that's been cutting? You're not paranoid. The restructuring you're witnessing is real. Here's how to position yourself:
- Build visibility, not just velocity. Engineers who ship quietly and don't communicate their impact are first on the cut list when teams are evaluated. Document your wins. Make sure leadership knows what your team has delivered.
- Develop AI collaboration skills deliberately. Not just "use Copilot" — develop a systematic approach to leveraging AI tools that demonstrably increases your output. Be the engineer who can show, concretely, how AI tools have changed your work.
- Maintain your network. Stay in touch with former colleagues and peers. The engineers who weather layoffs best are the ones who have relationships to lean on when they need them. Invest in these relationships while you don't urgently need them.
- Build optionality. Keep your skills current. Contribute to open source. Write publicly about what you're learning. A public portfolio is a layoff insurance policy.
- Have an honest conversation with your manager. "Where does my team fit in the company's plans for the next 12 months?" isn't disloyal. It's mature. You can't plan your life around uncertainty you haven't acknowledged.
Common questions
Because AI tools have made individual engineers dramatically more productive. A team of 10 engineers with AI coding assistants can now do the work that previously required 20. Companies are trading headcount for velocity — and the math, however painful, makes short-term financial sense.
Both, but for different reasons. Junior engineers face the steepest competition (entry-level roles have collapsed as AI handles the scaffolding work). Senior engineers face different pressure: their high salaries make them tempting targets for "right-sizing," and some struggle to articulate the value that doesn't show up in code velocity metrics.
It's both. The 2023-2024 wave was partly corrections after over-hiring during COVID and rising interest rates. But 2025-2026 is structural: AI is genuinely eliminating certain categories of work. The engineers who will thrive long-term are those who can leverage AI to be 10x while maintaining the judgment, architecture, and interpersonal skills AI can't replicate.
First: let yourself feel it. This is a genuine loss — of income, identity, community, and routine. Don't rush to "optimize your job search" before you've processed the emotional hit. Then: file for unemployment, check your health insurance options (COBRA or the marketplace), and give yourself 2 weeks before making any big decisions about what's next.
Only if you genuinely want to. Taking a role significantly below your level because you're scared you can't get anything else often leads to frustration and quick turnover. The better framing: look for roles where your experience is actually leverage, even if the title is different. A senior engineer who takes a mid-level role doing the same work isn't "stepping down" — they're making a market calculation.
The honest answer: "The company made a workforce reduction affecting my team. I was laid off along with colleagues I respect." That's it. Don't blame AI, the economy, or management. Focus on what you learned and what you're looking for next. Interviewers have been laid off too — they understand. The bitterness smell is a bigger red flag than the gap.
If this resonated: You're not imagining the pressure. The Clearing has a recovery guide, a daily check-in tool, and a AI Fatigue Quiz for engineers navigating this exact moment. No accounts. No tracking. Just tools that actually help.
Recovery Guide
A practical 7-phase guide to recovering from AI fatigue and job loss. Built for engineers who are running on empty.
Mental Health
When the stress becomes more than a burnout detox can fix. Crisis resources, therapist directories, and clinical frameworks.
Developer Identity
When your job title feels like the only thing holding your identity together. It's not. Here's how to find the rest.
Engineer Communities
Find the people who've been through this.