Oracle Is Hiring Thousands on H-1B Visas While Laying Off Thousands

What Happened

Oracle has filed thousands of H-1B visa petitions with USCIS while simultaneously executing mass layoffs that have affected thousands of US-based employees. The juxtaposition — new visa applications going out while pink slips land — drew immediate scrutiny after the filings became visible in public USCIS data and reporting surfaced in early April 2026.

Oracle is far from the first major tech company to file H-1B petitions during a layoff cycle, but the scale and simultaneity here are difficult to ignore. The affected domestic employees span multiple divisions, and the H-1B petitions cover roles across Oracle's cloud infrastructure, enterprise software, and AI divisions — areas that overlap significantly with the teams being cut.

Oracle has not issued a detailed public statement reconciling the two actions. The company's position, consistent with past industry practice, is that hiring and workforce reductions are independent decisions driven by different business needs.

The Legal Framework — and Its Gap

The reason this is legal is straightforward and worth understanding precisely: H-1B regulations require employers to attest that they will pay the prevailing wage and that hiring a foreign worker won't adversely affect the working conditions of similarly employed US workers. But there is no requirement to demonstrate that the company attempted to fill the role with a recently laid-off domestic employee — or even that the role is materially different from one that was just eliminated.

The law treats hiring and layoffs as legally unrelated acts, even when they occur in the same quarter, in the same division, at the same company. For H-1B-dependent employers (those with 15%+ of their workforce on H-1B visas), there are additional attestation requirements. But Oracle, with its massive overall headcount, likely falls below that threshold despite filing thousands of petitions.

This structural gap has been a known issue in immigration policy for over two decades. Legislative proposals to add a "no recent layoffs" condition to H-1B filings have been introduced in multiple Congressional sessions. None have passed. The political dynamics are complex: business lobbies argue it would create unworkable rigidity, while labor advocates call the current system a loophole large enough to drive a workforce through.

Why This Story Hit 455 Points on Hacker News

The Hacker News response reflects a community that is personally affected on multiple sides. The thread (and stories like it) reliably generate some of the most heated discussion on the platform because the developer workforce includes:

Laid-off domestic workers who see roles that match their skills being filled by visa holders, often at or near prevailing-wage floors that may sit below what the laid-off employee was earning. The frustration is concrete: you lost your job, and a role that looks identical is being filled by someone who costs the company less.

H-1B holders who are acutely aware that they're being used as a political football. Most H-1B workers didn't design the immigration system — they applied through it, often waited years, and face deportation if they lose their job. The framing of "H-1B workers taking jobs" elides the fact that the employer holds all the leverage in this arrangement. A worker tied to their employer for visa status has significantly less bargaining power than a domestic employee, which is precisely why some employers prefer them.

Hiring managers who will tell you, off the record, that the calculus isn't always about cost. In some specialized areas — certain database internals, enterprise middleware, specific cloud infrastructure domains — the domestic talent pipeline is genuinely thin. Oracle's legacy codebase spans decades. Finding engineers who can work on it isn't trivial. But the H-1B system doesn't distinguish between "we genuinely cannot find this skill domestically" and "we prefer this hiring channel for cost and retention reasons."

The Prevailing Wage Problem

The most empirically grounded criticism of the current system isn't about immigration — it's about wage suppression. H-1B prevailing wages are set using Department of Labor wage survey data divided into four tiers. Multiple analyses have shown that the majority of H-1B petitions are filed at Level 1 or Level 2 wages — the bottom half of the pay distribution for a given role and geography — which is inconsistent with the program's stated purpose of filling roles that require specialized expertise.

If you're hiring a specialist that US workers can't match, you'd expect to see Level 3 and Level 4 wages dominating. The data shows the opposite. This doesn't prove every H-1B hire is a cost play, but it does undermine the aggregate narrative that the program primarily serves hard-to-fill specialist roles.

Oracle's specific wage data for these petitions isn't yet public in disaggregated form, but the company's historical H-1B filings have followed industry-wide patterns — concentrated in the lower wage tiers.

What This Means for Your Career

If you're a developer navigating this market, there are practical takeaways that don't require taking a political position:

Watch the LCA data. Every H-1B petition requires a Labor Condition Application, which is public. Sites like H1BGrader and the DOL's OFLC disclosure data let you see exactly what a company is willing to pay for a given role in a given city. If a company's LCA filings for "Software Engineer" in Austin show $95K while Levels.fyi shows a median of $165K for the same title and location, that tells you something about how the company values that role.

Specialization matters more than ever. Roles that are genuinely hard to fill — regardless of visa status — command higher compensation and more stability. The H-1B dynamic disproportionately affects fungible roles: generalist backend engineers, QA, IT operations. Roles requiring deep domain expertise, security clearances, or client-facing trust relationships are structurally insulated.

Understand your employer's H-1B dependency. Companies that file thousands of H-1B petitions annually have a different relationship with labor costs than companies that file dozens. This isn't inherently good or bad, but it affects compensation dynamics, promotion velocity, and layoff patterns.

Looking Ahead

The Oracle situation will almost certainly draw Congressional attention — it arrives during an election cycle where tech labor practices are already under scrutiny. But legislative change remains unlikely in the near term. The more probable outcome is what always happens: intense public discussion, a few oversight hearings, and no structural reform. For practitioners, the actionable move is the same as it's always been — build skills that are hard to commoditize, use public data to understand your market value, and don't mistake your employer's hiring strategy for a commentary on your worth.