How to tell if a remote job is actually remote
“Remote” often hides a country, a timezone, or a quiet return to the office. Here is how to read a listing before you spend an hour applying.
2 min read · Updated Oct 2026
Plenty of roles are labelled "remote" when they mean "remote if you happen to live near our head office", or "remote until we change our minds". Here is how to separate the genuinely location-independent roles from the optimistic ones.
Read the location field, not the badge
Start with the location string. The words around "remote" tell you almost everything:
- Remote - anywhere / worldwide, genuinely open.
- Remote - EMEA / APAC / the Americas, broad, but tied to a region.
- Remote - United States / UK / Germany, you must be in that country.
- Remote (within 3 hours of CET), a timezone requirement in disguise.
Then scan the body for the catches
Search the description for these phrases. Any one of them can void a "remote" label:
- "must be authorized to work in…"
- "must reside in…" or "must be based in…"
- "only considering candidates in…"
- "we are unable to sponsor visas"
What "remote-friendly" really means
If a company only says "remote-friendly", treat it as hybrid until proven otherwise. See remote-first vs remote-friendly vs hybrid for exactly what each phrase promises. Ask one question early: "Which countries can this role be performed from, and does that change?" Vague answers are answers.
Why we grade it
Every listing here shows whether a role is truly Remote - anywhere or limited to a region or country, and flags the restriction we found. Use the Remote anywhere filter to see only roles with no geographic catch. If a listing looks too good to be true, run it past our red flags checklist.
Related guides
Find a role that's actually remote
Search fresh, genuinely-remote developer jobs - free.
Browse jobs