H-1B Salary and Wage Guide for Bellevue Employers

H-1B salary is not only a compensation issue. It affects Labor Condition Application compliance, petition strategy, employer obligations, cap-subject registration planning, and the credibility of the record filed with the government.

For Bellevue employers, salary review should happen before the LCA is filed and before the H-1B petition is assembled. The wage offered to the worker must fit the occupation, the area of intended employment, the actual job duties, the required experience, the employer's internal pay practices, and the worksite arrangement.

The salary question is also practical. A compensation package may look competitive from a recruiting perspective but still create immigration issues if the guaranteed wage does not meet the required wage, if the worksite has changed, or if the role has been leveled in a way that does not match the job. Early review reduces the risk of LCA problems, petition inconsistencies, delayed filings, and difficult corrections after the employee has already started work.

The H-1B required wage is generally the higher of the prevailing wage or the employer's actual wage for similarly employed workers. The prevailing wage is tied to the occupation and area of intended employment. The actual wage is tied to what the employer pays other workers with similar experience and qualifications for the specific employment in question.

The prevailing wage analysis usually starts with the correct occupational classification. Employers should identify the SOC or O*NET occupation that best matches the worker's real job duties, not merely the job title. A software engineer, data scientist, product manager, finance analyst, or business operations role may need a careful match because the title alone may not reflect the correct occupation.

The area of intended employment matters as well. A Bellevue worksite may fall into a different wage analysis than a worker based in another Washington location or a remote employee working from another metro area. The employer should confirm the work location before filing the LCA because the wage, notice, and worksite obligations are connected.

Employers commonly use the OFLC FLAG Wage Search to review OEWS wage data. Some employers use another legitimate wage source where allowed, but the source must be supportable and documented. If the wage source, SOC code, area, or wage level is weak, the problem may show up later in an audit, investigation, RFE, amendment, or extension.

H-1B wage levels are meant to reflect differences in skill, responsibility, supervision, experience, and role complexity within an occupation and area. They are not a simple seniority label, and they are not selected only because a company wants a higher or lower wage outcome.

Level 1 is generally associated with entry-level roles that require basic understanding of the occupation and closer supervision. Level 2 generally reflects qualified workers who perform moderately complex tasks. Level 3 generally reflects experienced workers who exercise more independent judgment. Level 4 generally reflects the highest level of responsibility, advanced expertise, or senior-level work within the occupation.

Those descriptions are practical shorthand, not a substitute for legal analysis. The right level depends on the full job description, minimum education, years of experience, special skills, supervisory duties, licenses, travel requirements, and whether the role contains duties that are more complex than the baseline occupation.

Bellevue and Seattle technology roles can be especially easy to misread. A startup may use broad titles, equity-heavy offers, or fast-changing responsibilities. A worker may have a senior title but perform a narrow individual contributor role. Another worker may have a modest title but own a complex technical architecture or supervise specialized staff. The wage level should follow the actual job, not the label.

The prevailing wage is the outside wage floor for the occupation and location. The actual wage is the employer's internal wage for similarly employed workers. DOL's required wage framework protects both U.S. workers and H-1B workers by requiring the employer to satisfy the higher of these wage obligations.

Actual wage is not simply the average salary across a department. It requires looking at workers with similar experience and qualifications for the specific employment. The employer should be able to explain the compensation system, including how it treats education, experience, performance, responsibilities, location, and specialized skills.

This is where documentation matters. An employer that pays the H-1B worker at the prevailing wage but pays similarly employed workers more may have an actual wage problem. An employer that pays the worker more than internal comparators but below the prevailing wage may have a prevailing wage problem. The analysis should address both.

Employers should preserve the wage analysis, the wage source, the actual wage explanation, the LCA, notice documentation, and related public access file materials. The public access file is not just paperwork. It is part of the employer's ability to show that the LCA attestations were made carefully and supported by records.

Bellevue and Seattle employers often compete in high-wage labor markets, especially in software, cloud infrastructure, AI, data, gaming, cybersecurity, telecommunications, and biotech-adjacent roles. That local market reality can affect recruiting expectations, but immigration compliance still turns on the required wage analysis, not a general sense that the offer is competitive.

A Bellevue salary may be high compared with national averages and still require review against the correct local prevailing wage and actual wage. Conversely, a startup offer may rely heavily on equity or future upside, but H-1B wage compliance is focused on the required wage that is guaranteed and paid. Employers should be cautious about treating equity, discretionary bonuses, or future raises as a substitute for compliant base compensation.

Remote and distributed teams add another layer. A worker who is nominally tied to a Bellevue company may actually perform the role from another state or metro area. That location may change the prevailing wage, notice obligations, and amendment analysis. Employers should not assume the headquarters location controls if the worker is performing the job somewhere else.

DOL worksite rules tie many H-1B obligations to the place where the worker actually performs the job. The LCA is connected to the geographic area of intended employment, the prevailing wage, the required worker notice, and other worksite-related obligations.

A hybrid worker who splits time between Bellevue and a home office may require a different analysis than a fully onsite worker. A remote worker outside the Seattle-Bellevue area may require a wage analysis for the remote location. A temporary visit to a client site or a short business trip may be treated differently from a long-term worksite change. The details matter.

Material worksite changes can require a new LCA and, in some cases, an amended H-1B petition. Employers should review moves before they happen, not after payroll, onboarding, and team assignments have already changed. This is especially important for companies with flexible work policies because immigration filings may not automatically track internal HR systems.

From a planning standpoint, employers should document where the worker will actually work, whether the arrangement is remote, hybrid, or onsite, whether the worker will move, and whether any client or third-party sites are involved. That worksite record should align with the LCA and petition.

Raises usually create fewer immigration issues than reductions, assuming the job duties, worksite, hours, and petition remain accurate. But even a raise should be documented if it reflects a role change, promotion, new duties, or a new worksite arrangement that may require H-1B review.

Salary reductions require more caution. A pay cut may create a required wage problem, an LCA problem, or a petition inconsistency. Reduced hours, benching, furloughs, unpaid leave, or demotions can raise additional issues because H-1B employers generally have wage obligations tied to the terms of employment and the LCA.

Bonuses, commissions, and equity can be part of a compensation package, but they need careful treatment. Guaranteed compensation is easier to analyze than discretionary compensation. A bonus that may or may not be paid, stock options that may never vest in meaningful value, or commissions dependent on future sales should not be casually counted as the required wage without review.

Equity-heavy startup offers are common in the Bellevue and Seattle market. They can be legitimate business compensation, but they do not remove the H-1B wage obligation. Employers should confirm that the guaranteed wage alone satisfies the required wage unless there is a carefully documented reason to treat other compensation as wage-compliant.

The Labor Condition Application is not just a filing step before the H-1B petition. It contains employer attestations about wages, working conditions, notice, and the absence of certain labor disputes. Those attestations should be accurate when made and supported by records.

Employers should maintain the public access file materials required by DOL, including the LCA, the wage rate to be paid, an explanation of the actual wage system, the prevailing wage and its source, notice documentation, and required benefit information. Some employers may need additional records depending on H-1B dependency, willful violator status, corporate changes, or other facts.

Internal documentation should also connect the immigration filing to the HR record. The offer letter, job description, payroll setup, worksite location, remote work arrangement, job code, salary band, and manager expectations should not conflict with the petition. When these records disagree, the employer may face avoidable questions later.

Common documentation mistakes include using an outdated job description, selecting an SOC code without reviewing duties, failing to document the actual wage system, forgetting new worksite notice, relying on discretionary compensation, or filing an amendment late after a material change. These issues are easier to prevent than repair.

For the FY 2027 H-1B cap season, DHS implemented a weighted selection process that generally favors higher-skilled and higher-paid beneficiaries while preserving an opportunity for workers at all wage levels. The rule is tied generally to equivalent wage levels and does not guarantee selection.

Employers should not inflate wages, manipulate SOC codes, or adjust work locations to chase selection odds. The wage level should reflect the real position, the real location, and the real documentation. If the petition filed after selection does not match the registration strategy, the employer may create risk for the case.

For Bellevue employers, this makes early salary analysis more important. The wage, SOC code, worksite, job duties, and requirements should be reviewed before registration, not reconstructed after selection. A sound registration strategy is one that the employer can support in the later petition.

The most common mistake is treating the H-1B salary question as a single number. In reality, the analysis involves occupation, wage level, worksite, actual wage, guaranteed compensation, LCA notice, petition consistency, and documentation.

Another common mistake is relying too heavily on job titles. A title such as engineer, analyst, manager, researcher, architect, or consultant can cover very different jobs. The duties and requirements drive the analysis.

Employers also create risk when they change compensation or worksite arrangements after filing without immigration review. A remote move, pay reduction, promotion, new client site, or material change in duties can affect the LCA and petition. The earlier those changes are reviewed, the easier they are to handle.

Workers can make mistakes too. An H-1B worker who believes they are underpaid should keep records of pay, hours, duties, work location, offer terms, LCA information, and employer communications. They should get legal advice before taking steps that could affect status or employment.

Legal review is especially important before filing the LCA, before submitting a cap registration, before reducing pay or hours, before moving a worker to a remote or hybrid arrangement, before changing the worksite, or before promoting the worker into a materially different role.

Review is also important when the employer uses equity-heavy compensation, commission-heavy compensation, multiple worksites, third-party client sites, unusual SOC codes, or a wage source other than the standard OFLC wage data. These facts are not automatically disqualifying, but they need supportable documentation.

For Bellevue and Eastside employers, the goal is not to overcomplicate every hire. The goal is to make the salary record consistent before filing so the company can defend the LCA, the petition, and later changes. A careful wage review can prevent avoidable RFEs, amendments, compliance problems, and worker status issues.