O-1 Strategy
How to Build an O-1A Case When Your Primary Research Output Is Software or Code
Researchers whose primary output is software, code, or datasets face a genuine O-1A challenge because the criteria were designed with journal publications in mind. Here is how to map a software-centric research career onto the regulatory framework and build a petition adjudicators can evaluate on its merits.
Why software-primary researchers face a distinctive evidence problem
A growing category of researchers in computer science, computational biology, data science, and related fields produces its most significant contributions not in peer-reviewed papers but in open-source software tools, codebases, benchmarks, and datasets. A researcher whose primary output is a widely adopted machine learning library, a computational genomics pipeline, or an influential benchmark suite faces a genuine O-1A challenge: the USCIS regulatory framework was written with traditional academic-science careers in mind, and its eight criteria map most naturally onto journal publications, grant funding, and formal awards. Mapping a software-centric research career onto those criteria requires deliberate framing and a petition structure that explains to the adjudicator how software contributions function as extraordinary achievement in the field.
The eight O-1A criteria at 8 C.F.R. § 214.2(o)(3)(iii) — awards, membership, press coverage, judging, original contributions, scholarly articles, critical role, and high salary — do not explicitly address software, but none of them excludes it. USCIS policy and AAO guidance confirm that the criteria are evaluated in light of the specific standards of excellence in the petitioner's field. For fields where software is the primary medium of research contribution, a petition should open with expert letters that explain this field norm — that adoption metrics, GitHub stars, citations to software papers, and downstream research enabled by the tool are the relevant indicators of significance, not journal impact factors alone. This framing is the foundation on which every criterion exhibit rests.
Petitioners and their counsel should begin by auditing the software-centric record against each criterion and identifying where it is strongest. Most software-primary researchers have a solid original contributions showing, often a strong scholarly articles showing if they have published software papers in venues such as NeurIPS, ICML, or Journal of Open Source Software, and frequently a strong critical role showing if their tool is adopted at major research institutions. Judging through peer review for software conferences and workshops is increasingly available. The petition structure should lead with the two or three criteria that are documentable most directly, then supplement with additional criteria that round out the extraordinary ability showing.
Original contributions when the contribution is a software tool
The original contributions of major significance criterion at 8 C.F.R. § 214.2(o)(3)(iii)(E) is typically the most important criterion for software-primary researchers. Original contributions require evidence that the contribution is both original — not a derivative of existing tools — and of major significance to the field. For software tools, major significance is most directly demonstrated by adoption: how many research teams use the tool, how many papers published in peer-reviewed venues cite it or describe experiments conducted with it, and whether the tool is incorporated into research infrastructure at major universities or national laboratories. A bioinformatics pipeline adopted as the standard preprocessing step for a widely used genomics dataset, or a machine learning framework used in hundreds of published experiments, represents a contribution of major significance that few adjudicators would question if properly documented.
The adoption exhibit for a software contribution should be specific rather than relying on a raw GitHub star count. GitHub stars are a noisy popularity metric that correlates imperfectly with research adoption. More persuasive evidence includes: a curated list of published papers that explicitly describe using the petitioner's tool in their methodology section, with DOIs and publication venue names; letters from research directors at universities or national laboratories confirming that the tool is used in their active research programs; citations in other software tools that build on the petitioner's codebase; and any formal adoption decisions by professional communities such as Bioconductor, CRAN, PyPI package index statistics with institutional download breakdowns, or domain-specific consortia.
Where the petitioner's software contribution is accompanied by a peer-reviewed publication — a software paper in Journal of Open Source Software, a Methods paper in Nature Methods, or a systems paper at OSDI or SOSP — the citation record for that paper is directly relevant. Software papers in these venues are reviewed for methodological soundness and significance before publication, and citation counts for software methods papers should be contextualized against field norms by an expert letter. The expert should note whether citations at a given level reflect above-median adoption for the venue, subfield, and publication year, providing the adjudicator with the interpretive frame needed to assess the significance.
Scholarly articles and conference publications for code-primary researchers
The scholarly articles criterion at 8 C.F.R. § 214.2(o)(3)(iii)(F) requires published articles in professional or major trade publications. For computer science researchers, peer-reviewed conference proceedings at venues such as NeurIPS, ICML, ICLR, ACL, EMNLP, CVPR, ICCV, SIGMOD, VLDB, OSDI, and SOSP satisfy this criterion because these proceedings have competitive review processes, are indexed in major academic databases, and are treated as the primary publication venue in their subfields. The DBLP and ACM Digital Library serve as standard citation databases for this community, and the petitioner's publication record should be documented from one of these sources. USCIS has accepted conference publications in competitive CS venues as scholarly articles in prior adjudications.
For researchers whose software work is documented in technical reports, white papers, or preprints rather than formally published proceedings, the scholarly articles criterion may be thinner unless those documents meet the major trade publication standard on their own. arXiv preprints are widely circulated and cited in the field but do not have a peer review process, and their evidentiary status under this criterion is lower than publications in venues with formal editorial review. Where the petitioner's most significant software contribution is documented primarily in a preprint, the petition should supplement the scholarly articles exhibit with adoption evidence and expert letters explaining the preprint's field significance, and rely more heavily on the original contributions criterion.
Software documentation published as book chapters, O'Reilly or Springer technical books, or edited reference volumes may satisfy the scholarly articles criterion under the major trade publication prong when the publisher is recognized and the publication went through editorial review. A petitioner who has written an authoritative book-length treatment of their tool or the research methodology it implements — particularly where the book is adopted as a reference in university courses or graduate training — should include this in the scholarly articles exhibit with documentation of its adoption and sales or citation record.
Critical role at research institutions and in open-source communities
The critical role criterion at 8 C.F.R. § 214.2(o)(3)(iii)(G) requires evidence that the petitioner has performed in a critical or indispensable role for organizations or establishments with a distinguished reputation. For software-primary researchers, this criterion maps onto two distinct situations. The first is formal employment at a research institution, industry research laboratory, or national laboratory — where the petitioner's software work is integral to the organization's research mission. A principal researcher at a major industry research laboratory such as Google Brain, Microsoft Research, Meta FAIR, or a DOE national laboratory whose codebase is central to the organization's published research satisfies this criterion when the documentation shows that the organization's research output depends on the petitioner's contributions.
The second situation is stewardship of a widely adopted open-source project. A petitioner who is the principal maintainer or core developer of a software project used in research at multiple major universities occupies a critical role for the distributed research community that depends on the tool. Documenting this situation requires evidence of the petitioner's specific contribution to the project — not just that the project is widely used, but that the petitioner's continued work is what makes the project function. Commit history reports from the repository, statements from other contributors confirming the petitioner's central role, and letters from research users describing their dependency on the petitioner's continued development all contribute to this exhibit.
For petitioners at companies or laboratories where their software work enables commercial products or services — common in applied AI, data infrastructure, and developer tooling — the critical role exhibit should document the relationship between the petitioner's research software and the organization's strategic output. Internal performance reviews, promotional records, or statements from senior leadership describing the petitioner's role in the organization's research roadmap provide this documentation. Where the petitioner is listed as the technical lead or principal architect of a research infrastructure that supports a distinguished organization's scientific mission, that designation itself is strong critical role evidence.
Judging and peer review in software and computer science
The judging criterion at 8 C.F.R. § 214.2(o)(3)(iii)(D) requires evidence of judging the work of others. For software-primary researchers in computer science, qualifying judging service includes: program committee membership for top-tier venues such as NeurIPS, ICML, ICLR, ACL, CVPR, or SIGMOD; reviewing for systems and software engineering conferences at SOSP, OSDI, or EuroSys; and grant review panel service for NSF or NIH programs in computational research. Program committee service for NeurIPS or ICML in particular is highly selective — the organizing committees invite reviewers based on their demonstrated expertise — and a multi-year history of PC service at multiple top-tier venues provides strong judging evidence.
For researchers whose primary community is an open-source ecosystem, reviewing contributions to major projects — pull request review on high-profile repositories, technical leadership review for contributions to Apache Software Foundation projects, or editorial review for Journal of Open Source Software — can contribute to the judging exhibit. Journal of Open Source Software's review process is particularly well-documented and produces a publicly accessible review history that names reviewers, which makes it easy to include in the petition. Mentorship and evaluation of Google Summer of Code projects under a petitioner's supervision also provides documented evidence of judging the technical work of others.
Area chair and senior reviewer roles at top-tier venues carry more weight than standard reviewer roles because they involve meta-reviewing — evaluating reviewer assessments and making final recommendations to program chairs. A petitioner who has served as an area chair at NeurIPS, ICML, or ACL demonstrates that the organizing committee trusted their judgment enough to grant them evaluative authority over a set of submission outcomes. This is a meaningful indicator of recognized expertise in the field that distinguishes the petitioner from the broader pool of conference reviewers.
Assembling a coherent petition around a software-centric record
The O-1A petition for a software-primary researcher needs an attorney brief that performs explicit field-norm explanation. The brief should open by describing what extraordinary achievement looks like in the petitioner's field — the adoption metrics, the downstream research enabled, the institutional integration — and then map those field norms onto the regulatory criteria. An adjudicator unfamiliar with machine learning infrastructure or computational biology pipelines needs this framework before evaluating the exhibits. Without it, a software tool with a million downloads and citations in 500 published papers can appear like a popular consumer product rather than a foundational scientific contribution.
Expert letters are essential and should come from individuals with named institutional affiliations in the field — faculty at major research universities, research directors at national laboratories, or senior researchers at recognized industry labs — who can speak with authority about the petitioner's standing and the significance of their software contributions. Each letter should do three things: establish the letter writer's own credentials, describe the petitioner's specific contribution in technical terms the letter writer can verify, and situate that contribution within a comparative assessment of what the field considers extraordinary. Generic letters that describe the petitioner as brilliant without making comparisons to the field norm carry limited evidentiary weight.
The high salary criterion at 8 C.F.R. § 214.2(o)(3)(iii)(H) is often overlooked but is highly documentable for software-primary researchers at industry research laboratories or senior positions at technology companies. BLS OEWS data for computer and information research scientists (SOC 15-1221) shows the 90th percentile compensation for this occupation by metropolitan area, and researchers at Google Brain, Microsoft Research, Meta FAIR, or comparable organizations commonly earn at or above this threshold. A salary exhibit documenting compensation relative to the BLS 90th percentile benchmark, combined with strong original contributions and critical role exhibits, produces a petition that covers the required criteria with specific and credible evidence.
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.
See if you qualify
Lando reviews your background against the O-1 visa criteria and tells you honestly where you stand. Free, no commitment.