You spend hours perfecting your bullet points, dialing in your skills section, and tailoring your summary for every role. Then you type your hometown in the contact field and move on without a second thought. Just a formality, right? That two-word field (city, state) is actively shaping whether recruiters ever find your resume in the first place.
Location isn't just a label. Inside an ATS, it's a structured data field that gets parsed, indexed, and filtered. Recruiters use it to sort candidates before they read a single line of your experience. And with hybrid work policies now fragmented by company, role, and department, the stakes on getting location right have never been higher. Hybrid roles in particular are often searched by office ZIP code radius, which means listing 'Remote' instead of your actual city can quietly lower your ATS score for those roles before a recruiter ever opens your file.
43.4%
Of Recruiters Filter by Location
Making it the 5th most common ATS filter used, per a 2025 survey of recruiters
City + State
Is All You Need
Full addresses introduce distance bias and privacy risk without improving ATS visibility
51%
Of Remote-Capable Employees
Now work in hybrid arrangements, making location strategy more complex than ever (Gable, 2024)
How ATS Systems Actually Use Your Location
When you upload a resume, the ATS parser doesn't read it the way a human does. It extracts structured fields: your name, your email, your job titles, your skills, and your location. That location data gets normalized (think: 'NYC' becomes 'New York, NY') and stored for search and ranking. It's not decoration. It's a database entry.
Key Terms to Know
- ATS Location Parsing
- The process by which an ATS extracts your city/state from your resume and stores it as a structured field used for filtering and ranking candidates.
- Location Filter
- A recruiter-set parameter that limits candidate results to a specific city, metro area, or radius. A 2025 survey of recruiters found that 43.4% apply this filter, making it one of the most commonly used.
- Distance Bias
- The tendency for ATS systems and recruiters to deprioritize candidates whose listed location suggests a long commute or relocation need, even for remote-eligible roles.
- Knockout Question
- An employer-configured pre-screen question with a disqualifying threshold. Location eligibility is one of the most common knockout criteria, and unlike ATS scoring, these are hard gates set by the hiring team.
Here's the detail that changes everything: location isn't just a filter field. It also appears to function as a keyword signal in ATS scoring algorithms. Resume optimization research consistently shows that including 'New York' or 'NYC' on a resume targeted at a New York-based role can give your overall ATS score a slight boost, because the system recognizes geographic alignment. You're not just avoiding a filter. You're actively improving where you rank in the candidate pool.
The Four Location Scenarios (And What to Write for Each)
There's no single correct answer for what to put in your location field. The right choice depends on your situation. Here are the four most common scenarios, and the strategy that serves you best in each one.
You Live in a Major Hub and Are Applying Locally
This is the straightforward case. List your city and state ('Chicago, IL' or 'Austin, TX') and you're done. Skip the street address entirely. Full addresses aren't needed for ATS geo-matching, and they introduce two real risks: distance bias (if you're on the far edge of the metro) and unnecessary privacy exposure. City and state is sufficient for the system to categorize and score your application correctly.
You Live in a Suburb or Secondary Market
This is where most candidates leave visibility on the table. If you live in Broomfield, Colorado and you're targeting Denver-area roles, list 'Denver, CO' (not Broomfield). Recruiters searching for Denver candidates may never see Broomfield in their results. Your actual suburb simply won't match their geographic filter. The same logic applies coast to coast: Hoboken becomes New York, Bellevue becomes Seattle, Pasadena becomes Los Angeles. List the market you're in, not the municipality on your driver's license.
You're Planning to Relocate
This one surprises people. If you're in Phoenix applying for roles in Boston, listing your Phoenix address can trigger a location filter that pushes you down before a recruiter ever reads your name. The counterintuitive move: list your target city. A phrasing like 'Relocating to Boston, MA' or simply 'Boston, MA (Relocating)' in your contact block positions you correctly in recruiter searches for that market. Recruiters have documented dismissing out-of-state candidates outright, a bias that compounds the ATS filter problem if your listed location doesn't match the target city.
You're Applying to Fully Remote Roles
Listing only 'Remote' without a city and state seems logical, but it can quietly hurt your visibility. Many companies are legally limited to hiring remotely only in states where they have registered business presence (tax registration, workers' comp, and business licensing all create state-specific hiring constraints). If a recruiter is searching for candidates eligible to work remotely in California or Texas, and your resume says only 'Remote,' you may not surface in that search at all. This is especially true for hybrid roles, where recruiters often filter by office ZIP code radius and 'Remote' won't register in those results. List your actual city and state, then add '(Open to Remote)' or '(Remote)' as a secondary signal.
Location Formatting: What Works vs. What Doesn't
Do This
Avoid This
Denver, CO: clear, parseable, metro-level precision
1234 Maple Street, Broomfield, Colorado 80021: full address introduces distance bias and privacy risk
Relocating to Seattle, WA: positions you correctly in target-market searches
Phoenix, AZ: when applying to Seattle roles, this can push you down in location-filtered results
Austin, TX (Open to Remote): surfaces in state-specific remote searches
Remote: no city or state means you may disappear from state-filtered and radius-filtered recruiter searches
New York, NY: lists the recognizable metro, not a specific borough or ZIP code
11201 (ZIP code only): ZIP-level data can trigger distance bias in radius-based ATS searches
Do This
Denver, CO: clear, parseable, metro-level precision
Avoid This
1234 Maple Street, Broomfield, Colorado 80021: full address introduces distance bias and privacy risk
Do This
Relocating to Seattle, WA: positions you correctly in target-market searches
Avoid This
Phoenix, AZ: when applying to Seattle roles, this can push you down in location-filtered results
Do This
Austin, TX (Open to Remote): surfaces in state-specific remote searches
Avoid This
Remote: no city or state means you may disappear from state-filtered and radius-filtered recruiter searches
Do This
New York, NY: lists the recognizable metro, not a specific borough or ZIP code
Avoid This
11201 (ZIP code only): ZIP-level data can trigger distance bias in radius-based ATS searches
The Hybrid Work Wrinkle
If you think remote work made location irrelevant, the current landscape tells a different story. Hybrid is now the dominant work model. 51% of remote-capable employees work in hybrid arrangements, but 'hybrid' means something completely different depending on where you're applying. Some employers mandate four or five days in-office. Others require two or three days for employees within commuting range of an office. Still others allow fully remote work from anywhere. These aren't edge cases. They're the mainstream.
This fragmentation means you can't apply a single location strategy uniformly across your job search. A resume that works perfectly for a fully remote role could get deprioritized by a recruiter searching for candidates within commuting range of a specific office campus. Read each job posting for its actual location requirements and match your resume's location field accordingly.
The Contact Block: Order Matters More Than You Think
Where you put your location on the page also affects whether it parses correctly. ATS systems are trained to expect contact information in a specific sequence. When that sequence breaks, parsing accuracy drops. A misread contact block means your location field may not register at all.
The Correct Contact Info Sequence for ATS Parsing
Full Name
Your name should appear first, alone on its own line, in plain text. Not in a header, not in a text box, not in a graphic element. Plain body text only.
Phone Number
A single, current phone number. Labels like 'Cell:' or 'Mobile:' are unnecessary and can confuse certain parsers.
Email Address
Professional email, plain text. Avoid embedding it as a hyperlink only, since some parsers don't extract link-only emails correctly.
City, State (and LinkedIn URL)
Your location comes last in the contact block. Format it simply: 'Denver, CO' or 'Relocating to Seattle, WA.' Your LinkedIn URL can follow on the same line or just below.
A Note on Work Experience Location
Location strategy doesn't stop at your contact block. Your work experience section has its own location consideration, especially if you worked remotely. The standard approach: list your employer's city in the experience section, not your personal location, and add '(Remote)' next to it. This preserves the recognizable company location for ATS parsing and recruiter searches, while being fully transparent about your work arrangement.
How to Format Remote Work Experience Location
Software Engineer | Acme Corp | Austin, TX Jan 2022 - Present
Software Engineer | Acme Corp | San Francisco, CA (Remote) Jan 2022 - Present
Why does this matter? If Acme Corp is a San Francisco-based company and a recruiter searches for candidates with Bay Area employer experience, listing your personal Austin address in the experience block could mean your resume doesn't surface. The employer's location is the recognizable signal. Your arrangement is the qualifier.
What Knockout Questions Mean for You
Some ATS platforms go beyond parsing and filtering. They include employer-configured pre-screen questions, and location eligibility is one of the most common. These are hard gates set by the hiring team, not autonomous ATS decisions. If a posting asks 'Are you located in or willing to relocate to [City]?' and you answer 'No,' the employer's configured rules flag your application as ineligible regardless of your keyword match score or experience level. The effect is the same as being deprioritized to the bottom of the pile, and it happens instantly.
Your Location Audit: A Quick Checklist
Before your next application goes out, run through this checklist. Small formatting decisions compound across dozens of applications, and getting them right is one of the highest-leverage moves you can make on a resume that's already strong on experience and skills.
Resume Location Checklist
Tools like ResumeXray can show you exactly how an ATS parses your contact block, including whether your location field is being read correctly, and flag formatting issues that might cause your location data to register incorrectly. If you've been applying consistently without hearing back, a parsing audit is worth the look. Sometimes the problem isn't your experience. It's that the system never correctly registered where you are.
Frequently Asked Questions
Do I need to include my full address on my resume?
No. Full street addresses are no longer necessary and can actually work against you by introducing distance bias if you live far from the office, and by exposing personal information unnecessarily. City and state is all an ATS needs to categorize your location correctly.
What if I live in a small town nowhere near a major city?
For roles that are fully remote, list your actual city and state plus '(Open to Remote).' For in-person or hybrid roles in a distant city, you'll likely need to address relocation directly, either with a 'Relocating to [City]' note or in your cover letter. Be honest about your situation while positioning yourself correctly for the market you're targeting.
Should I include a ZIP code for radius-based searches?
No. Including a ZIP code can trigger distance bias in ATS platforms that support radius-based filtering. If your ZIP puts you 30 miles from the office, that radius filter may deprioritize you even if you'd happily make the commute. Stick with city and state.
What if the job posting doesn't specify whether it's remote or in-office?
In those cases, list your actual city and state, and consider adding '(Open to Remote)' if you'd prefer flexibility. You can always clarify your preferences in a cover letter or during the screening call. When in doubt, defaulting to your real city and state keeps you visible in the widest range of searches.
My resume location says one thing and my LinkedIn says another. Does that actually matter?
Yes. Recruiters frequently cross-reference both. Inconsistency creates confusion and can cost you visibility in LinkedIn Recruiter searches, which use your LinkedIn location field as a primary search input. Update both at the same time to keep your profile consistent.
Why did I get a response within minutes of applying? Was I auto-rejected?
Very fast responses almost always reflect employer-configured knockout rules, not autonomous ATS decisions. If a hiring team has set a hard location requirement and your application doesn't meet it, their system flags it immediately. The ATS itself doesn't reject anyone, but employer-set rules can deprioritize applications in seconds. Check location requirements carefully before applying.