NIW for Software Engineers: What 1,069 AAO Cases Show

Software engineers win 7.2% of NIW appeals

Our database holds 6,362 AAO decisions on NIW appeals. The Information Technology & Computing category is the single largest profession bucket in it, with 1,069 decided appeals. Of those, 77 were approved. That is a 7.2% approval rate on appeal.

One important caveat before you read anything into that figure: these are appeals, not first-pass petitions. Every case in the database had already been denied once by USCIS before reaching the Administrative Appeals Office. The 7.2% is the share that AAO overturned. First-pass approval at a service center is much higher and is not what this number measures. Read it as a map of what AAO does when an IT petition lands in front of it after a denial — which is exactly the position you do not want to be in.

If you narrow to petitioners who listed their job specifically as software engineering, the sample is smaller (74 appeals) and the rate is 6.76% — five approvals. The pattern holds at both the broad and the narrow cut: software work is one of the harder profiles to win an NIW appeal with.

Why the rate is low: Prong 1 does most of the killing

The denial language in our corpus clusters heavily on Prong 1, the national-importance prong. AAO rarely tells a software engineer they lack skill. It tells them the work they have described — however skilled — has not been shown to matter at a national scale rather than to their employer or their product.

That distinction is the whole game. A petition that argues "I build features used by millions of customers" is describing commercial reach, and AAO consistently treats commercial reach as a benefit to the company, not the country. A petition that argues "I work on a documented federal priority and here is the federal document" is on much firmer ground. The wins in the IT bucket almost all do the second thing.

What the 77 approved cases tend to have

Looking at the approved IT appeals, a few recurring features stand out:

• The work sits inside a named federal priority. AI safety, cybersecurity for critical infrastructure, healthcare or public-health systems, secure communications. Not "important technology" in the abstract — a specific area an agency or statute has identified.
• Recognition comes from outside the employer. Citations to published work, invitations to speak, adoption of open-source contributions by parties with no business relationship to the petitioner.
• The endeavor is described concretely. A specific line of work the petitioner will continue, not a job title.

Framings that hold up

• Machine-learning or AI-safety research, especially published work that others cite
• Cybersecurity work protecting infrastructure or government systems
• Healthcare technology — clinical software, FDA-regulated systems, public-health infrastructure
• Major contributions to widely-adopted open-source projects, where adoption is verifiable and independent of any one company

Framings that recur in the denials

• General product development, including at well-known companies
• Consumer apps with large user counts — reach is not national importance
• Business SaaS
• "My employer is important to the economy" — AAO rejects this in case after case

Building Prong 2 with engineering evidence

Prong 2 asks whether you are well positioned to advance the endeavor. Software engineers usually have more raw material here than they realize, but the material has to be the kind AAO weighs.

1. Published work and its reception. Peer-reviewed papers carry the most weight, but conference papers and technical writing that gets cited also count. A citation analysis report turns "I have publications" into a measurable claim.
2. Open-source contributions with verifiable adoption. Maintainer status on a project that others depend on. Adoption figures matter more than star counts.
3. Patents. Granted patents in applied AI, security, or systems work are weighed; pending applications much less so.
4. Independent expert recognition. Program-committee roles, invited talks at selective venues, advisory positions — all from people and organizations with no employment tie to you.

The denial reasons that come up most

1. Not distinguished from a skilled worker. AAO acknowledges the petitioner is a capable engineer, then says nothing shows their contribution matters more than that of many other capable engineers.
2. Employer benefit standing in for national benefit. Arguments about company revenue, valuation, or headcount instead of national impact.
3. Evidence that is all internal. Manager letters, performance reviews, colleague recommendations — no recognition from outside the organization.
4. No concrete forward-looking endeavor. A record of past work with no specific plan for what comes next.

There is also a procedural cluster worth naming: a meaningful share of the denied appeals in our data failed for timeliness or filing-process reasons rather than the merits. An appeal filed late does not get a merits review. If you reach the appeal stage, the calendar matters as much as the argument.

Where you file changes the odds

AAO approval rates differ sharply by the service center that issued the original denial. Across all professions in our data: Texas overturns 4.7% of appeals (180 of 3,798), Nebraska 7.2% (144 of 1,996), California 11.3% (12 of 106), Vermont 13.4% (38 of 284). Texas handles the largest share of NIW filings and is the toughest on appeal. You can compare them yourself with our service center comparison tool.

What a stronger software-engineer petition does

• Gets letters from researchers and engineers who have used or cited your work — not from your manager
• Ties the work to a specific, citable federal priority or documented national need
• Backs any publication claim with a professional citation analysis
• States a concrete forward-looking endeavor, not a job title
• Files on time, every deadline, if it ever reaches the appeal stage

Our $10 case review reads your profile against the recurring patterns in the IT bucket and tells you which prong is weakest. The profession lookup tool shows the same rates for adjacent fields if your work spans more than one category.