EB-1A for Software Engineers
Your commits, design docs, and production systems already contain EB-1A evidence. The problem is that USCIS does not read GitHub — it reads packaged exhibits. Here is how engineering work converts into extraordinary ability proof.
Built for: Senior, staff, and principal software engineers at product companies, infrastructure teams, and open-source projects.
Evidence matrix: your work mapped to USCIS criteria
Each row converts routine professional output into a packaged exhibit an adjudicator can score.
Daily work
Maintaining a widely-adopted open-source library or framework
USCIS criterion
Original contributions of major significanceEvidence packaging
Download/dependency metrics, downstream adoption by named companies, and expert letters explaining the technical novelty and field-wide impact.
Daily work
Designing distributed systems that carry production traffic at scale
USCIS criterion
Original contributions of major significanceEvidence packaging
Architecture decision records, internal impact memos, latency/cost reduction figures, and independent testimony that the design influenced practice beyond your employer.
Daily work
Reviewing conference submissions or serving on a technical program committee
USCIS criterion
Judging the work of othersEvidence packaging
Invitation emails, reviewer dashboards, and a signed statement from the program chair confirming the selectivity of the review pool.
Daily work
Publishing engineering blog posts, RFCs, or conference talks
USCIS criterion
Authorship of scholarly articles / published materialEvidence packaging
Publication record with venue circulation data, citation or reference trails, and evidence the venue is recognized in the field.
Daily work
Being recruited into a staff/principal role at a top-tier engineering org
USCIS criterion
Critical role for distinguished organizationsEvidence packaging
Org chart placement, offer and promotion documents, revenue or reliability outcomes owned, and a letter from an executive describing the criticality of the role.
Daily work
Compensation in the top decile for your metro and level
USCIS criterion
High remunerationEvidence packaging
Total-comp statements (base, equity, bonus) benchmarked against BLS/OES 90th percentile wage data and Levels.fyi distributions for the same title and location.
Daily work
Winning hackathons, internal engineering awards, or industry recognition
USCIS criterion
Nationally or internationally recognized awardsEvidence packaging
Award criteria, judging panel credentials, entrant pool size, and press or third-party coverage of the award.
High remuneration benchmarks
Indicative BLS/OES-style 90th percentile total compensation for this occupation by metro. Your petition must compare your compensation against the correct occupation code and location.
$268,000
Bay Area — 90th percentile
$239,000
New York City — 90th percentile
$252,000
Seattle — 90th percentile
RFE mitigation for this profile
Where USCIS pushes back
The most common RFE for software engineers is the "good employee, not extraordinary" objection: USCIS accepts that you are highly paid and productive, but argues your work benefited only your employer. Mitigate this by proving external adoption — engineers outside your company using your library, your design pattern cited in others' work, or independent experts attesting that the field changed because of you. Never let the record rest on internal performance reviews alone.
Frequently asked questions
Related visa guides
See where your profile stands today
Run the free profile audit and get a criterion-by-criterion read on your EB-1A eligibility, tuned to your role.