Success Stories
From Denial to Approval: engineer's O-1 Journey — February 2025
Detailed analysis with practical recommendations for O-1 applicants at every stage.
Understanding Why the First Petition Failed
A denied O-1A petition is not a permanent bar to approval — it is a diagnostic document. The denial notice, typically framed as a Notice of Intent to Deny (NOID) or a final denial following an RFE response, contains USCIS's specific findings about which criteria were not met and why the submitted evidence was deemed insufficient. Engineers who receive denials in February 2025 should treat the denial letter as a roadmap for the rebuild rather than a definitive judgment on their eligibility. The vast majority of O-1 denials stem from evidentiary gaps that are correctable, not from fundamental ineligibility under 8 CFR 214.2(o).
The most common failure pattern in software and hardware engineering O-1 petitions is overreliance on internal employment metrics — performance reviews, promotion histories, internal awards — without sufficient external validation. An engineer who has been consistently rated in the top 5% of their cohort at a major technology company has impressive internal recognition, but USCIS adjudicators look for evidence that the field — not just the employer — recognizes the person as extraordinary. Under 8 CFR 214.2(o)(3)(iii)(B), the eight criteria all require external markers of recognition, and petitions that fail typically do so because the evidentiary record is confined within the petitioner's employer rather than radiating outward into the profession.
A gap diagnosis begins by mapping the denied petition's evidence against each of the eight criteria under 8 CFR 214.2(o)(3)(iii)(B)(1)-(8) and identifying where the adjudicator found the evidence insufficient. Common findings include: salary evidence that was not benchmarked against a valid comparator group; judging evidence that reflected internal hackathon judging rather than external peer review; and press coverage that was about the employer or product rather than about the engineer personally. Once the specific gaps are identified, practitioners can build a targeted evidence supplementation plan for the new petition.
Rebuilding the High-Salary Criterion with Levels.fyi and BLS Data
One of the most frequently contested criteria in denied engineering petitions is the high-remuneration criterion under 8 CFR 214.2(o)(3)(iii)(B)(3). The typical failure mode is either submitting a compensation figure without adequate comparator data, or using a comparator dataset that the adjudicator finds unreliable or insufficiently specific to the relevant geographic market and specialization. Rebuilding this criterion requires both a more precise compensation figure and a more defensible comparator methodology.
Levels.fyi has become the gold standard for software engineering compensation comparisons in O-1 practice. The platform aggregates self-reported total compensation — base salary, annual bonus, equity refresh, and signing bonus — from engineers at named technology companies, filterable by job title, years of experience, and geographic location. For an engineer based in San Francisco or Seattle whose total compensation exceeds the 90th percentile on Levels.fyi for their role and experience band, the high-remuneration criterion is readily supportable. Practitioners should generate a Levels.fyi report filtered to the specific job title and city, download the data with date-stamp visible, and submit a declaration from a compensation expert or the petitioner's human resources department confirming that the total compensation figure on the offer letter or pay stub matches what is being claimed.
Bureau of Labor Statistics Occupational Employment and Wage Statistics (OEWS) data is a useful supplement because it is government-published and carries inherent credibility with USCIS adjudicators, even though its annual survey data tends to lag the market and understate top-of-market compensation at major technology companies. The recommended approach is to use BLS data to establish a national floor — showing that the petitioner earns well above even the national 90th percentile for their occupational code — and use Levels.fyi or comparable market surveys to show that even within the high-paying tech sector, the petitioner is an outlier. Layering both sources creates a more compelling cumulative picture than either source alone.
GitHub and Open-Source Contributions as Comparable Evidence
For engineers whose denial included a finding that press coverage was insufficient, open-source contributions and GitHub metrics offer a powerful alternative route under the 'comparable evidence' provision of 8 CFR 214.2(o)(3)(iv)(B). The regulation explicitly allows petitioners to submit comparable evidence when the enumerated criteria do not readily apply to the person's occupation. For software engineers, external recognition of technical work through open-source community adoption is directly analogous to the published material and original contributions criteria, even if it does not fit neatly into a traditional press article format.
The strongest GitHub-based evidence combines quantitative metrics — star counts, fork counts, contributor statistics, download counts for published packages — with qualitative third-party validation. A repository with 10,000+ GitHub stars demonstrates that a large community of developers finds the work valuable enough to bookmark and build upon; this is a form of peer recognition that carries genuine weight. Practitioners should document the star count and fork count on a specific date, provide context about what is typical for repositories in the same technical domain, and supplement with evidence of downstream adoption — companies or projects that publicly credit the petitioner's library or framework in their own codebases or documentation.
Common mistake: Submitting GitHub statistics without context about what those numbers mean in the field. An adjudicator who is not a software engineer cannot independently evaluate whether 2,000 GitHub stars represents extraordinary recognition or median performance for a repository of that type. Every quantitative metric needs an expert declaration or published industry reference explaining why the figure demonstrates extraordinary-level achievement. The expert declaration under 8 CFR 214.2(o)(5) is the appropriate vehicle for this contextualization, and the consulting expert should be selected for their credibility in the open-source or developer tooling community.
Individual Contributor Ladder Evidence for the Critical Role Criterion
Large technology companies typically maintain two parallel career tracks: a management track (engineering manager, director, VP) and an individual contributor (IC) track (senior engineer, staff engineer, principal engineer, distinguished engineer, fellow). For engineers on the IC track, demonstrating a critical or essential role under 8 CFR 214.2(o)(3)(iii)(B)(8) requires translating the internal leveling system into language that an immigration adjudicator can understand and credit.
The IC ladder is relevant because major technology companies — Google, Meta, Apple, Microsoft, Amazon — have published or widely acknowledged leveling frameworks in which the highest IC levels (Google L7 and above, Meta E7 and above, Microsoft Principal and above) are occupied by a tiny fraction of the engineering workforce and carry responsibilities that would otherwise belong to a director or VP on the management track. A staff or principal engineer at a major tech company who owns the architecture of a system used by hundreds of millions of users, and who is one of fewer than a dozen engineers company-wide at that level in their specialty, has a strong factual basis for the critical role criterion.
Practitioners should request that the petitioning employer provide a declaration from a senior technical or HR executive that: (1) describes the petitioner's specific role and technical contributions; (2) explains the company's leveling framework and the rarity of the petitioner's level; (3) quantifies the user impact or business significance of the systems the petitioner is responsible for; and (4) addresses why the organization's technical objectives could not be achieved without someone of the petitioner's particular expertise. Under 8 CFR 214.2(o)(2)(iv)(E), the employer's filing must include a statement of the services to be performed, and this declaration should expand on that statement with the level of specificity needed to satisfy the critical role criterion.
RFE Response Strategy: Structure and Tone
An RFE in an engineering O-1 case is an opportunity to supplement the record and directly rebut the adjudicator's concerns, not merely to submit additional documents. The most effective RFE responses in February 2025 practice follow a structured format: a brief executive summary of the response's key points, a section-by-section rebuttal organized by criterion, a table of contents keyed to the appended exhibits, and a clear statement of why the totality of the evidence — both original and supplemental — satisfies the O-1 standard under the applicable legal framework.
The 'totality of evidence' standard is articulated in the USCIS Policy Manual and stems from the Matter of Chawathe line of precedents. Engineers who satisfy only three criteria at a borderline level face a harder path than those who clearly satisfy five or six criteria. An RFE response is an opportunity to push the petition toward clear sufficiency by adding criteria rather than merely shoring up the original three. If the original petition addressed high salary, judging, and press coverage, the RFE response might add original contributions documentation (through patent filings or published technical papers), association membership evidence (through IEEE or ACM membership with selection criteria), and additional critical role documentation — turning a three-criterion petition into a six-criterion petition.
Common mistake: Responding to an RFE by repeating arguments that already failed without introducing new evidence or legal argument. Adjudicators are required to consider the totality of the evidence, but they are not required to change their conclusions simply because the petitioner restates their position more forcefully. Every new document submitted in response to an RFE should be accompanied by a specific explanation of what it demonstrates and how it responds to the particular concern raised in the RFE. A response that submits 200 pages of new exhibits without a clear analytical roadmap places the burden of interpretation on the adjudicator — a burden that may not be discharged in the petitioner's favor.
Building the Record Before Refiling: A Six-Month Plan
Engineers who received a denial in late 2024 or early 2025 and are planning to refile should treat the intervening period as a credential-building window rather than a waiting period. A targeted six-month plan might include: submitting abstracts to technical conferences in the engineer's specialty for judging or speaking opportunities; making targeted contributions to high-visibility open-source projects to build GitHub credibility; pursuing publication of a technical blog post, white paper, or conference paper that can serve as original contributions evidence; and identifying media opportunities through their employer's PR team or through direct outreach to technology journalists who cover their specialty.
The judging criterion under 8 CFR 214.2(o)(3)(iii)(B)(4) is one of the most buildable in a short timeframe. Academic conference program committees — even at venues below the top-tier NeurIPS/ICML/CVPR level — constitute valid judging evidence if the review process is genuinely peer-reviewed. Engineers who have never served as reviewers can often obtain an invitation simply by emailing a program chair they know or by volunteering through the conference's reviewer recruitment process. Several major software engineering venues, including IEEE International Conference on Software Engineering (ICSE) and ACM CHI, actively recruit reviewers and welcome mid-career practitioner reviewers from industry.
Under 8 CFR 214.2(o)(3)(iv)(B), where the listed criteria do not readily apply, a petitioner may submit comparable evidence. Engineers working in highly specialized fields — quantum computing, semiconductor design, novel hardware architectures — should document the field's unique professional structures in collaboration with their consulting expert under 8 CFR 214.2(o)(5). If the field does not have the traditional press coverage or award structures that USCIS adjudicators are accustomed to, the comparable evidence argument must explain why and then provide the closest functional equivalents. This argument is most persuasive when made proactively in the initial petition rather than reactively in an RFE response.
Timing the Refile and Managing Status Transitions
Engineers whose prior O-1 petition was denied and who are currently in H-1B or other nonimmigrant status face a timing dilemma: refiling immediately with supplemented evidence versus waiting until the credential-building plan is complete. The answer depends on the severity of the evidentiary gaps identified in the denial and the petitioner's current status expiration date. Where the denial reflects a borderline evidentiary record rather than a fundamental misconception of the regulatory standard, an immediate refile with targeted supplementation may succeed. Where the record has structural gaps — no judging evidence, no press coverage, borderline salary evidence — waiting until those gaps are filled is the more prudent approach.
While waiting, engineers should ensure their underlying nonimmigrant status remains valid and properly maintained. An H-1B extension filed before the current status expires preserves legal status pending adjudication under the cap-gap or timely-filed rules. Engineers in F-1 OPT status face a harder timeline constraint; if the OPT period expires before the O-1 is approved, there is no cap-gap equivalent for O-1 petitions. Premium processing under the current $2,805 fee is typically the appropriate election for engineers in OPT whose authorization period is running out.
Common mistake: Assuming that a previously denied petition can simply be refiled as an amendment or a continuation of the prior case. Under USCIS procedures, a denied petition is a closed case, and a new petition must be filed as a fresh filing with new fees. The new petition should address the grounds for the prior denial directly — not to relitigate the denial, but to demonstrate that the new evidentiary record cures the identified deficiencies. Failing to acknowledge and respond to a prior denial in the new filing can create the impression that the petitioner is ignoring USCIS's concerns, which is rarely a persuasive posture.