Tech Layoffs Hit 55,775 in Q1 2026—But Only 20% Are AI-Related. What's Really Happening?

General
1

The tech industry narrative right now is simple: AI is taking our jobs. Open any news feed and you’ll see headlines about automation, efficiency gains, and the rise of machines replacing workers. But when you actually look at the data, something doesn’t add up.

The Numbers Tell a Different Story

As of early March 2026, the tech industry has shed 55,775 jobs across 166 companies in just the first 74 days of the year. That’s roughly 689 job losses per day. If this pace continues, we’re looking at 264,730 layoffs by year-end—the worst year for tech employment since the dot-com bust.

Here’s what caught my attention: only about 20% of these layoffs (roughly 9,238-12,000 jobs) are actually linked to AI implementation and organizational restructuring around AI. That means 80% of tech layoffs have nothing to do with AI automation.

So what’s really driving these cuts?

The Real Culprits

After talking with fellow VPs and leaders across different companies, here’s what I’m seeing:

  1. The COVID Overhiring Hangover - During the pandemic, tech companies went on a hiring spree. We all did it. Demand for digital services exploded, money was cheap, and everyone was scaling like crazy. Now we’re paying the price. Many companies are simply recalibrating to match actual workload needs versus the inflated headcounts we built during lockdowns.

  2. Efficiency Mandates from Boards - Investors are demanding profitability over growth. The “grow at all costs” era is over. Boards are pushing executives to do more with less, and unfortunately, that means headcount reductions.

  3. Economic Headwinds - Slowing growth, rising interest rates, and ongoing economic uncertainty are forcing companies to cut costs and streamline operations. This isn’t about AI—it’s about surviving in a tougher economic environment.

  4. Market Correction - Some of the hiring during 2020-2021 wasn’t just aggressive—it was irrational. We’re now seeing a market correction back to sustainable staffing levels.

The AI Washing Problem

Here’s what troubles me most: companies are using AI as cover for business decisions that have nothing to do with automation. It sounds better in a press release to say “we’re restructuring to leverage AI” than to admit “we overhired and now we need to cut costs.”

I call this “AI washing.” It helps executives frame layoffs as forward-looking strategic moves rather than corrections for past mistakes. But it creates a false narrative that AI is the primary driver of job losses, which the data simply doesn’t support.

Major Players and Their Real Reasons

  • Amazon (16,000 jobs): Cited reducing layers and bureaucracy, not AI replacement
  • Oracle (~30,000 jobs): Business restructuring and efficiency
  • Block (4,000 jobs): AI was mentioned, but main driver was profitability push
  • Meta (planning significant cuts): Offsetting AI infrastructure costs, not replacing workers with AI

What This Means for Leadership

As leaders, we need to be honest about what’s happening:

  1. Stop the AI scapegoating - If we’re making cuts for business reasons, say so. Our teams deserve transparency.

  2. Learn from the overhiring mistakes - The pandemic hiring spree taught us that growth-at-all-costs thinking has consequences. Let’s build sustainable teams.

  3. Prepare for continued pressure - Board demands for efficiency aren’t going away. Think strategically about workforce planning.

  4. Support affected team members - Whether someone loses their job to AI or to a market correction, the impact on their life is the same. Lead with empathy.

Let’s Have the Real Conversation

I’d love to hear what others are seeing. Are you experiencing pressure from leadership for “efficiency gains”? How are you communicating with your teams about industry turbulence without creating panic? What are the real drivers of workforce changes at your companies?

The AI revolution is real, but let’s not let it become a convenient excuse for every business decision. We owe our teams—and ourselves—more honesty than that.

Sources: Tech Layoffs 2026 Tracker, Tech Layoffs Analysis, AI Layoffs Data

2

This hits close to home. My startup failed in 2023, but during our growth phase in 2021, I was part of the problem Keisha’s describing.

The Pressure to Hire Fast Was Real

We raised a Series A during peak COVID times, and every investor, every advisor, every board member was telling us the same thing: “Hire now while you can. Talent is scarce. Scale your team.” We went from 8 people to 35 in six months. Looking back, it was reckless.

We hired designers and engineers faster than we could integrate them. We created roles that didn’t need to exist yet. We justified it with revenue projections that, in hindsight, were wildly optimistic. And when the market shifted? Those same advisors were suddenly quiet about the hiring spree they’d encouraged.

Have We Actually Learned Anything?

That’s what frustrates me about these 2026 layoffs. The overhiring happened 4-5 years ago. These companies had smart people running them. They had access to better data than my tiny startup ever did. And yet here we are, with the entire industry making the same “correction” at the same time.

It makes me wonder: did anyone actually learn from this? Or will we just repeat the cycle next time capital gets cheap again?

The Design Impact No One Talks About

What worries me now, watching from the design systems side, is what happens to product quality during these mass restructurings. When you cut 20% of your workforce, you’re not just losing bodies—you’re losing:

  • Institutional knowledge about why decisions were made
  • The people who understood user pain points
  • Designers who advocated for accessibility (always first to go, let’s be honest)
  • The cross-functional relationships that made shipping actually work

I’ve seen this pattern in reorganizations: the team gets smaller, the pressure to ship increases, and suddenly accessibility reviews become “nice to have” instead of requirements. User research gets cut. Design systems work gets deprioritized because it’s not “customer-facing.”

The Long-Term UX Debt

Just like technical debt, there’s UX debt. When you cut too deep and move too fast, you accumulate it. Users might not notice immediately, but over 6-12 months, products start to feel less polished, less intuitive, less inclusive.

And here’s the kicker: fixing that debt later costs more than maintaining quality during the restructuring would have. But that’s a problem for Future Company, right?

I don’t have answers, but I’m watching these layoffs with two questions:

  1. Are companies building sustainable teams this time, or just cutting to a number the board approved?
  2. How do we protect product quality and user experience when the pressure is purely about efficiency?

Anyone else seeing the product impact of these cuts in their orgs?

3

Keisha, this analysis is spot-on, and it’s creating real challenges for those of us trying to lead teams through this uncertainty.

The Pressure Is Real, Even in Financial Services

I’m leading a 40+ person engineering team at a major financial services company. We haven’t had mass layoffs—yet—but the pressure from executives for “efficiency gains” is constant. Every quarterly planning cycle, I’m asked to justify headcount. Every project review includes questions about whether we could do this with fewer people.

Here’s the interesting part: we’re in financial services, where regulatory requirements actually constrain how quickly we can change our workforce. We need engineers who understand SOX compliance, banking regulations, audit trails. You can’t just cut 20% of your team and maintain the same regulatory standards.

But that doesn’t stop the pressure.

What the Data Doesn’t Capture

The 55,775 number is staggering, but it doesn’t capture the uncertainty affecting the engineers who weren’t laid off. In my org:

  • People are worried about job security even though we’re stable
  • Morale takes a hit when peers at other companies get cut
  • Recruiting becomes harder because candidates see the industry turbulence
  • Retention risk increases as people start polishing resumes “just in case”

The Mentoring Challenge

As someone who mentors Latino engineers through SHPE, I’m fielding anxious questions weekly:

“Should I stay in tech or pivot to a more stable industry?”
“How do I know if my company is next?”
“What skills should I focus on to be ‘cut-proof’?”

The honest answer is: there’s no such thing as cut-proof anymore. But I can’t say that to someone who just bought a house or has a family depending on them.

How I’m Handling It

Here’s what I’m trying to do without creating panic:

  1. Radical transparency with my team - I share what I know about our company’s financial health and strategic direction. No sugarcoating, but also no fearmongering.

  2. Focus on impact, not headcount - I’m shifting conversations with leadership from “how many people do we need” to “what outcomes are we trying to achieve.” Sometimes that does mean hiring. Sometimes it means better tools or processes.

  3. Cross-training and documentation - If we ever do face cuts, I want my team to be resilient. That means reducing single points of failure and making sure knowledge isn’t siloed in one person’s head.

  4. Support career growth even if it’s elsewhere - If someone on my team is worried about the industry, I help them build skills and connections. If that means they eventually leave for a more stable field, so be it. I’d rather support people than have them leave feeling abandoned.

The Question I Can’t Answer

What I don’t know is how long this climate lasts. Are we in for years of “efficiency” pressure? Or is this a 2026 blip before tech resumes growth?

Either way, Keisha’s point about AI washing is critical. If my leadership ever asks me to frame business cuts as “AI-driven transformation,” I’ll push back. Our teams deserve honesty, even when the truth is just “the board wants lower costs.”

How are other engineering leaders handling team morale during this? What’s working for you?

4

As someone sitting in the C-suite, I need to add perspective from the other side of these decisions—because Luis and Keisha are right about the board pressure, and it’s not going away.

The Board Reality

Every board meeting I attend includes questions about efficiency. Not “are we efficient enough”—but “how are you improving efficiency this quarter?” It’s relentless. And when board members point to companies like Amazon or Meta making cuts, there’s an implicit question: “Why aren’t you doing the same?”

The pressure isn’t coming from a place of malice. Boards are responding to:

  • Investor demands for profitability over growth
  • Economic uncertainty that makes them risk-averse
  • Competitive pressure (if competitors are cutting costs, we should too)
  • Legitimate concerns about whether pandemic hiring levels were sustainable

But here’s what Keisha nailed: the AI washing is real, and it’s coming from the top.

Why CTOs Use AI as Cover

I’ll be blunt about why tech leaders frame layoffs as “AI-driven transformation”:

  1. It sounds strategic - “We’re restructuring for the AI era” plays better with boards and press than “we overhired and now we’re fixing it”

  2. It protects executive reputation - Admitting you over-hired means admitting you made a mistake. Claiming AI transformation makes you look forward-thinking

  3. It might justify future budgets - If you frame cuts as “investing in AI,” you can potentially ask for AI infrastructure budget later

But it’s dishonest, and it creates exactly the fear Luis mentioned among teams.

Strategic vs. Reactive Layoffs

There’s a difference between strategic workforce planning and panic cuts:

Reactive layoffs (what we’re seeing in 2026):

  • Across-the-board percentage cuts
  • Little consideration for which roles are actually needed
  • Driven by hitting a headcount number the board approved
  • Loss of institutional knowledge and critical expertise

Strategic workforce planning (what CTOs should do):

  • Natural attrition where possible
  • Selective reorg based on actual business needs
  • Investing in remaining team members
  • Building resilient teams that can weather cycles

At my company, we’ve avoided mass layoffs by:

  • Slowing hiring dramatically (natural attrition handles some reduction)
  • Being honest with the board about trade-offs (fewer people = slower velocity)
  • Redeploying people from lower-priority to higher-priority work
  • Investing in automation and better tools for the team we have

The Institutional Knowledge Problem

Maya’s point about losing institutional knowledge is critical. I’ve seen companies cut 30% of their workforce, then spend 18 months rebuilding the same capabilities because they lost the people who understood why systems were built a certain way.

One of my former companies did mass layoffs in 2015. We lost the architect who designed our payment system. Nine months later, we had a major outage because no one understood the failure modes he’d designed around. That outage cost more than we “saved” from his salary.

What CTOs Should Be Doing

If you’re in technical leadership right now:

  1. Push back on AI washing - Tell your board the real reasons for any workforce changes
  2. Plan for resilience, not just efficiency - A team cut to bare minimum can’t handle unexpected challenges
  3. Invest in the people you keep - Better tools, better processes, better growth opportunities
  4. Document everything - Institutional knowledge matters more when teams are smaller
  5. Be honest with your teams - They’d rather hear “we’re reducing costs” than wonder if AI is taking their jobs

The Long View

Economic cycles come and go. The companies that build sustainable teams—not just lean teams—will be the ones that thrive when growth returns.

If your board is pushing for cuts, make them strategic. If you’re making cuts, be honest about why. And if you’re using AI as cover for business decisions, remember: your teams aren’t stupid. They see through it.

How are other CTOs navigating board pressure while protecting team morale and capability?

5

Coming at this from the product side, these layoffs create a cascading set of problems that don’t show up in the immediate cost savings but definitely show up 6-12 months later.

The Velocity Paradox

Here’s what I’m seeing: companies cut 20-30% of their workforce expecting to maintain 80-90% of their output. The math doesn’t work that way.

What actually happens:

  • Remaining team members are stretched across more responsibilities
  • Context switching increases
  • Quality drops as people rush to cover gaps
  • Technical debt accumulates faster
  • Innovation effectively stops (everyone’s in firefighting mode)

Within 6 months, velocity isn’t 80% of before—it’s more like 50-60%. And nobody wants to tell the board that the “efficiency gains” actually made the company less efficient.

Survivor Guilt Is Real

The psychological impact on teams that survive layoffs is massurable:

Research shows productivity drops 20-30% in the months after layoffs, even among retained employees. Why?

  • Guilt about keeping their job while friends lost theirs
  • Fear that they’re next if they don’t prove their value
  • Increased workload from covering departed colleagues
  • Erosion of trust in leadership
  • “Resume updating” time instead of focused work

I’ve seen this firsthand. After our last reorg, my engineering partners were constantly distracted, morale tanked, and our Q2 roadmap basically imploded. We delivered maybe 40% of what we’d committed to.

The Communication Vacuum

What makes this worse is how poorly companies communicate during layoffs.

The pattern I see:

  1. Rumors start circulating
  2. Leadership goes silent (“we can’t comment on speculation”)
  3. Layoffs happen with minimal explanation
  4. Survivors are told “focus on the work” with no acknowledgment of impact
  5. Roadmaps don’t change despite losing 30% of the team
  6. When projects slip, management acts surprised

What Product Leaders Should Be Doing

If you’re in product leadership during this period:

  1. Ruthlessly re-prioritize - If you lost 30% of eng capacity, you can’t deliver 100% of the roadmap. Cut scope NOW, not when you miss deadlines.

  2. Over-communicate with stakeholders - The board needs to understand that fewer people means fewer features. Set realistic expectations immediately.

  3. Protect your remaining team - Push back on unrealistic demands. Your job is to shield the team from thrash, not add to it.

  4. Be honest about what’s getting cut - Don’t pretend everything is still on track. Tell sales, marketing, and customers what’s changing.

  5. Invest in team morale - Your best people have options. If they’re miserable, they’ll leave, creating a second wave of talent loss.

The Long-Term Competitive Risk

Here’s what worries me most: while companies are cutting to hit efficiency targets, they’re also cutting their ability to innovate and compete.

Tech markets move fast. If you spend 2026-2027 in survival mode while competitors invest in new capabilities, you might save money short-term but lose market position long-term.

I’m watching companies make cuts that feel like they’re optimizing for this quarter’s numbers at the expense of next year’s competitive position.

The Question for Leadership

Michelle’s point about strategic vs. reactive layoffs is crucial from a product perspective too.

Reactive cuts mean you lose people based on cost, not based on what capabilities you need for your roadmap. Then you’re stuck trying to deliver a product vision with a team that wasn’t designed for it.

Strategic workforce planning means asking: “What do we need to build in the next 2 years, and what team composition supports that?”

But that requires long-term thinking, and when boards are demanding immediate efficiency gains, long-term thinking gets squeezed out.

How are other product leaders managing roadmap expectations and team morale during this period? What’s actually working?