2026 Tech Layoffs Passed 2025 in August. "Ex-Google" Finds 11.

If you are still typing "ex-Google open to work" into LinkedIn and reading the first 200 results, you are competing over a rounding error of the actual alumni pool. In early August 2026, layoffs.fyi confirmed 2026 tech layoffs officially passed 2025's full-year total of ~245,000 with four months left on the calendar, and the naive company-prefix filter is not just noisy now, it is structurally broken.

This piece lays out why the "ex-Company" search returns garbage in 2026, what the Oracle March 31 cohort looks like as a sharper alternative, and the compound-filter playbook I would run this quarter to actually reach the people who just got walked out.

The scoreboard: 2026 already beat 2025, and the pace is accelerating

2026 tech layoffs overtook 2025's full-year total by early August, roughly four months ahead, across more than 250 companies. TrueUp counts 511 events impacting 173,908 people at 801 per day, up from 674 per day in 2025. That is a 19% jump in daily pace, and per Yahoo Finance a 72% jump in monthly workers impacted (10,217 per month in 2025 vs 17,542 per month in 2026).

The composition also shifted. Average cut size climbed from ~440 people across 278 firms in 2025 to ~518 across 237 firms in 2026. Fewer companies, bigger cohorts. The largest single event is Oracle's roughly 30,000-person cut on March 31, 2026, alongside IBM's 9,000 US positions. Oracle, Amazon, Dell, and Meta account for most of the volume; California alone shed over 16,000 tech jobs, with Meta responsible for about a fifth.

801

Why "ex-Google open to work" now returns garbage

The literal ex-Company open to work filter is a self-selection trap that most laid-off engineers never opt into. It surfaces the tiny slice who rebranded their headline, not the actual alumni pool.

In Refolk's index of US professional profiles, here is the gap between the literal filter and the real cohort:

Eleven people. That is the entire national result set for the phrase every recruiter is pasting into LinkedIn's search bar right now. Meanwhile there are 31,660 US software engineers with Google in their profile, and a nontrivial fraction of them just watched a friend get walked out.

The mechanism is simple: senior ICs do not rebrand. They update start and end dates, maybe flip the green #OpenToWork frame, and go back to job hunting through their network. Rewriting a headline to say "ex-Google" reads as either desperate or performative to the people they most want to talk to. So they do not do it. The LinkedIn open to work filter captures the 0.03% who did.

Eleven people is the entire national result set for the phrase every recruiter is pasting into LinkedIn right now.

The Oracle March 31 cohort is the sharpest signal on the market

The cleanest sourcing target in 2026 is not "ex-Oracle." It is "left Oracle between May 30 and June 15, 2026," which is when Oracle's WARN Act last-working-days clustered after the March 31 announcement.

Oracle's cut was ~30,000 people delivered via a 6 a.m. email from "Oracle Leadership" with no HR warning, effective immediately. TD Cowen estimated 20,000 to 30,000 people, roughly 18% of Oracle's ~162,000 global workforce, spanning the US, India, Romania, and the UK. Concentration was heaviest in RHS (Health Sciences) and SVOS (Server Virtualization OS) divisions, with Blind and r/employeesOfOracle posts reporting 30%+ team reductions. Principal PM Venkatraman Raguraman publicly posted his own layoff on LinkedIn, one of many name-checkable examples if you want to seed a graph search.

Two things make this cohort a sourcer's dream:

1. Hard date boundaries. WARN filings confirm separations by June 1, 2026. If you filter by "end date at Oracle in May or June 2026," you get a real cohort, not a self-selection artifact. If the 60-day WARN notice was skipped, affected employees may be owed 60 days of back pay, which is another reason WARN databases like WARNTracker carry the most reliable dates.
2. Undervalued skill mismatch. Lisa Ellis at MoffettNathanson called Oracle "the only Big Tech company executing a true zero-based-budgeting reset around AI." Translation: the people cut are not the people AI is replacing. Displaced OCI, database, and cloud infra engineers are mispriced, not obsolete.

This is the exact query shape that breaks LinkedIn's built-in search. Describe the person in plain English (role, employer, date window, product area) and Refolk returns a ranked shortlist pulled from GitHub, LinkedIn, and the open web, not the 8-person result set LinkedIn's literal filter gives you for Oracle.

Compound filters that actually work in 2026

Replace the single-token ex-Company search with a compound of four signals: tenure band, cohort date, product-area keywords, and team-level context. Any one alone is weak. Together they cut through the noise.

Here is the mental model I run for sourcing laid off engineers in 2026:

• Tenure band. "3 to 8 years at Oracle" filters out both interns and long-tenured executives who are unlikely to move. IBM's cut, per Kore1, hit senior US ICs while entry-level hiring tripled in India, so the tenure band for IBM should skew 5 to 15 years.
• Cohort date. End date at previous employer within the WARN window. For Oracle: May 30 to June 15, 2026. For Meta's California cuts: mid-2026 filings by state.
• Product-area keywords. "OCI" or "Exadata" or "Fusion Apps" beats "Oracle." "Ads Quality" or "Waymo Perception" beats "Google." The product-area token filters out the generalist noise and pulls the people who actually did the work you care about.
• Team-level context via public signals. GitHub org membership at time of departure, conference talks, patent authorship, papers on arXiv. These are the signals LinkedIn does not index and the LinkedIn open to work filter cannot see.

Not every "ex-*" tag means the same thing

Treat companies as distinct cohorts with distinct sourcing implications, not a monoculture of "laid off tech workers."

• Oracle (30,000 cut, March 31, 2026). Senior US and international ICs displaced. High-value cohort. Product-area filtering is essential because the pool is functionally diverse.
• IBM (9,000 US positions). Senior US ICs displaced, entry-level hiring tripled in India per Kore1. "Ex-IBM US senior IC" is a real, sourceable cohort. The India shift means the US alumni pool skews experienced.
• Cisco. Per Kore1, net headcount is actually up vs 2023. Cisco's "layoffs" are largely reshuffles and voluntary attrition mislabeled. "Ex-Cisco" as a distress signal barely exists.
• Meta (California, mid-2026). Roughly a fifth of California's 16,000+ tech losses. Concentrated geographically, so state WARN filings are unusually precise here.

Grouping all of these under "laid off tech workers 2026" is how you end up sending the same InMail to a Cisco engineer who never actually got laid off and a Meta PM who did. The ex-FAANG candidate pool is not one pool. It is a handful of pools with wildly different dynamics.

The AI-cited cuts are an arbitrage, not a warning

Over 20% of 2026 layoffs were explicitly linked to AI, and 61% of tracked companies cited AI as the major factor, per GoodReturns. This is often misread as "these engineers are obsolete." The mechanism says the opposite.

Oracle fired cloud engineers while committing $50B to cloud infrastructure. The engineers cut are not the ones AI is replacing. They are the ones caught in zero-based-budgeting resets, cost cuts justified with AI narratives to investors, or middle-management compressions. Their skills (distributed systems, database internals, cloud infra) are precisely what the buyers hiring in 2026 want.

If you are a founder or engineering leader, this is the arbitrage: the "AI-cited" tag depresses perceived candidate quality in the market, and the correction is not priced in yet. Filter for AI-cited cohorts at companies with strong infra pedigrees and you are effectively buying a mispriced asset.

2,878x

A 5-step 2026 sourcing playbook

Here is the playbook I would run this quarter to staff an engineering team from the 2026 layoff wave. Each step swaps out a broken 2024-era habit for a 2026-appropriate one.

1. Build a watchlist of cohort-events, not a market scan. Because the market barbelled toward fewer, bigger cuts (from ~440 people across 278 firms to ~518 across 237), a short watchlist covers most of the volume. Anchor on Oracle March 31, IBM 9,000 US, Meta California, Amazon, Dell.
2. Pull WARN filings for date-precise cohorts. WARNTracker for US filings. For Oracle specifically: last-working-days May 30 to June 15, 2026.
3. Query in plain English against a real index. Instead of stacking LinkedIn boolean filters that top out at 11 results, describe the person: role, employer, date window, product area, seniority. This is where Refolk earns its keep, because the LinkedIn search box cannot express "left Oracle in June 2026 and worked on OCI."
4. Cross-reference GitHub. For infra and platform roles, a laid-off engineer's public commit history in the 90 days after their end date is a stronger signal of availability and skill than any LinkedIn frame.
5. Skip the InMail. Warm-intro through a peer. The 11 people who set the open to work frame are drowning in outreach. The 31,660 who did not are reachable through one or two mutual connections and have not been contacted 40 times this week.

The through-line: stop treating "ex-Google" as a filter and start treating it as a starting condition. The real filter is the compound of cohort date, product area, tenure, and public signal, and it lives outside LinkedIn's search box.

FAQ

How do I find the exact Oracle March 31, 2026 cohort without pinging every "ex-Oracle" profile?

Filter on end date at Oracle between May 30 and June 15, 2026 (the WARN last-working-day window), plus a product-area token like OCI, Exadata, Fusion Apps, or RHS. Cross-reference against WARNTracker's Oracle filings for state-level precision. This gets you the actual ~30,000-person cohort, not the 8 US profiles that literally wrote "ex-Oracle open to work" in their headline.

Is the LinkedIn open to work filter useful at all in 2026?

Barely. The green #OpenToWork frame captures a self-selecting slice, and senior ICs generally avoid it because it signals distress to their network. Refolk's index shows 11 US profiles use "ex-Google open to work" versus 31,660 US software engineers with Google in their profile. Use the frame as a tiebreaker on a candidate you already found, not as a primary filter.

Why is "ex-Cisco" different from "ex-Oracle" or "ex-IBM"?

Cisco's net headcount is actually up vs 2023, per Kore1, so its 2026 "layoffs" are largely reshuffles and voluntary attrition mislabeled as cuts in press coverage. Oracle and IBM, by contrast, executed real senior-IC reductions (30,000 and 9,000 US respectively). Treating all three as equivalent "ex-*" pools sends you chasing candidates who never actually left involuntarily.

What is the fastest way to build a 2026 layoff sourcing pipeline this week?

Pick 4 or 5 cohort-events from the top of layoffs.fyi (Oracle, IBM, Meta, Amazon, Dell), pull their WARN filings from WARNTracker for date-precise end windows, and run compound queries combining end-date + product-area + tenure band against a real index rather than LinkedIn's native search. You will have a ranked shortlist of a few hundred real matches in an afternoon instead of scrolling through 31,660 undifferentiated Google alums.