The location field on a 'remote' job isn't asking what you think it's asking
Remote postings still carry a location field, and it usually means work authorization jurisdiction or hub-office proximity, not where your laptop happens to be. Here's how to read it per field and answer correctly.
A posting says "Remote," and the application form still has a location field. This isn't a leftover from a template nobody bothered to remove — the field is usually doing real work, and answering it as if it just wants your city is how remote candidates get filtered out before anyone reads the résumé.
What the field is actually checking
There are three different things a "location" field can mean on a remote posting, and the label rarely tells you which one you're looking at.
Work authorization jurisdiction. Most companies hiring "remote" mean remote within a specific country or region — because payroll, tax withholding, and employment law are set up for that jurisdiction and nowhere else. A US company's "remote" role is very often remote-within-the-US; a "Remote, EU" posting usually means any EU member state, not literally anywhere with an internet connection. If the field is paired with a dropdown of countries or states rather than a free-text box, that's your signal: they're checking whether you're inside their approved footprint, not asking for trivia.
Hub-office proximity. Some "remote" roles are really "remote, but expected to be near enough to an office for occasional in-person weeks" — common at companies still building out their remote posture. If the form asks for a time zone alongside location, or specifically asks how far you are from a named city, this is what's being checked.
Nothing at all — legacy field. Occasionally the field really is vestigial, carried over from a template built for in-office roles and never removed. You can usually tell because it's a single free-text box, unpaired with any authorization or time zone question, on a company that's clearly remote-first in every other part of the listing.
How to answer it, field by field
- Country/state dropdown, no free text: answer with where you're legally eligible to work and physically located, full stop. Don't try to game this one — if the option you need isn't in the list, that's the company telling you the role isn't actually open to your location, not a form bug to work around.
- Free-text "location": put your city and country or state, not "Remote" or "Anywhere." Recruiters filtering a candidate list by location can't filter on "Remote" — you'll just get skipped in the sort, which is worse than being correctly excluded.
- Time zone field: answer with your actual UTC offset, not a city name if a city isn't asked for. If the posting specifies a required overlap window ("must have 4 hours overlap with PST"), and you don't meet it, decide before you apply whether that's a dealbreaker for them — it usually is, and no amount of enthusiasm in the cover letter fixes a scheduling constraint.
- "Are you willing to relocate?" on an otherwise remote posting is usually there for a hybrid or future-office-return contingency. Answer honestly; a "yes" you don't mean creates a mismatch that surfaces later, at a worse moment than now.
The failure mode to avoid
The single most common mistake is writing "Remote" into a free-text location field and leaving it there. It reads to a human as evasive, and it breaks automated sorting on the recruiter's end — most ATS location filters are built around actual geography, and "Remote" doesn't parse as one. If you're not sure which of the three things above is being asked, default to giving your real, specific location; it's the answer that's correct under all three interpretations.
It's a small field to get wrong, and an easy one to get right consistently — which matters more than it sounds, since a location field filled with a vague placeholder is one of the more common reasons a genuinely qualified remote application gets silently dropped from a sorted candidate list before anyone opens it.