15 Words That Mean Not Actually Remote on a Job Posting (Beyond Hybrid)

Source: Dev.to

There is a vocabulary problem in remote job postings, and it is costing senior developers real time. After reviewing 400+ “Remote” postings in the last quarter, the gap between what the words mean and what the job actually is has gotten worse, not better, in 2026.

If you see two or more of the following 15 words or phrases 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.”
   The phrase is now used so loosely that it has no signal. About 40 % of “remote‑first” postings 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. The realistic interpretation is hybrid.

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].”
   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” does 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

1. “Must be located in [city] metro area.”
   Some companies still tag these as “Remote” because the role does not require daily in‑office work. It is not remote; it is local with WFH flexibility.

2. “Within [N] hour drive of [city].”
   Often appears in remote search filters. Three hours from Chicago is not remote; it is regional.

3. “Eligible candidates must reside in [list of states].”
   Tax/legal reason, not flexibility. The list is usually 8‑12 states where the company has payroll set up.

4. “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.

5. “Some travel required (10‑15 %).”
   10 % means about five weeks per year of travel. Listings rarely tell you whether the travel is a single team offsite or weekly client visits.

The compensation tells

1. “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.

2. “Salary commensurate with location.”
   Same as #1 but without admitting it. The dodge is the giveaway.

The cultural tells

1. “We come together onsite a few times a year.”
   Translation: 2‑4 trips per year, expensed but mandatory. Not a deal‑breaker for many, but a genuine constraint for those with caregiving obligations.

2. “Strong async culture but…”
   Whatever follows the “but” is what the culture actually is. “Strong async culture but we have 9 am standups in EST” is a synchronous culture that uses Slack.

3. “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 an honestly remote posting looks like

Postings that are truly remote across the listings I read share the same vocabulary:

• “Fully remote”
• A specific eligibility geography (e.g., “any US time zone” or “Americas timezones”)
• An explicit compensation 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 elements, 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 a deeper read.

For a broader playbook on finding genuinely remote senior roles before they get flooded, see Remote Developer Jobs in 2026: Where to Actually Find Them.

If you want the full taxonomy of what “remote” means at different companies, check Companies Saying “Remote” in 2026 Mean 6 Different Things.