Three interviews into a process for a “fully remote” operations role, David asked a routine scheduling question — “just confirming, is there any expectation to be near the office for team days?” — and the recruiter paused a beat too long before answering “well, it’s remote-first, but yes, we do like folks within driving distance for quarterly planning.” Driving distance meant relocating. The listing had said “remote” nine times. It never once said “remote-first,” “hybrid,” or anything that would have flagged the real expectation, until week three of a process he’d already turned down two other interviews to prioritize.
This happens constantly, and it isn’t always a scam or bad faith — sometimes it’s sloppy internal language, sometimes it’s a recruiter using “remote” loosely because their own team calls it that. Either way, the cost lands on the applicant, not the company. Learning to read a listing before you apply is the difference between three weeks wasted and three weeks well spent.
What “Remote” Legally Means vs. What Companies Actually Mean by It
“Remote” has no enforced legal definition in job postings, which is exactly the problem. A company can label a role “remote” if employees work from home most days but are expected in an office for occasional planning sessions, all-hands weeks, or “culture” events. None of that is illegal or even necessarily dishonest — it’s just a much looser use of the word than most applicants assume, a gap SHRM’s research on hybrid and remote work definitions has flagged repeatedly as a source of candidate confusion.
There’s a real spectrum here, and most job seekers only know two points on it: fully remote (work from anywhere, no office ties) and hybrid (fixed office days each week). The truth is there are at least four distinct categories hiding under the single word “remote” in job postings: fully distributed, remote-with-occasional-travel, remote-but-must-live-near-a-hub, and hybrid-mislabeled-as-remote. Only the first one is what most applicants picture when they see the word. These phrasing patterns sit alongside the broader set of remote company culture red flags you can spot before you ever apply.
The Six Phrases That Signal a Hybrid Job Wearing a Remote Label
Certain phrases show up disproportionately often in listings that turn out to have an in-person expectation the title doesn’t mention. None of these guarantee a bait-and-switch on their own, but each one is worth a direct follow-up question before you invest hours in an application.
“Remote-first.” This phrase almost always means “remote is the default, but not the requirement.” It’s one of the more honest signals once you know to read it that way — the company is telling you, in coded language, that some roles or some employees on the team are not fully remote.
“Must be located within commuting distance of [city].” This is functionally a hybrid job. Companies use it to keep their applicant pool officially “remote” for recruiting-marketing purposes while quietly requiring proximity.
“Occasional travel for team collaboration.” “Occasional” is doing a lot of unstated work here. I’ve seen this mean two days a year and I’ve seen it mean two days a month — it’s worth asking for a real number before you assume the lighter version.
“In-office culture with remote flexibility.” This is a hybrid job described from the office’s point of view. Read it as: primarily in-office, remote days available as an exception, not the norm.
“Digital-first” or “distributed-first” without “fully.” Companies that are genuinely fully remote almost always say so explicitly, because it’s a strong selling point they want credit for. The absence of “fully” in an otherwise remote-sounding description is often not an accident.
Location filters that only list specific metro areas. If a “remote” posting restricts applicants to five named cities instead of a country or region, that’s rarely about time zone — it’s almost always about wanting people close enough to come in.
Is This Job Really Remote? A Five-Minute Verification Process
Before you spend twenty minutes tailoring a resume and cover letter, spend five minutes running the listing through a quick check. Look at the company’s own careers page, not just the job board repost — job boards sometimes strip nuance from the original listing when they syndicate it. Search the company name plus “return to office” or “hybrid” in quotes; if they’ve made any recent policy announcement, it usually surfaces in the first page of results. Check LinkedIn for a handful of current employees in the target role or team, and look at their listed location — if they’re all clustered in one metro area despite a “remote, anywhere” posting, that tells you something the listing didn’t. This same instinct — verify before you invest — is worth applying more broadly; see how to vet a remote employer before you accept an offer for the fuller version of this process.
Then, if you’re still unsure, ask directly and early — in the first recruiter screen, not the final round. “I want to make sure I understand the day-to-day: is this a fully remote role with no expectation of in-person time, or is there a hybrid or occasional-travel component?” Recruiters answer this question far more honestly when it’s asked plainly in week one than when it surfaces as a surprise in week three, mostly because by week three there’s social pressure on both sides not to derail a process that’s gone well so far.
One more source worth checking that most people skip: Glassdoor and Blind reviews, filtered to the last six to twelve months, specifically for mentions of “remote” or “office.” Older reviews reflect old policy. I’ve seen candidates rule out a genuinely remote company because of a two-year-old review complaining about a mandatory office, written before the company’s policy changed — and I’ve seen the reverse, where recent reviews flagged a return-to-office push that hadn’t made it into the job posting yet. Recency matters more than volume when you’re reading these.
Why Companies Post Hybrid Roles as Remote in the First Place
It’s rarely pure deception. Three things are usually happening at once. First, “remote” postings get measurably more applications than “hybrid” ones, so recruiters under pressure to fill a role fast have an incentive to use the broader, more attractive label even when it’s not fully accurate — a pattern Buffer’s State of Remote Work research has also tracked as remote postings have grown more competitive. Second, internal definitions genuinely drift — a team that started fully remote in 2022 and slowly reintroduced quarterly in-person weeks may just not have updated its careers-page language to match. Third, some roles are posted as remote at the org level while a specific hiring manager, without updating the job description, quietly expects their own team to be different. That distinction matters, because it’s different from the deliberate patterns covered in remote job scam red flags that actually predict a scam — a mislabeled hybrid role is a communication problem, not a scam.
Knowing which of the three you’re dealing with changes your response. Drift and inconsistent updating are worth a clarifying question and probably still worth pursuing. Deliberate mislabeling to inflate the applicant pool is worth walking away from, because it usually signals a broader pattern of the company saying what’s convenient rather than what’s accurate.
I once coached a client through exactly this decision for a “remote” marketing coordinator role that turned out to require two fixed office days a week — not occasional travel, a standing weekly requirement, discovered only when she asked for specifics after an offer was extended. The company wasn’t hiding it maliciously; the posting had simply been copied from a fully-remote role on the same team and never updated when that particular position’s terms changed. She still took the job, because the two office days happened to be workable for her specific location, but she negotiated a slightly higher salary to offset the commute cost — a detail she’d never have had standing to raise if she hadn’t asked the question and gotten the real number before signing.
Where This Actually Breaks: When the Listing Was Honest and the Manager Wasn’t
The failure mode that catches even careful applicants isn’t a badly written listing — it’s an accurate listing paired with a hiring manager who has a different, unstated mental model of the role. The job description says fully remote. HR believes it’s fully remote. The hiring manager, who joined the company after the listing was written, privately expects their direct reports to be reachable during their specific working hours regardless of time zone, which functions like a hybrid constraint even though nothing was ever mislabeled on paper.
This is why verifying with the recruiter alone isn’t always enough — recruiters often don’t have visibility into a specific manager’s unwritten expectations. If you’re far enough into a process to be talking with the actual hiring manager, ask them directly what a typical week looks like for the team, including how often anyone is expected to be reachable in real time versus working async. Their answer will tell you more than the job posting ever could. For the fuller map of who’s involved and when, the remote hiring process, stage by stage shows where a hiring manager’s unwritten expectations typically surface.
A Worked Example: David’s Almost-Mistake
Going back to David: after that week-three conversation revealed the “driving distance” expectation, he had a decision to make, not just a disappointment to sit with. He’d already declined two other interview processes to focus on this one. Walking away meant re-opening cold outreach from scratch.
He asked one more question before deciding: how often, specifically, was quarterly planning, and was remote attendance ever an option. The honest answer was four in-person days a year, with remote attendance genuinely available but “discouraged.” That’s a real hybrid constraint, but a much smaller one than “driving distance” first implied — four days a year is closer to occasional business travel than a relocation requirement. David took the offer, with the tradeoff clearly understood going in rather than discovered after signing.
The lesson wasn’t “always walk away from ambiguity.” It was that the follow-up question is what turns a vague red flag into an actual, comparable fact you can decide on. Most people either apply blind and get surprised later, or reflexively rule out anything with a hint of ambiguity and lose good roles over language that turns out to mean less than it sounded like. The better move sits in between: ask, get the real number, then decide.
What to Do If You’re Already Mid-Process and Suspect a Bait-and-Switch
If you’re several interviews deep and picking up signals — a stray comment about “when you’re in the office,” a photo-heavy careers page full of in-person team shots, a recruiter who gets vague instead of direct — don’t wait for the offer letter to raise it. Ask the direct question at your next scheduled touchpoint, framed neutrally: “Before we go further, I want to confirm the remote expectations line up with what I understood from the posting — can you walk me through what a typical week looks like?”
If the answer confirms a mismatch you can’t accept, it’s fair to say so plainly and end the process there. You’re not obligated to complete an interview loop for a job you now know you can’t take. If the answer resolves the concern, you’ve just saved yourself from a nagging doubt that would otherwise follow you into salary negotiation and, eventually, into the job itself.
I’ve seen candidates handle this two very different ways, and only one of them holds up over time. Some treat any hint of hybrid language as an automatic disqualifier and withdraw immediately, without asking a single clarifying question — protecting their time, at the cost of sometimes walking away from a role where the real expectation was minor. Others assume every ambiguity will resolve in their favor and only ask once an offer is on the table, which is exactly how David nearly ended up committing to a relocation he hadn’t budgeted for. The candidates who end up satisfied with where they land are the ones who ask early and specifically, then make the call on real information instead of a guess in either direction.
The Pre-Application Checklist That Takes Five Minutes and Saves Weeks
| Check | Where to Look | Red Flag |
|---|---|---|
| Original listing language | Company careers page, not just job board | “Remote-first” instead of “fully remote” |
| Location restrictions | Job posting’s stated eligible locations | Specific metro areas only, not country/region |
| Employee location pattern | LinkedIn, filtered by company + role | Current team clustered in one city |
| Recent company news | Search “[company] hybrid” or “return to office” | Any policy announcement in the last 12 months |
| Direct confirmation | First recruiter screen | Vague or delayed answer to a direct question |
Running this checklist before you apply costs less time than writing one tailored cover letter. Running it after week three of a process costs you the process itself, plus whatever else you turned down to prioritize it. A remote job search already asks enough of your time and patience — spend five minutes protecting both before the next application goes in, and ask the direct question earlier than feels natural. The applicants who get burned by this aren’t the ones who ask too many questions too soon. They’re the ones who assumed the label was the whole story.
References
- Society for Human Resource Management (SHRM), research on hybrid and remote work definitions — https://www.shrm.org
- Gartner, research on distributed and hybrid workforce trends — https://www.gartner.com
- Buffer, State of Remote Work — https://buffer.com/state-of-remote-work
- LinkedIn Economic Graph, workforce and remote hiring trend reporting — https://economicgraph.linkedin.com