Saved
ORIGINAL DATA RESEARCH / FY2026 Q4

The same job title can mean very different occupations

We analyzed an official U.S. Department of Labor disclosure file to see how employers classified the titles they submitted. The result explains a core problem with salary websites: a job title often is not a precise government wage category.

119,207administrative records with decision statuses
42,035distinct title-to-SOC combinations in the file
FY2026 Q4source disclosure period

These are not job openings or labor-market salary observations. The source is a selected immigration-program filing dataset that includes certified, withdrawn and denied cases. Its records do not represent the full U.S. workforce, and employers may classify the same title differently.

01 / WHAT THE DATA SHOWS

One name, multiple occupational codes

Consider Machine Learning Engineer. Among the FY2026 Q4 records bearing that exact normalized title, employers used ten different SOC codes. Most matching records were classified as Software Developers or Data Scientists, and a smaller number used still other categories. A salary site that silently maps the title to just one occupation would hide that ambiguity.

The pattern is not confined to AI. Senior Technical Program Manager and Software Engineer were also recorded under multiple codes. Not every variation is a meaningful professional distinction; some may be coding differences, old classifications or errors. The data shows that classification varies, not that all classifications are equally correct.

EMPLOYER-SUBMITTED TITLE

Machine Learning Engineer

151 filing records

Reported across 10 occupational codes in this source.

Software DevelopersSOC 15-1252 · 79 records
Data ScientistsSOC 15-2051 · 55 records
Computer and Information Research ScientistsSOC 15-1221 · 6 records

Additional reported codes account for the remaining 11 records.

EMPLOYER-SUBMITTED TITLE

Software Engineer

5,371 filing records

Reported across 24 occupational codes in this source.

Software DevelopersSOC 15-1252 · 4,301 records
Computer ProgrammersSOC 15-1251 · 860 records
Computer Occupations, All OtherSOC 15-1299 · 86 records

Additional reported codes account for the remaining 124 records.

EMPLOYER-SUBMITTED TITLE

AI Product Manager

15 filing records

Reported across 4 occupational codes in this source.

Computer Occupations, All OtherSOC 15-1299 · 10 records
Project Management SpecialistsSOC 13-1082 · 2 records
Software DevelopersSOC 15-1252 · 2 records

Additional reported codes account for the remaining 1 records.

EMPLOYER-SUBMITTED TITLE

Senior Technical Program Manager

43 filing records

Reported across 8 occupational codes in this source.

Computer Occupations, All OtherSOC 15-1299 · 21 records
Computer and Information Systems ManagersSOC 11-3021 · 7 records
Project Management SpecialistsSOC 13-1082 · 5 records

Additional reported codes account for the remaining 10 records.

EMPLOYER-SUBMITTED TITLE

Manufacturing Quality Engineer

15 filing records

Reported across 2 occupational codes in this source.

Industrial EngineersSOC 17-2112 · 14 records
Mechanical EngineersSOC 17-2141 · 1 records
EMPLOYER-SUBMITTED TITLE

Software Developer

3,876 filing records

Reported across 15 occupational codes in this source.

Software DevelopersSOC 15-1252 · 3,713 records
Computer ProgrammersSOC 15-1251 · 110 records
Software Developers, Applications (legacy reporting code)SOC 15-1132 · 16 records

Additional reported codes account for the remaining 37 records.

02 / WHAT IT MEANS FOR SALARY RESEARCH

The title is the question. The occupation is evidence.

A person looking up “Senior Technical Program Manager salary” is asking about a specific type of responsibility and seniority. A BLS estimate for Computer and Information Systems Managers, Project Management Specialists, or another occupation can provide context, but none automatically measures pay for that particular title. The occupational category may mix junior and senior workers, different industries and different job scopes.

AvgPay therefore treats real-world title identification as distinct from occupational wage statistics. Where we have source-backed role-level detail, specific role guides explain what the work involves. Where a title is ambiguous, title search displays plausible classifications rather than assigning one silently. Our role comparison tool examines responsibilities and skills directly, while keeping salary evidence tied to its actual source population.

03 / METHODOLOGY & LIMITATIONS

How we audited the source

We inspected the official FY2026 Q4 Labor Condition Application disclosure spreadsheet, excluded blank worksheet-formatting rows, standardized submitted job-title casing and punctuation for comparison, and grouped records by exact normalized title and recorded seven-character SOC code. We then counted entries under each title-code combination. We did not use any wage fields, model job demand, scrape private profiles, or infer an individual's compensation.

Case statuses in the source include Certified (106,746), Certified - Withdrawn (10,127), Withdrawn (1,924), Denied (410). This is an administrative dataset for certain immigration programs: multiple records can relate to a single employer or position, and it cannot be generalized into national title demand. Some records use legacy or questionable SOC codes; we retained the reported codes without declaring them correct.

Source file, checks and reproducibility

Original agency: U.S. Department of Labor, Office of Foreign Labor Certification, Labor Condition Application public disclosure data

Release: LCA_Disclosure_Data_FY2026_Q4.xlsx, FY2026 Q4. Audited 2026-11-21.

Source SHA-256: 525a090def156e650a33797dde22bcb2307f51bf6b1b46a52ef84cb01af67c03

Streaming audit of supplied official Excel release, ignoring empty formatting rows, normalizing job-title whitespace/punctuation/case, and grouping by exact normalized employer-submitted title plus recorded SOC. Counts are disclosure rows, not unique workers or active vacancies. No wage fields were used. All mapped SOC codes from the filing are retained without assuming the employer selected the correct statistical occupation.

  • An LCA record is not a unique job posting, worker, hire, or job opening. One or more filings may concern the same employer or position.
  • The filings cover only certain employers and visa programs; they do not measure national job-title frequency or occupational demand.
  • Recorded SOC classifications are employer-submitted administrative fields and may include old codes, errors or classification differences. Do not treat all mappings as equally correct.
  • An employer's use of a title does not establish a representative salary, promotion premium or wage distribution.
  • Small groups and rare title variants are included for classification illustration only, not extrapolation.

Read the official Department of Labor disclosure data or our research methodology. This analysis should not be used to draw conclusions about prevailing pay, worker shortages, hiring probabilities, wage premiums, or employment trends.

Where to next