You found the perfect posting. Right skills, right level, right company. One problem: it is in Denver and you are in Cleveland, and you have heard the machines toss out-of-town resumes before anyone human ever weighs your actual plan to move. So now you are staring at the address line wondering whether to delete it, fudge it, or borrow your cousin's zip code.
Take a breath. Location filtering is real, but it works differently than the horror stories suggest, and the honest playbook performs better than the fake-address trick ever has. Here is how your location actually moves through the system, and what to write instead.
How your location becomes a database field
When your resume is parsed, the city and state near your contact info get extracted into a dedicated location field in your candidate record, often alongside whatever location you typed into the application form itself. Parsers look for recognizable patterns, "Cleveland, OH" style, near the top of the document.
Two practical notes before anything else:
- Placement matters. If your contact block lives in the page header, some parsers skip it entirely and your location field comes up empty, along with your phone number. Keep contact details in the document body; do headers and footers hurt ATS resumes explains the mechanics.
- Parsers sometimes grab the wrong city. A resume with employer locations sprinkled through the work history can occasionally mis-assign one of them as your location. Worth verifying rather than assuming.
You do not need a street address, and you should not include one; city and state are what the field wants, and what privacy suggests anyway.
How recruiters actually use the location field
The field exists because recruiters filter on it, mostly in three ways:
- Metro and radius filters. For onsite and hybrid roles, a recruiter reviewing hundreds of applicants will often filter to candidates within the metro area or a mileage radius of the site. Out-of-area candidates are not rejected; they just are not in the list being reviewed, which lands the same.
- Application form questions. Many portals ask directly: "Are you located in, or willing to relocate to, [city]?" or "Are you authorized to work in [country]?" These answers can feed knockout rules, which are the closest thing to true auto-rejection in most systems. Answer them thoughtfully; they outweigh anything on the resume itself. How knockout questions screen you out covers this layer.
- Remote-role eligibility. Remote does not mean location-blind. Companies hire remotely only in states or countries where they are registered for payroll and tax, and teams often need time-zone overlap. So remote requisitions filter on state, country, and sometimes time zone.
Notice what is missing from this list: any system that reads "Cleveland" and hits reject on its own. The risk is invisibility inside a filtered view, not robotic rejection. That distinction shapes the fix.
The fake address trap
The old-school trick, borrowing a local address or just typing the target city as if you live there, feels harmless. It is not, and it usually is not even effective.
- It surfaces fast. "When could you come in this week?" is often the first scheduling question for local candidates. Your area code, your LinkedIn location, and your work history geography all tell the real story. Recruiters cross-check LinkedIn constantly, which is why your LinkedIn location setting should agree with your resume.
- It becomes a formal problem later. Background checks surface address history. Onboarding, payroll, and tax forms require your actual residence. A candidacy built on a false address either unravels before the offer or converts into an awkward confession after it.
- It poisons trust on day one. Even when it "works," you start the relationship having misled the employer about a basic fact, and they will remember that when your start date slips because you are, in fact, moving across the country.
The deeper issue is the same one that governs every resume decision: anything you write, you will eventually have to defend in a live conversation. A fake address has no defensible version.
The honest playbook for relocators
Here is what actually works, and it costs you nothing you were not going to give anyway.
1. State your real location plus a specific relocation line, right at the top. In the contact block, where parsers read location:
Cleveland, OH | Relocating to Denver, CO (March 2027)
Specificity is what makes this work. "Willing to relocate" is wallpaper; every desperate applicant says it. A named city with a timeframe reads as a plan, not a wish. If your move is certain and dated, some relocators reasonably lead with the destination: "Relocating to Denver, CO, March 2027 (currently Cleveland, OH)." Both facts stay on the page; only the emphasis changes.
2. Repeat the plan in your summary with one line of substance. "Operations manager relocating to Denver in March 2027 (family move already scheduled); available for onsite from day one." If the move is independent of the job, say so; it removes the recruiter's quiet worry that you will withdraw when reality hits.
3. Answer portal questions as the relocator you are. "Willing to relocate: yes." If asked whether you are currently local, answer truthfully; if there is a free-text field, add the date. Never claim to be local now when you are not.
4. Expect and address the real objections. Recruiters hesitate on out-of-area candidates for concrete reasons: interview logistics, start-date risk, relocation cost expectations. A line like "no relocation assistance needed" (if true) and availability for video interviews defuses most of it. The complete strategy, including cover letter framing, lives in resume for out-of-state jobs before you relocate.
Will some radius filters still exclude you? Yes. A recruiter filtering strictly to current metro residents will not see you, honest or not, and the fake address would only have deferred that mismatch to a worse moment. The relocation line wins in every scenario where you can actually win.
The honest playbook for remote seekers
Remote candidates make the opposite mistake: deleting location entirely, hoping to qualify everywhere. A blank location field does not read as "anywhere," it reads as unknown, and unknown fails eligibility filters that a truthful answer would have passed.
- List city and state, or at minimum state and time zone. "Columbus, OH (Eastern Time)" answers the three questions remote employers legally and practically need: country, state, and overlap hours.
- Say what you are actually open to. "Open to remote (US-based) or hybrid in Columbus" is one line that routes you correctly in both kinds of searches.
- Check the posting's fine print. "Remote (US)" often means "remote in the states where we are registered." If the posting lists eligible states and yours is not one, that is a real constraint; applying anyway with an obscured location just wastes a slot you could spend on an eligible role.
Verify what the field actually says
Everything above assumes your location parsed the way you wrote it. Sometimes it did not: contact block in a skipped header, a stray employer city captured as yours, a relocation line formatted so the parser read only half of it.
Check it the same way a recruiter's filter will read it. Run the free scan at careerbounce.io and see exactly what parsing software extracts from your resume, your location line included, along with your titles, dates, and skills. Free, private, entirely on your device; your resume never gets uploaded anywhere.
An honest location plus a specific plan will not beat a hard radius filter every time, and nothing will. What it does is keep you findable for every role you can genuinely take, with a story that holds up from the first phone screen to the first day of work. That is the only kind of advantage worth having.