Evidence Building
Building a High Salary Evidence Package for O-1A Software Engineers in 2026
Software engineers in industry roles often have the clearest path to satisfying the O-1A high salary criterion, but the documentation errors in salary exhibits are consistent and avoidable. This guide covers which compensation sources USCIS accepts, how to handle equity-heavy packages, and how to present borderline records effectively.
The criterion and what's at stake
The high salary criterion is one of eight O-1A criteria under 8 C.F.R. § 214.2(o)(3)(iii), and for software engineers in industry roles, it is frequently the most direct and well-documented criterion in the petition. Unlike the scholarly articles criterion — which requires peer-reviewed publications that many industry engineers do not hold — or the awards criterion — which requires recognition from a limited set of highly competitive institutions — the high salary criterion is accessible to any engineer whose total compensation package is structured at the level typical for senior practitioners at high-paying technology employers. The criterion carries weight in the overall O-1A analysis in proportion to how clearly it is documented: a well-supported high salary exhibit is difficult for an adjudicator to question, which makes it a reliable anchor for the three-criterion threshold.
The strategic importance of the high salary criterion for software engineer petitions extends beyond its individual evidentiary value. In the O-1A framework, no single criterion is dispositive — the petition must satisfy at least three of eight criteria, and each criterion contributes to the overall extraordinary ability finding. A high salary criterion that is clearly satisfied and thoroughly documented provides a stable foundation that allows the attorney to focus the petition's more complex argumentative work on the other two criteria, rather than having to argue three criteria simultaneously from positions of partial evidence. Petitioners who underinvest in salary documentation — submitting only a single offer letter without wage benchmarks — create unnecessary vulnerability in what should be the easiest criterion to close.
USCIS adjudicators are not industry compensation experts, and even adjudicators with significant experience in software engineer O-1A petitions benefit from salary evidence that is self-explanatory rather than requiring field knowledge to interpret. A petition that presents a total compensation figure of $400,000 annually without context provides much less useful evidence than one that pairs that figure with BLS OEWS 90th percentile data showing that software developers in San Francisco earn a 90th percentile wage of $250,000, followed by an explanation of how the petitioner's base salary alone exceeds that benchmark, with equity and bonus as additional compensation components. The petition does not win on the merits alone — it wins when the merits are presented in a format an adjudicator can evaluate without supplemental research.
What the regulation requires
The regulatory text for the high salary criterion is brief: 8 C.F.R. § 214.2(o)(3)(iii)(B)(7) requires evidence that the alien has either commanded a high salary or will command a high salary or other remuneration for services, evidenced by contracts or other reliable evidence. The operative analytical question — what constitutes a high salary relative to others in the field — is not defined in the regulation itself but is addressed in the USCIS Policy Manual and in AAO non-precedent decisions applying the extraordinary ability standard. The field comparison must be to others in the field rather than to the general labor market, which means the petition must benchmark the petitioner's compensation against compensation data for comparable workers in the specific occupation — software developers, or the more specific engineering specialty at issue — rather than against median household income or general professional compensation.
The 90th percentile of the relevant BLS OEWS occupation group is the threshold that USCIS adjudicators most commonly treat as the benchmark for a finding of high salary, though the regulations do not specify a percentile threshold. In practice, petitions where compensation falls clearly above the 75th percentile but short of the 90th often succeed with supplemental evidence — multiple benchmark sources, employer-provided context, or expert letter testimony placing the compensation in a field-specific context. Petitions where the base salary is at the 50th to 70th percentile for the relevant occupation face a more difficult burden regardless of supplemental evidence. For software engineers in high-wage metropolitan areas, the gap between median and 90th-percentile compensation is substantial — often $100,000 or more on base salary alone — which makes the geographic specificity of the benchmark critically important.
The others in the field comparison must reflect the correct occupation code and geography. A software engineer employed at a San Francisco-area technology company should be benchmarked against OEWS data for Computer and Information Research Scientists (SOC 15-1221), Software Developers (SOC 15-1252), or Software Quality Assurance Analysts and Testers (SOC 15-1253), as applicable, in the San Francisco-Oakland-Hayward metropolitan statistical area rather than in national aggregate data. National data systematically understates the relevant compensation range for technology-sector roles because it is diluted by lower-wage regions. Using national data to benchmark a San Francisco engineer produces a misleadingly high apparent percentile ranking and can create an accuracy problem if an adjudicator independently checks the claim against regional data. Geographic specificity is not optional.
Evidence that routinely satisfies the criterion
The primary salary documentation for a software engineer O-1A petition consists of three elements: the offer letter or current employment agreement documenting base salary and additional compensation components, current paystubs or W-2 records confirming the compensation has been paid as stated, and a BLS OEWS wage table for the correct occupation and metropolitan statistical area documenting the 90th percentile wage. These three elements, properly cross-referenced and clearly organized, constitute the core of a complete high salary exhibit. The offer letter or employment agreement should be as recent as possible — ideally within 12 months of the petition filing date — and should document each compensation element separately: base salary, target annual bonus, equity compensation with vesting schedule and per-share FMV valuation basis, and any other regular compensation elements.
Equity compensation — restricted stock units, stock options, or performance shares — is includable in the high salary analysis when it is regularly scheduled as a component of the compensation structure and when its current value can be established by reference to publicly verifiable data or a qualified valuation. For engineers at publicly traded companies, RSU compensation can be valued using the current stock price and the number of units scheduled to vest in the relevant year, creating a dollar-equivalent equity component that is added to base salary and cash bonus for a total annual compensation figure. For engineers at private companies, equity valuation requires a 409A valuation or a comparable independent fair market value determination. Unvested equity that is subject to forfeiture on departure should be disclosed as such rather than presented as a definitive compensation element.
H-1B Labor Condition Application data and levels.fyi market data can supplement BLS OEWS data as secondary benchmarks, but each source has limitations that the petition should acknowledge. LCA data captures only the prevailing wage floor required for H-1B compliance, not the actual distribution of compensation at leading technology companies, and draws from a different methodology than OEWS data. Levels.fyi provides crowdsourced compensation data from technology company employees and covers total compensation more comprehensively than BLS data for senior software engineering roles, but has no regulatory standing as an official wage source and may not be accepted as a substitute for OEWS data. Using these sources as supplemental context — to show that the BLS 90th percentile benchmark is itself conservative for senior roles at leading technology employers — is a legitimate and often persuasive framing.
Evidence USCIS regularly discounts
Total compensation figures that include unvested equity presented without disclosure of the vesting schedule are the most common salary exhibit error in software engineer O-1A petitions. If the petition states that the petitioner's annual compensation is $600,000 but $400,000 of that figure represents unvested RSUs scheduled to vest over four years, the sustainable annual compensation is materially different from the headline figure. Adjudicators and reviewing attorneys who conduct audits of such petitions regularly flag these presentations as overstated, and an RFE asking the petitioner to clarify the compensation structure typically results in a revised figure that is significantly lower. Presenting compensation clearly — with base salary, target bonus, and annualized equity separately itemized — eliminates this vulnerability rather than managing it after the fact.
Self-reported compensation figures without supporting documentation from the employer or from payroll records carry limited evidentiary weight. A petitioner who submits only an offer letter without paystubs, W-2s, or employer verification cannot demonstrate that the stated compensation was actually received rather than offered. Adjudicators cannot verify self-reported figures independently, and the absence of corroborating documentation creates a credibility gap that an RFE will address by requesting the missing records. Petitioners who have recently changed employers, or who are filing on the basis of a new employment offer, should document the new compensation with the offer letter and supplement with prior employer W-2 records showing compensation at the same or comparable levels to establish a compensation pattern rather than a one-time arrangement.
Compensation benchmarks drawn from incorrect geographic regions or incorrect occupation codes systematically overstate the petitioner's standing relative to comparable workers. A software engineer in Austin, Texas, benchmarked against San Francisco MSA data at the 90th percentile appears to exceed the benchmark — but the correct benchmark for Austin produces a lower threshold that may not be exceeded. Using the highest available regional benchmark regardless of the petitioner's actual work location produces a presentation that is technically inaccurate and undermines the petition's credibility if reviewed by an adjudicator who checks the source data. Similarly, benchmarking a software quality assurance engineer against the Computer and Information Research Scientists SOC category — which covers a narrower and higher-paid occupational group — overstates the benchmark threshold and misrepresents the relevant comparison.
How to present borderline evidence
When base salary alone falls at approximately the 80th to 85th percentile for the relevant occupation and geography, the petition has two standard approaches to crossing the high salary threshold. The first is to add documented equity and bonus compensation to establish that total annual compensation clearly exceeds the 90th percentile, provided the equity can be valued using publicly available market data or a qualified valuation report. The second is to argue that the threshold is the 75th percentile rather than the 90th, supporting this with a field-specific expert letter establishing what compensation level reflects extraordinary achievement in the petitioner's specific specialty — particularly where the specialty is a subfield with a more compressed wage distribution than the broader occupation category captures.
Multiple benchmark sources — OEWS data, employer-conducted compensation surveys, and professional association salary benchmarks for the relevant specialty — used in combination can establish that the petitioner's compensation exceeds the relevant threshold even when no single source produces a clean result. An employer declaration explaining that the petitioner's compensation is in the top quintile of engineers at the company, in the context of a company known for leading-market compensation, supplements the objective benchmark data with a contextual claim about relative positioning that is credible coming from an informed insider source. The employer declaration should stop short of making unverifiable statistical claims but can credibly state how the petitioner's compensation ranks within the employer's internal compensation bands for equivalent roles.
Where the petitioner is at an early career stage — fewer than five years of post-degree professional experience — with compensation that exceeds the 90th percentile for junior engineers but falls below the 90th percentile for the full occupation distribution, the petition should argue the comparison against peers at the petitioner's career stage rather than against the full occupational distribution. USCIS has accepted this framing in non-precedent AAO decisions where the petitioner's extraordinary ability finding depends on demonstrating achievement substantially above that ordinarily encountered at the same career stage. The petition must make this argument explicitly and support it with wage data or expert testimony establishing what compensation at the petitioner's career stage represents the 90th percentile, and why the petitioner's compensation clearly exceeds that mark.
Building and auditing the salary exhibit
A complete high salary exhibit for a software engineer O-1A petition should contain, in this order: a cover exhibit letter explaining the criterion and summarizing the petitioner's compensation, the current offer letter or employment agreement with all compensation components itemized, the most recent two or three W-2 or 1099 forms, two to four recent paystubs confirming current compensation is being paid as stated, a printout of the relevant BLS OEWS wage table with the 90th percentile figure highlighted and the data download date noted, a compensation summary memorandum from the employer's finance or HR function confirming total annual compensation in dollar equivalents, and any equity valuation documents referenced in the compensation summary.
Before submitting the salary exhibit, the petitioner's attorney should audit the compensation calculation to confirm that the methodology is internally consistent. Base salary on the offer letter should match base salary on the paystubs. The W-2 Box 1 wages for prior years should reflect the compensation levels stated in prior offer letters, adjusted for any raises or restructured compensation. Equity grant records should show vesting dates and FMV valuation dates that are consistent with the claimed per-share or per-unit values used in the compensation summary. An internally inconsistent salary exhibit invites adjudicator scrutiny and RFE requests even when the underlying compensation is genuinely high. Consistency between documents — not merely the total figure — is what makes the exhibit credible.
The petition should be filed with the most current salary documentation available. If the petitioner has received a salary increase in the 12 months preceding the filing date, the petition should reflect the current, higher compensation rather than prior-year data, using the most recent paystub and an updated employer compensation letter. For petitions where the petitioner's compensation at filing is materially higher than the compensation documented in prior-year W-2 records, the petition should explain the increase — a promotion, a role change, a significant equity grant — to preempt adjudicator questions about the reliability of the current compensation claim. A petition that documents a compensation trajectory demonstrates both the absolute level of current compensation and a pattern of achievement consistent with the extraordinary ability standard.
What we typically gather for this kind of case
| Document | Where to source | Why it matters |
|---|---|---|
| Peer-reviewed publications | Web of Science / Scopus exports | Anchors original-contributions and authorship criteria |
| Citation analysis | Google Scholar profile + ESI top-1% data | Quantifies major significance in the field |
| Salary benchmark | BLS OEWS for SOC code + locality | Documents high-salary criterion at 90th-percentile or above |
| Critical-role letters | Direct supervisor + program director | Establishes role's importance, not just title |
What we see go wrong, again and again
- 01Treating extraordinary ability as a credentials checklist rather than a story of field-wide impact.
- 02Submitting bibliometric data (h-index, citation counts) without explaining what makes those numbers high relative to peers in the same sub-field.
- 03Relying on letters from collaborators or co-authors rather than independent experts who can speak to influence.