Guide
There is a very specific kind of panic that kicks in when the H-1B math finally lands in your body. You do not need another motivational speech there. You need a cleaner read on what the O-1 path actually asks from an engineer.
AI architect. International student. O-1 approval in roughly three years.
Fresh enough that the pain still sounds real, which is exactly why it is useful.
The page you are reading exists because too many engineers still think the O-1 is reserved for famous researchers.
The mistake almost everyone makes
Harsh says the internet keeps feeding engineers the same bad story: if you do not have a stack of publications, you are out. That is a nice way to stay stuck.
His version was much less theatrical. He built a case around real work, real stakes, and receipts that another adult could verify.
What he built the case on
The three buckets
This is the cheat sheet version. Short enough to scan. Honest enough to be useful.
1. Original contributions
Harsh did not lean on papers. He leaned on patented work and systems that changed how users found doctors. If your work materially changed search, revenue, product performance, infra, or customer outcomes, start keeping the paper trail now.
2. Critical role
The O-1 story gets easier when the stakes are obvious. Harsh stepped into a project tied to patient attrition and a very large business problem. If you want stronger evidence later, pick work with visible consequences now.
3. Trajectory
This is not about flexing salary on the internet. It is about showing that the market kept trusting you with bigger things, faster than usual. That pattern helps the whole case make sense.
First moves
If this is starting to feel relevant to your life, do these before you open another Reddit tab. (Yes, that was a direct attack.)
From the transcript
These are short on purpose. If one of them punches you in the face a little, good.
H1B seat is just 85,000 and we are having what like four lakh applications every year. The moment you know the first H1 was no, I decided H1 may not be first H1 was no, I decided H1 may not be the path for me. So he did not wait. My
the path for me. So he did not wait. My guest today Hush Maheshwari engineered a way to speedun from intern to director in just about 2 years. >> I was aiming for a principal role and
>> I was aiming for a principal role and started behaving that right on day one. So it was purely one strategic decision after other. Hush realized pretty early on in his career that if he
pretty early on in his career that if he did the work no one else wanted to do or did the work no one else wanted to do or no one else could do, he would get promoted and and this is a big and he
Fast scan
Keep going
FAQ
Fair questions. This stuff is not exactly low-stakes.
No. The bigger point from Harsh's story is that the case is built on evidence, not academic cosplay. Patents, high-impact internal work, critical projects, salary history, and proof that your work changed something can all matter.
Harsh built around three things: original contributions, a critical role on hard projects, and a compensation story that matched the level of responsibility he kept taking on. The common thread is proof, not vibes.
The lesson here is no. Harsh started moving right after the first H-1B rejection. If this path may matter for you, the smart move is to start collecting evidence while you still have time to shape the story.
They think the bar is fame. That is the wrong frame. The real question is whether you can prove rare impact in a specific lane and document it like a grown-up.