How I Got My EB-1A Approved as an Amazon Engineer (India Backlog)

If you're an Indian-born engineer staring down a 50+ year EB-2 backlog, you've probably wondered: can someone like me actually get an EB-1A? The answer is yes. This is the story of how one Amazon software engineer did exactly that - and a breakdown of the evidence strategy that made it work.

This isn't a "I won a Nobel Prize" story. It's an L6 engineer at Amazon who built a deliberate case over 18 months, filed as a self-petitioner, and got approved without an RFE.

Why EB-1A? The India EB-2 Math Is Brutal

Let's start with the obvious. If you're born in India and your employer filed your EB-2 PERM in 2024, your estimated wait for a green card is somewhere north of 50 years. That's not a typo.

The eb1 vs eb2 India wait time difference is staggering. EB-1 India dates have been moving - sometimes current, sometimes with a backlog of 2-3 years. But even a 3-year wait beats a lifetime. That's why more Indian H-1B holders are looking at EB-1A as a real alternative, not a long shot reserved for Nobel laureates.

The other advantage? EB-1A is a self-petition. You don't need your employer's involvement or permission. No PERM labor certification. No dependency on your company's immigration team moving at their pace.

The Profile: An L6 Amazon Engineer, Not a Celebrity

Here's what this engineer's profile looked like before they started building their EB-1A case:

• Title: SDE-3 (L6) at Amazon, 8 years of total experience
• Education: Master's in Computer Science from a mid-tier US university
• Publications: Zero peer-reviewed papers at the time
• Patents: One filed, not yet granted
• Awards: None of the traditional kind
• Salary: Senior band at Amazon, around $350K total compensation

On paper, this doesn't scream "extraordinary ability". But USCIS doesn't require you to be famous. They require you to meet at least 3 of the 10 criteria and demonstrate that you're in the top of your field. That's a different bar entirely.

The 3 Criteria That Got It Done

USCIS requires evidence in at least 3 of the 10 regulatory criteria. Here's what this engineer used:

1. Original Contributions of Major Significance

This is where most eb1a approvals for software engineers are won or lost. The engineer documented three major system contributions:

• A distributed caching system deployed across Amazon's retail platform, handling 2M+ requests per second. They got letters from two principal engineers explaining why the architecture was novel.
• An open-source library with 1,200+ GitHub stars that was adopted by three other companies. Downloads, citations, and adoption metrics all went into the evidence packet.
• A machine learning pipeline that reduced fraud detection latency by 40%, saving an estimated $12M annually. Internal metrics plus a letter from the VP of the fraud team.

2. High Salary (Commanding a High Remuneration)

This one is straightforward for senior engineers at big tech companies. The engineer submitted:

• Total compensation statements showing $350K+ annually
• Data from levels.fyi and Bureau of Labor Statistics showing this placed them in the top 5% of software engineers nationally
• An expert letter from a compensation consultant confirming the percentile

Amazon's equity-heavy compensation structure actually helps here. USCIS looks at total compensation, not just base salary.

3. Judging the Work of Others

This criterion surprises a lot of engineers because they don't realize they're already doing it. The evidence included:

• Peer review records for 30+ design documents at Amazon (internal promotion committee reviews and architecture reviews)
• Conference paper reviews - the engineer signed up to review for two mid-tier IEEE conferences and reviewed 8 papers over a year
• Open-source PR reviews on the library they maintained, showing they were an authority others sought out

The Evidence Strategy: 18 Months of Deliberate Preparation

This wasn't a "let me gather what I have and file" situation. The engineer spent 18 months deliberately building evidence before filing. Here's the rough timeline:

The most important decision? Starting the evidence-building process before filing. Too many engineers try to file with whatever they have today. That almost always leads to an RFE or denial.

The Recommendation Letters: Quality Over Quantity

The petition included 6 recommendation letters. Here's the breakdown:

• 2 from Amazon - a principal engineer and a director who could speak to the impact of the engineer's work
• 4 from independent experts - engineers and researchers at other companies (Google, Microsoft, a university professor, and a startup CTO) who could speak to the significance of the contributions

Each letter was 3-4 pages and followed a specific structure: the expert's own credentials, how they became aware of the engineer's work, and why that work constitutes an original contribution of major significance to the field. No generic praise. Every paragraph tied back to specific evidence.

What About the "Final Merits" Analysis?

Meeting 3 criteria gets you past the first step. But USCIS also conducts a "final merits determination" where they ask: does the totality of evidence show this person is in the extraordinary ability category?

This is where the overall narrative matters. The petition framed the engineer not as "a good engineer at a big company" but as "a recognized expert in distributed systems whose work has been adopted industry-wide". Every piece of evidence pointed back to that narrative.

The petition included a 15-page cover letter that wove together all the evidence into a coherent story. The GitHub stars, the conference reviews, the letters, the salary - they all supported a single claim: this person is at the top of the distributed systems field.

The Cost Breakdown

How much did this actually cost?

• Attorney fees: $8,500 (flat fee, included petition preparation and all revisions)
• I-140 filing fee: $715
• Premium processing: $2,805
• Expert letters coordination: $0 (but significant time investment)
• Total: approximately $12,000

Compare that to a typical EB-2 PERM process where the employer spends $10,000-$15,000 and you wait decades. The eb1a self petition route for an Indian H-1B holder can actually be cheaper and faster.

Common Questions from Engineers Considering EB-1A

"Do I need publications?" No. This engineer had zero peer-reviewed publications at the time of filing. Open-source contributions, system designs at scale, and patents can substitute for traditional academic output.

"Do I need to be at a FAANG company?" No. But working at a large, well-known company does help because the scale of your impact is easier to quantify. Engineers at smaller companies can still qualify - they just need to show external recognition and adoption of their work.

"Can I file while my employer has a PERM pending?" Absolutely. EB-1A is a completely separate petition. You can have an EB-2 PERM in progress and file your own EB-1A simultaneously. In fact, that's what this engineer did - they kept their Amazon EB-2 as a backup.

"What if I get denied?" A denial doesn't affect your current visa status or any pending employer-sponsored petitions. The risk is limited to the money and time you invest. You can also file again with a stronger case.

Lessons for Other Tech Workers

If you're considering the eb1a extraordinary ability route as a software engineer, here's what this case teaches:

Start building evidence now. Don't wait until you're ready to file. Volunteer to review conference papers. Open-source a tool you've built. Document the impact of your systems with metrics.

Think beyond academia. The eb1a criteria for tech workers look different than for researchers. Industry impact, adoption metrics, revenue impact, and scale of systems all count.

Get an experienced attorney. Not just any immigration attorney - one who has handled EB-1A petitions for tech workers specifically. The framing matters enormously.

Be strategic about your 3 criteria. Don't try to claim 7 criteria weakly. Pick 3 you can prove strongly with documentary evidence.

The eb1a India backlog alternative is real. It's not easy, and not everyone will qualify. But if you're a senior engineer with demonstrable impact, it's worth a serious look before resigning yourself to a 50-year wait.