15% vs 61%: The H-1B Wage Level Trap Rewriting FY 2027

If you need sponsorship for the FY 2027 H-1B cycle, the lottery is no longer a lottery. On February 27, 2026, DHS's weighted selection rule took effect, and the projected selection rate at Wage Level I collapsed to 15.29% while Level IV climbed to 61.16%. That is a 4x spread, and it means the postings you choose to apply to between now and the March 4 registration open are worth more than any resume edit you make this quarter.

The new math: 15.29% vs 61.16%

Under the DHS weighted rule, your H-1B odds are set by the Labor Condition Application (LCA) wage level your employer files (I through IV), not by luck. Level IV registrations get four entries in the pool, Level III gets three, Level II gets two, and Level I gets one. DHS's own projections tell you what that does to your chances.

The bracket you land in matters more than any single line on your resume. Independent modeling from immigration counsel suggests the real spread could be even wider once employers adjust registration strategies, with Level I sinking toward 10-12% and Level IV reaching 65-70%. Either way, the trap is obvious: 83% of historical H-1B petitions sat at Levels I and II, which is now the losing half of the pie.

Why "high salary" no longer means "high wage level"

Wage level is a function of the LCA occupation code (SOC), metro, and required experience, not the number on your offer letter. This is the single most misunderstood fact in the new regime, and it is why $140K Bay Area engineers are still getting filed at Level I.

The Department of Labor's OEWS survey publishes four wage thresholds per SOC code per metro. Employers must pick the highest level the offered wage meets or exceeds for that specific occupation and location. But wage level also reflects seniority and job complexity: if the posting only requires a bachelor's degree and two years of experience, the LCA is capped at Level I or II regardless of what the company is willing to pay. Fisher Phillips put it plainly in their analysis of the final rule: many H-1B workers earn well above US averages but still fall into Level I or II because of SOC code, location, or required-experience mismatch.

The mechanism to internalize:

• The SOC code picks the wage table. "Software Developers, Applications" (15-1252) has different Level III thresholds than "Computer and Information Research Scientists" (15-1221).
• The metro picks the row. Same SOC, San Jose vs Austin, wildly different Level III cutoffs.
• The posting's required experience and duties cap the level. "Entry-level, 0-2 years" caps at Level I. "Independent judgment, leads projects, 5+ years" opens Level III/IV.

Before you apply, look up the exact Level III and IV wage for your target SOC and metro on flcdatacenter.com or the DOL FLAG portal. If the posted salary sits below Level III for that metro, sponsorship at that role will file at Level I or II. That is a 15% or 30% ticket.

The single sentence that should change your search

Filter every posting for signals that support a Level III or IV filing, and reject the rest. That is the whole job-search strategy for FY 2027. Apply broadly and you will land in the 15% bucket by default.

Concrete signals in a job description that make Level III/IV realistic:

1. Title includes "Senior," "Staff," "Principal," "Lead," or "Manager" (not just "II" or "III" within a leveling system).
2. Required experience is 5+ years, ideally 7+.
3. Duties include "independent judgment," "leads projects," "sets technical direction," "mentors," or "architects."
4. Single-location posting, ideally in a metro where Level III/IV wages are within the company's normal band.
5. The company shows up in the USCIS H-1B Employer Data Hub with prior Level III or IV filings for that same SOC code.

That last one is underused. The USCIS Employer Data Hub publishes prior H-1B petition history by employer, and every LCA on DOL FLAG discloses wage level. You can literally verify whether Workday, Atlassian, or SailPoint filed their last twenty "Senior Data Scientist" LCAs at Level III versus Level I.

Rewriting each application to mirror the exact required-experience and duty language of a Level III/IV posting is the work most candidates skip because it is slow. That is the exact work Refolk takes off you: paste the posting, and Refolk rewrites your resume from your own history to match the seniority and duty signals the LCA needs to support.

Multi-city and "remote, US" postings are quietly demoting you

If a posting names multiple work locations, the employer must file the LCA at the lowest wage level among those locations. A "remote, US" role is the worst offender because it forces the employer to pick the lowest Level III threshold across whichever metros they list, which usually pulls the filing down to Level I or II.

Buchanan Ingersoll's summary of the rule states it directly: if the employee will work in multiple locations, the lowest wage level among those locations must be chosen. Translation for the sponsorship-dependent applicant:

• A New York-only Senior Engineer role beats a "New York, Austin, remote" role for the same title and pay.
• A Bay Area Staff role at $220K in a single office beats a hybrid role at $240K spanning three metros.
• A "remote, US" posting is almost always a Level I trap even when the salary is high, because the LCA has to accommodate the cheapest metro on the list.

If you are looking at distributed roles or "hire from anywhere" pitches, understand that you are trading a 61% ticket for a 15% ticket. For FY 2027, geographic concentration is a feature, not a constraint.

Backup offers can sabotage the primary

USCIS applies the lowest wage level across all registrations tied to your passport. If two employers register you, and one files Level IV while the other files Level II, your entire weighting drops to Level II. This is a landmine in the fine print of the rule, and most candidates have not heard it.

What to do:

• If a Level III/IV registration is already lined up, decline registration from any employer whose LCA would file at Level I or II.
• If you have two Level III/IV offers, both are fine. Backup offers only hurt when they file lower.
• Ask the recruiter directly: "What SOC code and wage level will this LCA be filed at?" Any competent immigration team can answer in an email.

Where the Level III/IV postings actually live

Senior and staff-level titles concentrate at a small number of employers, and Refolk's index of professional profiles gives a directional map of where sponsorship-friendly Level III/IV filings realistically exist. Two slices matter most for this cycle.

Senior software engineering

In Refolk's index, there are roughly 68,933 US-based Staff, Principal, and Senior Staff Software Engineers. That title band is where Level III and Level IV LCAs actually get filed, because the required-experience floor supports it. Employers appearing prominently in that senior slice include:

• Workday
• Airbyte
• Starburst Data
• Omada Health
• Medium

The point is not that these five will sponsor you. The point is that "Level IV sponsor" is not synonymous with FAANG. Mid-stage infrastructure and data companies file Level III/IV LCAs for senior individual contributors all the time, and their postings often get less traffic than the equivalent Meta or Google listing.

Data science and analytics

Refolk's index shows roughly 91,593 US-based Data Scientist and Data Analyst profiles combined, with current employers concentrated at Meta, Atlassian, SailPoint, and Sia among others. Analytics candidates should note that "Data Analyst" often files under a different SOC than "Data Scientist" (15-2051), with materially different Level III/IV thresholds. Same person, same skills, different wage tables. Choose the posting whose SOC yields a higher Level III number in your metro.

The resume rewrite that actually moves the needle

Your resume needs to justify the required-experience and duty language of a Level III or IV filing, in the exact phrasing DOL uses. Wage level is capped by what the position supports, so if your resume reads "entry-level" the immigration attorney has no choice but to file low.

The specific edits that matter:

• Replace "worked on" and "helped build" with "led," "architected," "set technical direction for."
• Quantify scope in a way that supports "independent judgment": team size, budget, systems owned, decisions made without escalation.
• Move the years-of-experience total into the top third of the resume, not the bottom.
• Match the SOC's canonical duty language. For Software Developers, that means "designed, developed, and modified software systems, using scientific analysis and mathematical models."
• Kill any "junior," "associate," or "entry-level" language, even from three jobs ago.

This is where Refolk earns its keep on a sponsorship-dependent search. Refolk drafts the resume from your own history, tailors it to every posting you apply to, and scores how well you actually fit the seniority signals the role requires. If the score comes back low on "independent judgment" language for a Level III posting, that is a real signal, not a vanity metric, and you have time to fix it before the March 19 registration deadline.

The FY 2027 calendar, and what to do this week

The clock is short. The FY 2027 H-1B cap registration period opens March 4, 2026 and closes March 19, 2026. USCIS should announce selections by March 31, 2026, with the petition filing window running April 1 through June 30, 2026. Layered on top: the September 19, 2025 presidential proclamation established a $100,000 fee for petitions filed on behalf of beneficiaries residing outside the US, which makes marginal Level I sponsorship even less rational for employers.

Between now and March 19:

1. Look up Level III and IV wages for your top three SOC codes across your top three metros on flcdatacenter.com.
2. Pull the USCIS Employer Data Hub and filter for employers who filed Level III/IV at your SOC in the last two cycles.
3. Apply only to single-location, senior-titled postings whose salary bands clear Level III for the metro.
4. Ask every recruiter, in writing, what SOC and wage level the LCA will file at.
5. Decline registration from any employer filing below Level III if you already have a Level III/IV registration in play.

The 61% ticket exists. It is a Level IV filing, in one metro, with duties written for a senior operator, from an employer with a Level IV track record. Everything else is a 15% ticket dressed up as a job search.

FAQ

Does a higher salary automatically move me to Level IV?

No. Wage level is set by the intersection of SOC code, metro, and the required experience and duties in the posting, not by the offer amount alone. A $150K Software Engineer role in the Bay Area can still file at Level I if the required experience is 0-2 years and the duties are entry-level. Check the OEWS Level III and Level IV thresholds for your exact SOC and metro on flcdatacenter.com before assuming a high salary rescues you.

Should I take a backup offer if it files at Level I?

No. USCIS uses the lowest wage level across all registrations tied to you, so a Level I backup will drag your primary Level III or IV registration down to Level I weighting. If your primary is strong, decline the low-tier registration. Backup offers only help when they file at the same level or higher.

Are remote roles a dealbreaker for sponsorship in FY 2027?

Effectively yes, if you care about odds. Multi-location LCAs must be filed at the lowest wage level among the listed locations, and "remote, US" postings force employers to accommodate the cheapest metro they might place you in. That almost always drops the filing to Level I or II. Target single-location postings in metros where Level III/IV thresholds fit the company's salary band.

How do I find companies that actually file at Level III/IV?

Pull the USCIS H-1B Employer Data Hub, filter by SOC code, and cross-reference wage levels on DOL FLAG. Employers with a consistent Level III/IV filing history for your occupation are the realistic targets. Refolk's index surfaces senior title concentrations at companies like Workday, Atlassian, Meta, SailPoint, Airbyte, and Starburst Data, which is a useful starting map before you verify each one's prior filings.