Published on

Reading H-1B sponsorship data before you apply

Authors

For a job seeker who needs work authorization, the most expensive mistake is applying broadly and finding out about sponsorship at the offer stage — or worse, after. The good news: a lot of the answer is public, and you can check it before you invest in an application.

The data that exists

US employers who hire H-1B workers file paperwork that becomes public record — most usefully the Department of Labor's LCA (Labor Condition Application) disclosures and USCIS petition counts. Together they tell you, per employer:

  • Whether they have sponsored at all, and roughly how much (filing counts over recent years).
  • Which roles they sponsor, by job title.
  • What they paid those roles — LCAs include wage figures, so you get a real salary signal, not a guess.

Absence of a company from the data means "no recent record," which is not the same as "won't sponsor" — small or newly-sponsoring employers may simply not have filed yet. Read it as a strong positive signal when present, and an "unknown, ask early" when absent.

Turning it into a filter

The practical workflow:

  1. Check sponsorship before applying. If a company has a track record, it moves up your list.
  2. Match the role. A company that sponsors data scientists heavily may not sponsor the sales role you are eyeing. Look at which titles actually appear.
  3. Use the wage data. If recent LCAs for your role cluster around a number, that is your grounded expectation — useful for both targeting and negotiation.

How JobHakken surfaces it

JobHakken checks each job's company against known H-1B sponsor data (DOL LCA records, FY2019–2026) and, when there's a match, flags it right on the listing — a Known H-1B sponsor badge, the number of filings, and the typical H-1B pay for roles like the one you're viewing. So instead of opening twenty tabs to research sponsorship by hand, you see the signal next to the score and the fit, and spend your evening on the applications that can actually go somewhere.

A quick example: when Jordan Rivera filtered to roles at known sponsors first, the application list got shorter and the response rate went up — not because fewer applications is inherently better, but because none of them were dead ends on the one hard requirement.

The caveats worth keeping

Public data lags reality, company policies change, and a specific team's budget is not in any dataset. Treat the signal as a strong prior that saves you time, then confirm sponsorship early in the conversation. The point is to stop discovering the blocker after the work — and start routing around it before.