No. A remote job can still require you to live in a specific country or state, keep set hours or travel to an office. In JobShifu's October 4, 2026 audit, 64% of US remote postings, 54% of Canadian and 54% of UK ones had no region label JobShifu could extract, so an empty location field is a reason to ask.
Remote describes a working arrangement. Where an employer can hire you, which hours you must keep and whether you travel are separate conditions, and each one can rule an application out.
A remote company can still restrict a role's location
GitLab is a useful example because its working model is explicitly all-remote. Its candidate handbook still directs applicants to the individual listing to check whether their country is eligible. Its relocation policy also describes roles tied to particular countries, regions or time zones. Those are company-specific policies, not a rule for every remote employer. [1] [2]
For your application, the role's current wording matters more than a company's reputation for remote work. Read the location field, the responsibilities and requirements, and the application questions. If they disagree, ask which condition applies.
How often a remote posting states where you can work
JobShifu extracts a remote region from each posting it crawls: US only, Canada, US and Canada, UK, EU, worldwide and so on. The first audit, on September 15, 2026, found 8,693 of 11,973 remote-classified posting records, or 72.6%, had no extracted region label. [3]
| Extracted region field, September 15 | Posting records | Employers represented |
|---|---|---|
| No region label extracted | 8,693 | 2,176 |
| A region label extracted | 3,280 | 1,197 |
| All included remote-classified records | 11,973 | 2,887 |
Employers can appear in both groups, so the employer counts do not add up. That is a measurement of JobShifu's data coverage, not the share of employers that leave location unclear: a missing label can reflect wording the extractor did not capture, incomplete source information or an unstated condition, and the audit did not decide which applied to each record.
By country: the US, Canada and the UK
The same query, run again on October 4, 2026 and split by the country of the posting's stated location, shows where the gap is widest. [4]
| Posting country | Remote records | No region label | Restricted to that country | Employers |
|---|---|---|---|---|
| United States | 7,545 | 64.3% | 34.8% (US only) | 2,027 |
| Canada | 392 | 54.1% | 38.0% (Canada) | 220 |
| United Kingdom | 365 | 53.7% | 42.5% (UK) | 224 |
| All countries | 10,776 | 69.5% | 2,726 |
The last column is the share whose label limits the role to its own country. Most of the remaining labeled records point to a neighboring region: 7.1% of Canadian records read US and Canada. Labels that say worldwide were rare in all three countries, below the disclosure floor of 25 records and five employers, which is itself worth knowing: when JobShifu could extract a region from a US, Canadian or UK remote posting, it almost always named a country or region rather than "anywhere".
Two cautions. The Canadian and UK groups are small, a few hundred records each, so read the gap between them and the US as a difference in this snapshot, not a market fact. And the all-countries share moved from 72.6% to 69.5% between the two dates; two snapshots of a crawler's output are not a trend.
How the snapshots were measured
Both read-only queries included records classified as remote, marked open in the corpus and seen within the preceding seven days, and excluded blocked feed sources and companies. Being marked open is a crawler observation, not confirmation that an employer is actively interviewing. The unit is a posting record: the October records span 10,383 stored employer/requisition keys, and different records can refer to the same vacancy. Every published cell clears the research disclosure floor of 25 records and five employers.
These are dated diagnostic snapshots. They do not estimate the global supply of remote jobs or establish why a particular application was rejected. The September and October data and measurement notes are published under CC BY 4.0.
Read a remote listing in five passes
Here is an invented listing that packs the usual conditions into four sentences:
Remote support specialist. Applicants must reside in Oregon or Washington. Working hours are 9 a.m. to 5 p.m. Pacific. Quarterly team meetings take place in Seattle.
| Check | What the example tells you | What it does not settle |
|---|---|---|
| Country | Two US states are named | Whether relocation before starting is accepted |
| State or region | Oregon or Washington | Whether nearby states qualify |
| Working hours | A Pacific-time workday | Whether the schedule is flexible |
| Office attendance | Quarterly meetings | Whether other visits are expected |
| Travel | Seattle meetings require attendance | Who pays and how much notice is given |
A reader in California should not read the Pacific-time schedule as permission to apply from California. A reader in Oregon who cannot travel should clarify the meetings before assuming the arrangement fits.
Ask a question the employer can answer
A useful clarification names your situation and the unresolved requirement:
I currently live in California. The posting lists Oregon and Washington. Is this role open to someone relocating to an eligible state before the start date?
Or, if the posting says remote but mentions regular office attendance:
Is office attendance required for this role? If so, how often and at which location?
Use an official recruiting contact when one is provided. Do not assume no response means permission, and do not choose an inaccurate application answer to get past a location question. Work authorization and sponsorship are separate conditions; confirm them rather than inferring them from the remote label.
Settle eligibility before tailoring
For each promising role, note the allowed location, schedule, travel expectations and any open question beside the application, and resolve a hard mismatch before spending an evening on a rewrite. JobShifu puts each job's requirements in one format next to your saved experience and preferences, which makes a location condition easier to spot; its direct employer links let you check the current source, and they do not guarantee the employer will accept your location. To confirm the role itself is still open, paste the employer's link into the job-status checker.
Common questions
Does no location listed mean worldwide?
No. The location may be missing from the page you saw or from a tool's extracted fields. Look for explicit eligibility wording or ask the employer.
Are UK and Canadian remote jobs clearer about location than US ones?
In JobShifu's October snapshot, a larger share of UK and Canadian remote postings carried an extracted region label than US ones, about 46% against 36%. That compares extraction coverage on a few hundred non-US records, so it is not proof that employers in one country write clearer postings. Read each listing either way.
Can I work remotely while traveling abroad?
Do not infer that permission from the job's remote label. Ask the employer about the proposed destination and dates before making plans. A hiring location and a temporary travel arrangement are different questions.
Should I skip a role if the location is unclear?
An unanswered question is not automatically a rejection. Check the employer's page and ask where practical, and keep the role marked as unresolved rather than treating it as either permission or a confirmed restriction.
Sources
- GitLab, Candidate Handbook: where GitLab hires. Accessed September 15, 2026 UTC.
- GitLab, Relocation: location and time-zone considerations. Accessed September 15, 2026 UTC.
- JobShifu Posting Corpus, remote-region field coverage snapshot. Measured September 15, 2026 at 05:57 UTC. Posting-record coverage audit, not a labor-market estimate.
- JobShifu Posting Corpus, remote job postings with and without a stated region, by country. Measured October 4, 2026 at 06:15 UTC. Posting-record coverage audit, not a labor-market estimate.