O-1 Strategy
How to Build an O-1A Case When Your Primary Contribution Is Open-Source Software Infrastructure Used by Thousands of Research Institutions in 2026
Open-source software that powers research infrastructure at thousands of institutions worldwide can support an O-1A petition, but only when petitioners translate code contributions into the regulatory criteria. This article explains how to frame OSS impact as original contributions, critical role, and expert recognition evidence in 2026.
The O-1A challenge for open-source software contributors
Open-source software contributors whose work underpins research computing infrastructure at universities, national laboratories, and scientific collaborations worldwide face a counterintuitive petition challenge: the scale of their impact is visible in downloads, GitHub adoption metrics, and institutional references, but USCIS adjudicators typically evaluate O-1A petitions through a lens calibrated for traditional academic careers — journal publications, grant awards, faculty positions. A researcher whose primary contribution is a widely adopted numerical methods library or distributed computing framework has produced work with extraordinary impact, but that impact must be translated carefully into the evidentiary categories the O-1A regulation recognizes.
The eight criteria for O-1A extraordinary ability under 8 C.F.R. § 214.2(o)(3)(ii) include prizes or awards, membership in elite associations, press coverage, judging of others' work, original contributions of major significance, scholarly articles, critical role at a distinguished organization, and high salary or remuneration. For a software infrastructure contributor, the most relevant criteria are original contributions, critical role, scholarly articles when papers accompany the software, and judging in the form of grant review panels and technical committees. High salary evidence is often available from technology-sector employment data and should not be overlooked, as it is frequently the criterion least in need of framing explanation.
The petition brief must explain what the software does, why it is used by thousands of institutions, and what distinguished the petitioner's specific technical decisions from comparable work in the same space. This is not a matter of exaggerating the contribution — a scientific computing library that is genuinely foundational to a research community is an extraordinary contribution by any reasonable standard — but of explaining that contribution in a form accessible to a non-technical adjudicator. The brief should describe the software's user base, its position in the research computing stack, the problem it solved, and why comparable alternatives did not adequately address that problem.
Original contributions of major significance
The original contributions criterion requires evidence that the petitioner has made original scientific, scholarly, or business-related contributions of major significance in the field. For a software infrastructure contributor, the clearest evidence comes from documentation of widespread institutional adoption and expert testimony that the contribution advanced the state of the art in a way that would not have occurred otherwise, or would have occurred more slowly. Adoption by agencies such as NSF-funded supercomputing centers — ACCESS-affiliated institutions including TACC, SDSC, NCAR, and NCSA — national laboratories such as Argonne, Lawrence Berkeley, or Oak Ridge, and major research universities demonstrates a scale of impact difficult to achieve through ordinary professional work.
Download statistics and package repository data — from PyPI, Conda-forge, CRAN, or equivalent repositories — provide quantitative evidence of adoption breadth. These statistics should be contextualized by an expert letter from a senior researcher who uses the software, explaining what problem it solves, why existing alternatives were inadequate, and how the petitioner's specific design decisions or algorithmic contributions made the software significantly more capable or accessible than comparable tools. A letter from a director of a national computing facility or a senior faculty member at an R1 institution who has integrated the software into their research infrastructure is particularly persuasive because the institutional context establishes that the expert is evaluating the contribution against high research standards.
Citations to academic papers describing the software provide the most direct link between the open-source contribution and the scholarly community USCIS adjudicators understand. A software paper published in the Journal of Open Source Software, SoftwareX, the Journal of Statistical Software, or a conference proceedings paper that introduces the software and its methodology converts the code contribution into a recognizable scholarly record. When the software paper has accumulated substantial citations from researchers across multiple disciplines who rely on the software in their own published work, the citation record documents the original contribution's significance in a form directly accessible to a non-specialist adjudicator.
Scholarly articles and research publications
For software infrastructure contributors with academic affiliations or research roles, the scholarly articles criterion is accessible through papers that describe the software's design, methodology, and scientific applications. Conference proceedings at venues such as SC (the ACM/IEEE International Conference for High Performance Computing), SciPy, SOSP, and USENIX venues, as well as systems papers at machine learning conferences such as NeurIPS and ICML, can establish a peer-reviewed publication record directly tied to the software contribution. Papers in these venues are reviewed through competitive double-blind processes and acceptance decisions reflect the judgment of senior researchers in the relevant technical community.
Papers in which other researchers use the petitioner's software to conduct published research provide indirect evidence of the contribution's significance and can be compiled as part of the original contributions exhibit. The petition should aggregate all papers that cite the software or its introductory paper from the ACL Anthology, arXiv, Semantic Scholar, or relevant disciplinary databases, and present this citation record with expert commentary explaining what portion of papers in the field now depend on the petitioner's infrastructure. When a substantial fraction of published research in a given subfield relies on the same software stack, an expert can credibly attest that the petitioner's contribution is foundational rather than incidental.
For contributors who have not published formal papers describing their software, a research technical report, a preprint that has been widely cited on arXiv, or a documentation-style reference that has been formally acknowledged in peer-reviewed publications can serve as supplemental evidence when combined with strong expert testimony. The petition brief should acknowledge the non-traditional publication form and explain why technical contributions in the software infrastructure space are often disseminated through repositories and technical reports rather than traditional journals — a practice that is standard in the field and does not diminish the significance of the contribution. Expert letters from senior researchers who can attest to this norm add important credibility to this argument.
Critical role at a distinguished organization
Open-source software maintainers who lead foundational projects are often employed by technology companies, universities, or nonprofit software foundations — organizations whose distinguished reputations support the critical role criterion. A principal engineer or software architect role at a company with recognized leadership in the industry, a research scientist role at a university whose computing infrastructure program is nationally recognized, or a staff position at a nonprofit such as NumFOCUS, the Apache Software Foundation, or the Python Software Foundation can establish the organizational component of the criterion. The petition should document the organization's reputation with objective markers: headcount, revenue, research publications, or institutional rankings as appropriate.
The critical role element requires showing that the petitioner's role is both distinguished in nature and central to the organization's operation or mission. For an open-source project lead, this means documenting the decision-making authority that comes with the maintainer role: the ability to accept or reject contributions from other developers worldwide, the authority to set the technical direction of the project, and the responsibility for design decisions that affect all downstream users. Letters from collaborators, institutional users, or other senior developers explaining that the petitioner's technical judgment is what distinguishes the project's direction from what a committee of competent engineers would produce support the critical role argument effectively.
When the petitioner is employed by a university as a research software engineer or faculty member with a software infrastructure focus, the critical role criterion can be established through leadership of a research computing group, directorship of a campus cyberinfrastructure facility, or a principal investigator role on NSF-funded projects funding the development of the software. NSF's cyberinfrastructure grants through the Office of Advanced Cyberinfrastructure are specifically designed to fund research software tools with broad community use, and PI status on such a grant establishes both critical role and original contributions evidence simultaneously, as the selection process validates both the software's importance and the petitioner's leadership of its development.
Judging, peer review, and professional recognition
Peer review service for NSF, DOE, or equivalent funding agencies contributes judging criterion evidence for software infrastructure contributors who are invited to evaluate technical grant proposals. NSF's Office of Advanced Cyberinfrastructure regularly convenes expert review panels for cyberinfrastructure grant programs, and service on such a panel reflects the agency's judgment that the reviewer has the expertise and standing to assess the scientific merit of proposed software development projects. An expert letter from a senior NSF program officer or panel organizer confirming the invitation process and its selection criteria converts the review service into accessible judging criterion evidence.
Program committee service for technical conferences — including reviewing roles at SC, SciPy, SOSP, OSDI, or the systems track of machine learning conferences — constitutes judging evidence drawn from the research computing and software engineering communities. The petition should document specific conferences and years of service, with a letter from a program chair or senior area chair explaining the selection process for technical reviewers and the expertise threshold required. Selection as a program committee member for a highly selective computing conference, particularly in a senior capacity such as area chair or technical program co-chair, reflects community recognition that the petitioner's technical judgment is among the most valued in the relevant subfield.
Membership in technical committees such as the IEEE Technical Committee on High Performance Computing, the ACM Software System Award selection committee, or comparable professional society bodies constitutes membership criterion evidence. Professional society recognition through senior membership or fellowship in IEEE or ACM — which require peer nomination and documented evidence of outstanding professional achievement — directly satisfies the O-1A membership criterion and provides an externally certified indicator of the petitioner's standing within the computing research community. Both IEEE Senior Member and IEEE Fellow programs involve peer review by independent committees evaluating candidates against documented criteria for sustained and recognized professional contribution.
Building the complete evidence strategy
A strong O-1A petition for an open-source software infrastructure contributor requires a brief that explains the contribution's significance in terms accessible to a non-technical adjudicator before presenting the evidentiary documents. The brief should describe the software in concrete terms — what problem it solves, who uses it, what research would not have been possible without it — and then systematically map the available evidence to the regulatory criteria. This translation layer is the work of the petition brief; without it, a USCIS adjudicator encountering an exhibit folder of GitHub traffic reports, download statistics, and conference papers may not understand how any of it relates to the legal standard for extraordinary ability.
Expert letters should come from researchers who can explain the petitioner's specific technical contributions in terms that connect to the broader scientific significance of the software. A useful letter for this type of petition comes from a senior computational scientist, a director of a national supercomputing facility, or a faculty member who has published research using the petitioner's software and can attest to what it enabled that was not previously possible. The strongest letters are specific: they describe a technical problem the software solved, explain why competing tools were inadequate, describe how the petitioner's design choices were non-obvious, and attest that the contribution is extraordinary by the standards of the international research computing community.
High salary evidence should be developed in parallel with the substantive criteria. For software engineers and research scientists working in technology or at well-funded research institutions, compensation data from the BLS Occupational Employment and Wage Statistics survey, Levels.fyi for technology-sector roles, or institution-specific published salary schedules provides the geographic benchmark needed to document that the petitioner's compensation is substantially above the median for comparable positions. USCIS has accepted compensation at or above the 90th percentile for comparable positions as evidence satisfying the high salary criterion, and the evidentiary bar for this criterion is relatively low compared to criteria requiring expert testimony about technical significance.
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.