Oracle's Second Wave Hits June 15. The Cerner Talent Won't Last 30 Days.

Oracle's March 31 layoff already filled your LinkedIn feed. The second wave hasn't, and that's the one worth your attention. Roughly 30,000 employees got the 6 a.m. email, but the U.S. workers protected by WARN Act notice are still technically on payroll, with last working days clustered between May 30 and June 15, 2026. They are not on Open to Work. They are not on TheLayoff.com triumphal threads. They are sitting on garden leave with niche skills that haven't been openly available in a decade.

If you're hiring healthcare IT, mid-market ERP, or cloud infrastructure talent, you have about three weeks before this cohort gets absorbed. The recruiters who win this window are the ones who understand that "Oracle layoff sourcing" in May 2026 is not the same job it was in April.

Why the second wave is different from the first

The April flood was the non-WARN cohort: international employees, contractors, and U.S. workers Oracle classified as remote and therefore (legally contestable) not tied to a single site. They updated LinkedIn within hours. AWS, Microsoft, Snowflake, and a long tail of AI startups were in their inboxes the same day. By mid-April, the obvious names were spoken for.

The WARN-protected cohort is structurally invisible to anyone watching the usual signals:

• Their LinkedIn still says "Oracle." They're on payroll until their effective termination date.
• They are not posting "looking for my next chapter" updates yet, because doing so before your last day at Oracle is a good way to lose your severance.
• Their Open to Work badge is off. Their recruiter inbox auto-replies are still the corporate template.
• State WARN trackers list them as a number, not a name. The Kansas City filing shows 539 layoffs at the Hillcrest Road campus. It does not list the 539 people.

539

If your sourcing process starts with a LinkedIn Recruiter search filtered to "open to work," you are going to miss this entire cohort. The people you want spent the last decade inside Cerner Millennium, NetSuite SuiteCloud, or OCI Tier 2 support, and the surface area they leave on the open web is GitHub commits to internal-flavored repos, HIMSS conference talks, patent filings, and Stack Overflow answers under handles that don't match their work email.

This is the exact gap Refolk was built for. You describe the person in plain English ("Cerner Millennium integration engineer, 10+ years, Kansas City area, currently at Oracle Health") and get a ranked shortlist pulled across GitHub, LinkedIn, and the open web, including people whose LinkedIn still says they're employed.

Who actually got cut, and who's still inside

The cuts are not evenly distributed across Oracle. They cluster hard in four areas:

Cerner / Oracle Health (estimated 8,000 to 10,000 cuts, ~30 to 35% of the unit)

This is the most interesting pool on the market right now. Oracle Health lost 57 acute care clients in three years while Epic Systems consolidated share. Cerner Millennium expertise was a closed talent pool: Oracle hoarded it internally for the VA and DoD contracts, and Epic doesn't hire Cerner people, it trains its own. So the engineers coming out of Kansas City have skills that haven't been openly recruitable since before the 2022 acquisition.

If you run a health system still on Cerner, this is your one-time chance to in-house implementation and integration talent. If you're a healthcare IT vendor, this is the cohort that knows where the bodies are buried in HL7 interfaces, CCL reports, and PowerChart customization.

NetSuite (Revenue and Health Sciences, plus India Development Centre)

NetSuite hit $1B in quarterly revenue for the first time in Q4 FY2025, with 43,000 customers across 219 countries. Then Oracle fired a chunk of the people who build and support it. The India Development Centre saw cuts across PM, IC, and manager levels. Revenue and Health Sciences (RHS) lost roughly 30% of staff.

For NetSuite developer recruiting in the mid-market, this changes the math. Implementation partners like Myers-Holum, Big Bang ERP, BlueBridge One, and RSM US are absorbing SuiteScript and SuiteCloud talent fast. If you have a NetSuite implementation queued for Q3, lock the contract before consultants reprice.

OCI Tier 1/Tier 2 support and customer success (6,000 to 8,000)

The least sexy, most undervalued pool. These are the people who actually know how OCI breaks. AWS and Azure recruiters know exactly what that's worth and are moving accordingly.

ERP consulting and Fusion Cloud Applications professional services (5,000 to 7,000)

The SaaS/Virtual Operations Services (SVOS) unit lost ~30% of staff. Fusion ERP implementation talent is now available in volume for the first time in years.

What's still inside (and probably won't stay safe)

Oracle explicitly protected AI data center engineering, security, and database engineering. Those teams are still hiring. But TD Cowen modeling suggests another 10,000 to 15,000 positions could be cut to hit a 25% total reduction. The Microsoft and Meta pattern of repeated cuts every 6 to 9 months is the base case, not the bear case. If you're sourcing into Oracle's protected divisions, build the warm pipeline now. The next email goes out before Q4.

The WARN remote-worker loophole is a sourcing signal

Here's a detail that hasn't gotten enough attention. Oracle classified many U.S. remote employees as not tied to a single site, which the company may argue exempts them from WARN's 60-day notice requirement. Class-action firms are reportedly looking at it. The legal question will take years.

The sourcing implication is immediate: a portion of the WARN-eligible cohort got no 60-day protection and is already on the market without showing up in any state filing. They're motivated. They're fast-moving. They're invisible to recruiters scraping WARN trackers, because they were never on a WARN tracker.

The recruiters who win this window understand that the second wave isn't on Open to Work yet, and won't be until it's too late.

This is why pure list-buying from layoff trackers is a bad strategy here. The trackers capture the legal filings, not the actual market. The signal that matters is "ex-Oracle, hands-on Cerner Millennium or SuiteCloud, posting in r/employeesOfOracle or Blind threads, GitHub activity ticking up in the last 30 days."

Severance is 26 weeks. Your window is shorter than that.

Oracle's package caps at 26 weeks (two weeks per year of service, 8-week minimum). That's notably stingier than Meta's February 2026 package of 16 weeks base plus 2 per year with six months of COBRA. Tenured employees, including 15+ year veterans, have publicly criticized the cap on Blind and TheLayoff.com.

What that means for hiring:

• The senior cohort (15+ years, the deepest Cerner and Fusion expertise) is feeling under-paid out and motivated to land fast.
• "Garden leave" runway is real but short. The May 30 to June 15 cliff is when offers start closing in 11 to 14 days for strong Cerner candidates, based on what implementation partners are seeing.
• Counter-offers from inside Oracle are not a meaningful risk for this cohort. They were just fired.

If you're moving slow because your loop has six rounds and a take-home, you'll lose. The teams winning here are running 2-step loops (technical screen plus onsite) and making offers within a week of first contact.

A practical sourcing playbook for the next three weeks

1. Stop relying on Open to Work

It's a lagging signal in normal markets and an actively misleading one for the WARN cohort. Source on tenure, employer, skill, and recent activity. The fact that someone's LinkedIn still says "Oracle" right now is a feature, not a bug, if their effective termination date is June 1.

2. Mine the right communities

The active discussion is happening in four places: r/employeesOfOracle on Reddit, Blind threads tagged Oracle, TheLayoff.com's Oracle board, and the Cerner Millennium user community on HIMSS forums. People are venting, comparing severance, and (importantly) naming hiring managers who've already reached out. That's a public signal you can act on.

3. Source on artifacts, not titles

For Cerner engineer hiring specifically, "Cerner Millennium" rarely shows up cleanly on a LinkedIn profile. The artifacts that matter: HL7 interface work, CCL (Cerner Command Language) mentions, PowerChart customization, HIMSS talks, and Epic-to-Cerner migration project work. The same goes for NetSuite developer recruiting: SuiteScript GitHub repos, SuiteCloud Developer Network forum activity, and SuiteWorld speaker history are stronger signals than a job title.

This is exactly the kind of multi-source, natural-language search Refolk handles in one query. Instead of building eight Boolean strings across LinkedIn, GitHub, and conference sites, you describe the person and let the tool reconcile the signals.

4. Time your outreach to the cliff

Reaching out on May 28 hits differently than reaching out on June 18. Before the effective date, candidates are constrained by what they can say without jeopardizing severance. Right after, the floodgates open and so does competition. The sweet spot is the week before the effective date with a low-pressure message: no pitch, just an offer to talk after their last day.

5. Build a warm pipeline into the still-employed

The TD Cowen 10,000 to 15,000 second-cut projection is your pipeline plan for Q3 and Q4. Identify Oracle's protected divisions (AI infra, security, database engineering) and start relationships now, not in a panic when the next email goes out. The candidates worth hiring are the ones you'd want even without a layoff catalyst.

The structural opportunity nobody's pricing in

Cerner expertise is structurally scarce, not cyclically cheap. Epic dominates net-new EHR wins. Cerner specialists were a closed pool. The 8,000 to 10,000 people leaving Oracle Health are the largest single release of that expertise into the open market in the product's history, and probably the last one of this size, because TD Cowen has reportedly floated a Cerner divestiture entirely.

NetSuite is the inverse story. The product is growing ($1B/quarter, 43,000 customers) while the headcount that supports it shrinks. Mid-market companies running NetSuite are about to feel that as longer support tickets and slower implementations from partners. The companies that hire NetSuite talent now lock in a margin advantage for the next 18 months.

Both of those are real businesses you can build hiring decisions around in the next three weeks. After June 15, the talent is still findable, but the price and the speed are not the same.

FAQ

How is the WARN Act different from a normal layoff for sourcing purposes?

WARN requires 60 days of notice for covered U.S. layoffs at a single site of 50+ people. Affected workers stay on payroll during that period, which means their LinkedIn, email, and benefits all still say "current employee" until the effective date. For WARN Act tech layoffs, that creates a sourcing window where the cohort is technically still employed but functionally on garden leave. They're reachable, motivated, and invisible to any tool that filters on Open to Work or recent job changes.

Why focus on Cerner specifically when there are 30,000 cuts to choose from?

Because Cerner Millennium expertise is the rarest skill in the bunch and the one that's about to disappear from the open market. Epic doesn't hire Cerner engineers, it trains its own. Oracle was the only large employer of Cerner specialists, and it just released 8,000 to 10,000 of them. Health systems and healthcare IT vendors still running Cerner installations have a one-time chance to in-house this talent. NetSuite and OCI engineers are valuable, but they'll be available again in the next cycle. Cerner engineers won't be.

What's the right outreach message for a candidate who's still technically at Oracle?

Short, low-pressure, and aware of their constraints. Acknowledge you saw the news, don't ask them to confirm anything that could affect severance, and offer to talk after their effective date. Lead with a specific reason you reached out (a project, a paper, a conference talk), not a job description. The candidates getting 40 generic pitches a week ignore them all. The one tailored message that names their actual work gets the reply.

Is Refolk useful for ongoing pipelining or just the layoff window?

Both, and the layoff window is just where the gap is most obvious. Anytime you're sourcing for skills that don't map to clean LinkedIn titles (Cerner Millennium, SuiteCloud, OCI internals, founding AI engineer profiles), title-based search misses most of the market. Refolk lets you describe the person in plain English and pulls signals from GitHub, LinkedIn, and the open web in one query, which is the right shape for ongoing pipelining into protected Oracle divisions before the next wave hits.