.png)
Remote Work
How to Tell If a Job Is Really Remote Before You Apply
Most misleading job posts are written by tired people using last year's template, not by criminals. Here are the phrases that reveal the real location policy, and the three-question email that settles it in ninety seconds.
Dillon Price · August 6, 2026 · 8 min read
The posting said Remote. Four paragraphs down, under a heading nobody reads, it mentioned that the team gathers in Denver twice a quarter. Both sentences were true. Only one of them made it into the filter you searched with. Knowing how to tell if a job is really remote is the cheapest skill in a job search, and almost nobody teaches it.
This isn't about spotting criminals. Most misleading postings are written by tired people using last year's template. The damage is the same either way. You spend three rounds and a fortnight discovering something that was decidable in ninety seconds.
Why is it so hard to tell if a job is really remote?
A job post is not one document. It's a committee, spread over time. Somebody in talent writes the summary, a hiring manager pastes in the requirements, legal adds a line about authorization, and the location field gets set by whoever creates the req in the system. Those four people rarely speak to each other, and one of them left the company in March.
The location field itself is the deeper problem. Most applicant tracking systems offer three or four options for a decision that has closer to forty. Remote, Hybrid, On-site. A policy that actually reads "remote within the EU, four hours overlap with Berlin, two weeks onsite per year" has nowhere to go. It gets flattened to Remote, and the detail survives only if somebody remembered to type it into the body.
Recruiters often don't know either. Ask one whether the role permits Portugal and you'll likely get a genuine pause, because a finance team has the answer and the recruiter never bothered to ask them. That pause is information. It tells you the policy hasn't been tested, which means it can still be shaped.
Recycling makes it worse. Companies rarely write a req from scratch. They clone last year's, change the title, and ship it. A posting from 2023 that said Remote will still say Remote in 2026, long after three return-to-office memos have overwritten what it describes. Figuring out how to tell if a job is really remote often means working out how old the words are as much as what they say. Check whether the benefits section mentions a perk the company scrapped, or whether the tech stack lists something the team has since replaced. Stale details in one part of a posting suggest stale policy in another.
Which phrases reveal the real location policy?
Location policy hides in vocabulary, not in the location field. These are the phrases worth reading closely:
- "Remote-first" versus "remote-friendly." The first usually describes infrastructure and defaults. The second usually describes tolerance, which is revocable.
- "Must be located in" or "authorized to work in." This is the payroll boundary showing through. It's the hardest constraint in the posting and the least negotiable.
- "Overlap with [timezone] required." Geography may be open. The clock is the real fence.
- "Occasional travel to HQ." Undefined by design. Ask for the number, in days per quarter, and watch how quickly it arrives.
- "Distributed team." Describes where colleagues sit, not where you may sit. These are different claims.
- Silence on location entirely. The most common case, and the one people misread as permission.
The salary band tell
A geo-adjusted salary band discloses the true permitted geography faster than the location field does. If a posting lists one national band, the company is thinking in one country. If it lists tiers by metro, somebody has already mapped which places you're allowed to be. Read the compensation section as a map.
What silence actually means
Most postings say nothing about location beyond the field itself, and most applicants read that silence as permission. It isn't. Silence usually means the decision hasn't been made, or has been made somewhere the writer couldn't see. Learning how to tell if a job is really remote means treating an absent policy as an open question rather than a generous one. The practical upside is real, though. An undecided policy is the only kind you can influence, and candidates who ask early are occasionally the reason a company adds a country to its list.
Where the contradiction usually sits
Hybrid jobs disguised as remote almost always give themselves away in one of three places: the third paragraph of the summary, a bullet buried in Requirements, or the benefits list, where "free lunch at our office" answers the question. Scan those three before anything else and make sure you understand how to read a job description in a recruiter's language.
EnRoute Jobs AI tool
Skills Gap Analyzer
See how your skills match a target role and what to learn next.
How do you tell if a job is really remote before you apply?
You simply ask. The reason people skip this step is a belief that questions look presumptuous before an application exists. In practice recruiters answer, because a candidate who self-selects out early saves them more time than they save you.
Send three questions. No preamble and no apology for asking.
- Which countries or states can this role be performed from today?
- How many hours of overlap are required, and with which timezone?
- How many in-person days per quarter should I plan for?
Send it to the recruiter listed on the posting, or to whoever appears as the poster on LinkedIn. Keep it under sixty words. A reply with three specifics means the policy exists on paper. A reply with one specific and two deflections means it exists in somebody's head. Silence means the req may not be live at all, which brings us to the more uncomfortable half of this.
What separates a vague posting from a fake one?
Vagueness is disorganization. Fraud is extraction. They call for different responses, and conflating them makes people paranoid about the wrong things.
Start with the structural context. Bureau of Labor Statistics JOLTS data has shown job openings consistently outnumbering actual hires, month after month. A posting is a statement of intent, not a hiring commitment. Ghost jobs, the listings kept live to build a pipeline or to signal growth, sit inside that gap. They aren't illegal and they aren't aimed at you personally. They're just noise you're being asked to treat as signal.
Fraud is a separate and growing problem. The Federal Trade Commission reported that job and employment agency scam complaints roughly tripled between 2020 and 2024, with reported losses climbing from about $90 million to roughly $501 million over that period. Fake remote jobs are attractive to criminals precisely because remote hiring normalizes never meeting anyone.
The tell is direction of value. A legitimate employer spends time on you. Remote job posting scams ask you to spend money, share bank details, or process a payment. If a conversation moves toward your wallet before it moves toward your calendar, stop. Our full breakdown of remote job scams and the red flags worth memorizing goes through the current playbooks in detail. Remote job red flags of this kind are worth learning once and never relearning.
Sorting the two costs you nothing. A vague posting deserves one email and a week of patience. A suspicious one deserves a closed tab. The failure mode worth avoiding is applying the wrong response to each, which is what happens when somebody decides how to tell if a job is really remote is the same question as whether the employer exists. Verify the company through a source the posting didn't hand you. Find the careers page yourself rather than following the link in the message, and check whether the role appears there too. Legitimate employers survive that check without noticing it happened.
How do you make this a habit instead of a chore?
Stop searching the remote checkbox. Search the language instead. Saved searches built on phrases like "supported countries," "core hours," or "overlap required" surface postings written by people who had to think about policy. That's a better proxy for quality than any filter.
Keep a running list of employers who answered your three questions with three numbers. Six months of that list is a private index nobody else has, and it builds in a way that scrolling never does.
Learning how to tell if a job is really remote also changes what you do next. Once you can read the policy off the page, the useful move is to write down your own constraints so you can compare the two directly. The next piece in this series covers building that constraints document, including the day-count and tax thresholds that decide how long you can stay anywhere. Later in the series we cover the twelve questions worth asking once an offer is actually on the table, when your bargaining power peaks and most people stop asking anything. For the wider framing of what these four location policies are, start with what geo-flexible work actually means.
Ninety seconds of reading, or three weeks of interviews. That has always been the trade. Most people take the second one because the first one feels like doing nothing.
Skip the guesswork on how to tell if a job is really remote
EnRoute tags every listing with its actual location policy, overlap requirement and in-person expectation, so the answer is on the card before you click through.
EnRoute Jobs
Tips, guides, and resources for remote workers, digital nomads, and seasonal adventurers.