You open your LCA or your PERM wage determination and see it: Level 2. No explanation, no narrative, just a number that quietly shapes your offered salary and, later, your immigration case file. Most consultants never learn how that number got there.
It is not a judgment call by your recruiter and it is not negotiable the way your bill rate is. It comes out of a defined federal process that starts with your actual job duties and ends with a dollar figure pulled from a government wage library. Understanding that chain helps you read your own paperwork intelligently — and ask your employer or attorney better questions when something looks off.
This piece walks through each link in the chain: SOC code selection, the four wage levels, geographic area, the alternative survey option, and why the level matters later in your case.
Step 1: The SOC Code Comes From Duties, Not Your Title
Every prevailing wage determination starts with a Standard Occupational Classification (SOC) code. The employer's immigration team (often with counsel) maps your actual day-to-day duties — not your business card title — to the closest SOC occupation defined by the Bureau of Labor Statistics.
A "Senior Consultant" doing data engineering work gets classified under a data-engineering-adjacent SOC code, regardless of the title on your offer letter. This matters because wage data, and therefore your prevailing wage, is published per SOC code. Pick the wrong code and everything downstream — the wage level, the dollar figure, the evidentiary record — shifts with it.
For H-1B cases, the SOC code and wage level appear on the Labor Condition Application (Form ETA-9035/9035E), filed through the Department of Labor's FLAG system. For green card cases, the same logic applies on Form ETA-9141, the Application for Prevailing Wage Determination, filed with the National Prevailing Wage Center (NPWC) ahead of PERM.
Step 2: The Four Wage Levels, Explained
Once the SOC code is set, OFLC's wage methodology assigns a level from I to IV based on four factors: experience required, education required, the degree of judgment exercised, and the amount of supervision received or given. These factors are evaluated against the job requirements stated in the position description, not against your personal resume.
| Level | Profile | Typical Signals |
|---|---|---|
| Level I | Entry | Basic understanding of duties, works under close supervision, little or no exercise of independent judgment |
| Level II | Qualified | Moderate experience, performs moderately complex tasks, some independent judgment |
| Level III | Experienced | Requires exercise of judgment on complex tasks, may supervise others, limited direct oversight |
| Level IV | Fully competent | Highest level of complexity, broad authority, independent decision-making, may direct the work of others |
Most of the four factors are additive on OFLC's worksheet: each one that points to higher complexity nudges the role up a level. A role requiring a master's degree, three to five years of specialized experience, and independent client-facing judgment will rarely land at Level I — regardless of what the job title implies.
Step 3: Geography Sets the Dollar Figure
The SOC code and level together point to a wage band, but the actual number depends on where the job is performed. OFLC uses Occupational Employment and Wage Statistics (OES) survey data from the BLS, broken out by Metropolitan Statistical Area (MSA) or, where MSA data doesn't exist, statewide averages.
This is why the same Level II Software Developer role pays a different prevailing wage in Austin than in rural Ohio — the underlying labor market data differs, not the methodology. For consultants who work on client sites across multiple states during a single assignment, this geographic sensitivity is worth tracking, since a worksite change can trigger a new wage determination.
Employers and attorneys typically look up these figures using the Department of Labor's Online Wage Library, accessible through the FLAG system at flag.dol.gov. It's public. You can look up your own SOC code, level, and worksite area yourself.
Step 4: The Alternative Wage Source Option
OES/OFLC data isn't the only legally permissible source. Employers may instead submit an independent, employer-conducted or third-party wage survey, provided it meets DOL's published criteria for a legitimate source — methodological soundness, currency, and proper coverage of the occupation and area.
This path is less common for staffing-model H-1B and PERM cases, mostly because it adds administrative overhead and must be separately defensible if audited. But it exists, and some employers use it for niche or emerging-technology roles where OES data lags the actual market. If your wage figure doesn't match what you'd expect from the OES library, ask whether an alternative survey was used — it's a legitimate, auditable choice, not a red flag by itself.
Why the Level Matters in Your Case File
The wage level itself doesn't determine whether a petition is approved or denied. But it does become part of the evidentiary record an adjudicator reads, and inconsistency inside that record is what draws scrutiny.
- H-1B petitions: USCIS often cross-reads the job duties described in the petition against the wage level on the LCA. A Level I wage paired with a job description full of advanced, independent-judgment language is the kind of mismatch that can trigger a Request for Evidence — not because Level I is disqualifying, but because the narrative doesn't line up with the number.
- PERM cases: The wage level set on the ETA-9141 becomes the floor the employer must pay once the green card process proceeds. A level set too low relative to the actual role can create downstream pay-compliance questions; a level set too high can make recruitment and the final ETA-9089 harder to defend if a qualified U.S. worker applicant appears to be paid less.
- Amendments and transfers: If your duties change meaningfully with a new client assignment, the wage level analysis should be revisited — it is not fixed for the life of your employment.
Treat the wage level as context the government reads alongside everything else in your file, not as a scorecard with a single right answer.
A Quick Self-Check
- Does the SOC code on your LCA or ETA-9141 actually describe what you do day to day?
- Does the wage level description (entry, qualified, experienced, fully competent) match the seniority implied in your job description and offer letter?
- Does your worksite ZIP code or MSA match where you are actually performing the work?
- If an alternative wage survey was used, can your employer point to the source and its DOL-compliant methodology?
This article explains a federal wage methodology in general terms. It is not legal advice, and wage levels, SOC mappings, and PERM strategy can vary with your specific facts — confirm your own situation with a licensed immigration attorney before relying on anything here.
Talk Through Your Own Wage Determination
If a wage level on your LCA or PERM case looks out of step with your actual role, the Josh Pros LLC team can help you think through the right questions to bring to your employer or counsel. Reach out at contact@joshpros.com or visit https://joshpros.com.
#PrevailingWage #H1BWageLevel #OFLCWageDetermination #SOCCodeH1B #PERMWageDetermination #ImmigrationCompliance #H1BTransfer #GreenCardProcess #TechConsultants #WorkAuthorization #ETA9089 #ETA9141
This is general information, not legal advice. Immigration rules change and outcomes depend on your individual circumstances. Confirm anything that affects your case with a licensed immigration attorney.
Talk to a real recruiter, not a bot.
We'll tell you the rate, the client, and the terms before you interview. And if we're not the right fit, we'll say so.