DEV Community

charlie-morrison
charlie-morrison

Posted on

Companies Saying "Remote" in 2026 Mean 6 Different Things — Here's How to Tell Which One Before You Apply

#career #remote #webdev #discuss

Companies Saying "Remote" in 2026 Mean 6 Different Things — Here's How to Tell Which One Before You Apply

Follow-up to Remote Developer Jobs in 2026: Where to Actually Find Them — the most-read post I've published so far. The follow-up question I keep getting in DMs is some variation of: "I applied to a 'remote' role and they want me onsite three days a week, what gives?"

Yeah. "Remote" stopped meaning one thing about two years ago. Here are the six dialects I've tracked across 200-ish 2026 job postings, with the tells that let you decode which one a listing is using before you waste an application.

1. Truly remote ("work from anywhere in the country")

  • Tells in the JD: "Fully distributed." "No HQ." Lists timezone overlap requirement (e.g. "4 hours overlap with PT") instead of a city.
  • Where to verify: Check if the company has any office address in the listing footer. Truly remote companies often have a registered agent address and that's it.
  • Red flag that contradicts: Phrases like "team-building offsites" without travel reimbursement detail. Sometimes those mean "come to HQ on your dime, twice a quarter."
  • Examples in the wild: Most YC W24-onwards startups, indie SaaS shops, async-by-design teams.

2. Remote within a country/region

  • Tells: "Remote (US)." "Anywhere in EU." Sometimes lists specific states excluded (CA, NY, WA — usually a payroll-tax workaround).
  • Why: Tax registration. They genuinely don't care where you sit, but their payroll provider only covers certain jurisdictions.
  • What to check: State exclusions. If you're in one of the excluded states, you're not eligible no matter how good a fit you are.

3. Remote within commuting distance

  • Tells: "Remote" but "must be within 2 hours of $CITY." Sometimes phrased as "remote-friendly with occasional onsite."
  • Translation: They mean hybrid that occasionally tilts remote. You'll be in the office 1–2 days a week or 2–3 days a month.
  • Tell to confirm: Search for the role title plus "hybrid" on the same company's careers page. If the same posting exists labeled hybrid, the "remote" version is the same job.

4. "Remote-first" (which is hybrid that wants to feel virtuous)

  • Tells: "Remote-first culture." "Office is optional." "We have HQs in [city] and [city]."
  • Translation: Officially you can work from anywhere. Practically, the people who get promoted are the ones who show up.
  • How to verify before applying: Look at the engineering managers' LinkedIn locations. If 8 of 10 are within 30 miles of HQ, "remote-first" is marketing.

5. Remote during a window (return-to-office in N months)

  • Tells: Vague language about "current workplace flexibility" or "flexible arrangement subject to change." Sometimes the only tell is the phrase "during this phase."
  • Translation: They have an internal RTO date, often Q3 or Q4 2026, and they don't want to scare candidates.
  • How to ask without being a jerk: In the recruiter screen, ask: "What's your team's expected in-office cadence over the next 12 months?" — gets straight answers ~80% of the time.

6. "Remote" but really international contractor

  • Tells: Posted as remote, but compensation is "based on local market rates" or paid via Deel/Remote.com. Sometimes routed through a third-party recruiter.
  • Translation: You're not an employee — you're a contractor in your country, the company doesn't sponsor benefits, and the "salary" is often 30–60% of the equivalent US W2.
  • How to verify: Ask if the role is W2/PAYE/CDI in your country, or 1099/contractor. If they hesitate, it's contractor.

The 30-second decode flow

Before applying to anything that says "remote," do this:

  1. Run the JD through a keyword extractor — the one I built works in 5 seconds. If "hybrid," "flexible," "office," "HQ," or "in-person" rank in the top 25, the listing is mislabeled.
  2. Open the company's careers page directly. Search the same role title. If the posting also exists with "hybrid" in the title, you have your answer.
  3. Check 3 LinkedIn profiles of people in the same team — current location field. Cluster around HQ city = the "remote" version is HQ-adjacent only.
  4. Confirm in the screen. Single direct question: "Is this role expected to be in-office any number of days, now or in the next 12 months?" Vague answer = treat it as hybrid.

This routine takes me about 4 minutes. It's saved me from at least a dozen wasted applications in the last two months.

Why this matters more in 2026 than it did in 2024

2024 was peak RTO panic — companies announcing 5-day RTO mandates and losing senior engineers to anyone who'd let them stay home. Late 2025 the pendulum swung again: companies realized they couldn't fill senior roles without offering some flexibility, so they re-labeled hybrid jobs as "remote" to widen the funnel.

The net effect: "remote" in a 2026 job title is now the lowest-information signal it's ever been. Decode before you spend the application energy.

Related:

Top comments (0)