Layoff Survivors Report 90-Hour Weeks as AI Gets the Credit

On August 13, reporting came out that should make a lot of tech executives' talking points awkward. Leaders spent the week telling investors that AI has cut the amount of work their companies need done. Their own employees, in the same reporting, described weeks running up to 90 hours.

Those can't both be true. We think the gap between them is where a lot of careers are breaking right now, mostly out of sight.

Across Oracle, Microsoft, Salesforce and LinkedIn the pattern repeats: people come out, the roadmap stays in. AI-linked layoffs have hit roughly 205,000 workers in 2026, and total tech cuts are closing in on the full-year 2025 figure with four and a half months left on the calendar. Some workflows really are faster with AI. Taking that gain as payroll savings instead of shorter weeks was a management choice, and the people who kept their jobs are paying for it in hours.

Executives and employees describe different workloads

The executive version goes like this: AI handles the routine layer, so fewer people can ship the same output. Employees at AI-forward companies describe covering work that used to be spread across bigger teams. AI can draft a test suite or a first-pass marketing brief. It won't sit through the incident review, and it won't take the customer escalation at 11pm.

So when a leader says AI reduced the need for a function, read the claim narrowly. What you can verify is that the budget for that function went down. Whether the work went away is a separate question, and you usually find out about six weeks later, in your calendar.

Oracle cut 21,000 jobs and kept its plans

Oracle is the cleanest example. It has eliminated roughly 21,000 full-time positions, spent most of a $2.1 billion restructuring budget, and is reported to be planning more cuts for September, with some teams facing double-digit percentage reductions. Demand didn't fall. The cuts are happening next to roughly $55.7 billion in AI-related spending that has loaded the balance sheet with debt.

If you work there, read that as a workload forecast as much as a job-security one. A team that loses 10 to 15 percent of its people while its infrastructure commitments grow is being asked to do the same work with fewer hands. The senior engineers who stay become single points of failure on systems that used to have two or three owners.

Cuts elsewhere this month show you which teams are next to overload. Salesforce cut around 1,000 roles in marketing, product and communications. Microsoft is set to cut nearly 5,000 jobs as Xbox downsizes. LinkedIn is shutting its Israeli R&D operation and laying off nearly all of those employees, and whatever those teams built still needs an owner somewhere.

When product and program managers leave, engineers pick up the scoping, the stakeholder updates and the release comms. Surviving marketing and communications staff inherit more brands, regions and launch calendars, with the same approval bottlenecks as before. Close a satellite R&D site and the handover lands on a team in another timezone that got no new headcount. In support and QA, automation takes the volume but not the judgment, so the hard escalations pile up on the few experienced reviewers left.

Toptal sees the same work coming back as contracts

A Toptal report covered on August 14 found experienced tech professionals getting stronger demand even as layoffs speed up. We read that as the back half of the same deal. A company removes full-time roles to hit a headcount target, finds out the work still exists, and buys it back on a contract or fractional basis at a higher rate, in a different budget line.

It's one report, from a company in the business of placing contract talent, so we wouldn't lean on it too hard. It does match what the cuts would predict. The demand is for depth in a system a company can't afford to break, much more than breadth across tools AI already covers. The people getting calls are the ones who can be dropped into a half-abandoned codebase or a half-owned go-to-market motion and steady it without a ramp-up period.

It also explains why this hurts some careers more than others. Senior specialists have pricing power. Generalists in the middle, whose value was coordination and coverage, are being asked to do three jobs for one salary while their employer pays market rate for the fourth.

How to tell your team is absorbing cut jobs

Nobody announces absorption. It shows up as a string of small reorganizations that each look reasonable on their own. The test we'd use is whether commitments shrank in line with the people who left, and in most of this year's cases they didn't. If several of these sound familiar, you're in it:

• Your team lost people and nobody re-scoped or re-dated the quarterly roadmap.
• Backfills only get approved as contractors, agencies or offshore vendors.
• You inherited a system, region or account with no documented handover.
• Leadership cites AI tooling as the reason a vacancy won't be filled.
• On-call went from six or eight people to three or four.
• Performance conversations moved from the quality of your output to raw throughput.

If that list describes your team, get the change in writing first. List what you owned in January and what you own now, with the names of the roles that were eliminated. Send it to your manager as a scoping question, asking which of the new items should be dropped. It forces a real priority call, and it gives you a paper trail for a title or pay conversation later.

Then price yourself against the contract market Toptal is describing. If your employer would have to hire a senior contractor to cover what you've absorbed, that rate is your argument, and a better one than internal band comparisons. Ask for a level change or a retention adjustment tied to the bigger scope. We'd pass on a spot bonus, since it won't follow you to your next job.

Hold on to the one area that makes you hard to replace. Pick a system, domain or customer segment where leadership can't route around you, and defend the time to stay deep in it while coordination work piles up.

Keep your portfolio current, take the recruiter call even if you plan to stay, and know your number before anyone asks for it. The 90-hour weeks in this month's reporting are roughly what burnout looks like two quarters before people start quitting. And absorption tends to arrive ahead of the next round, because companies that cut without re-scoping usually cut again. That's the shape of Oracle's year so far, from the March cuts to the September round.