EB1A Approved after RFE (AWS / Cloud Tech Profile) – 4 Criteria
Hi everyone,
Finally I am ready to share my EB1A experience, specifically for folks with an industry-focused AWS / Cloud Architecture background on an H-1B who might be wondering how to position their profile. I had created this account to gain knowledge more on the EB1A and I'm glad I found so may helpful sub reddits.😄 Thus, I am planning to official post my first content on Reddit and I am so overwhelmed while writing it.
Profile & Filing Overview:
• Field: AWS Cloud Infrastructure / Cloud Architecture (Industry)
• Status at Filing: H-1B
• Service Center: Texas Service Center (TSC)
• Processing: Premium Processing
• Criteria Claimed (4):
Leading / Critical Role
Original Contributions of Major Significance
High Salary
Scholarly Articles
Timeline:
- Initial Submission: March 9, 2026
- RFE Received: April 10, 2026
- RFE Response Submitted: May 4, 2026
- Approval: May 15, 2026
The RFE & How We Responded:
USCIS challenged two specific criteria: Leading/Critical Role and Original Contributions.
For Critical Role: The officer questioned whether my work demonstrated a critical role within the broader company rather than being limited to standard day-to-day responsibilities.
We responded with detailed architecture diagrams, internal impact reports, project metrics, and evidence showing the measurable business impact of the cloud initiatives I was responsible for. We also expanded the testimonial letters from senior executives to clearly explain my responsibilities, the importance of the projects, and how my contributions affected the organization.
For Original Contributions: This was probably the more challenging part of the RFE.
Since I don't have a traditional academic background with hundreds of citations, we focused on demonstrating industry impact rather than relying primarily on academic recognition.
We provided evidence around the scale of enterprise deployments, technical solutions I had developed, measurable improvements in infrastructure efficiency, and the broader adoption and impact of those solutions within the organization.
The biggest change was not necessarily adding more documents - it was reorganizing and explaining the existing evidence in a way that directly addressed USCIS's concerns.
Key Lesson Learned:
The RFE made me realize that technical achievements don't always speak for themselves.
As cloud/technology professionals, we're used to talking about architectures, migrations, uptime, scalability, automation, cost optimization, etc. But for an EB1A petition, it's important to connect those technical achievements to measurable organizational or industry impact.
For the RFE response, we went point-by-point through the officer's concerns and mapped each piece of evidence directly to the issue being questioned. That made the response much more focused.
Thankfully, the petition was ultimately approved after the RFE.
Happy to answer questions about positioning an industry-focused cloud/AWS profile, demonstrating critical role or original contributions or handling an RFE in details.