811 Layoffs a Day, 55 Whales: Stop Refreshing Layoffs.fyi

If you still start your morning by refreshing Layoffs.fyi, you are watching the wrong screen. The 2026 shape of tech layoffs is not a stream of 20-person cuts you can pick through with coffee, it is a handful of 5,000-plus events that swallow the tracker feed and close their sourcing windows before you finish reading the comments.

The 2026 layoff shape is five whales and a lot of noise

Fewer companies are cutting deeper, so the tracker feed misrepresents where the sourceable talent actually is. Skillsyncer's 2026 tech layoffs tracker logs 383 layoff events impacting 210,741 workers as of September 17, 2026, an average of 811 job losses per day. In 2025 the same tracker showed 338 events and 205,773 people, or 564 per day. Event count is up 13%. Total displaced is up 2.4%. The daily rate is up 43.8%. Those three numbers only reconcile one way: individual events got much bigger.

Oracle alone accounts for 30,000 of the 210,741, or 14.2% of the year. Add Amazon's rolling 16,000, Meta's 8,000, Microsoft's 9,000, and IBM's 9,000 and the top five whales are roughly 35% of the year in five names.

811

The mechanism is straightforward. Boards that approved 200-person "efficiency" trims in 2023 are now approving 8,000 to 30,000-person restructures tied to AI capex. Oracle's 30,000 is being spent on data-center buildout. Amazon's rolling 30,000-target is funding its AI stack. Meta's February 8,000, a 10% cut, is TBD Lab money. The events are fewer because the CFO conversations are bigger.

Why refreshing Layoffs.fyi daily has negative ROI

Daily tracker-watching costs you the sourcing window, because the strongest candidates in each cohort are gone before the tracker updates. KORE1's reporting puts the median re-placement time for displaced Oracle professionals at 17 to 30 days, and the top decile lands faster than that. By the time an event has 60 comments on Layoffs.fyi, the best names in the cohort have accepted offers.

Here is what actually happens on the ground:

• T+0: WARN filing hits or the internal email lands. Oracle's went out at 6am with same-day cutoff.
• T+2 hours: LinkedIn floods with "Open to Work" banners and post-and-pray posts.
• T+48 hours: Layoffs.fyi entry goes live and the tracker updates.
• T+7 days: First-tier candidates are in final rounds.
• T+17 days: Median offer accepted per KORE1.

If your workflow is "check the tracker in the morning, source in the afternoon," you are consistently entering at T+2 days into a market that closes at T+17. That is the exact gap Refolk closes for post-layoff candidate outreach: describe the person in plain English ("staff-level ex-Oracle Fusion engineer, US-based, willing to move to hyperscaler") and get a ranked shortlist before the WARN filing has been indexed by news aggregators.

Build a 55-company whale watch instead

A whale watch is a pre-loaded list of ~55 companies where concentrated cuts are likely, each mapped to a boolean search, a WARN state, and a target hiring-manager audience. It replaces daily tracker scrolling with alert-driven sprints.

The composition should be roughly:

1. Confirmed whales already in motion (Oracle, Amazon, Meta, Microsoft, IBM). Names you already know, ongoing waves.
2. Reshuffle whales, not shrink whales (Cisco, IBM). Net headcount flat or up, but role composition churning hard, which is where senior IC talent quietly exits.
3. Post-IPO concentration risk. Series D and later, still hemorrhaging, still hiring in narrow slices.
4. Second-tier enterprise SaaS on Oracle's flight path (Workday, ServiceNow, Salesforce adjacencies where AI capex pressure is next).
5. Category-specific certainties like Cerner/Oracle Health, estimated at 8,000 to 10,000 roles on its own.

For each name, you pre-build:

• The boolean, or in Refolk's case the plain-English prompt.
• The WARN state and the notification threshold. California, Texas, Washington, New York, and Massachusetts cover most of it.
• Three landing-pad employers already visible in your data for that company's alumni.
• Two hiring-manager audiences that would pay a fee for that exact cohort.

The Oracle case: 55,017 in the diaspora, 1,867 in engineering

The Oracle cut is the sharpest example of why "one whale" is actually two or three distinct sourcing plays. In Refolk's index, 55,017 US-based professionals list Oracle-specific stack skills (OCI, NetSuite, Oracle Fusion). Narrow to ex-Oracle engineering titles across the US and India and Refolk returns 1,867 profiles, with top current employers already visible: Oracle (still-employed remnants), EPAM Systems, Google, Walmart Global Tech, Meta, and Wipro.

Landing regions matter as much as the count. The top three surfaced by title and location are Bengaluru (6), Hyderabad (3), and Pune (3), with US landings skewing to Sunnyvale, Santa Clara, Austin, Arlington MA, and Brooklyn. Two things fall out of that:

• The India cohort, roughly 12,000 of the 30,000 cut, is where the volume actually is. US sourcers hunting the "Oracle diaspora" as if the 30,000 sat in California are competing over the wrong ~9,000.
• The US rebound is hyperscaler-plus-services (Google, Meta, EPAM), not other enterprise SaaS. That reshapes who the passive-candidate pitch is aimed at.

What the numbers actually say, side by side

The dataset behind the whale watch fits in one table. Print this and put it next to your monitor instead of the Layoffs.fyi tab.

The row that changes behavior is the last one. If the median re-placement window is 17 to 30 days, then any workflow that adds three days of latency between the event and your first message costs you the top decile of the cohort.

Watching Layoffs.fyi daily is watching noise around five signals that matter, three weeks too late.

The four whales worth pre-loading now

Four names carry disproportionate 2026 sourcing weight. Each has a different signal shape, which means each gets a different boolean, a different landing-pad hypothesis, and a different pitch.

Oracle: the archetypal shrink whale

Oracle cut 30,000 globally, roughly 9,000 in the US and 12,000 in India per tech-insider reporting. Revenue and Health Sciences (RHS) and SaaS/Virtual Operations Services (SVOS) each lost about 30% of staff. Termination emails hit at 6am with same-day cutoff, and hiring was frozen across parts of the cloud business. This is the deepest single-company reduction at any enterprise software firm since IBM's 60,000 in 1993. Watch Cerner/Oracle Health separately, estimated at 8,000 to 10,000 additional roles.

Sourcing move: treat OCI, Exadata, Fusion, NetSuite, and Cerner as skills that need translating into AWS/Azure/GCP-friendly impact language. That is a resume problem, not a talent-quality problem, which means the sharpest recruiters get bargain access to fully current engineers who read as "obsolete stack" to a lazy screen.

Amazon: the rolling reshuffle

Amazon reduced 14,000 white-collar roles in October 2025 as part of a 30,000-target restructure and is laying off another 16,000 in the current AI restructure plan. The signal is not one event, it is a 12-month sequence of overlapping cuts, mostly in the Seattle/Arlington VA corridor. WARN filings there will be your best trigger.

IBM: the reshuffle whale that hires while it cuts

IBM cut 9,000 US positions while tripling entry-level hiring and shifting experienced roles to India. Net posture: flat headcount, radically different composition. The displaced are senior US ICs and managers, and the highest-value cohort is the one that will not show up on any "IBM laid off" LinkedIn cluster because they were quietly moved out over a quarter.

Meta: the second wave

Meta cut 8,000 in February 2026, roughly 10% of the company. The alumni cohort is unusually senior and unusually ML-heavy, which means the buyer for that outreach is Series B/C AI startups, not enterprise SaaS.

Map whales to hiring startups, not just to outreach

The whale watch is worth twice as much when each whale is pre-mapped to a set of hiring-manager audiences on the other side of the trade. Layoffs.fyi's post-IPO concentration (128 firms driving 108,459 of 128,536 cuts on their board) means displaced talent skews to senior IC and manager profiles with scale experience. That profile is what Series B/C founders want and usually cannot afford.

Concretely, for each whale on your list, name:

• Three Series B/C companies in the same metro hiring the exact seniority band.
• One late-stage private that just raised and needs the cohort's specific stack.
• One public-company competitor that will absorb the top decile at premium comp.

Then run parallel outreach: candidate side gets a warm message inside 72 hours of the event, hiring-manager side gets a note that says "I have 12 ex-Oracle RHS staff engineers landing on the market next week, want first look?" That is the trade, and it is the one that scales.

This is where Refolk earns its keep for a sourcing team. Instead of maintaining 55 separate saved searches on LinkedIn Recruiter and hoping the alert emails land in the right order, describe each whale's exit cohort once as a plain-English prompt and re-run it whenever the trigger fires.

What to actually do Monday morning

Kill the Layoffs.fyi tab. Open a spreadsheet. Put 55 rows in it. For the first 10, use Oracle, Amazon (both waves), Meta, Microsoft, IBM, Cisco, Cerner/Oracle Health, Salesforce, ServiceNow, and Workday. Fill the other 45 from the post-IPO concentration list on Layoffs.fyi's own board. For each, write:

1. One-line description of the expected exit cohort.
2. WARN state and notification threshold.
3. Three landing-pad employers already visible.
4. Two hiring-manager audiences that would pay for the cohort.
5. A plain-English Refolk prompt you can re-run on trigger.

That is a half-day of setup that replaces roughly 200 hours a year of tracker scrolling, and it is the layoffs.fyi strategy that actually maps to how the 2026 tech layoffs tracker data is shaped.

FAQ

Is Layoffs.fyi still worth checking at all?

Yes, but weekly, not daily, and as a backfill, not a trigger. The site is useful for post-hoc analysis (the 128 post-IPO cut, industry breakdowns) and poor as a real-time sourcing signal because event announcements lag WARN filings and internal emails by 24 to 72 hours. Use it Sunday evening to update your whale watch composition, not Monday morning to source.

How do WARN filings compare as a trigger?

WARN Act filings are the sharpest legal trigger available: employers with 100+ employees must file 60 days ahead of mass layoffs in most US states, so you can see the event before the employees do. California, Texas, Washington, New York, and Massachusetts cover the bulk of tech events, and each state publishes a public database. WARN misses non-US cuts entirely, so for whales like Oracle where 12,000 of 30,000 sat in India, you need social listening in parallel: Blind, r/employeesOfOracle, and LinkedIn "Open to Work" clusters.

Why is Cisco on the whale watch if headcount is up?

Because reshuffle whales produce as much sourceable talent as shrink whales, and often at higher quality. Cisco's net headcount is up versus 2023, but legacy switching roles are being cut to make room for AI networking, custom silicon, and cloud security hires. The displaced engineers are fully current, technically strong, and rarely marked as "laid off" on LinkedIn because they were managed out quietly. That cohort is invisible to Layoffs.fyi and completely visible to a sourcer running the right query.

Does the 17-30 day re-placement window apply outside Oracle?

The KORE1 figure is specifically Oracle 2026, but the pattern generalizes for any large enterprise cut with a strong stack signal. The more specific the stack (Fusion, Cerner, ML infra), the shorter the window and the more valuable a pre-loaded sourcing sprint is. For broader cohorts like Amazon PM cuts, expect closer to 45 to 60 days because the pool is larger and less differentiated.