Oracle's Leaked Title Sheet: Why "Software Developer III" Is the Wrong Boolean

On September 22, 2026, Business Insider published a leaked title-level breakdown of Oracle's September 14 America Cloud Infrastructure layoff: 546 workers cut from a 7,185-person org, with "Software Developer III" the single largest title at 57 people. For once, sourcers get an internal org chart instead of a WARN summary. The catch: if you paste "Software Developer III" into LinkedIn, you will miss most of the pool.

What the leaked document actually says

Business Insider's document breaks the 546-person cut into titles, and the shape is unusually top-heavy for a cloud engineering org. Managers took 128 of the 546 seats, roughly 23.4% of the round, which is well above the 10 to 15% manager ratio typical of an infrastructure team.

The headline numbers, all sourced to the leaked doc unless noted:

• 546 employees cut from Oracle's America Cloud Infrastructure organization.
• 7,185 workers covered by the filing, so the cut is 7.6% of that org.
• 57 Software Developer IIIs, the single largest title bucket (10.4% of the entire round).
• 128 managers across levels (23.4%).
• 61 program managers (11.2%).
• 41 cuts from Data Center Support Services, including one VP and two senior directors.
• Most affected employees were over 40, and roughly one in six was at least 60, per the OWBPA disclosure Refolk covered previously.

Context matters here. This round follows a prior 21,000-employee reduction, when Oracle's headcount fell by 13%. TD Cowen wrote in January that Oracle could free up as much as $10 billion in cash flow by cutting up to 30,000 employees, and The Register has already flagged an October round. The Boolean strings you build off this leak are a durable asset, not a one-week story.

10.4%

Why "Software Developer III" is the wrong Boolean

The single largest title in the leaked document is not the string that will surface the most ex-OCI engineers on LinkedIn, because Oracle's internal HR titles and the titles its engineers write on their profiles diverge sharply. Pasting the leaked title verbatim is the rookie move.

In Refolk's index of professional profiles, a query for "Software Developer / Member of Technical Staff / Principal MTS" plus the keyword "Oracle Cloud Infrastructure" returns 262 profiles. Of the top 25 by recency and OCI signal:

• 13 currently list "Principal Member of Technical Staff" (PMTS).
• 5 currently list "Member of Technical Staff" (MTS).
• 2 currently list "Software Developer" in any form.
• 22 of 25 still list Oracle as their current employer, meaning the ex-OCI pool from this specific title cluster is still small on the open market.

The mechanism is straightforward. Oracle's HR system tracks people as "Software Developer I/II/III/IV/V" for pay-band reasons. The engineers themselves default to the older, higher-prestige "Principal MTS" and "MTS" ladder when they write their LinkedIn headline, because that is what the industry recognizes. If your Boolean starts with "Software Developer III" AND Oracle, you are searching against the HR title, not the profile title. You will hit 2 of the 25 highest-signal candidates.

The fix is a title-cluster Boolean, not a title-exact one:

("Principal Member of Technical Staff" OR "Member of Technical Staff" OR PMTS OR MTS OR "Software Developer") AND ("Oracle Cloud Infrastructure" OR OCI)

The title-by-title Boolean playbook

Here is the leaked title distribution mapped against what Refolk's index actually shows for each cluster, so you can pick the strings with the best signal-to-noise ratio.

Three practical strings that fall out of that table:

1. The PMTS anchor. ("Principal Member of Technical Staff" OR PMTS) AND ("OCI" OR "Oracle Cloud Infrastructure") AND ("past" OR "former" OR NOT current:Oracle). This is where the 57-headcount cut actually lives, once you translate HR title into profile title.
2. The core-infra string. "Principal Core Infrastructure Engineer" OR ("Core Infrastructure" AND Oracle). Calcalist flagged principal core infrastructure engineers as among the more heavily affected; the exact-string search will be small, so the broadened form does the real work.
3. The manager string. ("Software Development Manager" OR "Engineering Manager" OR "Senior Manager") AND Oracle AND (OCI OR "Cloud Infrastructure"). 128 managers is 23.4% of the round, well above the typical 10 to 15% for an infra org. Oracle over-cut middle management, and players-coaches with fresh OCI context are exactly what competitor cloud orgs want.

57 Software Developer IIIs on the HR sheet map to two profiles on LinkedIn. The other 55 call themselves something else.

The geography Boolean the leak hides

The leaked document is US-only, and the sourcing implication is bigger than the headcount: the US cut creates a knowledge-transfer vacuum that Oracle's India MTS bench will backfill within roughly 90 days. If you want ex-OCI US ICs, that is your window.

Refolk's index makes the shape concrete. For "Software Developer / MTS / Principal MTS" plus the OCI keyword:

• 10 of the top 25 profiles sit in Bengaluru.
• 1 each in Seattle, Austin, and Houston.
• The US-only "Principal / Senior Software Engineer" plus "Oracle OCI" pool totals 62 profiles, with Seattle (4) and Austin (3) leading.

That Seattle number is not a coincidence. Washington's WARN database shows Oracle filed a notice on September 2 to eliminate 101 jobs in Seattle, effective November 3. The 62-profile US pool is your addressable market for this round; the 10 Bengaluru profiles in the top 25 are the reason it is not larger. If your Boolean does not include a US-location filter, you will spend the next week emailing engineers who are not affected and were never on the leaked sheet.

Two location clusters worth pinning:

• Oracle Abilene, TX campus. The flagship data center, explicitly named in coverage as taking cuts on September 14. Combine with the Data Center Support Services title cluster for the 41-person subsegment.
• Oracle Pleasanton campus. Acquired in the 2005 PeopleSoft deal, hit for 36 additional cuts on top of an August round, per the California WARN signed by Oracle HR SVP Anje Dodson. Useful both as a geography filter and as a signatory name you can cross-reference to verify the authenticity of any further leaked docs.

Where the 546 will surface next

Most of the 546 will hit LinkedIn's "Open to Work" and Blind within 30 days, and a smaller cohort will self-identify on r/oracle, X, and GitHub commit history. The sourcers who move first work off the leaked title sheet; the sourcers who move second wait for the profile updates.

Coverage confirms that details of the round began surfacing through employees posting on Reddit, X, and Blind before any official disclosure. Those are your secondary verification channels, not your primary sourcing surface. Concrete places to look:

• Blind. Search the Oracle channel for posts dated September 14 through September 21. Handles are anonymous, but self-reported titles are usually accurate.
• r/oracle. Cross-reference "laid off" threads with the title distribution in the leaked doc. A "Principal MTS, 12 years, OCI networking" post lines up cleanly with the PMTS anchor above.
• GitHub. Engineers who worked on OCI open-source repos (Terraform provider, OCI SDK forks) are searchable by commit email. Filter to commits with @oracle.com email domains that stopped between September 1 and September 15.

That is the exact gap Refolk closes: you describe the person in plain English ("ex-OCI PMTS or MTS in the US who left Oracle in the last 60 days") and get a ranked shortlist across LinkedIn, GitHub, and the open web without hand-tuning the title alternation or merging spreadsheets.

Why the Boolean is a durable asset, not a one-week play

Two independent signals point to more Oracle rounds inside the next two quarters, which means the title-cluster Boolean you build off the September 14 leak will keep paying out. Save the strings.

The signals:

• TD Cowen's January thesis. Analysts wrote Oracle could free up as much as $10 billion in cash flow by cutting up to 30,000 employees. The September round is 546 of that theoretical 30,000.
• The October round. The Register has already reported a follow-on round, and the OWBPA age disclosure pattern (most affected over 40, one in six over 60) is one Oracle will likely repeat.
• CFO Hilary Maxson's denial. Maxson told employees at a companywide meeting that the layoffs should not be interpreted as a directive to accomplish more work with fewer resources, per Business Insider. Read that as: the cuts are structural, not productivity-driven, which means the same title clusters get hit again.

The practical implication is that the PMTS/MTS/Core Infrastructure Boolean, plus the US-only geography filter, plus a 60-day recency window on "left Oracle," is a saved search you rerun monthly. Every rerun catches the next tranche.

FAQ

Does pasting the leaked "Software Developer III" title into LinkedIn work?

Not well. Refolk's index shows that in the top 25 profiles matching the OCI keyword cluster, only 2 use "Software Developer" in any form on their profile, while 13 use "Principal Member of Technical Staff" and 5 use "Member of Technical Staff." Oracle's internal HR title and the engineer's profile title diverge, so the highest-signal Boolean anchors on PMTS and MTS, not on the leaked HR string.

How large is the addressable ex-OCI US pool right now?

Small, and that is the sourcing edge. Refolk's index shows 262 profiles in the broad "Software Developer / MTS / Principal MTS" plus OCI cluster, with 22 of the top 25 still listing Oracle as their current employer. The US-only "Principal / Senior Software Engineer" plus OCI pool is 62 profiles. Sourcers who move on the leak inside 30 days are working against a small, well-defined market with limited competition.

What about the 128 managers in the leaked round?

Managers are the highest-value slice and the most under-searched. 128 out of 546 is 23.4%, well above the 10 to 15% manager ratio typical of an infrastructure org, which means Oracle over-cut middle management. Players-coaches with recent OCI context are exactly what competitor cloud teams want, and they sit in a different Boolean cluster than the IC search, so most sourcers miss them entirely on the first pass.

Should I expect a second wave of Oracle cuts?

Yes, and it changes how you treat the Boolean. TD Cowen's $10B/30,000-employee thesis, The Register's October reporting, and CFO Hilary Maxson's framing all point to structural cuts, not one-off productivity moves. The title-cluster strings you build for September 14 are worth saving as a monthly rerun rather than a one-week campaign, because the next tranche will land in the same PMTS, MTS, and Core Infrastructure buckets.