Evidence Building
Documenting Original Contributions of Major Significance for Software Engineers Whose Work Is Proprietary and Not Publicly Disclosed
Software engineers whose most significant work is protected by NDAs or security classifications can still satisfy the O-1A original contributions criterion. The approach requires patents, targeted expert letters, and public-facing signals of field recognition — not disclosure of the proprietary system itself.
The original contributions criterion and why software engineers face a distinct challenge
The original contributions criterion under 8 C.F.R. § 214.2(o)(3)(iii)(B)(5) requires a petitioner to show that they have made original scientific, scholarly, or business-related contributions of major significance in their field. For software engineers and applied technologists working in corporate settings, this criterion presents a particular structural problem: the work itself is typically owned by the employer, covered by non-disclosure agreements, and not published in any academic or public forum. A researcher at a university can point to journal articles, conference proceedings, and open-source tools. A software engineer at a financial firm, a cloud provider, or a defense contractor may have designed systems that are genuinely significant but are classified, proprietary, or simply never disclosed to the public.
The problem is not that proprietary work cannot satisfy the criterion. It is that USCIS adjudicators reviewing the petition have no independent way to evaluate the significance of work they cannot see. The regulatory language requires original contributions of major significance to the field, and the word field implies a community of practitioners who can assess the contribution's value. When the work is not disclosed, the evidence of its significance must come entirely from expert attestation, internal documentation that can be disclosed, and indirect markers of impact — patent records, industry citations where they exist, adoption metrics that have been publicly reported, or recognition by third parties who are aware of the work. Each of these proxies has limitations that the petition must account for.
For petitioners who cannot disclose the work itself, the quality of the expert letters carrying the evidentiary weight becomes critical in a way it is not for researchers with public publication records. A generalist letter that praises the petitioner's skills without describing specific contributions provides almost nothing for the original contributions criterion when the work is proprietary. The letter writers must be individuals who have direct knowledge of the petitioner's specific technical work — colleagues, former supervisors, external collaborators who interacted with the technology — and who can describe what was done and why it represents a meaningful advance in the field, even if they cannot disclose confidential details.
What the regulation actually requires for original contributions
The regulatory text requires that the petitioner have made original scientific, scholarly, or business-related contributions of major significance in the field. Each element of this phrase has been interpreted through USCIS policy guidance and AAO decisions. Original means the contribution was new — the petitioner did not simply apply existing techniques to a standard problem, but developed something that was not previously available in the field. Major significance is the harder threshold, and it means that the contribution must have had actual impact on how others in the field approach similar problems. A system that was deployed internally and used only by the petitioner's employer does not automatically satisfy major significance simply because it was technically sophisticated.
The AAO has consistently interpreted major significance to require more than mere competence or successful project delivery. The petitioner's contribution must have changed something for the broader field — influenced how others design systems, been adopted or adapted by others, addressed a problem that the field recognized as important, or contributed to standards, benchmarks, or practices that others rely on. For software engineers working on proprietary systems, demonstrating major significance requires showing that the work's impact extended beyond the immediate employer. This can take the form of conference presentations, industry talks, technical blog posts that influenced practitioners, citations in publicly available academic or industry literature, or patents that prompted responses from competing organizations.
Business-related contributions receive different treatment than scientific contributions in USCIS adjudication. Under the policy manual, contributions to a company's internal efficiency, revenue growth, or product development that are significant to the company but have no measurable impact on the broader field do not satisfy the criterion. An engineer who built a proprietary recommendation engine that increased conversion rates for a single organization has made a contribution that was significant to the employer, but significance to a single organization is not significance to the field. Petitioners must frame their contributions in terms of their impact on the field as a discipline — the broader community of practitioners who design and evaluate similar systems.
Evidence that routinely satisfies the criterion for proprietary work
Patents and patent applications are the most direct public record of original technical contributions and are explicitly cited in the O-1A criteria regulation. When a software engineer's work has been patented, the patent record establishes that an independent expert evaluator at the USPTO determined the invention to be novel and non-obvious. A granted patent, particularly one that has been cited by subsequent patents from other companies or institutions, provides direct evidence that the contribution was both original and recognized as significant by others in the field. A series of granted patents in a technical area, with citation records from subsequent filers, creates a strong portfolio for the original contributions criterion even when the underlying code or system is never publicly disclosed.
Expert letters from credentialed practitioners outside the petitioner's employer are the second core element for proprietary work cases. These letters work best when the letter writer can describe the petitioner's contribution in technical terms that establish its novelty — not simply assert that the petitioner is a talented engineer, but explain the specific problem the work solved and why that approach represents a meaningful advance beyond what was previously available. Letter writers who have knowledge of the petitioner's work through conference interactions, collaborative projects across institutional lines, or review of a patent or published paper written by the petitioner are better positioned to write letters that will survive adjudicator scrutiny than former colleagues bound by the same NDA.
Published technical work that preceded or followed the proprietary contribution can provide a useful anchoring record. A software engineer who published papers at NeurIPS, ICML, ICLR, or a comparable venue before moving into a corporate role can use that publication record to establish that they were operating at a level of original technical contribution recognized in the academic field. The proprietary corporate work is then presented as a continuation of that established research trajectory. This approach is most effective when the published work and the proprietary work address related technical problems, so that the letter writers can speak to both in a coherent narrative.
Evidence USCIS regularly discounts for proprietary contributions
Performance reviews, internal awards, and employer declarations that the petitioner's work was of exceptional quality within the company receive little weight in USCIS adjudications of the original contributions criterion. These documents speak to the petitioner's value to a single organization, not to the significance of their contribution to the broader field. An adjudicator reviewing an O-1A petition is not evaluating whether the petitioner was a top performer at their employer — the criterion requires significance to the field, and internal employer recognition does not establish external field significance. Petitions that lead with lengthy descriptions of internal promotions, performance ratings, or business impact metrics as evidence for original contributions consistently draw RFEs requesting external evidence of field significance.
Invitations to give company-internal or invite-only technical talks do not satisfy the original contributions criterion unless the talks were at externally recognized industry conferences or gatherings where the audience consisted of practitioners from across the field. A technical talk given to colleagues at an internal engineering summit is not evidence that the field recognizes the contribution as significant. Talks at major externally recognized conferences — whether academic venues like ICLR or industry events with broad practitioner audiences — provide more useful evidence because they show that the petitioner's contribution was considered worth presenting to practitioners outside the employer. The invitation itself is the evidence — it reflects a programming committee's judgment that the topic merited presentation.
Vague expert letters from former managers or senior colleagues that praise the petitioner's general technical skill without describing specific contributions are routinely discounted. A letter that says this engineer is among the best and their work has been critical to company success may be sincere, but it does not describe an original contribution of major significance to the field. USCIS adjudicators reading this language see an employer reference letter, not evidence satisfying the regulatory criterion. For the letter to provide evidentiary value, it must describe a specific technical problem, what the petitioner did that was original, and why that approach represents a meaningful advance beyond what was previously available.
Presenting borderline evidence when disclosure is restricted
When an employer's NDA or security classification prevents specific technical disclosure, petitioners can use a structured approach to present evidence in general terms that still conveys specificity. Rather than disclosing the architecture of a proprietary system, a letter writer can describe the class of problems the system addresses, the limitations of the prior art in addressing those problems, and the category of approach the petitioner developed — without disclosing specific implementation details. This framing allows adjudicators to assess the originality and significance of the work without gaining access to proprietary information. USCIS officers are not required to verify that disclosed technical descriptions are accurate, but they must be convinced that the description reflects a genuine original advance rather than a generic claim of innovation.
Where possible, petitioners should identify any public-facing signals of the work's significance that exist despite the proprietary nature of the underlying code or system. A software system described in a published technical blog post by a technical director, cited in an industry analyst report, referenced in trade publication coverage, or discussed in an open-source library that uses a similar technique provides evidence of field recognition that does not require disclosing proprietary details. Even a brief mention in an external technical context establishes that professionals outside the employer are aware of the contribution and have treated it as meaningful. A comprehensive search for public-facing signals is typically worth conducting before concluding that the record must rest entirely on expert letters.
Impact metrics that are partly public can also support the contribution's significance even without disclosing the system itself. A petitioner who designed infrastructure processing a documented volume of transactions, a model used in products serving a published number of users, or a system handling a reported percentage of a market segment's traffic can reference those figures to contextualize the scale at which the contribution operates. These metrics do not disclose proprietary technical details, but they establish that the contribution is not a laboratory prototype — it is deployed at a scale that makes its technical properties consequential to a measurable portion of the field's practitioners.
Auditing your original contributions file before filing
A strong original contributions exhibit for a proprietary-work petitioner typically includes at least three to five expert letters from individuals outside the employer, each describing specific technical contributions in terms that establish novelty and field significance; patent records with citation analyses showing subsequent reliance by other organizations; any public-facing technical writing by the petitioner, including conference papers, invited talks, blog posts, or published technical reports; and third-party recognition in the form of press coverage, industry analyst citations, or inclusion of the petitioner's work in academic or industry reference materials. Petitioners who cannot assemble at least three of these four categories should consider whether the petition is ready to file or whether additional evidence development is needed first.
The audit should include a review of all expert letters for specificity. A letter that could plausibly have been written about any competent engineer in the field has not satisfied its evidentiary function. The test for a strong original contributions letter is whether it describes something distinctively true about this petitioner's work — a specific technical problem, a specific approach, a specific impact — that would not apply to a different practitioner at the same seniority level working on generic engineering tasks. Letters that pass this test are useful evidence. Letters that fail it should be returned to the writer with a request for revision or replaced with letters from writers who have more direct knowledge of the specific work.
Finally, petitioners should assess whether the contributions claimed in the petition are consistent with the scope of work described in the petitioner's supporting letter from the employer. If the original contributions exhibit describes a petitioner who designed fundamental infrastructure serving millions of users, but the employer's support letter describes a software engineer who was a member of a team working on product development, the inconsistency will invite scrutiny. The petition's description of the petitioner's role and contribution level should be coordinated across all exhibits, and the employer's support letter should explicitly confirm that the petitioner had the lead technical responsibility for the innovations described in the expert letters.
What we typically gather for this kind of case
| Document | Where to source | Why it matters |
|---|---|---|
| Expert letters | 5–8 independent recognized experts | Quality and independence beat volume |
| Certified translations | ATA-certified translator | Required for any non-English source document |
| Exhibit cover sheets | Drafted by counsel, one per exhibit | Tells the adjudicator what each piece shows |
| Bibliometric reports | Web of Science / Scopus | Quantifies impact for original-contributions criterion |
What we see go wrong, again and again
- 01Sending exhibits without a one-paragraph framing memo explaining what each shows and why it matters.
- 02Relying on volume over specificity — five well-targeted expert letters beat fifteen generic recommendations.
- 03Skipping certified translations or using AI translation for foreign-language source documents.
See if you qualify
Lando reviews your background against the O-1 visa criteria and tells you honestly where you stand. Free, no commitment.