125,759 by August 6: Why Your Whole Team Hits the Market Together

On August 6, 2026, Layoffs.fyi's counter quietly ticked past the entire 2025 total. Seven months of 2026 had already produced more tech layoffs than all twelve of 2025, and it happened in a week where Zillow, TikTok, Etsy and Google all announced cuts. If you still have your job, the useful question isn't whether your company will be next. It's whether you can differentiate your resume before the twenty people who sit near you write theirs.

The 2026 layoff math, in one table

2026 has already surpassed 2025 in fewer companies with bigger cuts per event, and the daily pace is up 18%. That specific shape, concentrated rather than diffuse, is what creates the cohort problem for job seekers.

Here is the picture as of Aug 6, 2026, pulling from Layoffs.fyi, TrueUp, and Refolk's internal profile index:

Layoffs.fyi and TrueUp disagree on absolute counts (TrueUp shows 174,661 people across 519 events in 2026, using looser inclusion rules), but they agree on direction: faster pace, fewer companies, larger per-event size.

Why "fewer companies, bigger cuts" is worse than the reverse

A 500-person cut from one company is harder to job-hunt out of than five 100-person cuts from five companies, even at identical headcount. The reason is cohort collision: hundreds of near-identical resumes hit the same recruiters, in the same city, for the same roles, in the same two weeks.

The mechanics are ugly:

• Fifty people from one Zillow team all list the same internal tools, the same manager, the same OKRs. Recruiters glaze over by candidate ten.
• Referrals get diluted. The three ex-coworkers who would normally vouch for you are also asking their networks for the same intros, into the same companies.
• Recruiters develop pattern-match fatigue. After the fourth "Ex-Zillow Senior Engineer, 6 years, led search relevance" resume, the fifth doesn't get read.
• Compensation anchoring drops. When a hiring manager sees ten candidates from the same layoff, they assume abundance and negotiate accordingly.

Zillow's Aug 4 announcement (roughly 500 people, about 7% of the company, per CEO Jeremy Wacksman) is the archetype. Oracle's 2026 reduction, which TrueUp puts in the tens of thousands, is the extreme version. If you were in either cohort, the differentiation problem isn't hypothetical, it's whether your resume looks different from the person who sat two desks away.

The Refolk index number that should scare you

In Refolk's index of professional profiles, 1,603 US software engineers describe themselves as "ex-Meta," but only 137 US SWEs total use "open to work" language in their headlines. The visible pool understates the real pool by roughly 10x for any single big-tech alumnus.

That gap has a mechanism. Most laid-off workers:

1. Wait two to six weeks to change their LinkedIn headline, because severance often includes non-disparagement or PR-timing clauses.
2. Keep the old employer listed as "current" while they quietly interview, to preserve the "employed candidate" premium. In a Refolk sample of 25 ex-Meta profiles, 16 still list Meta as current employer.
3. Never turn on the green "Open to Work" ring, because they've seen it hurt friends at senior levels.

So the hashtag you're scrolling isn't the market. The market is the 1,466 people you can't see yet. If you wait until #opentowork trends among your peers to start writing your own resume, you are already behind them by a month.

This is where writing your resume before you need it stops being a productivity cliche and becomes an actual edge. Pasting the job posting into Refolk and getting back a resume built from your own history, rewritten for that specific role, takes the "I'll do it this weekend" excuse off the table. The tailoring is the differentiation.

What the "team reorg" framing does to your resume

When your CEO calls it a "team-level reorganization" instead of a "layoff," your resume loses the clearest excuse recruiters accept. Google used exactly that framing with The Seattle Times for its August cuts, and the phrasing helps Google's PR more than it helps the workers.

The strategic problem: a Zillow ex-employee can write "affected by the August 2026 workforce reduction of ~500 people" and every recruiter in Seattle nods. A Google ex-employee whose team was "reorganized" gets a harder question: "So were you performance-managed out, or was your whole team cut?" That ambiguity is expensive in a screening call.

If you're inside a company that will likely frame cuts as a reorg, your defenses are:

• Bank quantified wins now. Ship metrics you own before the reorg, so your resume anchors on outcomes, not org charts.
• Get external proof. Conference talks, public commits, whitepapers, and blog posts read as "not performance issue" faster than any severance letter.
• Line up references outside your reporting chain. Cross-functional partners (PM, design, data) survive reorgs; managers get swept up in them.
• Write the neutral one-liner. Not "laid off," not "left to pursue opportunities," but a factual description of the org change that a recruiter can repeat to their hiring manager.

The AI-cited layoff paradox

AI is the most-cited reason for 2026 layoffs across every industry, and AI-adjacent skills are also the hottest hiring signal on the same resumes. If you built the AI systems that shrank your team, your resume needs to say that, not hide it.

The trap is defensive language. Workers laid off from AI-cited cuts often try to bury the AI angle, which makes them look like the replaced instead of the replacer. The correction is one line of framing:

Built the internal LLM pipeline that automated 40% of the team's tier-1 workload. Team reduced from 22 to 9 as a result.

That reads as "I did the work that changed the economics," not "the economics changed and I was collateral." Refolk's index confirms hiring is still active for exactly these skills: Amazon, AWS, Google, Uber, and Meta all appear as current employers in the same profile pool that contains thousands of ex-Meta engineers. The demand didn't vanish. It moved.

For a resume after mass layoff, the hierarchy of framings goes:

1. You built the automation. Highest value. Reframes the layoff as a delivery.
2. You operated the automation. Middle. Focus on scale, cost per call, uptime.
3. You were adjacent to the automation. Lowest. Emphasize cross-functional AI literacy, not passive exposure.

Geographic clustering is the escape hatch

California alone has lost over 16,000 tech jobs in 2026, with Meta responsible for about a fifth, and Refolk's index shows ex-Meta engineers concentrate in the SF Bay Area. The cohort you'll compete against lives where you live. Signaling openness to Austin, NYC, or fully remote hits a hiring pool the cohort largely can't touch.

Two moves that actually matter:

• Add a "willing to relocate to X, Y, Z" line under your header. Not "open to relocation" (vague), but three named cities. Recruiter search filters key on city names.
• Delete the metro from your headline if you want remote-only. "San Francisco Bay Area" in your top line pigeonholes you into Bay Area comp bands and Bay Area cohorts.

The Refolk workflow makes this concrete: you paste a posting from an Austin fintech or a remote-first infra company, and the resume that comes back doesn't waste its top third on your Bay Area context. That's the differentiation the cohort can't fake overnight because their profiles are still branded to the old headquarters.

The pre-layoff resume: what to do this week

If your company is on the 2026 watchlist (Oracle, Amazon, Dell, Meta, Workday, GitLab, and Robinhood have all cut in 2026), write the resume before the announcement, not after. The people who land fastest in a layoff cohort job search are the ones who had a tailored resume out the door within 48 hours of the news, not the ones who spent week one processing.

The checklist:

• Export your work history now. Titles, dates, teams, three metrics per role. Store it somewhere your work laptop can't lock you out of.
• Draft three role-target resumes. Not one generic resume: one for your obvious next step, one lateral, one adjacent (a stretch or a pivot).
• Get one metric from every project you shipped this year. If you don't have the number, ask your PM or data partner while you still have Slack access.
• Write the neutral layoff line before you need it. Two sentences, factual, no bitterness. You will not write it well the day it happens.
• Line up five references and tell them nothing. Just check they'd pick up if a recruiter called.

The tailoring step is the one people skip, and it's the one that beats the cohort. Twenty ex-coworkers with the same generic resume look like a cohort. Twenty ex-coworkers whose resumes each read like they were written for the specific posting look like twenty different candidates.

What to watch for the rest of 2026

Expect the cohort effect to intensify, not fade, because the layoffs are consolidating into larger single-company events. TikTok's U.S. Data Security joint venture is closing its Nashville office to streamline operations, per its press officer, which puts a geographically concentrated cohort into a single mid-size market on the same week.

Three things worth tracking:

• WARN filings by state. California, Washington, and New York WARN sites are the earliest hard signal of a coming cohort, ahead of the press release.
• Blind and r/layoffs threads. Not for gossip, for timing. Zillow layoff threads went active on Blind alongside the CEO's memo.
• Trackers that disagree. Layoffs.fyi at 125,759 and TrueUp at 174,661 aren't contradicting each other; they're using different inclusion rules. Watch the delta, because the widening gap is where the "quiet" cuts hide.

The point isn't to doom-scroll the trackers. It's to notice that getting laid off in a wave is now the default experience, not the exception, and the resume that survives it is the one written when you didn't need it yet.

FAQ

How is a layoff cohort job search different from a normal job search?

In a cohort search, you're competing against people with nearly identical resumes, in the same city, for the same roles, in the same two-week window. Recruiter pattern-match fatigue sets in fast, referrals get diluted because your network is being tapped by everyone else too, and compensation anchoring drops because hiring managers assume abundance. The tactical response is aggressive tailoring per posting, expanding geography, and applying within 48 hours of the announcement before the flood arrives.

Should I turn on LinkedIn's "Open to Work" green ring after a layoff?

At junior and mid levels, usually yes; at senior levels and above, usually no. Refolk's index shows only 137 US software engineers use "open to work" headline language, while 1,603 describe themselves as ex-Meta alone, which tells you senior candidates overwhelmingly job-hunt quietly. The green ring can hurt perceived leverage in recruiter conversations. A private "Open to Recruiters" setting plus an updated headline is usually the right compromise.

How do I write a resume after a mass layoff without sounding defensive?

Lead with what you built, not what happened to you. Bury the layoff context in one neutral line ("Role eliminated as part of the August 2026 workforce reduction of ~500 people") and spend the rest of the bullet on quantified outcomes. If the layoff was AI-cited, name the AI system and take credit for building it. Recruiters read defensive language as a performance-management signal, even when it isn't.

Which companies are still hiring ex-big-tech engineers in 2026?

Refolk's index shows Amazon, AWS, Google, Uber, and Meta all appearing as current employers across the same profile pool that contains thousands of recently-laid-off engineers, meaning big-tech is still hiring even while cutting. The pattern to avoid: applying only to companies in the same city as your last employer, because that's where your cohort is applying too. Broadening to remote-first infrastructure and AI-tooling companies opens roles the local cohort largely can't reach.