There is a vocabulary problem in remote job postings, and it is costing senior developers real time. I have read 400+ "Remote" postings in the last quarter and the gap between what the words mean and what the job actually is got worse, not better, in 2026.
Here are 15 words and phrases that almost always mean "this job is not what the headline says it is." If you see two or more of these in a single posting, it is almost certainly a hybrid or location-restricted role wearing remote clothing.
The hybrid-in-disguise tells
1. "Remote-first." This is the single biggest tell. The phrase is now used so loosely that it has no signal. About 40% of "remote-first" postings I read also list a required city or "1-2 days a week onsite preferred." Read the rest of the listing carefully before celebrating.
2. "Flexible workplace." Flexible to whom? Almost always means flexible for the company to call you in. Hybrid is the realistic interpretation.
3. "Hub city" mentioned anywhere. If the listing names "our SF hub" or "London office is our hub for this team," your future calendar will have onsite expectations. They are warning you upfront.
4. "Work from anywhere in [region]." This sounds great until you read the fine print. It is usually a tax / payroll constraint disguised as flexibility. Check whether "anywhere" includes your specific state. Most US-listed remote roles exclude 5-10 states for payroll reasons.
5. "Mostly remote." Mostly is doing a lot of work in that sentence. If they meant fully, they would say fully. Mostly = expect quarterly or monthly travel to a hub.
The location-restricted tells
6. "Must be located in [city] metro area." Obvious one but worth listing. Some companies still tag these as "Remote" because the role does not require daily in-office. It is not remote. It is local with WFH flexibility.
7. "Within [N] hour drive of [city]." Specifically punishing because the listing often shows up in remote search filters. Three hours from Chicago is not remote; it is regional.
8. "Eligible candidates must reside in [list of states]." Tax/legal reason, not flexibility. The list is usually 8-12 states they have payroll set up in.
9. "EST hours preferred." Different from "EST hours required" but in practice the same constraint. If the team is on EST and you are on PST, you will end up on EST hours within 60 days.
10. "Some travel required (10-15%)." 10% means about 5 weeks per year of travel. Weigh whether your life accommodates that. The listings rarely tell you whether the travel is a single team offsite or weekly Tuesday-Thursday client visits.
The compensation tells
11. "Geo-adjusted compensation." Code for: we will pay you less if you live somewhere cheap. The same role at the same level can pay 25-30% less in a Tier 3 metro than in San Francisco. If the listing mentions geo-adjustment without naming the bands, ask in the recruiter call.
12. "Salary commensurate with location." Same as #11 but without admitting it. The dodge is the giveaway.
The cultural tells
13. "We come together onsite a few times a year." Translation: 2-4 trips per year, expensed but mandatory. Not a deal-breaker for many people, but if you are choosing remote because you have caregiving obligations, this is a genuine constraint to know about.
14. "Strong async culture but..." Whatever follows the "but" is what the culture actually is. "Strong async culture but we have 9am standups in EST" is a synchronous culture that uses Slack.
15. "Distributed by default, [city] HQ." The HQ designation is the tell. There is an office, leadership is mostly there, and the unspoken expectation for senior IC and managerial roles is that you visit.
What does honestly remote sound like?
The postings that have actually been remote across the listings I read all share the same vocabulary:
- "Fully remote"
- A specific eligibility geography (e.g., "any US time zone" or "Americas timezones")
- An explicit comp band that does not mention geo-adjustment
- A team-page link that shows distributed team members across multiple cities/countries
- An "About our remote setup" section that explicitly addresses async work, travel cadence, and equipment stipend
When a listing has all five of those, it is usually the real thing.
The 20-second filter
Before you spend time on a "remote" listing, scan for the 15 phrases above. Two or more = probably hybrid or location-restricted, save your application time. None or one = likely worth the deeper read.
For the broader playbook on finding genuinely remote senior roles before they get flooded, Remote Developer Jobs in 2026: Where to Actually Find Them walks through the sourcing channels that have actually produced results. And if you want the full taxonomy of what "remote" means at different companies, Companies Saying "Remote" in 2026 Mean 6 Different Things breaks down the six dialects.
Top comments (0)