Oracle Cut 21,000 and Kept Filing H-1Bs. Source the April 2026 Cluster.

Oracle's FY2026 headcount fell from roughly 162,000 to about 141,000, a 21,000-person cut, while the company kept filing H-1B paperwork straight through the reduction. A DHS proposed rule cleared OIRA on August 27, 2026 that would strip the 60-day post-termination grace period from H-1B holders. If you source engineers for a living, this is a narrow window that will not repeat.

Why this is a sourcing event, not a news story

Oracle's cut is a sourcing event because the affected engineers are sponsor-ready, geographically pinned by LCA filings, and calendar-pinned by a March 31, 2026 termination date. Everything you need to build the outbound list is already public.

The facts, in order:

• Oracle shed about 21,000 roles (13% of workforce) in the fiscal year ended May 31, 2026. Headcount is now roughly 141,000.
• Severance and exit costs jumped to $1.84 billion, up from $374 million a year earlier.
• The main termination wave went out around 6 a.m. local time on March 31, 2026, across multiple countries.
• Oracle America filed 1,276 LCAs in FY25 and 785 LCAs in FY26, plus 1,101 I-129 H-1B petitions in FY26 (1,090 approved, an approval rate of 99.0%).
• On August 6, 2026, DHS sent a proposed rule to OIRA, "Eliminating the Discretionary 60-Day Grace Period" (RIN 1615-AD22). It cleared review on August 27, 2026.
• Blind and TheLayoff.com posts in early September 2026 allege another 10,000-plus cuts. Oracle has not confirmed a number, target, or date.

The rule is not final. Portability under INA 214(n) is statutory and untouched. But the perception that the window is closing is already changing reply rates, which is the point.

The 3,563 vs 35 problem

Inside Refolk's index there are 3,563 current U.S. software engineers whose profile keywords include "Oracle," but only 35 whose profile mentions OCI or Oracle Cloud Infrastructure specifically. That gap is your entire sourcing strategy in one number.

In a 25-profile sample of the broad pool, 17 still list Oracle as their current employer, meaning most people who ever touched an Oracle stack are still inside the building and are exactly the population about to churn. The OCI-specific slice is small enough to work by hand and defensible enough that a competitor cannot replicate it with a Boolean string in an afternoon.

The 1:22 ratio is the tell. Most of Oracle's H-1B filings are for general SWE and consulting roles, not OCI specialists. If you are staffing a cloud infra team, the 35-person OCI pool is your entire addressable market in the U.S., and it is being handed to you by a layoff calendar.

What LCA data gives you (and what it does not)

LCA disclosure recruiting works because filings list worksite city, wage, job title, and SOC code, but not the beneficiary's name. LCAs give you the role; you still have to join to a person.

Here is what a single Oracle LCA row typically contains:

1. Employer legal name (Oracle America, Oracle Cerner, NetSuite, Oracle Robotics)
2. Job title and SOC code
3. Worksite street address, city, state, ZIP
4. Wage level (1 through 4) and prevailing wage
5. Full-time status and period of employment
6. Case status and decision date

Two free primary sources cover this end-to-end:

• USCIS H-1B Employer Data Hub at uscis.gov/tools/reports-and-studies/h-1b-employer-data-hub, queryable by employer, city, and state, covering FY2009 through FY2026 Q3.
• DOL FLAG LCA disclosure at flag.dol.gov, which includes wage and full worksite address.

The join that nobody does at scale: pull Oracle LCA worksites for FY25 and FY26, then match against LinkedIn "Oracle" alumni within a 30-mile radius whose end date clusters in April 2026 and whose profile shows "Open to Work" or a start-date gap. That is the H-1B layoff sourcing playbook in one sentence.

21,000

The April 2026 end-date filter is a one-click Boolean

The single highest-signal filter for sourcing ex-Oracle engineers is a LinkedIn end-date of April 2026. Termination emails went out at 6 a.m. local time on March 31, meaning the end dates that show up on profiles the next week are almost certainly involuntary and H-1B-clock-eligible.

Most recruiters run "past company: Oracle" and stop. That returns 20 years of alumni. Layer these on top:

• End date between April 1 and May 15, 2026
• Current status: "Open to Work" or no current role listed
• Location within 30 miles of a known Oracle LCA worksite
• Title contains "Software Engineer," "Member of Technical Staff," "Principal," or "Senior Principal"
• Optional: profile mentions OCI, Fusion, Cerner, NetSuite, or Exadata

Kansas City is the underexploited one. Cerner is headquartered there, Oracle Health absorbed 8,000 to 10,000 of the cuts by available estimates, and most sourcers are still running SF Bay and Seattle Boolean. Two named WARN filings from August 2025 give you additional anchor cities: 161 cloud jobs in Seattle and 143 in Redwood City, with separation dates in October 2025.

This is the exact gap Refolk closes on the join step: you describe the person in plain English ("ex-Oracle backend engineer, worked in Seattle or Redwood City, left between March and May 2026, H-1B signals") and get a ranked shortlist back with GitHub and LinkedIn joined, without hand-writing a Boolean string.

The 60-day clock is a psychological window, not a legal one

The 60-day grace period is still available today, but candidates increasingly believe it is not, and that belief is what drives reply rates. As of late August 2026, the DHS rule cleared OIRA review but has not been published, has not gone through public comment, and is not final.

Two things a sourcer needs to understand cold:

• Portability under INA 214(n) is statutory. It lets an H-1B worker start a new job the day a new employer files the transfer petition, before USCIS approves it. The proposed rule does not touch it.
• The 60-day grace period is a discretionary regulation in effect since 2016. Before 2016, the window was 10 days. If the new rule reverts to 10 days, the effective sourcing window compresses from two months to less than two weeks.

The pitch that closes an ex-Oracle H-1B in September 2026 is not "the clock is ticking." It is: "I file the transfer under INA 214(n) portability the day you accept. You can start immediately. The grace period debate does not apply to you." Recruiters who know the statute out-close recruiters who cite the countdown.

The 60-day clock is a psychological pricing window, not a legal one. Price your outreach accordingly.

Oracle is still filing H-1Bs while firing them

The most cited Blind post on the situation reads: "Slap in our face: Oracle reportedly laying off 10k+ employees, while still filing H-1B petitions and LCAs." That is a sourcing signal, not just a grievance.

Oracle America filed 1,101 I-129 H-1B petitions in FY2026 with a 99.0% approval rate. If a company is cutting 21,000 roles and filing 1,101 new H-1B petitions in the same year, the delta is not headcount neutral. It is replacement hiring at different wage tiers or in different geographies. That means the workers being displaced are disproportionately Level 3 and Level 4 (the higher wage bands), which are exactly the transferable, sponsor-ready engineers your clients want.

Peer context matters here. IBM's 2026 pattern cut 9,000 U.S. positions while tripling entry-level hiring and shifting experienced roles to India. Same shape. Same sourcing opportunity for anyone paying attention to the wage-level column in the LCA file.

Worth also watching: in August 2026, DHS proposed a separate rule setting a $103,265 fee for cap-subject H-1B petitions. If that lands, the economics of replacement hiring change again, and the value of an already-sponsored ex-Oracle engineer goes up.

A same-week outbound workflow

The same-week workflow is: LCA pull Monday, LinkedIn and GitHub join Tuesday, personalized outbound Wednesday, portability pitch by Friday. Anything slower and a competitor gets there first.

Day by day:

1. Monday. Pull Oracle America, Oracle Cerner, NetSuite, and Oracle Robotics LCAs from FLAG for FY25 and FY26. Filter to SOC codes 15-1252, 15-1253, 15-1211. Keep worksite city, wage level, job title.
2. Tuesday. Join to LinkedIn: past company Oracle, end date April to May 2026, within 30 miles of an LCA worksite. Add GitHub: users whose bio or recent commits reference Oracle, OCI, Fusion, Cerner, or NetSuite.
3. Wednesday. Deduplicate. Rank by wage level (Level 3 and Level 4 first) and by scarcity (OCI over generic SWE). Aim for a list of 40 to 80 named people, not 500.
4. Thursday. Write outreach that names the specific product they worked on and offers a portability filing on acceptance day. Do not mention the 60-day clock.
5. Friday. Send. Track reply rate by wage level and by product area. Iterate next Monday.

What to do before the rule lands

The single most valuable action this week is to build the April-2026-end-date list and run it against a portability-first pitch, before either the DHS rule publishes or a competitor works the same cohort. Everything else is second-order.

Concretely:

• Pull the LCA join once, save the list, and refresh weekly through October.
• Build a Kansas City list separately. It is the least worked geography.
• Watch TheLayoff.com Oracle board and Blind for the September 2026 wave confirmation. If Oracle names a date, run the workflow again the next morning.
• Track the DHS rule's Federal Register publication. Public comment periods usually run 30 to 60 days. The window between publication and effective date is your last easy sourcing quarter.

FAQ

Is the 60-day H-1B grace period gone?

Not yet. As of late August 2026, DHS sent a proposed rule to eliminate the discretionary 60-day grace period, and OIRA cleared it on August 27, 2026, but the rule has not been published in the Federal Register, has not gone through public comment, and is not final. H-1B workers whose employment ends today are generally still able to use up to 60 days. The narrative shift is real; the legal shift is not, yet.

How do I actually find ex-Oracle engineers on H-1Bs?

Join three public data sources. Pull Oracle LCA filings from flag.dol.gov (worksite, wage, title). Pull USCIS H-1B Employer Data Hub aggregates. Then match against LinkedIn "past company Oracle" filtered to April 2026 end dates and within 30 miles of an LCA worksite. That combination is the closest you can legally get to naming ex-Oracle H-1B holders without inside data.

What is INA 214(n) portability and why does it matter more than the grace period?

INA 214(n) is the statutory provision that lets an H-1B worker begin employment with a new sponsor as soon as the new employer files a non-frivolous transfer petition, before USCIS adjudicates it. It is written into the Immigration and Nationality Act, not into a regulation, so the DHS proposed rule does not touch it. For an ex-Oracle candidate, a recruiter offering a same-day portability filing is offering something legally stronger than a 60-day countdown.

Which Oracle geography is most underworked right now?

Kansas City. Oracle Health absorbed an estimated 8,000 to 10,000 of the total cuts, and Cerner's headquarters is in the Kansas City metro. Most sourcers run Seattle and the SF Bay pipelines. The Kansas City ex-Oracle Health pool is smaller, less contested, and disproportionately senior on the healthcare-tech side.