The Labor Condition Application sets the wage floor for an H-1B role, and its two hardest choices are the occupational classification and the wage level. Core Rust and C++ systems development sits awkwardly inside broad software occupational categories that were written for general application development. Getting the classification and level right protects both the worker and the employer, and it makes the underlying petition far easier to defend.
Pick the occupational code that matches the work performed
Systems programming roles usually classify under software developer occupational categories, but the correct choice depends on whether the work is closer to systems software, application software, or network architecture. A developer writing kernel modules, device drivers, or a runtime is doing systems software work regardless of the internal job title.
Document the reasoning. A short internal memo explaining why the chosen code fits the day-to-day work is cheap insurance during any later review.
Assign the wage level from role requirements
The four-level analysis weighs experience, education beyond the entry requirement, special skills, supervisory duties, and independence of judgment. A role requiring several years of production Rust, ownership of an unsafe-code boundary, and authority to set memory-model policy is not an entry-level role.
Under-leveling is the most common and most damaging error. It creates a mismatch between a petition that argues for advanced complexity and a wage attestation that describes routine supervised work — a contradiction reviewers notice immediately.
Use supplemental surveys when the standard data is a poor fit
Core systems compensation frequently exceeds the published prevailing wage bands in a given area. Employers may rely on a legitimate independent survey that meets the regulatory criteria for methodology, sample, and recency. If you use one, keep the full methodology documentation in the public access file.
Remote and multi-site roles need a determination for each intended place of employment. A single determination for headquarters does not cover a distributed team.
Maintain the public access file and posting discipline
Notice requirements, the wage rate memo, the prevailing wage documentation, and the actual wage system must be assembled within one working day of filing and retained for the required period. Calendar the retention date at filing.
Reconcile the LCA wage with the offer letter and the payroll record on the first pay cycle. Small clerical divergences compound into material compliance problems over a three-year validity period.
key takeaways
- Classify by the work actually performed, not by the internal job title.
- Systems ownership and unsafe-code authority push roles above entry level.
- Document a supplemental survey fully if the standard band fits poorly.
- File a determination for every intended place of employment.
- Reconcile LCA wage, offer letter, and payroll on the first pay cycle.