Pre-Mortem 07 — Geography, Visa, and the Offer-Timing Risk¶

Failure vector: The plan works. The artifacts land. But the job market doesn’t cooperate for an Indian candidate applying to remote inference orgs, or the timing slips past month 13, or offers cluster in geographies you can’t reach.

Probability this hits in some form: ~55%. More than half the time, “great portfolio → offer” takes 15–18 months, not 13. This is the modal outcome, not a tail risk. Plan for it.

The Adversarial Scenario¶

It’s Aug 5, 2027. Every phase shipped. You have:

SGEMM ladder at 82% cuBLAS. ✅
Triton FA2 within 1.7× official. ✅
Quant bake-off (r/LocalLLaMA, 340 upvotes). ✅
Mini inference engine (1.4K stars). ✅
Two merged vLLM PRs. ✅
Enterprise reference architecture doc. ✅

But: zero offers in hand. Three study loops in progress, all inconclusive. Zoho’s internal inference pivot is stuck in a VP-level review that started in April. You’re staring at the portfolio wondering if you built the wrong thing.

You didn’t. The conversion phase just takes longer than the build phase, and no roadmap that promises “13 months to job offer” is being honest about the geography.

Why This Bites Harder For You Specifically¶

You’re in Tamil Nadu, India — applying to a US-anchored talent market. Even fully-remote inference orgs (Baseten, Fireworks, Together, Modal, Anyscale) still cluster hiring in US/EU time zones, still prefer W-2/PE candidates, still have contractor-only slots for international.
Compensation arbitrage cuts both ways. Remote roles will pay you $60k–$120k when the US baseline is $180k–$280k. That’s still 3–5× domestic senior-eng comp — but it’s how they justify the international contractor path.
Visa nightmares — H1B is a lottery, O1 is real but slow (6–9 months), UK Global Talent is viable, EU Blue Card is workable but slow. If a remote-first offer converts to on-site, the visa timeline can eat 6–12 months.
Indian recruiters filter for different signals — big-tech logos, IIT/IIIT credentials, competitive-programming rating — not “merged PR to vLLM.” The portfolio has to be re-narrated for the domestic audience.
The remote inference-hiring market may shrink by 2027. Not zero probability. Anthropic/OpenAI/xAI hiring bars keep rising; second-tier inference startups may consolidate.

Early Warning Signals (M8–M12)¶

Signal	What it says
Zero recruiter InMails after posting the mini-engine repo	Portfolio narrative not landing → rewrite READMEs, add benchmarks-first framing
“Great profile but we’re not hiring internationally right now” is the third such reply	Remote-international market softening → pivot ratio toward domestic + India offices of hyperscalers
Zoho VP review stuck > 6 weeks	Internal track is dying quietly → open external pipeline in parallel, don’t wait
studies reaching offer stage but ghosting at compensation	You’re getting reshaped as “cheap remote contractor” → negotiate the classification (contractor-to-employee timeline) up front
Cold emails to 2nd-degree contacts (GPU MODE Discord, PR reviewers) returning zero response	You’re a stranger, not a known name → double down on community presence, not applications

Mitigation — The Three-Track Application Plan¶

Do not run these sequentially. Run all three in parallel from month 10 onward.

Track A — Internal Zoho Pivot (highest probability, lowest ceiling)¶

What it is: Zoho pivots you into a formal Inference Infra role (staff eng track), possibly a new “Zoho Model Serving” internal product.
How you engineer it: The four flagship plays in 08_production/13_zoho_leverage_plan.md are your evidence. Get the prefix-cache play measured and internally-blogged by M4. Get the internal benchmark harness owned by you by M6. Get named on the on-prem inference roadmap by M9.
Probability of offer by M13: ~35%.
Ceiling: Comfortable, well-paid by Indian standards, but caps at India-standard senior-eng comp. Learning ceiling is lower than remote inference orgs.

Track B — Indian AI Companies and Hyperscaler India Offices (medium probability, medium ceiling)¶

Who: Sarvam AI, Ola Krutrim, Fractal, CRED (yes, CRED has an ML infra team), Zomato AI, Meesho, Google Bangalore (Gemini serving infra), Microsoft Hyderabad (Azure OpenAI serving), NVIDIA Bangalore (real DGX/DevRel team), AMD India (ROCm), Databricks Bangalore, Snowflake Cortex India (if it exists by 2027).
What they value: Merged PRs to vLLM/SGLang, IIT-adjacent credentials, referrals, English-language technical writing.
Cold-outreach path: Apply directly + get a warm intro from a GPU MODE Discord member who works there. LinkedIn cold-messages with “I built X, here’s the repo, would love to chat” work at ~5–10% response rate for senior ML infra roles.
Probability of offer by M15: ~50%.
Ceiling: Higher than Zoho, especially at NVIDIA/Google/Microsoft India offices where comp bands are US-linked.

Track C — Remote International (lower probability, highest ceiling)¶

Who: Baseten, Fireworks, Together, Modal, Anyscale, Predibase, Lightning, Weights & Biases (inference-adjacent), Deepgram, Perplexity infra, plus vLLM contributor→employee path (Neural Magic, Red Hat inference, IBM Research), plus AMD/NVIDIA developer relations.
What they value: Public artifacts, merged PRs, GPU MODE reputation, ability to work asynchronously in US time zones.
Cold-outreach path: Not “apply on jobs page” — that’s the low-EV route. Instead: (a) merge a PR, (b) get a review conversation going with a maintainer, (c) 2–3 weeks later DM them saying “I’ve been enjoying contributing to X, are you hiring?” This converts at 20–30% for candidates with visible work.
Probability of offer by M15: ~25%. By M18: ~45%.
Ceiling: Highest — $80k–$180k contractor comp, and if the role converts to employee (some orgs do this after 6–12 months of contractor performance), you’re on US comp bands.

Do not pick a track. Run all three. They cost different kinds of time.

Timeline Extension — The Honest Version¶

The plan is 13 months. The build finishes at M13. The conversion typically runs M11–M18. Frame it that way from day one.

If an offer lands at M13 you’re a full sigma above the median. Plan for M15–M18. Anything sooner is upside.

The “Portfolio Repackaging for Indian Audience” Play¶

The same artifacts get different narratives:

For US remote orgs, lead with:

“I built a mini inference engine that reaches within 3× vLLM throughput, shipped 2 merged PRs to vLLM’s V1 scheduler around chunked-prefill edge cases, and published a quantization bake-off that got picked up on r/LocalLLaMA. Full stack — kernels to K8s.”

For Indian companies, lead with:

“I own the LLM inference infrastructure for Zoho’s on-prem CRM Copilot deployment, serving 5000+ seats with 75% prefix-cache hit rate on multi-turn agent workloads. Cost per inference dropped 60% quarter over quarter. Reference architecture and benchmark harness both authored by me.”

Both are true. The framing determines whether the recruiter reads past line one.

The Cold-Email Template (Reusable)¶

Subject: Quick note re: your work on <specific PR / paper / blog>

Body:

Hi <first name>,

I've been reading through <specific PR / paper / repo> and had a
question about <specific technical thing>. My working understanding
is <your take>. Is that right, or am I missing something?

Some context: I've been building inference infrastructure for
<Zoho's agentic products>, and recently shipped <one concrete
artifact link>. Would love to hear how you'd approach
<a specific problem you're stuck on that they're an expert in>.

Not asking anything of you — just genuinely enjoy this work.

— <name>
<one-line portfolio link>

Rules:

Never ask for a job in the first email. Ever.
Reference a specific piece of their work. Show you did the reading.
Attach one artifact link, max. Not a whole portfolio dump.
If they respond, keep the conversation technical for 2–3 rounds. Then, if it’s natural, mention you’re exploring roles.
Response rate: ~30% if you did the technical reading properly; ~5% if you didn’t.

Escalation Trigger¶

If by M12 you have zero study loops in progress despite ≥30 targeted applications + 10 warm cold emails, something is structurally wrong with the pitch. Do NOT keep applying with the same materials.

Instead:

Get a portfolio review from someone in the field (GPU MODE Discord DM, ask nicely, offer to buy them a coffee).
Rewrite the top three artifact READMEs from scratch with their feedback.
Post a “what am I doing wrong” note on a friendly forum — vulnerability sometimes gets you 10× the signal a polished ask does.

If by M15 you still have no offer, it’s not you. It’s a market or geographic constraint. Take a real break. Then decide: extend the timeline by 6 months, pivot the track ratio, or take the domestic role while continuing the OSS work as a side project.

The One Line That Matters¶

The plan builds the artifacts. The market decides when it pays. Do not conflate the two.

If the artifacts are real (and they will be, if you follow the roadmap), the offer arrives. It might arrive at M11 (upside), M15 (median), or M18 (long-tail). Nothing in the first 13 months should be conditional on the offer arriving on schedule. The portfolio compounds whether or not the market moves on your timeline.

Compensation is a lagging indicator of skill. The lagging indicator lags. That’s the whole point.

Return to README.md · Next: 08_family_health_life_risk.md