Oracle Cuts 491 Washington Jobs as AI Spending Reshapes Workforce

What happened

Oracle is eliminating 491 jobs in Washington state, according to a Worker Adjustment and Retraining Notification filed with the state's Employment Security Department on March 31, 2026 81114. The cuts hit employees at two downtown Seattle offices — the Russell Investments Center at 1301 Second Ave. and a Fifth Avenue location at 2025 Fifth Ave. — as well as remote workers scattered across the state, including nearly 20 people in the South Sound region covering Olympia, Lacey, Tacoma, Auburn and Bonney Lake 19. Separations take effect June 1, 2026, though workers were notified of their termination on March 31 81011.

Oracle's filing describes the action as "a reduction in force and other terminations," explicitly states there are no bumping rights, and insists the cuts are not tied to relocating or outsourcing the affected jobs 1011. Crucially, the company told the state its two Seattle offices are not closing, even as its footprint and headcount there continue to shrink 8111314.

The Washington filing is one piece of a much larger, companywide restructuring. Business Insider and CNBC reported that Oracle was laying off thousands of employees globally, across the U.S., Canada, India and Mexico, as it works to free up between $8 billion and $10 billion for AI infrastructure spending 91012. Reuters separately reported in early March that Bloomberg had described a plan for thousands of job cuts tied specifically to the cash crunch created by Oracle's data-center buildout, with some reductions aimed squarely at job categories the company expects AI to shrink 16.

Who's affected and why it's happening

The Washington layoffs are concentrated in technical and product roles. GeekWire's count, based on the WARN filing, identifies more than 230 software developers plus 48 additional employees carrying "software development" titles, alongside software-development managers, directors, vice presidents, product and program managers, site-reliability developers, technical and financial analysts, and user-experience developers 8. The Independent cites a somewhat different breakdown of the same filing — 270 software developers, 46 software-development managers/directors/VPs, 40 program managers and 30 product managers 12. The two counts don't match line for line, but both land on the same statewide total of 491 and the same overwhelming concentration in engineering and product functions.

Oracle's own public explanation for why smaller teams can now do more work traces back to comments co-CEO Mike Sicilia made on the company's March 10 earnings call, where he said AI coding tools were enabling "smaller engineering teams to deliver more complete solutions" more quickly 81518. Executive chairman Larry Ellison struck a similar note on that same call, arguing that Oracle's embrace of AI coding tools would insulate it from the so-called "SaaS-apocalypse" that AI is expected to inflict on software vendors more broadly 17.

At the same time, Oracle's finances explain the urgency. The company said fiscal-2026 restructuring costs, mostly severance, could reach $2.1 billion 9. It has floated raising $45 billion to $50 billion in debt and equity to fund its cloud and data-center expansion 1016, tied in part to a reported $300 billion commitment to OpenAI 16. Despite the layoffs, Oracle's underlying business is growing fast: third-quarter revenue hit $17.19 billion, up 22% year over year, cloud revenue rose 44% to $8.9 billion, and remaining performance obligations reached $553 billion 171820. Shares rose more than 5% to 8% on the layoff and earnings news, respectively, even though the stock remains down roughly 25% to 29% for the year 91317.

Where the reporting agrees

Across GeekWire, Reuters, USA Today, The Independent, the Seattle Times (via Chronline), KOMO, Seattle Red and The News Tribune, the core facts line up cleanly: 491 Washington jobs, a WARN filing received March 31, a June 1 separation date, two Seattle offices affected, and explicit language from Oracle that those offices are not closing 8101113141920. Every outlet also connects the cuts to Oracle's AI strategy in some form — either the productivity argument from Sicilia's earnings call about smaller engineering teams, or the capital-reallocation argument that savings are funding data centers 89101215. There's also consistent agreement that this is not an isolated event: Oracle previously cut 161 Washington jobs in August and 101 in October, and the Seattle Times put the cumulative total at 757 Washington jobs eliminated since last year 813. Coverage uniformly situates Oracle within a wider regional wave that includes Meta, Amazon and T-Mobile cutting Washington jobs around the same period 81114.

Where it doesn't

The clearest discrepancy is the scale of the total, global layoff. USA Today cites Morningstar analyst Luke Yang putting the eventual number as high as 30,000 jobs, or about 18% of Oracle's workforce 10. TheStreet also reports "at least 30,000" based on unconfirmed reports 20. But Reuters is more circumspect, attributing the "thousands" figure to CNBC's sourcing rather than confirming a number itself, and noting Oracle declined to comment on the report altogether 9. Oracle has not officially confirmed any global total, so the 20,000-to-30,000 range should be read as analyst estimation and secondhand reporting, not a company disclosure.

There's also a small but real mismatch in how outlets break down the Washington job titles. GeekWire's tally (230-plus developers, 48 more with "software development" titles) doesn't match The Independent's version (270 developers, 46 managers/directors/VPs, 40 program managers, 30 product managers) 812. Both are reading the same underlying WARN filing, so the difference likely comes down to how each outlet grouped overlapping job titles rather than a factual dispute — but readers relying on one outlet alone would get a noticeably different occupational picture.

The most substantive disagreement is interpretive, not factual: how directly AI is actually responsible for these specific jobs disappearing. The Independent quotes H.P. Newquist of The Relayer Group arguing that the Oracle cuts are only indirectly AI-related — the savings fund AI infrastructure, but the layoffs themselves aren't a case of AI directly replacing employees' work 12. That same article quotes Culture Partners' Jessica Kriegel making a similar point: AI isn't yet replacing jobs at scale, but AI spending is forcing tradeoffs that show up as labor cuts 12. CIO's reporting, by contrast, foregrounds Oracle's own framing — that AI coding tools are letting smaller teams do the work previously done by larger ones, which is a more direct substitution claim 158. USA Today's Yang leans toward the direct-substitution reading too, saying software engineering is "most likely" the hardest-hit function because AI coding tools like Codex and Claude Code have measurably improved engineer productivity 10. Reuters, meanwhile, frames the story primarily as a financing and capital-expenditure issue — Oracle needs cash for data centers — with AI-driven job substitution as a secondary factor 916.

The read

The evidence supports a hybrid explanation over either extreme. Oracle's own executives, on the record during an earnings call, said AI coding tools are letting smaller engineering teams ship more product — that's a direct claim about substitution, not just a savings mechanism 8151718. But the company's WARN filing language, its restructuring-cost disclosures, and its simultaneous capital-raising for data centers make clear that this is also, unmistakably, about funding an extremely expensive AI infrastructure bet 91016. Those two things are not competing explanations; they're the same decision viewed from different angles. Oracle doesn't need as many engineers per product as it once did, and the money freed up by that realization is being redirected into chips, power and data centers rather than new hiring.

What the sources don't settle is the ultimate size of the cut. Until Oracle itself confirms a global number, the 20,000-to-30,000 figures circulating in USA Today and TheStreet should be treated as informed speculation, while the Washington total of 491 is the one number every outlet can verify against a public filing. That gap between a documented state-level layoff and an unconfirmed company-wide estimate is itself a useful lesson in how these stories get reported: hard numbers exist locally, where WARN Act disclosure law forces transparency, while the national picture remains dependent on anonymous sourcing and analyst modeling.

For tech workers, the Seattle case is a small but concrete data point in a much bigger argument about AI's labor-market effects. It doesn't show robots taking jobs. It shows a company concluding it can produce more software with fewer people, while that same company simultaneously expands its Nashville office by thousands of positions 20. That combination — contraction in one place, expansion in another, often in different roles and different cities — looks less like an apocalypse and more like the kind of uneven reallocation of labor that recurs whenever a major technology shift changes what a company needs its workforce to do.