Location, Remote, and the Fields That Filter

Location is a parsed field like any other: the software looks for something that resembles a place name near your contact block and stores it. If nothing is there, the field is empty — and an empty location field behaves differently from a location an employer would have accepted. Meanwhile the things you most want to communicate about location, like remote eligibility and willingness to relocate, are usually captured by form questions rather than by your document.

How a location gets recognised

Extraction looks for place-shaped text, most reliably in the contact block at the top of the document. The patterns it handles best are the conventional ones:

• Columbus, OH
• Columbus, Ohio, USA
• Manchester, UK
• Toronto, ON

What it handles less well:

• A neighbourhood or borough alone. Shoreditch or Capitol Hill may not resolve, and if it does it may resolve to the wrong country.
• A country alone. Germany fills the field with something very coarse; a radius filter around a specific city has nothing to work with.
• A postcode alone. Sometimes recognised, sometimes stored as an unrelated number.
• A full street address. Usually fine, and it fills the field, but it also puts your home address into a database that many people will see. Whether to include one is a privacy judgement rather than a parsing one; City, State gets the field populated without the rest.
• An airport code or a nickname. NYC usually works; the Bay Area and DFW metroplex are less certain, and PNW is not a place a taxonomy knows.

The reliable move is a City, Region pair on its own line in the contact block, in the body of the page rather than in a document header — because header text may not be extracted at all.

The empty field problem

A great deal of recent advice says to leave your location off entirely, usually on privacy grounds or to avoid being filtered out for being far away. It is worth understanding what actually happens when you do.

The parsed record ends up with a null location. Downstream, that can be handled several ways depending on the system and how the employer set it up: the candidate is excluded from any location-filtered search, or included but sorted last, or shown with a blank that a human has to resolve by asking you.

Note that only one of those outcomes is better for you than a truthfully stated distant city, and none of them is better than a truthfully stated nearby one. Omission does not read as “location flexible.” It reads as missing data, and missing data is not usually treated generously by a filter.

There is a real privacy consideration in giving a street address, and City, State answers it. Removing the city as well trades a visible fact for an invisible gap.

Remote work is a form question

Here is the part that surprises people. Your resume saying Remote or Open to remote does very little mechanically, because remote eligibility is normally captured as a structured field — a checkbox or a dropdown on the application form, or a screening question — not inferred from your document text.

Same for relocation, work authorisation, and on-site availability. These are exactly the attributes an employer wants as clean data, so they ask directly. The parser’s job is your history; the form’s job is your eligibility. There is more on this division in the screening questions that come before parsing.

Two practical consequences:

1. Answer the form questions carefully. They are frequently hard filters, and they are the highest-leverage text in the whole application. A misread dropdown can end the application before your resume is opened.
2. Still write your location on the resume, because the parsed field feeds recruiter searches that happen later and independently of the form you filled in today.

Remote as a job’s location

A different and more useful case: recording that a past role was remote. This one belongs on the resume, inside the job entry, because it is part of your history.

Senior Analyst — Calder Group (remote, US-based team), Jan 2021 – Mar 2024

That is factual, it parses as ordinary text, and it does real work for a human reader who wants evidence you can operate remotely. Writing Remote in place of a company location, with no city anywhere, leaves the entry’s location field empty in the same way as before.

If a role was hybrid or you moved during it, say so plainly rather than picking one: (hybrid, 2 days in Manchester).

Relocation, honestly

If you are applying to a city you do not live in and intend to move, the accurate way to say it is a short line in the contact block or summary:

Columbus, OH — relocating to Denver, CO in September

What not to do is put the target city in your contact block as though you already live there. It fills the field the way an employer wants and it is a false statement about a fact that becomes obvious the moment scheduling starts. It also creates a practical mess: interview logistics, right-to-work paperwork, and payroll all assume the location you gave.

Some guides suggest using a friend’s address in the target city. Same objection, slightly better disguised.

Multiple locations and international applications

Two homes. Pick the one that is true for work purposes and note the other in words if it matters.

Applying internationally. Include the country. Manchester alone can resolve to England or to New Hampshire, and the difference is consequential. Also expect a work-authorisation form question, which is the field that actually decides this, and answer it accurately.

A country-specific phone number. Write it in international form — +44 161 … — so the field is unambiguous. A local-format number can be stored as a number that nobody can dial.

What location parsing does not do

It does not measure your commute. It does not know that the city you named is forty minutes from the office by train, or that the two cities in your record are in the same metro area. A radius filter works from coordinates and a number, and it has no notion of whether the distance is practical.

That is worth knowing because it sets the limit of what formatting can achieve. If distance is genuinely the obstacle, no field will argue your case; a sentence in a cover letter or a note in the form’s free-text box is where a human can be persuaded, and that belongs to a different part of the application than the parser.

Check it

In the plain-text version of your resume, look for a City, Region pair in the first few lines. If it is not there, or it only exists in a page header, your location field is at risk of being empty. Then look at each job entry and ask whether a stranger could tell where that work happened. One short parenthetical per entry usually closes the gap.