Filtering job posts for India-eligible roles

Status: Outline — full guide coming soon. Get notified when it ships →

What this covers

• The 8 JD phrases that mean US-only (regardless of "remote" tag)
• The 6 phrases that mean truly global, including India
• Timezone red flags: "must overlap 9-5 PT" = 9:30PM-5:30AM IST
• The verify-before-apply 30-second script that saves the application slot

Why this matters for Indian devs going remote

Half the discouragement in an Indian dev's job search comes from spending hours on US-only listings disguised as global remote. Learning to filter in 30 seconds — before opening the application — recovers those hours into apps that can actually convert. This is the single skill with the highest ROI in the search.

Outline

The 8 US-only JD phrases

TODO — "US-based remote", "must be authorized to work in the US", "W-2", "PST hours required", "subject to US export controls", etc.

The 6 truly-global phrases

TODO — "anywhere in the world", "no timezone requirement", "async-first", "global remote", "all timezones welcome", "contractor".

Timezone red flags

TODO — "overlap PT", "core hours ET", "standups at 10am SF" — convert to IST, apply mental friction test.

The 30-second verify script

TODO — scan for the 8 / 6 phrases, check team page nationality mix, grep LinkedIn for India hires.

Common mistakes to avoid

• Trusting the "remote" tag without reading the JD body
• Applying anyway on a US-only role hoping they'll make an exception
• Ignoring timezone requirements because "I can work nights" (you can't, sustainably)

Templates / examples

TODO — a printable JD-signal cheat sheet, a 30-second verify script (4 steps), and a company-eligibility flowchart.

Related guides

• Where remote roles that actually hire from India live
• We Work Remotely: filtering the firehose

---

Have a question about this? DM me on LinkedIn or drop your email to get the full guide as soon as it's published.