Wait, “use” is banned. Let me rewrite that title.
TITLE: Oracle Said No, and 20,000 Engineers Learned What Their Loyalty Was Worth
—
It’s March 31. You open your laptop, maybe with a coffee still brewing, and there’s an email in your inbox. Not a meeting invite. Not a Slack ping. An email telling you that your job at Oracle is gone. No call. No manager conversation. Just a message, and a severance offer attached to it like a footnote. You have a few weeks to decide whether to sign away your right to sue in exchange for four weeks of base pay plus one additional week per year of service.
That’s the moment roughly 20,000 to 30,000 Oracle employees reportedly faced on March 31, when the company executed one of the largest single-day layoffs in recent tech history. And for a group of at least 90 of those workers, the story didn’t end there. They organized. They pushed back. They tried to negotiate.
Oracle said no.
What the Numbers Actually Look Like
To understand why those 90-plus workers felt the offer was worth fighting, you have to look at what other companies have been putting on the table. Oracle’s package — four weeks for the first year, one additional week per year after that — sits noticeably below what other major tech employers have offered during their own rounds of cuts. For context, Oracle itself reportedly offered 26 weeks of pay in some situations, which makes the terms extended to this group feel even more stark by comparison. Meta, often cited as a benchmark, offered 16 weeks plus 18 months of COBRA health coverage.
That gap matters. When you’re a senior engineer or an architect who has spent years building systems, a few weeks of runway is not a soft landing. It’s a short drop. And when you know other companies in the same industry are offering four or five times that amount, signing a legal release in exchange for what amounts to a month’s pay starts to feel less like a package and more like a pressure tactic.
Why This Hits Different in the Bot and AI Space
I build bots for a living. A lot of the people reading this site do too — or they’re learning to. And a significant chunk of the talent that Oracle just cut was working on cloud infrastructure, AI tooling, and enterprise automation. These are not peripheral roles. These are the people building the pipes that AI products run through.
When a company axes that many technical workers in a single day via email, it sends a signal that goes beyond one company’s HR policy. It tells every engineer currently building on top of Oracle Cloud, every developer integrating Oracle’s AI services, and every team evaluating enterprise platforms: the people who built this were treated as disposable. That’s worth factoring into your architecture decisions.
There’s also a practical angle here for anyone running a small team or a solo operation. If you’re hiring contractors or bringing on engineers who were recently laid off from Oracle, you’re likely looking at a pool of highly skilled people who are undervalued right now and motivated to prove themselves. That’s a real opportunity — but it also means understanding what they’ve just been through.
The Negotiation That Went Nowhere
The group of at least 90 employees who tried to negotiate deserves credit for attempting something that most laid-off workers never do. Collective action in tech is rare. The culture tends to reward individual negotiation and discourage anything that looks like organizing. These workers tried anyway, asking Oracle to match the terms offered by other major tech companies.
Oracle declined. No counteroffer was reported. No middle ground was found.
What that refusal tells us is less about Oracle specifically and more about the current power dynamic in tech employment. When a company can lay off tens of thousands of people in a single email blast and face no meaningful pressure to improve the terms, the negotiating position of individual workers — even organized ones — is limited. The legal release attached to the severance package is doing a lot of work here. Sign it and move on, or don’t sign it and get nothing.
What Builders Should Take From This
- Document your contributions continuously. When a layoff comes via email, you won’t have time to build a case for your value after the fact.
- Understand your severance rights before you need them. Most people don’t read their employment agreements until it’s too late.
- Collective negotiation is rare in tech, but this case shows it’s possible to organize — even if the outcome isn’t guaranteed.
- Platform dependency cuts both ways. The engineers who built Oracle’s AI infrastructure are now available. The companies that relied on that infrastructure are now watching.
Thirty thousand people lost their jobs in a single day. Ninety of them tried to do something about it. That’s not a small thing, even if Oracle’s answer was a firm and final no.
🕒 Published: