The Location Line Decoder: Reading Remote Postings Term by Term

This is a lookup document for reading the work-location language in a job posting and deciding, in under a minute, whether a role is genuinely remote for someone in your location. It is for job seekers who keep applying to "remote" listings and keep discovering an office, a commute, or a state exclusion after the fact. Each term below is mapped to what it proves about attendance and geography, how it misleads, and the exact line to check to confirm the real arrangement.

Most public advice on this stops at a listicle of "red flag phrases" or a generic remote-versus-hybrid definition. Neither adds the geography axis that actually decides whether you can apply: state-eligibility lists, work-authorization scope, and the pay-transparency tells. This guide is built to be jumped into. Find your term, read its row, leave.

Why the label is now the exception, not the default

The headline word on a posting deserves suspicion because fully remote postings have become rare. In Robert Half's advertised-posting data drawing on TalentNeuron analysis across more than 450 job titles, only 4% of new US job postings in Q1 2026 were fully remote, against 19% hybrid and 77% fully on-site.

That is a sharp compression from a year earlier, when postings ran at 12% fully remote and 24% hybrid in Q2 2025. The trend line matters more than any single quarter, because it tells you which direction ambiguous language is drifting.

Each row is a named quarterly Robert Half posting analysis; the Q2 2025 on-site figure is derived as 100 minus remote and hybrid, and the Q2 2026 figure is the fully in-office share alone. Read the direction, not the decimals: on-site rose from 65% to 77% in two quarters, and the fully in-office share reached 87% by Q2 2026. When a term is ambiguous in this climate, the base rate says bet on more office, not less.

Table: what each work-model term proves and how it misleads

Here is the core lookup. Each term carries a different amount of information about attendance and geography, and each fails in a specific way.

Two rows deserve emphasis. "Remote-first" is described by one practitioner analysis as the single biggest tell, used so loosely it has no signal. "Flexible workplace" almost always means flexible for the company to call you in, which makes hybrid the realistic interpretation. Neither term should move your confidence until you have checked the attendance line, the hub city, and the eligible-states list.

The phrases that signal a hidden in-office requirement

The reliable tells are attendance-conditional phrases and named hubs. Phrasing like "candidates must be able to work on-site as needed" or "may be required to work from the office from time to time" signals the role is not fully remote, however the headline reads.

A named hub is a warning delivered upfront. When a listing names an "SF hub" or says a city office "is our hub for this team," your future calendar will carry onsite expectations. Relocation language is the most decisive of all: jobs listed as remote that include a relocation requirement mean successful applicants must relocate to headquarters, which indicates at least occasional office days or in-person meetings.

The single line to verify pulls all of this together: the stated in-person expectation in days per week or month, plus any office or hub city, plus the eligible-states line. Where none of those appears, the posting has told you nothing binding, and you ask directly.

Employer-side location restrictions and the geography axis

Three restrictions show up in postings, and all three are about where you live, not what you can do. They are state eligibility or exclusion lists, country and work-authorization scope, and pay-transparency triggers.

Restrictions are near-universal. FlexJobs reports only about 5% of the remote jobs it features have zero state restrictions. The driver is compliance cost, not preference: some states apply income tax nexus, unemployment insurance registration, and in some cases sales tax nexus even when a company has just one remote employee in that state. One hire creates overhead, so employers cap the eligible states to contain it.

Pay transparency is the subtlest tell. The laws apply based on where the work will be performed, which for a remote position means anywhere an applicant could plausibly work from. A posted salary range therefore signals the employer is prepared to comply with a covered state. Its absence in a covered state can signal the reverse: that the role is quietly not open there. In one visible episode, Colorado issued guidance after a wave of postings excluded Colorado applicants rather than post a range, which is regulatory attention you can read straight off the page. Pay-transparency rules were active in roughly a dozen to seventeen states plus DC, including California, Colorado, Illinois, New York, and Washington, though counts vary by tracker.

Your location, not your skills, is what most often gates a remote application before anyone reads your resume.

Tailoring an application to a posting that quietly excludes your state is wasted effort, and the exclusion is easy to miss under culture copy. Refolk reads a posting and scores how well you actually fit it before you spend the time, which surfaces a location mismatch early rather than after a rejection.

The posting-versus-worker gap is your real edge

The share of advertised fully-remote roles runs far below the share of workers actually working remotely, and that gap is negotiating room. Among remote-capable US employees in Q2 2025, Gallup found 51% worked hybrid and 21% fully on-site, leaving roughly 28% fully remote. Postings advertised only 4% fully remote in Q1 2026.

Posting shares come from Robert Half; worker shares come from the Gallup Panel, with the remote worker share derived as 100 minus hybrid and on-site. The mechanism behind the gap: about 88% of employers offer some hybrid option but only about 25% extend it to all employees, so flexibility is real but rationed after hire, tied to role or seniority. The posting understates what is negotiable. A listing that says "hybrid, 3 days" may still contain a fully remote arrangement for the right candidate, which is a reason to ask rather than self-reject on the label alone.

The one-minute classification procedure

Run these steps in order. The first six take about two minutes total and use only the posting text. The seventh takes a day or two but is the only one that confirms the real arrangement in writing.

There is a defensible disagreement worth naming. Ask a Manager argues you should treat a "hybrid" label as binding before applying rather than probing it: if an ad says hybrid and you are not within reasonable driving distance, do not apply. That is sound when the ad names days and a city. The recruiter question in step seven is for the ambiguous cases, where "flexible" or an undefined "hybrid" leaves the real arrangement genuinely unknown.

The template that settles it in one message

The decisive step is a single written question. Getting the answer in writing matters, because it commits the employer and protects you from post-offer hybrid creep. Hidden in-person requirements turn a remote role into a commuter role with extra steps, and the fix is to clarify the in-person expectations by quarter and whether there are location restrictions before you invest in the process.

Hi [name], thanks for reaching out about the [role] position. Before I go further, two quick logistics questions so I can plan:

1. What are the in-person expectations for this role, by quarter? Is there a set number of office days per week or month, and is that policy new or long-standing?
2. Are there any location restrictions? I am based in [state/country] - is this role open to applicants there, and is there a pay range for it?

Appreciate the clarity - happy to move quickly once I understand the setup.

Two answers resolve the posting. If the days figure is higher than the ad implied, or the policy changed within the year, treat the ad's number as a floor. If your state is not on the eligible list, the attendance answer is moot.

How this classification goes wrong

Each failure mode below is a false positive: a way the posting looks better than it is. This is the section to reread before you get excited about a listing.

"Fully remote" with a buried states list

You celebrate the label and miss a line reading "not available to residents of [X]." The fix: some fully remote jobs carry country or state restrictions that are legal or payroll constraints, not an in-person requirement, so check the eligibility line rather than the headline.

"Remote-first" that actually means hybrid

You treat it as fully remote. Roughly four in ten remote-first postings also name a city. The fix: check for a hub city and any "days onsite" phrase before trusting the term at all.

"Hybrid" with no defined days

You assume it is light, one or two days. An undefined hybrid posting often hides a looming RTO mandate. The fix: ask for the days-per-week number in writing, and ask when the policy last changed.

"Remote" followed by a relocation ask

You take the title at face value. Postings marketed as remote across various cities have turned out to require relocation to a single headquarters city. The fix: ask whether a local office is assigned to the role.

A missing pay range

You assume the employer simply forgot. In a covered state, absence can mean the role is not open to that state. The fix: cross-check the eligible-states line against the pay-transparency states before assuming an accident.

Post-offer hybrid creep

You trust the ad's day count as permanent. Stealth increases are documented, with in-person days rising even where only 23% of employers formally changed policy. The fix: ask how long the stated policy has been in place.

"Work from anywhere in [region]"

You read it as global. It bounds you to a region and often signals country or authorization limits. The fix: verify the exact scope rather than assuming it means anywhere on earth.

What "remote" self-branding tells you about where to aim

Where people label themselves "remote" is concentrated and geographic, which shapes where genuinely remote roles cluster. In Refolk's index of professional profiles, 203 US-based profiles titled Software Engineer self-describe with "remote," against 27 in Germany - a gap of roughly 7.5x.

These counts come from Refolk's index for the title "Software Engineer" plus the keyword "remote" on current profiles. One caveat: seniority-band splits for Entry and Senior returned no matches for this filter, so band-level counts are not established in the index and should not be inferred. In the US index, the top employers of "remote"-tagged software engineers include Google, Walmart, Amazon, Meta, and Bloomberg; in Germany, Klarna and Mercedes-Benz.io appear. The pattern says remote identity tracks where remote hiring infrastructure and pay-transparency norms are densest, not where the talent lives, which is a reason to widen your target employers before you widen your skills.

If you want to test that pattern against real people, a search of who actually holds remote roles from your position is more useful than reading more listicles. Refolk answers exactly that kind of question from its index.

Keep the classification current

Verify these before you call a posting classified, and re-run the market check quarterly because the base rates move fast.

The single most perishable input here is the posting distribution. On-site postings climbed from 65% to 87% across recent quarters, so the base-rate assumption you carry into an ambiguous term should be re-checked against the latest quarterly posting analysis rather than a figure you memorized. The mechanism stays fixed even as the numbers move: attendance lives in the days line, geography lives in the eligibility line, and the label lives nowhere binding at all. When in doubt, ask the two questions in writing and let the reply, not the headline, decide whether you apply.