Tech layoffs in 2026, and the first 30 days after one

Tech layoffs 2026 already read worse than 2025 by any tracker’s count, and our own Search Console data, pulled on 6 September 2026, shows the query “ai layoff tracker” getting 3 impressions at an average position of 42 across three monitor runs in the last 45 days. Nobody’s clicking from page four, but the searches keep coming, which tells you something about how many people are checking a tracker instead of a newsfeed. That’s a smarter habit than it sounds, because tracker numbers and headline numbers disagree constantly, and the gap matters if you’re trying to read the market correctly.

Here’s the actual disagreement. KRON4 reported in 2026 that tech layoffs had already topped 100,000, citing tracker data. Other trackers running the same year land at different totals, some over 170,000, because each one counts differently: some count announced cuts, some count confirmed ones, some lag by weeks. Neither number is wrong, exactly. They’re measuring slightly different things with slightly different clocks.

What the tech layoffs 2026 numbers actually mean

The honest summary is that 2026 layoffs are running ahead of 2025’s monthly pace by a wide margin, and trackers broadly agree on direction even where they disagree on the exact total. What’s new this year, compared to the 2022 to 2023 wave, is the stated reason. A meaningful share of 2026 layoff announcements cite AI or automation explicitly, alongside the usual language about restructuring and cost discipline.

I’d treat any single tracker total as an estimate, not a fact, and say so if you’re quoting it to someone. The order of magnitude (tech layoffs are elevated in 2026, materially above 2025) is solid. The third-digit precision isn’t, and anyone presenting a tracker number as exact is skipping a caveat the tracker itself usually states.

None of that changes what to do if it’s you. So here’s the plan.

Week one: paperwork, not job boards

The instinct is to start applying immediately. Don’t, not yet. Week one is administrative, and skipping it costs money later.

Get the severance terms in writing and read them twice, specifically the health cover end date and whether it’s COBRA-style continuation or something else. In the US, a layoff commonly comes with what companies now call a non-working notice period, similar to garden leave, where you stay on payroll and keep benefits without duties. Amazon’s 2025 to 2026 layoffs reportedly included a 90-day non-working notice with full pay and stock vesting for some roles, which is a materially different situation than a same-day termination. Know which one you got before you plan anything else.

File for unemployment benefits the same week if you’re eligible, not after you’ve tried job hunting for a month and come up empty. It’s not an admission of anything. It’s a form.

Ask HR for a reference contact and get it in writing while the relationship is still warm. People forget this and regret it three months later when the goodwill has cooled.

If you’re on H-1B, the clock runs differently

If you’re on H-1B, the clock on week one runs differently and faster. Federal regulation gives you a discretionary grace period of up to 60 consecutive calendar days after your last day of employment, or until your I-94 expiry, whichever comes first, to find a new sponsoring employer, change status, or leave the country. That’s calendar days, not business days, and it starts the day after your last day of productive work, not the day severance runs out. The grace period keeps your status intact. It does not authorize you to work, which trips people up constantly, since the two sound like the same thing and legally aren’t. Our H-1B guide for software engineers goes into the transfer mechanics in more detail, and if there’s any chance you’ll be close to that 60-day line, talk to an immigration attorney in week one, not week five.

Weeks two and three: resume and targeting

Rewrite the resume before you send a single application, and rewrite it against the roles you’re actually targeting, not a generic version. A resume optimized for “senior backend engineer” reads differently than one aimed at “staff platform engineer,” even if the same person could plausibly do either job.

Build a target list of 25 to 40 companies, not 200. Wide, unfocused applying to hundreds of postings tends to produce a worse callback rate than a shorter list applied to carefully, because a tailored application takes longer and shows. Rank the list by fit, not by brand name.

Check whether the roles you’re eyeing are real before you spend hours on them. Postings that sit open for months with no hiring activity are common enough in a layoff wave that it’s worth a quick check with a ghost job detector before you invest a tailored cover letter into something that was never going to get filled.

Week four: applications and first interviews

Start applying in volume now, once the resume and list exist. This is also where a tool that submits applications and tracks responses earns its keep, because 30 to 40 tailored applications a week by hand is a full-time job on top of interview prep. Our Auto-Apply product runs a review queue, so nothing goes out without you approving it, and it’s included at 10 applications a month on the free tier, 50 on Starter, up to 400 on Ultimate.

Expect the first interview requests to trickle in toward the end of week four, not the start. Response rates in a layoff wave are slower across the board because everyone else who got cut from a similar role is applying to the same postings you are.

Prep as if the technical bar hasn’t moved, because it hasn’t. A hiring freeze thaw doesn’t mean lower standards, it usually means the opposite, since the company is choosing very carefully after cutting headcount once already this year.

A common piece of advice that doesn’t hold up in 2026

Advice from the 2022 to 2023 wave said pause entirely in week one and just process the news before touching a resume. That advice made more sense when hiring cooled but didn’t collapse. Tech layoffs 2026 are running against a thinner set of open roles, so the dead week costs more than it used to. The paperwork and the emotional processing can happen in parallel, and starting the resume rewrite slowly during week one beats a hard stop followed by a scramble in week two.

What still holds: don’t submit applications in week one, even if the resume draft is ready. The version you’d write three days after a layoff reads differently, usually worse, than the one written after a week of distance, and a rushed first wave of applications to the companies you actually want burns first impressions you don’t get back. Save the good targets for when the resume is done, not for when you’re most anxious to act.

If the search stretches past 60 days, that’s not unusual given 2026’s numbers, and it isn’t a signal that something is wrong with the approach. Our own writeup on bouncing back after a layoff goes deeper on the mental side of a search that runs long, and the state of the tech job market in 2026 covers hiring trends by sector if you’re deciding whether to widen your target list.

Reading a layoff announcement correctly

Company press releases about layoffs use consistent euphemisms, and knowing them saves time. “Organizational simplification” and “reducing layers of management” usually mean middle-management and senior IC roles first. “Reallocating resources toward priority areas” usually means a specific product line is being wound down, and roles tied to it go regardless of individual performance. “Right-sizing for efficiency” is the closest thing to a plain admission that this is about the cost line, not about anyone’s output.

This doesn’t tell you whether you personally were let go for cause or for headcount, and companies are legally careful not to conflate the two even when a manager privately says otherwise. What it does tell you is how to read the next twelve months at that company: a round framed around “simplification” is often followed by a second, smaller round within two quarters. If your severance offer includes a longer notice period or garden leave, that length is sometimes a quiet signal of how much more restructuring is still coming.

Watch for postings that reappear under a new title within weeks of a round. That’s frequently the same headcount, reorganized rather than actually cut, and it’s worth knowing before you assume the door there is closed for a year. A short cooling period, then a quiet reapply once the reorg settles, often beats writing the company off entirely for good.

Why tracker totals undercount the real number

Every tracker cited in this post, and every one you’ll find elsewhere, runs on the same basic method: crawl press releases, WARN Act filings, and news coverage, then add up whatever numbers get publicly reported. That method has a structural bias, and it’s worth naming plainly.

WARN Act filings only cover the US, and only trigger for mass layoffs above a size threshold at a single site. A company quietly cutting 40 people from an office in Pune, Berlin, or a distributed remote team generates no filing at all, and unless a journalist happens to report it, it never enters a tracker’s count. Non-tech companies doing tech layoffs, a bank cutting its internal engineering org or a retailer shrinking its data team, get missed even more often, since trackers built for the tech industry aren’t set up to catch cuts inside companies nobody classifies as tech.

So when a tracker says the year’s total is some six-figure number, read that as a floor built almost entirely from US-based, self-announcing tech employers, not a real headcount of everyone laid off from a technology role worldwide. The true number is higher. Nobody publishes it, because nobody can count it.

None of this makes tech layoffs 2026 feel smaller. It just makes them easier to plan around.