Tech Layoffs in 2026: What Job Seekers Should Do Now

Last updated August 24, 2026.

Tech layoffs in 2026 have already beaten the full-year total for 2025, and it is only late August. The tech-focused tracker Layoffs.fyi had logged roughly 125,759 tech workers cut through August 6, edging past all of 2025 in about seven months, while broader cross-industry trackers read north of 205,000. For a job seeker, the practical takeaway is narrow: hiring bars are higher, referral loops matter more, and interviewers expect tighter execution than they did two years ago. The one bit of good news this week is that the monthly pace is cooling and hiring announcements are ticking up. 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 (August 2026)

The headline number is large but no longer accelerating the way it was in spring. Two trackers frame the year. The tech-only tally from Layoffs.fyi reached about 125,759 employees across 264 companies through August 6, 2026, which already exceeds the roughly 122,606 workers the same tracker recorded for all of 2025, and it got there with fewer company announcements, meaning the average cut is bigger. A cross-industry tracker, Skillsyncer, counted 205,832 workers across 322 layoff events as of August 10, 2026, an average near 927 job losses per day. The tech number is a subset of the cross-industry number; both point the same way.

Treat the exact counts as directional, not precise. Trackers compile from public announcements, WARN notices, and reporting, so their totals differ based on what they count and when they log it. The trend, not the decimal place, is what matters.

The single largest round of the year remains Oracle. Forbes reported its April cuts at around 30,000 roles tied to a cloud and AI data-center buildout rather than a retreat. Oracle's own fiscal 2026 annual filing disclosed that AI adoption across its operations has resulted, and may continue to result, in workforce reductions, and reporting put its severance costs near $1.84 billion for the year, up sharply from roughly $374 million the prior year, which is the clearest financial signal of the scale. Behind Oracle, Microsoft cut about 4,800 jobs in early July as its Xbox unit downsized (CNBC), and cross-industry trackers attribute other large 2026 cuts to Amazon, Meta, Dell, and Nokia. Google, TikTok, Zillow, Etsy, Intel, and Samsung round out the names in the news.

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

AI is the most commonly cited reason. Challenger, Gray & Christmas reports that AI has led the stated reasons for US job cuts for a fifth straight month through its July report. Companies are reallocating headcount toward AI infrastructure, with TechTimes tying the cuts to the roughly $700 billion big tech is spending on the AI buildout, while trimming roles they consider automatable: content moderation, support, QA, data entry, and some traditional software work. Read the "AI did it" label with some skepticism: several August announcements, including Zillow's, were explicitly framed as cost discipline rather than automation, which suggests the label is sometimes a narrative choice.
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. TechTimes reported tech accounted for roughly 31% of all US layoffs in the first half of the year.
Some functions are hit harder. Sales, consulting, recruiting, middle management, content moderation, 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: the milestone is confirmed, and the monthly pace is cooling

Two things stand out since our last update. First, the milestone is now confirmed across multiple outlets: 2026 tech layoffs officially blew past the entire 2025 total, a point Futurism and other trackers reported in the past week. The recent cluster driving it: Zillow announced just over 500 job losses on August 4, framed by its CEO as a disciplined cost move rather than an AI story; TikTok's US venture is closing its Nashville office and cutting about 250 roles, with the office set to shut October 5; and Google trimmed hundreds in a team-level reorganization (Fast Company), with Etsy adding to the tally.

Second, and more useful for candidates: the monthly pace is slowing. Challenger's data showed June cuts cooling to 45,849, down 53% from May, and its July report was titled around layoffs falling while hiring plans pick up. Record year-to-date totals and a cooling monthly pace are not a contradiction. They mean the worst monthly spikes may be behind us while the bar to get hired stays high. That is the exact market you will interview in for the rest of the year: profitable firms spending on infrastructure, running leaner, and hiring selectively.

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 not personal; it is headcount friction. Keep multiple processes alive at once.

AI fluency as table stakes. With AI cited across so many of this year's cuts, interviewers increasingly ask how you use AI tools, and some now allow (or 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. 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 rather than preparing generically. Our per-company breakdowns for Amazon and Oracle show the exact question mix each uses, and you can compare formats across the full company list to 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 to run one 45 minute mock coding block on a timer and split it 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 and what you would improve. If you go silent for two minutes while thinking, that 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. You can see 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 concrete prompt like: "Tell me about a time you shipped something that broke in production. What happened, what was your role, and what did you change afterward?" Answer it 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, so companies announcing layoffs in one division are often hiring in AI, cloud, data, and security in another. Challenger's July data even showed hiring plans picking up as the monthly layoff pace cooled. 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, 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.

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?

Through August 6, 2026, the tech-focused Layoffs.fyi tally reached about 125,759 workers across 264 companies, which already passes the full-year 2025 total of roughly 122,606 in about seven months. A cross-industry tracker put the all-industry figure at 205,832 across 322 events as of August 10, 2026. The gap reflects different counting methods, not a real disagreement about the trend.