Last updated: October 2026. Checked against the USCIS Policy Manual (Volume 6, Part F, Chapter 5), USCIS’s EB-2 filing tips, and the White House National Security Science and Technology Strategy (August 2026).
Software engineers can qualify for EB-2 NIW, but the job title does not carry the case. An EB2 NIW software engineer petition has to clear two separate tests. First, you must qualify for EB-2 through a master’s degree, a bachelor’s plus five years of progressive experience in the specialty, or exceptional ability. Second, you must show a specific proposed endeavor with national importance that reaches beyond your employer. USCIS’s own Policy Manual warns that “a software engineer adapting their employer’s code for various clients will have difficulty demonstrating the national importance of that endeavor.”
This guide explains how USCIS looks at software work after the January 2025 Policy Manual update, and how the August 2026 Critical and Emerging Technologies list can help frame an endeavor. It also covers which evidence works for engineers without academic publications. The example endeavors below are hypothetical and clearly labelled.
Key takeaways
- USCIS checks EB-2 eligibility first, then the three Dhanasar prongs (January 2025 update).
- National importance is judged on your specific endeavor, not on how important software or AI is in general. “Benefits to a specific employer alone… are not sufficiently relevant.”
- The August 2026 Critical and Emerging Technologies (CET) list names 14 technology areas. Several of them, such as AI and autonomy, cybersecurity and future computing, contain software subfields.
- An advanced STEM degree, work in a critical and emerging technology, and being well positioned together count as a “strong positive factor” for the third prong.
- Publications are one kind of evidence among many. The Policy Manual also lists contracts, adoption of your technology by others, patents and licenses.
Can a software engineer qualify for EB-2 NIW?
Yes, if both layers are met. The Policy Manual (Volume 6, Part F, Chapter 5) says USCIS first decides whether you qualify for EB-2. If you do not, it can deny the petition “without reaching the national interest waiver determination.” If you do, it applies the three prongs of Matter of Dhanasar, 26 I&N Dec. 884 (AAO 2016):
- The proposed endeavor has substantial merit and national importance.
- You are well positioned to advance it.
- On balance, waiving the job offer and labor certification benefits the United States.
Step 1: EB2 NIW software engineer eligibility (the EB-2 threshold)
Advanced degree or bachelor’s plus five years
A U.S. master’s degree or higher (or a foreign equivalent) qualifies. So does a bachelor’s degree followed by at least five years of progressive experience in the specialty (8 CFR 204.5(k)(2)). On the bachelor’s route, the experience must come after the degree and relate to your degree field or your endeavor. Employer letters must give the writer’s name, address and title and a specific description of your duties (8 CFR 204.5(g)(1)).
Is software engineering a “profession”?
Since 2025, the occupation behind your endeavor must be a profession, meaning one with a bachelor’s degree as the minimum entry requirement. The Policy Manual uses the Bureau of Labor Statistics Occupational Outlook Handbook as a reference point. For this occupation, the BLS handbook states that “software developers, quality assurance analysts, and testers typically need a bachelor’s degree.” Cite a source like this rather than assuming the officer will accept it.
Exceptional ability as an alternative
The Policy Manual gives a computing example. A person whose computer science education or experience does not meet the advanced-degree definition may still qualify through exceptional ability for a computer-science endeavor. They need at least three of the six regulatory criteria and a favorable final merits determination. If the same person proposed an unrelated endeavor, they “would generally not qualify.”
Step 2: Framing a national-interest endeavor in software
The Policy Manual sets out three rules that matter most for engineers:
- Be specific. “The term ‘endeavor’ is more specific than the general occupation.” Describe the projects, goals and area of work, not the duties of a software engineer. A footnote asks petitioners to describe technical endeavors “in a way that an average person could understand.”
- Look beyond your employer. “Benefits to a specific employer alone, even an employer with a national footprint,” are not enough. You need broader implications “for a field, a region, or the public at large.”
- Show how others take up the technology. For someone developing technology at a company, the Policy Manual suggests showing “widespread interest in adoption or licensing of the technology, a novel and important manufacturing or operational process, or how the technology stands to impact the development of similar technology by other companies.”
You can pursue the endeavor through a particular employer. USCIS’s filing tips ask you to explain “whether the endeavor will be furthered through the course of your duties at a particular employer or some other way.” What matters is the reach of the impact, not who pays your salary. Our guide on how to write a proposed endeavor covers structure in more depth.
Using the Critical and Emerging Technologies list
The Policy Manual says USCIS recognizes the importance of STEM progress, “especially in focused critical and emerging technologies.” To identify such fields, officers consider “governmental, academic, and other authoritative and instructive sources.” The most recent governmental list is Appendix A of the White House National Security Science and Technology Strategy (August 2026). It defines CETs as technologies “that are or may become critically important to U.S. national security.” These are the software-relevant subfields it lists:
| CET area (2026 list) | Software-relevant subfields named in the list |
|---|---|
| Artificial intelligence and autonomy | Foundation models; multi-agent systems; interpretability and control; adversarial robustness and AI security; distributed and privacy-preserving machine learning; autonomous agent identification and authentication |
| Information management and cybersecurity | Data management, including storage and security; computing supply chain security and assurance; post-quantum cryptography; digital identity technologies; operational technology and industrial control system security; distributed ledger technologies |
| Future computing technologies | High-performance supercomputing, including for AI; edge computing; enabling technologies for high security computing; hardened operating systems for consumer use |
| Communications and networking | Software-defined networking and radios; modern data exchange techniques; adaptive network controls |
| Semiconductors and microelectronics | Design automation tools |
| Quantum information technologies | Enabling components, algorithms, materials and fabrication techniques |
Two cautions. First, the list is a national-security planning document, not an NIW eligibility list, and USCIS does not name it in the Policy Manual. Second, working in a listed area does not by itself establish national importance. You still need evidence about your specific endeavor and your role in it.
Want a quick read on whether your software work can be framed as a national-interest endeavor? Request a free EB-2 NIW profile evaluation, and our petition team will review your background and suggest a direction.
Hypothetical endeavor framings: weaker vs. stronger
All examples below are hypothetical, written for illustration only. They are not client cases and do not predict any outcome.
| Hypothetical framing | Why it reads as weaker or stronger |
|---|---|
| Weaker: “Continue working as a senior software engineer, building features for my employer’s e-commerce platform.” | It describes a job and an employer’s product. The Policy Manual flags this pattern directly: benefits to one employer, or adapting its code for clients. |
| Stronger: “Develop open-source tooling that detects tampering in software build pipelines, for adoption by U.S. operators of industrial control systems.” | Ties to the “computing supply chain security” and “industrial control system security” subfields. Needs evidence of adoption by other organizations and of the engineer’s lead role. |
| Stronger: “Design privacy-preserving machine-learning methods that let hospital networks train diagnostic models without sharing patient records.” | Ties to “distributed and privacy-preserving machine learning,” with a public-health dimension. Needs pilots, partner interest or publications showing traction. |
| Stronger: “Build migration tools that help financial institutions move legacy systems to post-quantum cryptography.” | Ties to “post-quantum cryptography.” Needs evidence that institutions beyond one employer are interested, such as letters, contracts or licensing talks. |
Notice the pattern. Each stronger framing names a specific problem and a group of users wider than one company, and each one depends on evidence. If you cannot document the claims, the framing will not hold up.
Evidence that works in an EB2 NIW software engineer petition
The Policy Manual’s list of “well positioned” evidence includes several items that fit engineers who do not publish papers. Its list “is not meant to be a checklist,” so choose what your record actually supports.
| Evidence type (from the Policy Manual) | Software example | Main prong supported |
|---|---|---|
| Contracts with companies using products you developed or helped develop | Licensing or integration agreements for a tool you built | 2 (and 1) |
| Documents showing technology you invented or helped invent, and how others use it | Adoption of your library by other organizations, with context | 1 and 2 |
| Patents or licenses, with documentation of why they are significant | A granted patent plus evidence it is licensed or cited | 2 |
| Published articles, citations, or “positive discourse around, or adoption of” your work | Conference papers, technical reports, independent write-ups | 2 |
| Correspondence from prospective customers, users or investors | Letters of intent or pilot agreements | 2 |
| Letters from experts with first-hand knowledge, backed by independent evidence | Recommenders who worked with or used your system | 2 |
| Letters from interested U.S. government agencies or quasi-governmental entities | A federally funded research and development center describing interest in the work | 1, 2 and 3 |
For publication and citation strategy, see how many citations EB-2 NIW requires. For letters, see recommendation letters for EB-2 NIW. Broader engineering context is in our EB-2 NIW for engineers hub.
Common pitfalls for software engineers
- The endeavor is a job description. Listing stacks, sprints and features instead of a problem and its wider impact.
- Employer-only impact. Revenue or efficiency gains that stay inside one company.
- Field-level arguments. Arguing that “AI is important” or “there is a shortage of engineers.” The Policy Manual says a national labor shortage alone does not satisfy prong 3 and is not enough for national importance.
- Metrics without context. Repository statistics or user counts that do not show who relies on the work and why it matters.
- Experience outside the specialty. On the bachelor’s route, years in a role unrelated to your degree or your endeavor may not count.
- Generic letters. Letters that praise you without specific examples or independent support.
Frequently Asked Questions
Do software engineers need publications for EB-2 NIW?
No single type of evidence is required. Publications and citations appear on the Policy Manual’s list, but so do contracts, licenses, patents and evidence that others use your technology.
Can I stay with my current employer and still file an NIW?
Yes. USCIS asks you to explain whether the endeavor will be pursued through your duties at a particular employer or some other way. The endeavor still needs impact beyond that employer.
Does working in AI or cybersecurity guarantee national importance?
No. Officers look at your specific endeavor and the evidence behind it. The CET list can support a framing, but it does not replace evidence of your impact and your role.
Can I qualify with a bachelor’s degree and no master’s?
Possibly. A bachelor’s plus at least five years of progressive post-degree experience in the specialty is treated as a master’s equivalent. The experience must relate to your degree or your endeavor.
Is premium processing available for software engineer NIW petitions?
Yes, for all E21 NIW petitions. Form I-907 costs $2,965 (G-1055). USCIS takes action within 45 business days, which can be an RFE rather than a decision (USCIS premium processing page).
Skycap prepares complete I-140 petition packages for self-petitioning engineers, with installment pricing on our plans page. To see how your software work could be framed, start with a free profile evaluation.
Related guides
This article is general information, not legal advice. Skycap Consultancy is a petition-preparation consultancy, not a law firm. Requirements and fees change; check the linked USCIS pages before filing.
