Tech Layoffs 2026: What Job Seekers Should Do Now

Last updated October 12, 2026.

Tech layoffs in 2026 have cleared the full-year total for 2025, with cross-industry trackers reading past 225,000 job losses. The direction had been improving: the monthly pace cooled sharply through late summer, and September posted the lowest monthly job-cut total in years. But the newest wrinkle is that Amazon has moved back to the front of the major layoff trackers this month, a reminder that one large announcement can interrupt a cooling trend. For a job seeker, the practical takeaway is narrow and unchanged: hiring bars are higher, referral loops matter more, and interviewers expect tighter execution than they did two years ago. The reassuring part is that hiring plans have held up year over year even as headcount gets reshuffled toward AI. This page tracks the current wave and, more usefully, tells you what to change in how you prepare. We update it weekly.

The state of layoffs right now (mid-October 2026)

The headline number is large but no longer accelerating the way it was in spring. Trackers disagree on the decimal while agreeing on the direction. The cross-industry tracker Skillsyncer is the cleanest read on the "record year" claim: as of October 3, 2026, it counted 519 layoff events in 2026, impacting 225,122 workers, averaging about 816 job losses per day. That total clears the same tracker's full 2025 count of 205,773 people.

Tech-only trackers tell a slightly different story. Layoffs.fyi passed its own 2025 tech total back in the summer, in roughly seven months and with fewer announcements, meaning the average cut got bigger. But TrueUp, which casts a wider tech net, has still not crossed its own 2025 line of 245,953 people impacted. The lesson is to treat exact counts as directional. Trackers compile from public announcements, WARN notices, and reporting, so totals differ based on what they count and when. The trend, not the decimal place, is what matters.

There is a second, broader counting story worth understanding. By the all-industry US measure from Challenger, Gray & Christmas, total job cuts are actually down this year: layoffs through September had declined about 40% from the same period a year earlier. That is not a contradiction. 2025 was inflated by enormous federal and government cuts; tech specifically is up, while the economy-wide total is down because last year's biggest driver has faded. Hold both facts at once: tech hiring is harder than two years ago, but the broader layoff panic has eased.

A few patterns are worth naming, because they change your strategy:

AI is now the single most commonly cited reason. Challenger, Gray & Christmas data shows AI has become the leading stated reason for job cuts this year. TechTimes ties the cuts to the roughly $700 billion big tech is spending on the AI buildout. Read the "AI did it" label with some skepticism, though. Several announcements were framed as removing management layers, which is old-fashioned cost discipline as much as automation. Even Microsoft, whose chief people officer said of a 4,800-role reduction that "the roles eliminated today are not being replaced by AI," still invoked AI as the strategic backdrop.
The cuts are broad, not just startups. The largest, best-capitalized companies are the ones making news. This is capital reallocation, not a solvency crisis, and the technology sector has accounted for an outsized share of announced cuts all year.
Some functions are hit harder. Sales, recruiting, middle management, content moderation, hardware, and gaming have absorbed disproportionate cuts. Core AI, cloud infrastructure, and platform engineering roles are being backfilled even at companies announcing reductions.

The uncomfortable summary: there is still real hiring, but it is concentrated, competitive, and skewed toward people who can ship with AI tooling rather than around it.

New this week: Amazon moves back to the top of the trackers

The freshest signal is a name, not a number. Yahoo's tech layoffs tracker now leads its 2026 coverage with Amazon, Xbox, Apple, Oracle, TikTok, and Meta. Three weeks earlier, the same tracker headlined Oracle, Uber, and Apple with no mention of Amazon, so the reordering signals a fresh, sizable Amazon reduction landing in early October. We are not going to quote a precise count we cannot verify yet; the point is directional. A major employer re-entering the headlines is exactly the kind of event that can pause, or temporarily reverse, the cooling trend the September data showed.

That September data is still the most useful anchor for direction. U.S. employers announced 43,281 job cuts in September, down 18% from the 52,881 announced in August, down 20% from the same month last year, and the lowest total for the month since 2022. At the same time, weak seasonal hiring plans meant year-to-date hiring was up just 3% over 2025.

Two structural patterns from earlier in the year still hold. Uber, a consistently profitable company, cut about 3,300 jobs (roughly 10% of its workforce), described as removing layers and simplifying team structures. A profitable company shedding a tenth of its staff to "remove layers" is the clearest sign that 2026's cuts are structural, not a response to a downturn. And buyouts have been replacing pink slips at the top: Microsoft opened a first-ever voluntary retirement program, and Apple's late-August cuts to its Siri, Vision Pro, and AI teams (more than 200 roles) are notable precisely because Apple almost never makes this list.

The more useful signal for candidates is direction. A cooling monthly pace, even with a big Amazon round on top of it, does not mean the bar dropped. Profitable firms are spending on infrastructure, running leaner, and hiring selectively, so getting hired stays hard even as the worst monthly spikes fade.

What this actually changes for job seekers

Layoffs do not make interviews harder in some abstract way. They change specific, observable things about the process. Here is what we see matter in the mock interviews we run every day.

More applicants per opening. A single mid-level backend role now competes against recently laid-off engineers from name-brand companies. That pushes recruiters toward referrals and toward candidates whose resumes require zero interpretation. Your resume has to pass a 10-second scan: shipped systems, measurable impact, current stack.

A higher execution bar in the loop. When a team has more candidates than slots, tie-breakers get strict. Interviewers stop giving credit for "almost solved it" and start weighting clean code, correct complexity analysis, and clear communication under time pressure. The gap between a hire and a no-hire is now often just how well you explained your approach.

Longer processes and more "no decision" outcomes. Backfill approvals move slowly. Expect gaps between rounds, roles frozen mid-pipeline, and offers that take longer to sign off. This is headcount friction, not a verdict on you, so keep multiple processes alive at once.

AI fluency as table stakes. With AI now the top cited reason across this year's cuts, interviewers increasingly ask how you use AI tools, and some now expect AI assistance in take-homes while grading how well you direct and verify it. Being able to say "I use it for scaffolding and test generation, and here is how I check its output" is now a real signal.

Where the hiring still is

Do not read the layoff headlines as a hiring freeze. The same companies cutting one org are hiring in another, and with hiring plans up slightly year over year, there is real demand to chase. Target the functions being funded: AI/ML platform, data infrastructure, security, and cloud reliability. Financial and enterprise players outside the pure-tech bucket, including Bloomberg, Goldman Sachs, and Visa, keep steady engineering pipelines that get overlooked when everyone chases the FAANG names.

If you are aiming at companies in the news for both cuts and hiring, study their loops specifically. Our per-company breakdowns for Amazon, Uber, and Oracle show the exact question mix each uses, and the full company list lets you compare formats and decide where your prep transfers.

How to adjust your interview prep

The instinct in a tight market is to grind more LeetCode. That is half right. Volume without communication practice is the most common mistake we watch candidates make. Rebalance like this.

Area	Old default	What we recommend now
Coding	Grind hard DP and obscure graph problems	Master the common patterns, then practice explaining out loud while coding
System design	Skip until senior	Prepare a basic design story even at mid-level; it is a common tie-breaker
Behavioral	Wing it	Rehearse 6-8 STAR stories, including one about a project that failed
AI usage	Ignore or hide it	Have a clear, honest answer on how you use and verify AI tools

Concretely:

Practice talking while you solve. Record yourself and narrate every step. A useful drill is a 45 minute mock coding block split deliberately: 5 minutes to restate the problem and clarify constraints, 5 minutes to state a brute-force approach out loud, 20 minutes to implement while narrating, 10 minutes to write and run tests including edge cases, and 5 minutes to recap complexity. Going silent for two minutes while you think is exactly the behavior that loses close decisions. You can practice with AI feedback on this narration habit.
Drill the high-frequency patterns, not the exotic ones. Most loops lean on the same handful of categories: arrays, strings, hash tables, two pointers, trees, and a manageable slice of dynamic programming. Check counts by category on the concepts page and prioritize the ones that actually show up.
Time-box aggressively. Amazon-style loops commonly ask two coding questions in about 45 minutes. If you cannot state a brute-force approach, refine it, and code it inside 20 minutes, that is the thing to drill.
Prepare a failure story. With more experienced candidates in the pool, behavioral rounds get more probing. Rehearse against a prompt like "Tell me about a time you shipped something that broke in production," answered in STAR form (Situation, Task, Action, Result) in under two minutes, non-defensively. A specific story about something that broke and what you fixed outperforms a polished win.
Do a full dry run of one target company's loop. Generic prep spreads you thin. Pick one company, learn its format, and simulate the whole thing end to end before you spend a real interview slot learning it live.

FAQ

Are tech companies still hiring in 2026 despite the layoffs?

Yes. The 2026 cuts are largely capital reallocation toward AI infrastructure, not a hiring freeze, and the monthly cut pace cooled into the fall while hiring plans ticked up slightly year over year. Companies announcing layoffs in one division are often hiring in AI, cloud, data, and security in another. The market is competitive, not closed, so target the funded functions rather than assuming everything is frozen.

Should I mention I was laid off in interviews?

Say it plainly and move on. Layoffs in 2026 have been broad and public, reaching profitable companies like Uber, Apple, and Amazon, so being part of a reduction carries little stigma; interviewers care far more about what you shipped and how you talk about it. Keep the explanation to one neutral sentence and spend your time on impact.

Does the current market change what companies ask in interviews?

The questions are similar, but the grading is stricter and communication weighs more heavily because there are more candidates per slot. Expect closer scrutiny on code quality, complexity analysis, and how clearly you narrate your approach. Many loops now also ask how you use AI tools in your workflow, since AI has become the top stated reason behind this year's cuts.

Is it worth applying to companies that just did layoffs?

Often, yes. A company cutting one org frequently backfills or expands another, and internal referral pools shrink right after cuts, which can open external hiring. Just expect slower processes and more mid-pipeline freezes, so keep several applications active at once.

How many people have been laid off in tech in 2026 so far?

It depends on the tracker. The cross-industry Skillsyncer count reached 225,122 workers across 519 events as of October 3, 2026, past its 2025 total of 205,773. TrueUp, which counts tech more broadly, still trails its own full-year 2025 total of 245,953. Meanwhile Challenger's all-industry US count is actually down about 40% year over year, because 2025 was inflated by large government cuts. The gaps reflect different counting methods, not a real disagreement about the trend.