All guides · Sciences
EB-1A for software engineers
Also searched as EB1A for software engineers.
EB-1A for software engineers: patents, open source, staff roles, judging. No PhD required. Same 10 criteria, including engineers born in India. Free check. Not a USCIS decision.
Who this is for
Staff, principal, and founding engineers who can self-petition without an employer sponsor.
Evidence that usually matters
- Original contributions: architecture adopted outside your company, patents with real use, widely used open source
- Critical role: a distinguished employer plus proof the outcome depended on you, not only a title
- Judging: program-committee or independent review, not only an internal hackathon
- High salary: total compensation versus peers in the same specialty and geography, with a published survey
What often does not hold up
- Job title and a well-known employer are not a criterion by themselves
- Internal awards and manager letters with no independent exhibits
- GitHub stars with no independent write-up of why the work matters in the field
- Artistic exhibitions and performing-arts commercial success usually do not apply. Mark them N/A
USCIS does not have a software-engineer visa
There is no separate EB-1A for engineers. The regulation is the same 10 criteria for sciences, arts, education, business, and athletics. Software work usually sits in sciences or business. You still need three of ten, or one true one-time major award, and then final merits: sustained acclaim at the top of the field.
A Staff or Principal title at a well-known company is useful context. It is not, by itself, extraordinary ability.
How the ten boxes usually look for engineers
Most engineer files that look plausible lean on original contributions, judging, a critical role, and sometimes high salary or scholarly articles. Awards, membership, and press about you can help if they are national and independent. Exhibitions and performing-arts commercial success almost never apply. Mark those N/A. Do not invent a weaker stand-in and call it comparable evidence.
- Original contributions: a method, protocol, or system others used without you in the room
- Judging: completed peer review or program-committee work for people outside your company
- Critical role: distinguished organization, and proof the result turned on your work
- High salary: a survey for the same specialty and city, not a company band
- Scholarly articles: peer-reviewed venues that circulate in the field, not an internal wiki
Exhibits that tend to help
Officers read documents, not LinkedIn. Pair each claim with something independent.
- Patent plus proof of use or license, not only the grant
- Commit history plus independent papers, standards, or companies that adopted the work
- Review invitations and proof you finished the reviews
- Offer letters or W-2s next to a published compensation survey
- Press or trade coverage about you or the contribution, not the employer’s blog
What usually fails at final merits
Three thin boxes from one employer. Hackathon judging only. A patent with no adoption. Letters from managers that restate the job description. GitHub popularity with no one outside the company explaining significance. That pattern can clear a self-assessment on paper and still look ordinary to an officer.
If the free check comes back thin, read EB-1A vs NIW before you buy a long plan. Some engineers have a national-interest story even when the acclaim file is not ready.
EB-1A is a self-petition. You can be in any country. The statute names five fields (sciences, arts, education, business, athletics). Meeting three criteria is only Step 1. Final merits still has to show sustained acclaim.
Related: original contributions, judging, EB-1A vs NIW, Indian software engineers.
This is not a law firm and does not file petitions. USCIS decides each case on its own record.