Oracle Severance Package 2026: 30K-Cut + 4+1/Yr Cap Decoded

Oracle’s Single-Email March 2026 Layoff

On March 31, 2026 at approximately 6 a.m. local time, Oracle Corporation terminated approximately 30,000 employees via a single email from “Oracle Leadership” — no advance HR or manager notification, no division-by-division rollout, no codenamed program. The single-email cut was the largest workforce reduction in Oracle’s 49-year history, eliminating roughly 18% of the company’s ~190,000 global headcount.

Bloomberg broke the story on March 5, 2026, citing sources describing reductions “in the thousands.” The actual scale was 5-10x larger than initial reporting. CNBC, TIME, TechCrunch, and the Financial Times subsequently corroborated the 30,000 figure, though Oracle has not officially confirmed the exact headcount in any SEC filing.

The structural distinctive: Oracle is cutting from a position of historic financial strength. The Q3 FY2026 earnings release on March 10, 2026 reported revenue of $17.2 billion (+22% YoY), GAAP net income of $3.7 billion (+27%), and remaining performance obligations of $553 billion (+325%). Oracle raised $30 billion in debt and equity in February 2026 and guided $50 billion in FY2026 capex for AI infrastructure including the Stargate Project partnership. Three weeks after that earnings release, the company terminated 30,000 employees.

Oracle’s Cash Severance Formula: 4 + 1/Yr Capped at 26 Weeks

Multi-source-confirmed reporting describes a uniform structure across the affected divisions:

• Base: 4 weeks of pay for the first year of service
• Accrual: 1 additional week of pay per additional year
• Cap: 26 weeks total

The formula is not SEC-filed by Oracle. The figures come from TechCrunch’s May 8 2026 reporting on the 600-employee collective petition, TIME’s April 30 deep coverage, and IndexBox aggregate analysis. Oracle’s CEO has publicly refused to negotiate collectively on package improvements, though some individual case-by-case appeals have produced accommodations per published reports.

The cap binds quickly. A 22-year veteran accrues 25 weeks under the formula and the cap doesn’t bind. A 25-year veteran accrues 28 weeks and receives the 26-week ceiling. Long-tenured affected staff lose 2-5 weeks of formula-derived severance to the cap — measurable money relative to the formula but small relative to the unvested-equity exposure (covered below).

Worked Examples: Severance by Tenure at Oracle

The published formula produces the following outcomes assuming standard eligibility:

Tenure	Weeks under formula	Weeks paid (after cap)	Typical pay range (Austin / Bay Area corporate base salaries)
1 year	4 weeks	4 weeks	$13,000 – $25,000
3 years	6 weeks	6 weeks	$19,000 – $40,000
5 years	8 weeks	8 weeks	$26,000 – $55,000
8 years	11 weeks	11 weeks	$36,000 – $75,000
12 years	15 weeks	15 weeks	$48,000 – $100,000
15 years	18 weeks	18 weeks	$58,000 – $120,000
20 years	23 weeks	23 weeks	$74,000 – $155,000
23+ years	26+ weeks (formula)	26 weeks (capped)	$84,000 – $175,000

Ranges reflect typical base salaries across Oracle’s Austin and Bay Area corporate populations. The Levels.fyi Austin median for senior software engineers is approximately $203K; IC-1 through IC-4 levels span roughly $160K-$266K total compensation. Sales force OTE ranges substantially higher ($180-$450K) but base salary alone (the severance calculation basis) clusters below total comp.

Oracle Severance vs Peer Tech Employers: A Lower Cash Floor

The major US tech employers converge on similar formula architectures but Oracle’s cash baseline is materially below peer norms.

Company	Base	Per year of service	Cap	COBRA subsidy
Oracle	4 weeks	1 week	26 weeks	1 month
Amazon	varies by L4-L7+	varies by level	8-20+ weeks	3 months
Microsoft	2 months	additional weeks per tenure	6 months continued health	6 months
Google	16 weeks	2 weeks	typically 24-32 weeks	6 months
Meta	16 weeks	2 weeks	typically 20-32 weeks	6 months

The contrast: Oracle’s 4-week base is one-quarter of Google or Meta’s 16-week base. Oracle’s 1-week-per-year accrual is half of Google or Meta’s 2-week rate. Oracle’s 1-month COBRA subsidy is one-sixth of Google or Meta’s 6-month subsidy. The Oracle package is structurally less generous than peer tech employer norms across multiple dimensions simultaneously.

For affected Oracle employees, the comparative context matters. The structural argument: peer tech employers in similar financial-strength positions have published more generous packages. Oracle’s documented Q3 FY2026 strength removes the financial-distress justification for the below-peer formula. This is the basis for above-formula negotiation asks. The 600-employee collective petition specifically requested 16 weeks + 2 weeks per year (matching Google/Meta) plus 6 months subsidized COBRA (matching peer norm).

The RSU Forfeiture: The Most Controversial Element

Oracle’s severance plan provides no RSU acceleration. Unvested RSUs forfeit at termination per the standard plan document. For affected employees with material unvested RSU positions, this forfeiture is often the single largest financial impact of the layoff — substantially exceeding the cash severance in dollar terms.

TechCrunch’s May 8 reporting documented specific cases of long-tenured employees losing approximately $1 million in unvested stock that was within months of vesting. RSU compensation represents roughly 70% of total compensation for senior IC and management staff per Levels.fyi data.

The 600-employee collective petition (April 17, 2026) specifically requested 6-month RSU acceleration as part of the broader package improvement request. Oracle publicly refused to negotiate collectively, but individual case-by-case appeals have produced some accommodations per published reports — typically partial cash buyouts in the 25-50% range of unvested value rather than full acceleration.

For affected employees with material unvested positions:

1. Document the forfeiture math precisely: pull RSU grant history, calculate dollar value at current Oracle stock price of each unvested tranche
2. Frame the ask in equitable-separation terms: “Equitable separation should reflect at least partial recognition of unvested value given Oracle’s documented Q3 FY2026 financial strength”
3. Cite the collective petition context: 600+ colleagues raised the same concern; some individual accommodations have been granted on appeal
4. Get the not-for-cause classification in writing: classification disputes void some discretionary-acceleration eligibility

The OWBPA 45-Day Window: Federal Age-Discrimination Protection

The federal Older Workers Benefit Protection Act treats severance releases differently for group reductions in force. For employees 40 and over in a group RIF, OWBPA requires:

1. 45 days to consider the release (not 21 days)
2. Disclosure of the “decisional unit” composition by job title and age
3. 7 days after signing to revoke

A TIME / What We Will survey of 272 laid-off Oracle workers found that 62% were over 40, and 22% had 15 or more years of tenure. The OWBPA 45-day window applied to most of the affected cohort.

If Oracle’s release didn’t meet the OWBPA group-RIF requirements — specifically the 45-day consideration window OR the decisional unit composition disclosure — the ADEA waiver in the release is invalid and unenforceable. Affected employees over 40 retain their right to file federal age-discrimination claims even after signing.

For the May 30 / June 15 last-working-day cohorts, the 45-day window from the original release-offer date is closing during this week. Affected employees over 40 should:

1. Pull the original release document and verify the 45-day consideration window is honored on its face
2. Document the decisional unit disclosure — Oracle should have provided composition data by job title and age
3. Consult an employment attorney before signing if any element of the OWBPA process appears defective

For comparable structural context on US bank severance regimes that don’t share this acute OWBPA-defect risk, see our JPMorgan severance package coverage — JPM’s clean group-RIF processes don’t typically generate this category of waiver-defect exposure.

The Texas vs California Asymmetry

Oracle moved its HQ from Redwood City, California to Austin, Texas in 2020. The relocation strips legacy California wage-protection benefits from new hires made in Austin, but Bay Area legacy staff retain materially stronger statutory floor.

California legacy employees: Labor Code §227.3 makes vested vacation payout non-waivable as a matter of state law. Release language attempting to waive vested vacation is unenforceable. The January 2026 California WARN filings covered approximately 254 Bay Area roles across Redwood City, Pleasanton, and Santa Clara — these affected employees retain the §227.3 statutory protection regardless of release-of-claims language.

Texas (Austin HQ) employees: no statutory PTO payout mandate. Unused PTO is paid out only if Oracle’s written policy says so. Final pay timing varies by Texas Workforce Commission rules.

For affected staff anticipating separation, the Bay Area legacy cohort has materially stronger negotiating ground on the PTO-payout dimension, independent of the broader formula negotiation. Severance is treated as supplemental wages with federal flat withholding at 22% under IRS Publication 15-A (37% on amounts above $1M in a calendar year). For senior Oracle staff with large vested RSU sales in the separation year, the total tax picture warrants CPA consultation before year-end.

The Last-Working-Day Cluster Mechanics

The May 30 and June 15, 2026 last-working-day cluster dates align with the federal WARN Act’s 60-day notice floor from the March 31 announcement. Practical consequences:

• Severance pay clock starts at last-working-day, not announcement date
• COBRA election window opens at last-working-day — 60-day federal election period; Oracle’s 1-month subsidy runs concurrently
• State unemployment claims: TWC and CA EDD claims become eligible at last-working-day; CA has a 1-week unpaid waiting period
• OWBPA 45-day consideration for 40+ employees ran from release-offer date in late March / early April — most cohorts at days 30-45 NOW

Severance Ledger does not provide legal advice; readers facing termination should consult an employment attorney licensed in their state. An employment attorney can review the release language in a few hours and identify clauses that warrant negotiation, particularly given the OWBPA-defect risk for 40+ employees specifically.

Negotiating Above the Oracle Formula

The published 4 + 1/year capped at 26 weeks formula is substantially below peer tech employer norms. Five structural arguments for above-formula severance:

The AI-spend paradox: Oracle’s documented Q3 FY2026 financial strength means the cuts are not from financial distress. The bank has balance sheet capacity ($30B raise + $50B capex guidance) to fund competitive packages.

The OWBPA defect threat (40+ employees): if the 45-day window or decisional unit disclosure wasn’t honored, the release is potentially defective. The threat of an ADEA claim creates real negotiation leverage. Get an attorney to review before signing.

The 600-employee collective petition context: Oracle’s public refusal to negotiate collectively is in the public record. Individual asks can reference the petition’s specific terms (16 weeks + 2 weeks/year, 6 months COBRA, RSU acceleration) as documented industry-peer norms.

Division-specific framing: Cerner-cohort employees can reference the 2022 acquisition integration completion. OCI support staff can frame their cut in the context of explicit AI-infrastructure-investment growth.

California legacy protections: Bay Area employees retain Labor Code §227.3 statutory floor that Austin staff don’t share.

Quantifying where a given Oracle offer sits relative to peer-tech-employer norms is the first useful step before bringing in counsel. The SeveranceCalc.com’s offer analysis tool handles the tier × tenure × cap math against Google, Meta, Microsoft, and Amazon published baselines, and flags atypical clause patterns — including the RSU forfeiture which Oracle’s plan handles uniquely punitively relative to peer tech.

Oracle severance in 2026 is structurally below peer tech employer norms across cash formula, COBRA subsidy, and equity treatment dimensions simultaneously. The published formula is the floor of a negotiation that is genuinely worth having, given the documented Q3 FY2026 financial strength that removes the financial-distress justification for the below-peer terms. The OWBPA 45-day window for 40+ employees is closing this week — review the release language before the deadline forces the decision.