Oracle's 10-K Math: 30,000 Was a Headline, 9,000 Is Your US Pool

Every sourcer with an OCI req open has a Slack channel full of "30,000 Oracle layoffs" screenshots and a pipeline that has not moved. The number is a TD Cowen analyst estimate that has been laundered into fact. Oracle's own fiscal 2026 10-K, filed June 22, 2026, tells a smaller and far more useful story: a net 21,000 global reduction, of which roughly 9,000 came out of the United States.

The audited number is 21,000, and only 9,000 of it is US

Oracle's FY26 10-K shows global headcount fell from about 162,000 to about 141,000 for the year ending May 31, 2026, with US headcount specifically dropping from 58,000 to roughly 49,000. That is the only audited figure, and it is the one you should be building a pipeline against.

The "30,000" number that has been passed around since March is a TD Cowen analyst estimate, not a company disclosure. It also conflates gross terminations with net headcount change. The 21,000 in the 10-K is net: it folds in unbacked attrition, hiring freezes, and small divestitures alongside the actual RIFs. So the pool of people who were involuntarily separated is smaller than 21,000 globally, and the US slice is smaller than 9,000.

The restructuring line is the tell. Oracle booked $1.84B in severance in FY26 against a plan capped at $2.1B, up from $374M the year before. That is a company that finished the vast majority of its planned cuts inside this fiscal year, not one that will keep printing separation notices through 2027.

R&D and Sales took the bulk, cloud specialists are a slice

If you are only interested in ex-OCI engineers, the 9,000 US figure still overshoots. R&D fell from 50,000 to 43,000 globally and Sales & Marketing dropped from 31,000 to 25,000, per Oracle's own segment data. Together those two functions account for roughly 13,000 of the 21,000 global net cut.

Most departures were legacy-stack R&D roles (on-prem database, middleware, retired product lines) and quota-carrying field sellers, not the OCI infrastructure engineers Oracle spent 2022 through 2024 poaching from AWS, Azure, and GCP at premium comp. In Refolk's index, only 211 US-based senior, manager, or director profiles carry "Oracle Cloud Infrastructure" or "OCI" in their headline or experience and are outside Oracle's current roster. That is roughly 2.3% of the headline 9,000 US cut.

211

Two hundred and eleven is not a rounding error, but it is not thirty thousand either. It is a defensible shortlist you can actually work in a quarter, and it is what you should be pitching to your hiring managers instead of the analyst headline.

Where they went

The destination distribution matters as much as the count. In Refolk's index, the ex-OCI senior US pool is not clustered at the obvious hyperscalers. It is scattered across:

• Systems integrators: Cognizant, Accenture, HCLTech.
• Enterprise infrastructure buyers: Dell Technologies, HDR.
• Oracle-partner ecosystem shops: INFOLOB, Astute Business Solutions, FourthSquare.
• AI-native infrastructure companies: CoreWeave, Anthropic, xAI (the smallest bucket, but the most competitive).

Sourcers who filter only for "currently at AWS, Azure, GCP, or Oracle" will miss most of this pool. The partner ecosystem in particular is a blind spot. INFOLOB and FourthSquare exist to resell OCI, so their engineering staff is by definition ex-Oracle or Oracle-adjacent, and those engineers are reachable without a Big Tech counter-offer.

India is a hiring signal, not a layoff signal

The non-US side of Oracle's headcount grew by about 12,000 in the same fiscal year, with India absorbing the majority. That is the single most misread number in the coverage.

Any US-based ex-Oracle cloud engineer on the market in 2026 was cut inside a deliberate geographic reshuffling, not a broad reduction in force. The company was hiring aggressively in Bengaluru and Hyderabad while it was cutting in Seattle, Austin, and the Bay Area. Which means the US pool skews:

1. Senior: junior roles got moved, not eliminated.
2. Expensive: Oracle paid premium-over-market to pull these people from AWS and Azure in 2022-2024, and they know it.
3. Hyperscaler-adjacent: their prior employer was almost certainly one of the top three clouds.

This is the opposite of the usual "layoff = junior talent flood" pattern. If you are recruiting for a Series C infra company at Series C comp, the US ex-OCI pool will say no politely and take an offer from Anthropic or CoreWeave. If you are recruiting for Anthropic or CoreWeave, this is the cleanest hyperscaler-veteran pool in the market right now.

Any US-based ex-Oracle cloud engineer on the market in 2026 was cut in a geographic reshuffling, not a broad RIF.

The India side of Refolk's index tells the mirror story. Of the 123 US+India ex-Oracle multi-cloud profiles with OCI plus AWS or Azure crossover, the India cohort is concentrated in Bengaluru (5), Hyderabad (3), and Kolkata (3), and the top destinations are Cognizant, Capgemini, and HCLTech, not other hyperscalers. If you are staffing an India delivery center, that flow is a gift. If you assumed ex-Oracle India talent was going to Amazon India or Microsoft India, you assumed wrong.

The 60 to 90 day window is closing

Oracle severance is 4 weeks of base pay plus 1 week per year of service, capped at 26 weeks. A 5-year employee gets 9 weeks. You need 22 years of tenure to hit the cap.

For the median ex-Oracle US cloud engineer cut in the March 31, 2026 same-day 6 a.m. email round (which also hit India, Canada, Mexico, and Uruguay), that means 8 to 12 weeks of runway. Those checks stopped clearing months ago. A separate WARN filing disclosed 491 additional remote Washington-based employees exiting effective June 1, 2026, so a second wave is roughly three months behind the March cohort. KORE1, one of the recruiting shops publicly marketing the pool, has been quoting a "30 to 60 day" window. By Q4 2026, the strong candidates are placed. What is left on the market is:

• Profiles with a specialization Oracle overpaid for and the market does not want (obscure OCI networking primitives).
• Mid-career engineers whose title inflation at Oracle does not survive a resume screen elsewhere.
• Candidates holding out for compensation that no longer exists.

This is the exact gap Refolk closes for teams still working this pool. Instead of running a Boolean against "ex-Oracle AND OCI" and drowning in false positives, you describe the person in plain English and get a ranked shortlist across GitHub, LinkedIn, and the open web.

The cloud infra market that is actually hiring them

Ex-OCI engineers are landing in a specific slice of the cloud infrastructure market: GPU-heavy AI infra companies, the partner integrator ecosystem, and enterprise buyers rebuilding their platform teams. Those are the openings you compete against when you pitch one of these candidates, and the openings you should point candidates at if you are the one doing outplacement.

If you are on the buy side and your reqs are for AWS or Azure pedigree only, widen the filter. The API differences between OCI, AWS, and Azure are surface-level. Networking, IAM, infrastructure-as-code, and Kubernetes patterns transfer one-to-one. An engineer who ran multi-region OCI networking at scale can run multi-region AWS networking after two sprints, and the reverse is why Oracle could poach them in the first place.

What to actually do this week

Stop refreshing the "30,000 Oracle layoffs" news alerts and build the list from the audited number down. Concretely:

1. Anchor on 9,000, not 30,000. Every hiring manager conversation should start with the 10-K figure. If you promise a 30,000-person pipeline, you will not deliver it.
2. Filter by prior employer, not current. The signal is "was at AWS, Azure, or GCP before Oracle." Current employer is often a systems integrator or an Oracle partner shop, which most Boolean searches skip.
3. Segment the US pool by specialization. Networking, IAM, and Kubernetes engineers have the cleanest transfer to AWS-equivalent roles. Database and middleware engineers are a harder sell outside the Oracle ecosystem.
4. Include the partner ecosystem. INFOLOB, Astute Business Solutions, and FourthSquare have absorbed ex-OCI engineers without the compensation reset they would have taken at a hyperscaler. They are reachable and they are underpaid relative to the market.
5. Move fast on the March cohort. Severance for anyone cut March 31 ran out in June for tenures under 8 years. If they are still visibly job-searching in Q4, treat that as a yellow flag and dig in on the reason.
6. Do not chase India for hyperscaler poaching. The India ex-Oracle flow is going to Cognizant, Capgemini, and HCLTech. If you are staffing a US infra team, the India pool is not your pool. If you are staffing an India delivery center, it is the best pool of the year.

The point of anchoring on the SEC filing rather than the analyst headline is that you can defend the number to a CFO. "There are approximately 211 senior US ex-OCI engineers we can name, sourced against Oracle's audited ~9,000 US departures" is a real conversation. "There are 30,000 ex-Oracle engineers in the market" is a conversation that ends when the hiring manager opens LinkedIn.

FAQ

Why is the 30,000 Oracle layoffs figure wrong?

It is unaudited. TD Cowen, a sell-side research shop, estimated 30,000 in March 2026 before Oracle filed its 10-K. When Oracle actually disclosed audited headcount on June 22, the net global reduction was 21,000, and the US portion was roughly 9,000. Analyst estimates are made to move stocks, not to size sourcing pipelines. The 10-K is the number you should quote to hiring managers.

How many ex-OCI cloud engineers are actually reachable in the US?

Refolk's index shows 211 US-based senior, manager, or director profiles with Oracle Cloud Infrastructure or OCI in their headline or experience who are not currently at Oracle. That is the working ceiling for senior-plus ex-OCI sourcing. If you widen to mid-level or include contractors at Oracle-partner shops like INFOLOB and FourthSquare, the pool grows, but the senior slice is where the ex-hyperscaler pedigree lives.

What compensation should I expect ex-Oracle cloud engineers to demand?

Higher than mid-market. Oracle recruited aggressively from AWS, Azure, and GCP during the 2022-2024 OCI buildout and paid premium-over-market to close those offers. Those engineers have anchored their comp expectations to Oracle's offers, which were themselves anchored to hyperscaler total comp. A Series C infra company at Series C comp will lose these candidates to CoreWeave, Anthropic, and xAI.

Is the India ex-Oracle pool worth sourcing from?

Yes, but only for India-based reqs. The +12,000 non-US headcount growth was concentrated in India, so most in-market India profiles left Oracle for adjacent employers like Cognizant, Capgemini, and HCLTech rather than being cut. If you are staffing a Bengaluru or Hyderabad delivery center, the pool is deep and the crossover with AWS or Azure experience is real. If you are staffing a US team, US ex-OCI is a different, much smaller, and much more senior market.