I Asked 12 Hiring Managers What 'Truly Remote' Means in 2026 — Their Answers Don't Match Their Job Postings

#career #jobs #remote #abotwrotethis

There is a phrase I see on roughly half of every "remote" posting I read this year: fully remote / work from anywhere.

Then I started asking the people who write those postings what the phrase actually means. Twelve hiring managers, four 1:1 conversations a week, written follow-ups for the rest. The answers don't match the postings.

This is not a complaint. It is the friction layer that keeps costing candidates real offers — accepting a "fully remote" role and then discovering, three months in, that there was a quiet expectation about quarterly travel, or a four-hour overlap window that wasn't disclosed, or a state-tax restriction the recruiter never asked about.

So I went back to the source. Here is what hiring managers actually meant when they wrote "fully remote."

The 12 answers

I sorted the responses into five buckets after about eight conversations. The remaining four didn't add a sixth bucket, just more variance inside the existing ones.

1. Time-zone-bounded remote (4 of 12). "We say fully remote, but you'd need to work US Pacific or close to it." Sometimes there's a 2-3 hour overlap window. Sometimes the engineering team is split across two time zones and they expect you to land in one of them. The posting almost never says this.

2. State/country-bounded remote (3 of 12). Payroll/tax/legal restrictions mean the company can only hire in specific states or countries. One had hired in 14 states; one had a four-state list; one was technically only allowed to hire in their HQ state but was making exceptions case-by-case. The posting said "remote, US."

3. Office-optional remote (2 of 12). "We say remote because you don't have to come in. But the senior staff comes in two days a week, and that's where the relationships get built." This is the bucket where remote candidates quietly don't get promoted.

4. Travel-required remote (2 of 12). "Fully remote, but onsites every quarter and a one-week kickoff at the start." The travel was real and not optional. It was also not in the posting.

5. Truly distributed (1 of 12). Async-first, time zones don't matter, no required onsites, hiring open globally subject to contractor terms. One company. Out of twelve.

If I extrapolate that to the broader market, "fully remote" means truly distributed about 8% of the time. Even if I'm off by 2x, that's still under 20%.

Why postings don't say this

Three reasons came up unprompted across the conversations.

The first is that the recruiter writing the JD doesn't know. They have a template, the hiring manager said "yes it's remote," and the line goes in. The hiring manager meant bucket 1 or 2. The recruiter posted bucket 5.

The second is that specifying narrows the candidate pool too much for the company's brand goals. "If we say 'remote, but only Pacific time zone' we lose 60% of applicants. If we say 'remote' we get more applicants and we screen for time zone in the first call." This is honest but it costs both sides time.

The third is that the company is genuinely figuring it out. They started fully remote in 2020-22, are now reconsidering, and the posting hasn't caught up. One manager admitted: "We are remote until we aren't. The team is small enough that one person joining who needs to be in-office for some reason could change the whole policy."

The four questions that close the gap

If the posting says fully remote and you don't know which of the five buckets it is, ask these four in your first recruiter call. They are not aggressive. They are just specific enough that handwaving stops working.

"What's the time-zone overlap requirement, in hours, with the rest of the team?" Note: not "do you have an overlap requirement." Hours. They will give you a number or admit there isn't one.
"What states or countries can you hire in for this role?" This is a payroll question. If they don't know, they will check and come back. If they say "anywhere" — write it down, because you will want it later.
"How often does this team travel for in-person meetings, and is it required?" Quarterly is normal. Monthly is a different job. "Optional but encouraged" is hiring-manager code for required-for-promotion.
"How many of the senior people on this team work fully remote vs. hybrid?" This is the bucket-3 trap-detector. If senior staff are mostly hybrid, the trajectory of the role is hybrid, regardless of what the posting says.

What "no" looks like in those answers

Watch for the patterns that mean it's not bucket 5.

"We are flexible on time zones, but the team is mostly in [city]." → bucket 1 or 3.
"Right now we can hire in [list of states under 10]." → bucket 2.
"Travel is rare, but the kickoff is in person." → bucket 4 (small dose).
"Most of our senior engineers come in 1-2 days a week." → bucket 3, full strength.

None of these are dealbreakers if you know about them upfront. They are dealbreakers when they show up after you've signed.

The one thing I changed in my own search

I stopped applying to "fully remote" without the answers. Not as a dealbreaker — just as a sequencing thing. I get the four answers in the recruiter call, then I decide whether to invest in the loop. It cuts about 30% of postings from the funnel and saves an enormous amount of mid-funnel time.

If you are early in the search and want to filter postings before even applying, the bucketing exercise above also works on the JD itself. "Distributed team," "async-first," "no onsites required," "we hire globally" — that's bucket 5 language. "Remote (US)," "remote with quarterly onsites," "remote within North America" — that's bucket 2 or 4 being honest.

The companies that mean bucket 5 say it. The ones that say "fully remote" without elaboration usually mean something else.

Free tools I built for the job search: resume-checker, job-keywords, resume-bullets. All free, all in the browser, no signup.

Earlier in this series: