EB-2 NIW RFE for Big Tech Employees: Why “National Importance” Keeps Getting Challenged

If you work at Amazon, Google, Meta, Microsoft, Apple, or Netflix and just opened a Request for Evidence (RFE) on your EB-2 NIW RFE petition, you’re probably wondering what went wrong. You may be thinking, “I work for a major tech company. My qualifications are strong. My work is important. So why is USCIS pushing back?”

Here’s the thing: in many cases, a national importance RFE for a Big Tech employee doesn’t mean your work is weak or that you’re not qualified. More often, the problem is how the proposed endeavor was presented in the petition.

In other words, the petition may have focused too much on your employer- its size, reputation, technology, or impact-instead of clearly explaining what you personally plan to do and why that work has national importance to the United States.

This is a pretty common, and often fixable, issue we see at Orange Law when reviewing EB-2 NIW cases for engineers, AI researchers, cybersecurity specialists, and product leaders working at large technology companies.

So, if you’ve received an RFE, don’t panic. In this guide, we’ll walk through why USCIS may raise this issue, what officers are actually looking for, and how you can strengthen your case-whether you’re responding to an RFE or considering refiling after a denial.

Why Does USCIS Send National Importance RFEs to Big Tech Employees?

Every EB-2 NIW case is evaluated under the three-prong test from Matter of Dhanasar (2016):

1. Does the proposed endeavor have substantial merit and national importance?
2. Is the petitioner well positioned to advance it?
3. Would it benefit the U.S. to waive the job offer and labor certification requirements?

For most engineers and technologists at large companies, prong one’s “substantial merit” half is rarely the issue. Building AI infrastructure, hardening cloud security, or improving distributed systems is obviously technically significant.

“National importance” is where things get harder. USCIS isn’t asking whether your work is impressive – it’s asking whether the benefit of that work extends past your employer’s four walls. A recommendation letter that says “this engineer improved our internal platform, which serves millions of our customers” describes a great employee. It doesn’t, on its own, describe a nationally important endeavor.

This is exactly why petitioners at Amazon, Google, Meta, Microsoft, and similar companies see this RFE pattern more than almost anyone else: their work is genuinely large in scale, but the petition often stops at “large scale” instead of connecting that scale to a broader U.S. interest.

Your Job Title Is Not Your Endeavor

This is the single biggest mix-up we see in EB-2 NIW petitions from tech professionals, and it’s worth sitting with.

Your occupation is what you do day to day – “Senior Software Engineer,” “Machine Learning Scientist,” “Staff Security Engineer.” Your proposed endeavor is the specific problem you’re advancing and why solving it matters to the country.

Occupation (weak framing)	Proposed Endeavor (strong framing)
Senior Software Engineer at a cloud company	Strengthening the reliability and security of cloud infrastructure relied on by U.S. healthcare, finance, and government systems
AI Researcher at a tech company	Developing machine learning methods to detect fraud and reduce financial-system risk at scale
Cybersecurity Engineer	Reducing vulnerabilities in software supply chains used across critical U.S. industries

Notice the pattern: the strong version names the employer’s technology as evidence, not as the endeavor itself. The company is where the work happens – it shouldn’t be the outer boundary of what the work means.

The “Amazon Problem” (And Why It Applies to Any Big Tech Employer)

Imagine a petition built around statements like:

• “My work improves Amazon’s cloud platform.”
• “My system increases operational efficiency for Amazon.”
• “My project benefits millions of Amazon customers.”

Every one of these is true and still leaves USCIS with the same unanswered question: why does this matter nationally, beyond Amazon?

The fix isn’t to remove the employer from the petition – employer projects are often your best evidence of scale and technical difficulty. The fix is to trace the work outward: does your cloud security work also protect infrastructure that hospitals, banks, and government agencies rely on? Does your supply-chain optimization touch broader U.S. logistics resilience? Does your AI research generalize to problems outside your team’s platform?

The same logic applies whether you work at Google, Meta, Apple, Microsoft, Netflix, Nvidia, or anywhere else with a recognizable name. A famous employer earns you nothing automatically – USCIS evaluates the endeavor, not the logo on your badge.

What Actually Convinces USCIS of National Importance?

A well-supported petition should answer, clearly and in order:

1. What specific problem are you solving?
2. Who is affected by that problem – beyond your immediate team or company?
3. Why does the U.S. have a stake in solving it (economic, security, infrastructure, healthcare, competitiveness)?
4. How does your work create effects beyond your employer?
5. What objective evidence shows this impact is real, not speculative?

Answering these five questions – explicitly, with evidence – is the difference between an approvable petition and one that draws another RFE.

How to Respond to an EB-2 NIW National Importance RFE

The instinct many petitioners have is to submit more recommendation letters saying they’re talented. Resist that instinct. USCIS already isn’t questioning your talent — that’s usually not what prong one is about. Piling on praise doesn’t fix a framing problem.

Instead, a stronger RFE response typically:

• Restates the endeavor in specific, employer-neutral language
• Explains the larger problem the endeavor addresses
• Ties that problem to a recognized U.S. priority (AI/ML competitiveness, cybersecurity, critical infrastructure, healthcare technology, supply chain resilience, etc.)
• Adds independent, third-party evidence – not just internal company documentation
• Shows adoption, replication, external reliance, or influence beyond the original team or platform
• Brings in expert letters that speak to field-level impact, not just the petitioner’s talent
• Responds point-by-point to every concern USCIS raised in the RFE

What Are Your Options After an EB-2 NIW Denial?

A denial isn’t necessarily the end of the road. Depending on why USCIS denied the case, petitioners generally have a few paths forward, and for many Big Tech professionals, filing a new I-140 petition is often the most practical option – especially when the underlying issue was how the endeavor was framed rather than a lack of qualifications.

Refiling lets you:

• Redefine the endeavor in employer-neutral terms from the outset
• Directly address every weakness USCIS identified
• Add new evidence and accomplishments developed since the original filing
• Build a more coherent, connected theory of the case
• Avoid the narrower, more limited scope of a motion to reopen/reconsider

Building a Stronger Petition: A Practical Checklist

Whether you’re responding to an RFE or preparing to refile, these are the core moves:

• Define the endeavor narrowly enough to be concrete, but broadly enough to reach beyond your employer. “Software engineering” is too broad and too vague. “Improving reliability of cloud infrastructure used across regulated U.S. industries” is specific and extensible.
• Anchor the endeavor to a named national priority — cite federal policy, agency initiatives, or authoritative industry research, and then explain how your specific work advances that priority. Citing the priority alone isn’t enough.
• Show impact outside your team — open-source contributions, external adoption, industry influence, cross-organization reliance, independent recognition, or downstream economic and security benefits.
• Use forward-looking language. NIW eligibility is about what you propose to advance going forward. Past achievements should support your trajectory, not be the entire case.
• Quantify scale — then explain why it matters. “Millions of users” shows size. “This technology addresses vulnerabilities affecting systems relied on across healthcare, finance, and government” shows why the size matters nationally. The second sentence is the one that moves the needle.

The Employer Should Support Your Case – Not Define It

Across the initial filing, the RFE response, and any refiled petition, the same principle holds: your petition’s strength comes from the proposed endeavor and its broader significance – not from your employer’s name recognition.

Working at a major tech company is strong evidence that you operate at scale and solve hard problems. It just can’t do the work of proving national importance on its own. The strongest EB-2 NIW petitions use company-specific achievements as supporting evidence while building an endeavor whose significance clearly reaches past any single employer’s commercial interests.

FAQ: EB-2 NIW RFEs for Tech Professionals

Does working at a company like Google or Amazon automatically help my EB-2 NIW case? 

Not by itself. It can support evidence of scale and technical ability, but USCIS evaluates your proposed endeavor’s broader impact — not your employer’s reputation.

Why do software engineers get more national importance RFEs than other professions? 

Because tech work is often described in terms of internal metrics (users, revenue, platform efficiency) that are easy to write but don’t automatically show impact beyond the employer. The fix is connecting that scale to a broader U.S. interest.

Should I add more recommendation letters after receiving an RFE? 

Only if they address the specific gap USCIS identified — typically national importance, not your individual talent. Letters that only praise your skills rarely resolve this type of RFE.

Is it better to appeal a denial or refile a new I-140? 

For many national-importance denials, refiling with a corrected, employer-neutral endeavor statement and stronger third-party evidence is often more effective than pursuing a motion or appeal.

Talk to Orange Law About Your EB-2 NIW Case

An RFE or denial on national importance is common for Big Tech professionals – and it’s usually about framing, not merit. At Orange Law, we work with engineers, researchers, and technical leaders to rebuild the endeavor statement, gather the right evidence, and respond to USCIS with a clear, connected case.

If you’ve received an RFE or denial, or you’re preparing to file, schedule a consultation with Orange Law to review your case and map out the strongest path forward.