My 2-Week EB2-NIW Timeline as a Principal Cybersecurity Architect (Approved, No RFE)

I’ve been reading a lot of posts here during my own process, so I wanted to give back and share what happened in my case.
My situation was stressful, and seeing other people’s experiences helped me understand what was possible and what wasn’t.

I’m a Pakistani national, based in the UK, with a little over 20 years in IT and around 15 years focused on cybersecurity. I currently work as a principal cybersecurity architect at a fintech. My work has been mostly around secure cloud architectures, platform security engineering, and building controls for regulated financial systems.

The urgency was the hardest part. I have 4 dependents and one was close to aging out. I had roughly 2 weeks to get a full EB2-NIW filing ready so that my eldest would qualify for derivative status. It was one of those moments where you realise that delays are not an option.

I worked with Beyond Border Global for the preparation. Not promoting them, just mentioning because they handled the heavy lifting and the speed. I would not have been able to assemble everything at this pace on my own.

How we framed the proposed endeavor

The first call was basically a deep dive into my work. We aligned the proposed endeavor with something that actually reflects what I do: advancing secure, compliant cloud and data-protection architectures for US financial-services and regulated enterprises. It made sense because I’ve built and run bank-grade security stacks before, including IPO-critical security controls for a fintech.

I learned quickly that NIW is very sensitive to how well the proposed endeavor is defined. It needs direction, outcomes, and national relevance. They had internal frameworks for structuring this, which helped a lot under the time pressure.

Why we chose the advanced degree route

I have two Master’s degrees, one in Software & Systems Security and one in Systems Auditing, so we used the advanced-degree prong. Even though certifications weren’t strictly required under that route, we still included CISSP/ISSAP, CCSP, AWS Security Specialty, and ISO 27001 Lead Auditor. The reasoning was to reinforce professional standing, especially since the timeline didn’t allow much margin for anything weak.

How we argued Dhanasar

Prong 1 – Merit and national importance
This part focused on financial-system resilience and consumer data protection. We tied my work on digital-bank infrastructure and IPO controls to the idea that secure digital finance is critical for the US economy. They had prior NIW arguments for fintech cases, so pulling that in helped.

Prong 2 – Well positioned
This was the most intense section because of the documentation. We needed references who could speak to my leadership in platform security architecture. They identified six people across a major bank and a large-scale fintech. I didn’t realise how much work goes into chasing org charts, HR confirmations, sanitized artifacts, and role descriptions until I saw what was needed. Doing this in two weeks felt impossible, but somehow they managed to line everything up.

Prong 3 – Waiving the job offer
The argument here was that requiring PERM would block me from doing the cross-institution work my proposed endeavor relies on. Security designs, reference architectures, and advisory work don’t fit well into a single-employer model. This was pretty aligned with my actual career plan, so it didn’t feel overstated.

Outcome
We filed within the two-week window.
I-140 approved.
No RFE.

Honestly, I expected at least a clarification request because of the speed, but it went through cleanly. The biggest relief was knowing it locked in eligibility for my eldest child.

Posting this for anyone dealing with tight family timelines or coming from technical security backgrounds. I didn’t find many cybersecurity-focused NIW posts while preparing, so hopefully this helps someone gauge what’s possible and what the process feels like.

Happy to answer questions if it helps anyone else on the same path.