EB-1A for Software Engineers and Tech Professionals: Filing Strategy

EB-1A is codified at INA 203(b)(1)(A) and 8 CFR 204.5(h). The statute requires “extraordinary ability in the sciences, arts, education, business, or athletics” demonstrated by “sustained national or international acclaim.” Software engineering sits under sciences. Hardware, systems design, data science, AI research, cybersecurity, and adjacent engineering disciplines all qualify as sciences for this petition type.

The regulation gives two paths. Path one is a one-time major internationally recognized award such as a Nobel, Pulitzer, Fields Medal, Turing Award, or Academy Award. Virtually no individual contributor software engineer qualifies here, and that is fine. Path two is satisfying at least three of ten listed criteria. This is the road nearly every tech self-petitioner takes.

Meeting three criteria does not mean the case is approved. USCIS applies the Kazarian two-step analysis from the 9th Circuit’s 2010 decision. Step one is a simple count: did you clear three regulatory boxes? Step two is the final-merits determination. Viewed as a whole, does the evidence show you are one of the small percentage at the top of your field with sustained acclaim? Most RFEs and denials come at step two. That is where a tech petition with three weak criteria loses and one with three well-documented criteria wins.

Ten criteria exist on paper. For software, hardware, and data engineers, six carry the weight. The other four (a major media feature profile, display of work at artistic exhibitions, commercial success in the performing arts, and leading role in a distinguished organization) are stretches for most individual contributors and waste petition space if forced.

The six that fit the tech profile are original contributions of major significance, authorship of scholarly articles, judging the work of others, high salary, membership in associations requiring outstanding achievement, and prizes or awards for excellence. Pick the three or four that you can document exhaustively. Build a separate exhibit binder per criterion.

Notice the pattern. The two strongest criteria for engineers are “original contributions” and “high salary.” Those are the ones where documentary evidence is concrete, countable, and hard for USCIS to dispute. Build the case around those two, then add one or two supporting criteria. A three-criterion tech petition anchored in contributions plus salary plus authorship wins at roughly double the rate of a petition that tries to scrape six criteria with thin evidence.

Original contributions of major significance is the hardest criterion and the one USCIS examines most carefully in step-two review. A patent by itself is not enough. A GitHub repo with stars is not enough. An internal tool adopted at one company is not enough. The officer needs proof that the contribution mattered beyond your employer, and that other people in the field adopted, cited, licensed, or built on it.

Six forms of tech evidence consistently clear this bar. First, granted US utility patents where you are a named inventor, especially when those patents are cited in later patent applications by unrelated companies. A forward citation count from the USPTO or Google Patents establishes that the invention influenced the field. Aim for cumulative forward citations of 25 or more across your patent portfolio for a strong showing.

Second, open-source projects you authored or led with verifiable adoption metrics. Aim for GitHub stars above 5,000, downloads via npm, PyPI, or Maven Central above 1 million, documented production use at named companies. A repo’s README listing “Used in production by Airbnb, Stripe, and Shopify” plus screenshots of those companies’ engineering blog posts citing the library is strong evidence.

Third, conference papers at tier-one venues with citation counts. For software, that is PLDI, POPL, OSDI, SOSP, USENIX Security, NDSS. For machine learning, NeurIPS, ICML, ICLR, ACL. For systems and hardware, ISCA, MICRO, ASPLOS, HotChips. Google Scholar printouts showing your h-index and citation totals are standard exhibit material.

Fourth, standards-body contributions. If you authored or co-authored an IETF RFC, a W3C specification, a Khronos standard, a JEP for Java, or a PEP for Python that shipped, that is original contribution at field scale. Include the specification text, the adoption roster, and any industry coverage.

Fifth, widely cited technical blog posts or engineering whitepapers that industry picked up. A post on your company’s engineering blog that High Scalability, Hacker News front page, or Morning Paper summarized counts. Include the original post, the referral metrics, and the secondary coverage.

Sixth, expert letters from independent recommenders who can document how your work influenced their own. Six to eight letters is the norm. Four must come from people you have never worked with directly such as senior engineers or researchers at other companies, academics, or industry analysts. Two or three can come from people you collaborated with. Each letter should cite the specific contribution, explain the impact on the field in concrete numbers, and avoid template language.

High salary is the single most winnable criterion for software engineers working in the United States. USCIS requires evidence that the petitioner commands a salary or other remuneration significantly above the field average. For engineers at FAANG-tier and near-FAANG employers, the total compensation numbers are routinely three to five times the BLS field mean. Winning this criterion requires three documents and careful comparison-set selection.

Document one is your W-2 wages plus equity vesting value for the most recent three calendar years. For a staff software engineer at Google, Meta, or Apple, that number in 2026 is typically in the $450,000 to $750,000 range. At principal or L7-equivalent, $700,000 to $1.4 million. Founder comp and RSU-heavy roles should include an equity appraisal letter.

Document two is the prevailing wage comparison set. Pull the Level 4 (fully competent) OES wage for your SOC code 15-1252 (Software Developers) or 15-1253 (Quality Assurance Analysts), in your specific metro area, from the FLC Data Center at flcdatacenter.com. For 2026 OES data, Level 4 software developer wages in the San Francisco MSA sit near $250,000 annual base. Your number must exceed that prevailing wage by a demonstrable margin, typically 1.5 times or more for an uncontested showing.

Document three is an independent salary benchmarking report. Levels.fyi, Glassdoor, H1BDataInfo.com, Radford survey excerpts, or a compensation consultant’s attestation are all acceptable. Use two independent sources so the officer can cross-check. If your comp is in the 95th percentile or higher for your SOC plus metro plus level, state that percentile directly in the cover letter with sourced numerical backing.

With contributions and salary anchored, you need one or two more criteria to clear step one. Any of the following four works if the evidence is concrete and sourced. Thin evidence on a fourth criterion is worse than no fourth criterion.

Authorship of scholarly articles. Publications in ACM, IEEE, USENIX, or tier-one machine-learning venues all count. Industry whitepapers with DOIs count. Medium posts and personal blog content do not, because the regulation reads “scholarly” which USCIS interprets to mean peer-reviewed or formally published. Three to six publications with citation counts is a strong showing. Include the paper PDF, the venue’s acceptance rate, and your Google Scholar profile.

Judging the work of others. Program committee invitations from peer-reviewed conferences count. Kaggle Grandmaster judging counts. Reviewer of patent applications at USPTO counts. Hackathon judging at university or industry scale counts. GitHub Sponsors’ distinguished reviewer program counts. Provide the invitation emails, the review load (how many papers or submissions you evaluated), and a confirmation letter from the organizing body.

Prizes or awards for excellence. Best Paper at a named conference, top 1 percent Kaggle finish, ACM SIGSOFT Distinguished Paper, IEEE Best Paper. Internal employer awards only count if the award selects from a pool larger than the employer. For example, Google’s internal “Innovation Award” does not count; a cross-company award judged by an external panel does. Forbes 30 Under 30, MIT TR35, and similar media-issued lists are strong.

Membership in associations requiring outstanding achievement. ACM Distinguished Member, IEEE Senior Member or Fellow, AAAI Senior Member, and Cherry Blossom Tech Fellowship all require formal nomination review. Membership that anyone can buy or join by paying dues, such as regular ACM or IEEE membership, does not count. Include the nomination letter, the bylaws showing the review process, and your membership certificate.

The petition letter is the document USCIS reads first and longest. It must do four things in sequence: introduce you and your field with specificity, walk through each claimed criterion with citations to tabbed exhibits, present the final-merits narrative showing sustained acclaim, and conclude with the eligibility showing. Typical length for tech petitions is 25 to 40 pages. Shorter petitions rarely survive the final-merits step.

Open with the field and your position in it. Not “I am a software engineer.” Rather, “I am a principal-level distributed systems engineer specializing in consensus algorithms and fault-tolerant database design, with eleven years of industry experience at two of the top five cloud infrastructure providers.” Specificity here tells the officer what “top of the field” means for this petitioner.

For each claimed criterion, use the same template: quote the regulatory text, state how the petitioner meets it, list the specific exhibits tabbed in the evidence binder, close with a sentence tying the evidence back to the “major significance” or “outstanding” standard. Do not rely on expert letters to carry a criterion. The letters supplement the documentary evidence; they do not replace it.

The final-merits narrative is the part most tech petitions get wrong. Three criteria cleared does not mean “I qualify.” The petition has to tell a coherent story: this engineer has sustained national or international acclaim in distributed systems across a decade of work, demonstrated by X, Y, and Z. Use comparison language such as “one of a small percentage at the very top,” “peers in the top decile of the field,” or “recognized beyond employer scale.” USCIS officers look for this framing explicitly.

EB-1A self-petitioners qualify as “self-petitioner” for the Asylum Program Fee tier, which drops that fee to $300 instead of the $600 standard employer rate. That plus the $715 base I-140 fee gives a total of $1,015 for a regular EB-1A filing. Premium processing adds $2,965 as of the March 2026 fee increase, bringing the total to $3,980.

Pay each fee by separate check payable to “U.S. Department of Homeland Security” spelled out in full. USCIS routinely rejects filings with the check made out to “USDHS” or “Department of Homeland Security.” Alternatively, use Form G-1450 for credit card or G-1650 for ACH. If any single fee is short or missing, the whole petition is rejected and mailed back. You lose nothing but time, but the time on an H-1B with limited runway can matter.

Premium processing is almost always worth it for software engineers. EB-1A premium is 15 business days. USCIS either approves, denies, issues an RFE, issues a NOID, or opens a fraud investigation within that window. For Indian-born petitioners facing a concurrent I-485 priority date opportunity, getting the I-140 approved in three weeks instead of seven months can mean the difference between filing adjustment of status this cycle and waiting another year.

RFEs on tech EB-1A petitions cluster around four themes. First, final-merits determination, where the officer accepts that three criteria are met on paper but disputes whether the evidence, viewed as a whole, shows sustained acclaim. Second, original contributions of major significance, where the officer argues the claimed contributions are routine employer work not field-changing. Third, expert letters, where USCIS questions whether letters are truly independent or boilerplate template copies. Fourth, salary comparison set, where the officer objects to the chosen metro, SOC code, or wage level used in the comparison.

The RFE response window is 87 days. Use it fully. Strong responses add new independent evidence where possible, reframe the narrative with additional cross-criteria citations, supplement expert letters with additional signatories where original letters were challenged, and directly answer the officer’s specific objections in a point-by-point format. The worst RFE responses resubmit the same evidence with a cover memo saying “as previously demonstrated.”

Once the I-140 is approved, your next move depends on priority date and country of birth. For non-retrogressed countries (including all countries other than India and China in most months of 2026), concurrent or immediate I-485 filing is available. For India-born petitioners, EB-1 Final Action Dates move more frequently than EB-2 or EB-3 but still retrogress multiple times per year. Check each monthly visa bulletin.