85,000 tech workers were laid off in Q1 2026. Where did they go?

85,156 people. 208 companies. That's the Q1 2026 tally from TrueUp's Layoffs Tracker, and it's already on pace to match 2024's full-year total.

But this is a different kind of layoff cycle than the one in 2022. That year felt like panic. Companies had overhired during the zero-interest-rate era and were correcting hard. In 2026, the companies doing layoffs are posting record quarterly earnings. They're simultaneously investing over $100 billion in AI infrastructure. They're cutting roles in one org while hiring aggressively in another.

The overall tech workforce is still growing. CompTIA's State of the Tech Workforce report puts growth at 1.9%, with the total reaching 9.8 million workers. And 87% of tech leaders say they're confident about 2026. So what's happening? Roles are shifting. Certain functions are being automated or consolidated. New functions are being created around AI tooling, ML infrastructure, and developer platforms. The net number is positive, but the churn is very real. 85,000 experienced engineers had to go somewhere.

Here's where they went.

Where displaced engineers actually went

Contract and freelance work

This is the biggest shift from previous layoff cycles. Experienced engineers with 5-15 years at companies like Google, Meta, and Amazon are choosing contract work over jumping back into another full-time search. The math makes sense for them. Senior contract engineers command $150-250/hr. A 30-hour week at $200/hr grosses $312K annually, with no on-call rotation and no performance review cycle.

There's a psychological element too. After two rounds of layoffs in three years, the stability promise of big tech feels hollow. Why go back to a company that might cut your team in 18 months when you can diversify across three or four clients? The downside is benefits and equity. The upside is control. A lot of senior engineers are choosing control.

Startups

Engineers who spent years at large companies are joining Series A-C startups, often at lower base salary but with meaningful equity. What they bring is hard to hire for directly: they know how to run an on-call rotation, set up CI/CD that actually works at scale, and design systems that won't fall over at 10x traffic. That operational maturity is worth more than any technical interview can measure. Startups know this. The smart ones are moving fast to close these candidates while the window is open.

Building their own projects

Some are taking 3-6 months to build and ship their own products. Savings from FAANG compensation (often $300-500K/year) give them runway. Their GitHub profiles light up during this period. They're pushing code daily, contributing to open source projects they'd been too busy for, and building in public for the first time. This group is especially interesting from a sourcing perspective because they're doing their best visible work right now.

Boomerang hires

A meaningful percentage return to the same company within 6-12 months, sometimes in a different org or at a renegotiated level. Companies that laid off 500 people in January are hiring 200 in June, sometimes for the exact same function with a slightly different title. It's cynical. It also happens constantly.

The bifurcation of the tech hiring market makes all of this more confusing than it needs to be. The market for generic engineering work is genuinely soft. The market for engineers with specific domain knowledge and architectural judgment is still extremely tight. Both things are true at the same time.

The sourcing opportunity

If you're a recruiter at a Series A-C startup, this is a window. Engineers who were previously impossible to reach, buried inside Google or Meta with no LinkedIn presence and no reason to respond to InMails, are now visible. And reachable.

Their GitHub activity often spikes during career transitions. Open source contributions go up. Side projects appear. They participate in communities they'd been too busy for. For sourcing tools that track public code activity (riem.ai analyzes 30M+ GitHub events per month for exactly this purpose), these transitions create a strong signal.

The numbers support acting now. 61% of companies plan to increase permanent headcount in H1 2026, according to Robert Half. That means competition for this displaced talent will intensify. 65% of hiring managers already say finding skilled professionals is getting harder (CompTIA). And 70% of software engineers are passive candidates per AIHR. Right now, a larger share than usual is in active transition, which means they're more responsive to outreach than they would be in a normal quarter.

But this window is 3-6 months. After that, most settle into a new role or a long-term contract and go quiet again. The engineers who are currently building in the open will go back to building behind closed doors.

How to reach them

The worst thing you can do is send a generic "I saw you were recently at Google" message. These engineers are getting dozens of those right now. Every recruiter on LinkedIn can see that someone changed their status. That's table stakes, and it's not enough.

What works: reference something specific from their recent public work. "I saw your PR to the OpenTelemetry Python SDK last week" is a message that shows you did real research. It signals that you understand what the candidate actually does, which immediately separates you from the 30 other recruiters in their inbox.

The data backs this up. Outreach that references specific GitHub contributions achieves a 30% response rate according to Codility research. Generic LinkedIn InMails average 10.3% per LinkedIn's own benchmarks. That's a 3x difference from a single change: making the message about their work instead of about your job opening.

Keep it under 400 characters. Be direct about the role and why their specific background fits. Don't ask to "hop on a quick call to learn more about what you're looking for." Tell them what you're building, why their work caught your attention, and what the role pays. Respect their time. They'll respect yours back. For more on what makes developer outreach emails actually work, we wrote a full breakdown.

FAQ

How many tech workers were laid off in 2026?

85,156 tech workers were laid off at 208 companies in Q1 2026, according to TrueUp's Layoffs Tracker. These layoffs occurred during a period of record corporate profits and over $100 billion in AI infrastructure investment. The overall tech workforce is still growing at 1.9%, reaching 9.8 million workers per CompTIA's State of the Tech Workforce report.

Are laid-off FAANG engineers going into contract work?

Yes. A significant portion of experienced engineers from Google, Meta, Amazon, and similar companies are choosing contract and freelance work over immediately seeking another full-time role. Senior contract engineers command $150-250 per hour. After two rounds of layoffs in three years, many prefer the flexibility and risk diversification of working with multiple clients.

Is 2026 a good time to hire engineers who were recently laid off?

Yes. Engineers who were previously unreachable inside large companies are now visible and more responsive to outreach. 61% of companies plan to increase permanent headcount in H1 2026 (Robert Half), so competition for this talent will intensify. The window to reach recently displaced engineers is roughly 3-6 months before they settle into new roles and go quiet.

How do you find and reach recently laid-off engineers?

Track public code activity rather than LinkedIn profiles. Engineers in career transitions often increase their GitHub contributions through open source work and side projects. When reaching out, reference something specific from their recent work. Outreach referencing GitHub contributions achieves a 30% response rate (Codility), compared to 10.3% for generic LinkedIn InMails (LinkedIn benchmarks). Keep messages under 400 characters and be direct about the role.