Yes, software engineers can qualify for the EB-2 National Interest Waiver, but being a skilled engineer isn't enough. You must qualify for EB-2 (usually a master's degree, or a bachelor's plus five years of progressive experience) and show a specific proposed endeavor with national importance, such as building software that solves a documented problem for many organizations, backed by measurable results from systems you've already built. The most common reason software engineers are denied is describing their job instead of an endeavor.
Key takeaways
- Software engineering is a profession, not an endeavor. USCIS needs to see what specific problem your work will solve and for whom.
- Measured impact is your strongest evidence: users served, cost or time saved, reliability improved, adoption by others.
- Confidential work can still be proven through senior-manager letters, patents and public outcomes.
- Open-source adoption, patents and technical talks help show influence beyond your employer.
- The "tech is important" argument fails. Officers have seen it thousands of times.
Yes, software engineers can qualify for the EB-2 National Interest Waiver, but being a skilled engineer isn't enough. You must qualify for EB-2 (usually a master's degree, or a bachelor's plus five years of progressive experience) and show a specific proposed endeavor with national importance, such as building software that solves a documented problem for many organizations, backed by measurable results from systems you've already built. The most common reason software engineers are denied is describing their job instead of an endeavor.
Key takeaways
- Software engineering is a profession, not an endeavor. USCIS needs to see what specific problem your work will solve and for whom.
- Measured impact is your strongest evidence: users served, cost or time saved, reliability improved, adoption by others.
- Confidential work can still be proven through senior-manager letters, patents and public outcomes.
- Open-source adoption, patents and technical talks help show influence beyond your employer.
- The "tech is important" argument fails. Officers have seen it thousands of times.
Can software engineers qualify for EB-2 NIW?
Yes, and many do. Software engineers are among the largest groups of NIW applicants, especially those already working in the U.S. on H-1B visas and those abroad who want a green card without waiting for an employer to sponsor them through PERM. The NIW appeals because it doesn't tie you to one employer and lets you file yourself.
But software engineers also make up a large share of denials. The reason is almost always the same. The petition explains that software matters to the economy, that the U.S. needs engineers and that the applicant is talented. None of that proves the national importance of a specific endeavor, which is what the Matter of Dhanasar test requires.
The good news is that engineering work naturally produces the kind of evidence USCIS values: measurable results, systems used by many people, patents, open-source contributions and technical writing. The challenge is framing it correctly. This guide shows how.
Merit and national importance
Your specific planned work has real value and impact beyond your own employer or clients.
Well positioned
Your education, record, plan and progress make you credible to carry it out.
Waiver benefits the U.S.
On balance, America gains more by letting you go ahead now than by requiring a job offer and PERM.
Meeting the EB-2 requirement
Before national interest is considered, you must qualify for EB-2. For software engineers, there are two usual routes.
| Route | Typical engineer profile | Watch out for |
|---|---|---|
| Advanced degree | MS in Computer Science, Software Engineering, Data Science or a related field | Foreign master's degrees built on three-year bachelor's degrees may evaluate as a U.S. bachelor's only |
| Bachelor's plus five years | BS or BE in Computer Science or Engineering, then five or more years of progressive experience | Experience must come after the degree and show growing responsibility |
Software careers usually show clear progression: engineer, senior engineer, staff or lead engineer, architect. Your experience letters should state these titles, the dates of each, full-time status and specific duties. If you were promoted within the same company, a single letter can cover all roles, as long as each role is described separately. See EB-2 NIW requirements for the full rules.
Endeavors that work for software engineers
Your proposed endeavor must describe a specific contribution with impact beyond one employer. Here's how weak and strong versions compare.
Fintech
Healthcare software
Infrastructure and reliability
Developer tools and open source
Notice what the stronger versions share: a named problem, a defined group that benefits, a measurable result already achieved and a clear path to wider impact. For a step-by-step method, read how to define your proposed endeavor.
Linking your endeavor to national priorities
USCIS guidance recognizes that work in critical and emerging technologies can weigh in favor of national importance. The federal Critical and Emerging Technologies list includes areas such as advanced computing, artificial intelligence, data privacy and cybersecurity technologies, and integrated communication and networking technologies. If your endeavor genuinely falls within one of these areas, say so and explain how. Don't stretch the connection: a generic web application isn't a critical technology.
Evidence that proves you're well positioned
Prong 2 asks whether you can deliver. For engineers, the strongest evidence is concrete and measurable.
| Evidence | What it proves | How to document it |
|---|---|---|
| Systems you built and their results | Track record of success | Senior-manager letters with metrics; internal reports (redacted if needed); public announcements |
| Scale | Your work affects many people | User counts, transaction volumes, uptime data, clients served |
| Patents | Original contributions | Granted patents or published applications naming you as inventor |
| Open-source adoption | Influence beyond your employer | GitHub stars, forks, downloads, dependent projects, notable adopters |
| Technical talks and papers | Recognition by peers | Conference programs, invitations, papers, citations |
| Code review and judging | Peers trust your expertise | Maintainer roles, hackathon judging, technical committee membership |
| Interest from U.S. organizations | Your plan is realistic | Letters of interest, contracts, partnership agreements |
Turning metrics into evidence
Most engineers know the impact of their work but have never written it down. Before you file, list your three to five most significant projects. For each, record the problem, your specific role, the technical approach, the measurable result and who can confirm it. Then get that confirmation in writing. A letter from a director stating that "the service Mr. Khan designed reduced checkout failures from 2.1% to 0.4% across 12 million monthly transactions" is far stronger than any description you write yourself.
Recommendation letters for engineers
Aim for a mix: managers or architects who saw your work directly, and independent engineers at other companies who used your open-source tools, adopted your design or heard you speak. See recommendation letters that work.
Proving confidential or proprietary work
Many software engineers build systems their employers won't let them describe publicly. That's a common concern, and it can be handled.
- Senior-manager letters: a director or VP can describe your contribution and its measured impact in general terms without disclosing trade secrets.
- Redacted documents: design documents, performance reports or internal awards with sensitive details removed, plus an explanation of what was redacted and why.
- Public outcomes: product launches, press releases, earnings calls or public statistics that reflect the results of systems you built, linked to your role by a letter.
- Patents: patent applications are public even when the product isn't.
- Conference talks: many companies allow engineers to present general architectures or lessons learned.
Never submit documents you're not authorized to share. Officers understand confidentiality; what they need is credible, verifiable evidence of impact.
Prong 3: why the waiver benefits the U.S.
For employed engineers, prong 3 needs careful thought, because a U.S. employer could, in principle, sponsor you through PERM. Strong arguments include:
- your endeavor spans many organizations (for example, an open-source tool or a platform serving many clients), so no single job captures it
- your specific expertise and results add value beyond filling a position, even if other engineers are available
- your work addresses an urgent need, such as security of critical systems, documented by credible sources
- you're founding or leading a venture, which makes labor certification impractical
"PERM takes too long" isn't a prong 3 argument. See the Dhanasar test explained.
Worked example: the same engineer, two petitions
A composite example, not a specific client.
Bilal has a bachelor's in Computer Science from Lahore and nine years of experience, the last four as a lead engineer at a U.S. payments company on an H-1B.
Version one (likely denied)
The endeavor: "to continue working as a software engineer to support the U.S. digital economy." Evidence: degree, evaluation, three letters from current colleagues praising his skills, and articles about the size of the U.S. technology sector.
Problems: prong 1 describes a profession; prong 2 relies on uncorroborated praise; prong 3 is missing.
Version two (much stronger)
The endeavor: "to develop fraud-detection infrastructure for small U.S. financial institutions that lack the resources of large banks, extending the real-time scoring system I designed, which reduced fraud losses by 25% for my current employer's 3 million customers."
Evidence:
- a credential evaluation confirming a U.S. bachelor's and letters showing nine years of progressive experience after it
- federal and industry data on fraud losses at community banks
- a VP's letter confirming the system's design and measured results
- a patent application naming Bilal as an inventor
- a conference talk and its recording
- a letter from an engineer at a credit union that adopted an open-source component Bilal released
- a letter of interest from a U.S. banking-technology provider
Same engineer, same career. The second petition gives the officer a specific endeavor and the evidence to approve it.
Open-source maintainers: proving influence
Open-source work can be some of the strongest evidence an engineer has, because it's public and others' use of it is measurable. Present it so an officer understands it:
- Adoption metrics: downloads from package registries, the number of dependent repositories, and stars and forks, each with a dated screenshot and a one-line explanation.
- Notable users: companies, government agencies or major projects that depend on your code, documented through their public repositories, documentation or letters.
- Your role: creator, maintainer or major contributor, shown through commit history, release notes or governance documents.
- Foundations and governance: if your project joined a recognized open-source foundation, or you hold a maintainer role in one, document it.
- What it enables: explain in plain terms what problem the project solves and why others rely on it.
Stars alone don't impress officers. A short explanation such as "used by 2,300 other projects, including tools maintained by two federal agencies" makes the significance clear.
Contractors, remote engineers and technical founders
Not every engineer has a single long-term employer. That's fine for the NIW, which doesn't require one.
- Contractors and consultants: client letters can serve as experience letters if they state your role, dates, hours and duties. Serving many clients can also support prong 3, because no single employer captures your work.
- Remote engineers abroad working for U.S. companies: your existing U.S. clients or employers are natural sources of letters of interest and evidence that your work already reaches the U.S.
- Technical founders: if you're building your own product, your case looks more like an entrepreneur's. See EB-2 NIW for entrepreneurs.
Engineers abroad: making the U.S. plan credible
Engineers filing from Pakistan, India and elsewhere often have excellent records but little visible connection to the United States. Officers may ask how you'll actually carry out your endeavor there. Help them by including:
- letters of interest from U.S. companies, clients or collaborators
- evidence that U.S. users or organizations already use your software or open-source work
- a clear description of how you'll work in the U.S.: employment, consulting or your own company
- evidence of any U.S. work you've done remotely
Pakistan-born engineers are in the Rest of World EB-2 queue, which is far shorter than India's. See our guide for Pakistani applicants.
Recommendation letters for software engineers
| Recommender | What they can confirm |
|---|---|
| Engineering director or VP | Your individual contribution and the measured results of systems you built |
| Staff engineer or architect who worked with you | Technical depth and the difficulty of the problems you solved |
| Engineer at another company using your open-source work | Adoption and influence beyond your employer |
| Conference organizer or program committee member | Selection of your talk or paper |
| U.S. company or client | Interest in your endeavor and its relevance in the U.S. |
Each letter should cover different ground. Five letters from teammates describing the same project add far less than a mix of internal and independent voices. See recommendation letters that work.
Mistakes software engineers make
- The job-title endeavor. "Senior software engineer" isn't an endeavor.
- The tech-economy argument. Statistics about the size of the tech sector prove nothing about you.
- Unquantified achievements. "Improved performance significantly" needs a number and a source.
- Only colleagues as recommenders. Add independent engineers who know your work.
- Buzzword stacking. "AI-powered blockchain cloud platform" without specifics invites skepticism.
- Ignoring prong 3. Employed engineers especially need a real argument here.
- A degree route that doesn't hold. Check your evaluation before relying on the advanced-degree route.
See all common reasons in why EB-2 NIW petitions get denied.
Process, cost and timeline in brief
| Stage | Key facts (November 2026) |
|---|---|
| File Form I-140 | $715 filing fee + $300 Asylum Program Fee for self-petitioners |
| Premium processing (optional) | $2,965; USCIS acts within 45 business days |
| Standard processing | USCIS reports about 30 months to complete 80% of NIW petitions |
| Visa Bulletin, EB-2 Rest of World | Final Action Date April 1, 2025; Date for Filing March 15, 2026 |
| Visa Bulletin, EB-2 India / China | November 1, 2013 / October 1, 2021 |
| Green card stage | Form I-485 in the U.S. ($1,440 per applicant) or consular processing abroad |
For full detail, see how to file EB-2 NIW, EB-2 NIW fees in 2026 and EB-2 NIW processing time.
H-1B engineers: why the NIW is worth considering
For engineers already in the U.S., the NIW offers advantages over employer-sponsored PERM:
- Independence: your green card isn't tied to one employer, so you can change jobs while continuing your endeavor.
- Speed: no labor certification stage, which can take a year or more on its own.
- H-1B extensions: an approved I-140 can allow H-1B extensions beyond six years when your priority date isn't current.
- Family: spouses of H-1B workers with an approved I-140 may be eligible for an H-4 work permit.
Many engineers pursue both: their employer files PERM while they self-petition for an NIW, and they use whichever succeeds first.
Self-check for software engineers
Is your profile NIW-ready?
- Do you have a master's, or a bachelor's plus five years of progressive experience after it?
- Can you name a specific problem your work solves for many organizations or people?
- Can you quantify the results of at least two or three major projects?
- Can someone senior confirm those results in writing?
- Has anyone outside your employer used, adopted or cited your work?
- Do you have patents, talks, papers or open-source contributions?
Four or more yes answers suggest a realistic NIW case. Fewer than three usually means building evidence first.
Find out if your engineering work makes a strong NIW
Send us your CV and a short note on your work. We'll tell you whether the NIW fits your profile, how to frame your proposed endeavor, and which evidence gaps to close before you file. Honest advice, in English or Urdu, online or at our Karachi office.
Get my free NIW assessment WhatsApp usEB-2 NIW for software engineers: FAQs
Can a software engineer get EB-2 NIW without publications?
Yes. Most software engineers who succeed don't rely on academic publications. They use measurable results from systems they built, patents, open-source adoption, technical talks and strong letters, all tied to a specific endeavor.
Is EB-2 NIW harder for software engineers?
It isn't harder in principle, but many software engineering petitions are denied because they describe a job rather than an endeavor. Engineers who frame a specific, nationally important endeavor and prove their impact do well.
Do I need to work in AI to get an NIW as a software engineer?
No. AI is one critical technology area, but endeavors in security, healthcare software, financial infrastructure, reliability, developer tools and many other areas can qualify when they have broad impact.
Can I file an NIW while my employer files PERM?
Yes. They're separate petitions. Many engineers pursue both and use whichever is approved first. Each I-140 has its own priority date.
How do I prove the impact of confidential projects?
Use letters from senior managers describing measured results in general terms, redacted documents with explanations, public outcomes linked to your role, patents and approved conference talks.
Does my GitHub profile count as evidence?
It can, especially if it shows adoption by others: stars, forks, downloads and notable projects that depend on your code. Explain what the numbers mean and why they matter.
Do I need a U.S. job offer as a software engineer?
No. The NIW waives the job offer requirement. You can describe how you'll carry out your endeavor through employment, consulting or your own venture.
Can I change jobs after my NIW is approved?
Generally yes, as long as you continue pursuing the endeavor described in your petition. This flexibility is a major advantage over PERM.
Is a bootcamp certificate enough for EB-2?
No. EB-2 requires an advanced degree, a bachelor's degree plus five years of progressive experience, or exceptional ability. A bootcamp certificate can support your profile but doesn't replace the degree requirement.
Should I mention the company I work for in my endeavor?
You can mention it as context, but the endeavor itself should describe the work and its impact, not a specific job. That way it remains valid if you change employers.
How many years of experience do software engineers usually have when filing?
There's no minimum beyond the EB-2 requirement, but successful applicants usually have several years of documented, measurable impact. With a master's degree, you need no specific number of years, just enough evidence for prong 2.
Can engineers in Pakistan or India apply without being in the U.S.?
Yes. You can file from abroad and complete the green card through a U.S. consulate. India-born applicants face a much longer EB-2 queue, while Pakistan-born applicants are in the Rest of World queue.
Can a software engineer with only a bachelor's degree get an NIW?
Yes, with at least five years of progressive experience after the degree. That combination meets the EB-2 requirement. You still need a specific endeavor and strong evidence.
Are hackathon wins useful evidence?
They can support your profile, especially at large, competitive events. Explain the competition's size and selectivity, and pair it with evidence of real-world impact.
Does working remotely for a U.S. company help my NIW?
It can, because it shows your work already reaches the U.S. Letters from U.S. clients or employers can describe your impact and their interest in your continued work.
Do technical blog posts count as NIW evidence?
They can support your profile, especially if widely read, cited or referenced by others. Your own posts are your claims, so pair them with evidence of their reach and influence.
Related EB-2 NIW guides
Official sources
- Matter of Dhanasar, 26 I&N Dec. 884 (AAO 2016)
- USCIS Policy Manual, Vol. 6, Part F, Ch. 5: Advanced Degree or Exceptional Ability
- USCIS: Updated Guidance on EB-2 National Interest Waiver Petitions (January 2025)
- Critical and Emerging Technologies List Update (February 2024)
- U.S. Department of State: Visa Bulletin
Phoenix Immigration Consulting Services LLC is an immigration consulting firm, not a law firm, and does not provide legal advice or representation. This article is general information, accurate as of the date above. Immigration rules, fees and dates change often, so check official USCIS and Department of State sources before acting. All decisions rest with USCIS and the U.S. Department of State.
Frequently asked questions
Can a software engineer get EB-2 NIW without publications?
Yes. Most software engineers who succeed don't rely on academic publications. They use measurable results from systems they built, patents, open-source adoption, technical talks and strong letters, all tied to a specific endeavor.
Is EB-2 NIW harder for software engineers?
It isn't harder in principle, but many software engineering petitions are denied because they describe a job rather than an endeavor. Engineers who frame a specific, nationally important endeavor and prove their impact do well.
Do I need to work in AI to get an NIW as a software engineer?
No. AI is one critical technology area, but endeavors in security, healthcare software, financial infrastructure, reliability, developer tools and many other areas can qualify when they have broad impact.
Can I file an NIW while my employer files PERM?
Yes. They're separate petitions. Many engineers pursue both and use whichever is approved first. Each I-140 has its own priority date.
How do I prove the impact of confidential projects?
Use letters from senior managers describing measured results in general terms, redacted documents with explanations, public outcomes linked to your role, patents and approved conference talks.
Does my GitHub profile count as evidence?
It can, especially if it shows adoption by others: stars, forks, downloads and notable projects that depend on your code. Explain what the numbers mean and why they matter.
Do I need a U.S. job offer as a software engineer?
No. The NIW waives the job offer requirement. You can describe how you'll carry out your endeavor through employment, consulting or your own venture.
Can I change jobs after my NIW is approved?
Generally yes, as long as you continue pursuing the endeavor described in your petition. This flexibility is a major advantage over PERM.
Is a bootcamp certificate enough for EB-2?
No. EB-2 requires an advanced degree, a bachelor's degree plus five years of progressive experience, or exceptional ability. A bootcamp certificate can support your profile but doesn't replace the degree requirement.
Should I mention the company I work for in my endeavor?
You can mention it as context, but the endeavor itself should describe the work and its impact, not a specific job. That way it remains valid if you change employers.
How many years of experience do software engineers usually have when filing?
There's no minimum beyond the EB-2 requirement, but successful applicants usually have several years of documented, measurable impact. With a master's degree, you need no specific number of years, just enough evidence for prong 2.
Can engineers in Pakistan or India apply without being in the U.S.?
Yes. You can file from abroad and complete the green card through a U.S. consulate. India-born applicants face a much longer EB-2 queue, while Pakistan-born applicants are in the Rest of World queue.
Can a software engineer with only a bachelor's degree get an NIW?
Yes, with at least five years of progressive experience after the degree. That combination meets the EB-2 requirement. You still need a specific endeavor and strong evidence.
Are hackathon wins useful evidence?
They can support your profile, especially at large, competitive events. Explain the competition's size and selectivity, and pair it with evidence of real-world impact.
Does working remotely for a U.S. company help my NIW?
It can, because it shows your work already reaches the U.S. Letters from U.S. clients or employers can describe your impact and their interest in your continued work.
Do technical blog posts count as NIW evidence?
They can support your profile, especially if widely read, cited or referenced by others. Your own posts are your claims, so pair them with evidence of their reach and influence.
Official sources
- justice.govjustice.gov
- uscis.govuscis.gov
- uscis.govuscis.gov
- bidenwhitehouse.archives.govbidenwhitehouse.archives.gov
- travel.state.govtravel.state.gov
Upload your CV for a free EB2NIW assessment and an honest view of your chances.
Phoenix Immigration Consulting Services LLC is an immigration consulting firm, not a law firm, and does not provide legal advice. This article is general information and may change; always confirm current rules on uscis.gov and travel.state.gov.
