Should you include an address on resume headers, or just city and state? Recruiter-tested guidance on ATS myths, remote roles, privacy, relocation, and the resu
Everyone seems to have a different opinion about what belongs in the contact section of a resume, and the loudest myth is that your address on resume must include a full street address or ATS will filter you out before a human ever sees your name. That myth has been repeated so many times that candidates still type out their apartment number and zip code by reflex, even when they'd prefer not to. The reality, backed by how applicant tracking systems actually parse contact data and what recruiters say they look for, is considerably less alarming — and more useful.
The question was never really about ATS. It was about giving a hiring team enough location context to make a screening decision. Those are different jobs, and conflating them is why so much resume advice sends people in the wrong direction.
Why the Full Address on Resume Myth Keeps Surviving
The Old-School Format That Never Really Left
Resume templates from the 1990s and early 2000s were built around the assumption that a hiring manager would mail you something — an interview invitation, a rejection letter, eventually an offer. A full mailing address wasn't optional; it was the only reliable way to reach a candidate. Those templates got passed down through career centers, Microsoft Word defaults, and well-meaning parents who helped their kids build their first resume. The format calcified into convention before most people thought to question it.
The problem is that hiring didn't change the templates. Email replaced postal mail as the primary channel, then LinkedIn arrived, then mobile phones made phone tag nearly obsolete. But the street address stayed on the resume because it had always been there, and nobody with authority over the format told candidates to take it off. Career advisors trained on older conventions kept teaching the old standard. The result is a generation of job seekers who include their home address not because it helps them, but because removing it feels like breaking a rule.
What ATS Actually Needs Is a Location Signal, Not Your Street
Applicant tracking systems parse resume contact blocks to extract fields: name, email, phone, and location. The location field is used for geographic filtering — if a company is hiring for a role that requires someone within commuting distance of Austin, the system flags candidates who list Austin or the surrounding metro area. It does not need, and in most implementations does not separately store, your specific street address.
According to guidance from major ATS vendors and recruiting practitioners, what matters is that the system can identify a usable location. City and state — or even just a metro area — satisfies that requirement cleanly. As one senior recruiter at a mid-size tech firm put it: "I have never once looked at the street address on a resume. I look at city and state to know if we need to talk about relocation. That's it." The street address is parsed and discarded, or ignored entirely. It does not improve your chances. It just exposes more of your personal information than the process requires.
Why Most Candidates Should Skip the Full Street Address
Privacy and Safety Are Not Paranoia
Posting your home address on a resume is not a neutral act. Resumes circulate — through ATS databases, recruiter inboxes, hiring manager desktops, and occasionally third-party sourcing tools. You rarely control where a resume ends up once it leaves your email outbox. The Federal Trade Commission has documented that home addresses are among the most commonly misused pieces of personally identifiable information in identity theft cases, and that risk doesn't disappear because the document is labeled "professional."
For candidates in certain situations — recent domestic violence survivors, people in contentious custody arrangements, or anyone with a public-facing role who prefers to keep their home location private — this isn't a theoretical concern. But even for candidates without those specific circumstances, there's no upside to publishing your home address on a document that gets forwarded without your knowledge. Privacy is a professional concern, not a personality quirk.
A Recruiter Does Not Need Your Porch Number to Call You
The functional goal of a contact block is to give a hiring team enough information to reach you and confirm you're in the right geography. A phone number handles the first. City and state handles the second. Your street address contributes nothing to either. Recruiters schedule calls by phone or email. They do not send a car to your address to pick you up for the interview. The only reason the full address was ever useful was for postal correspondence, and that era ended before most current job seekers entered the workforce.
What This Looks Like in Practice
A clean, functional contact header looks like this:
Jordan Lee jordan.lee@email.com | (512) 555-0182 | Austin, TX | linkedin.com/in/jordanlee
Compare that to the cluttered version still common on older resumes:
Jordan Lee 4821 Ridgewood Drive, Apt. 3B, Austin, TX 78701 | (512) 555-0182 | jordan.lee@email.com | linkedin.com/in/jordanlee
The second version gives a recruiter two lines of information they will never use. It also makes the header harder to scan. One hiring manager at a regional healthcare company described it plainly: "The street address just takes up space. I've never read one. I go straight to the phone number and city."
Address on Resume: When City and State Is Enough
What Local Hiring Teams Are Really Checking For
When a recruiter at a local company screens a resume, they're asking one question about location: is this person close enough that we don't have to worry about relocation, time zone conflicts, or jurisdiction issues? City and state answers that question immediately. It tells them you're in the metro, you're presumably within commuting range, and there's no conversation needed about moving expenses or start-date delays.
What they are not doing is cross-referencing your street address against a map to calculate your commute to the minute. That level of scrutiny doesn't happen at the resume stage, and in most cases it doesn't happen at all. The location check at the top of the funnel is binary: local or not local. City and state gives them the answer.
Why City and State Works Better Than a Blank Header
Leaving the location field entirely blank creates a small but real friction point. Recruiters who screen high volumes of resumes develop pattern recognition, and a missing location field is an anomaly that triggers a question: is this person local? Are they hiding something? Is this a relocation situation we'd have to budget for? That's not a disqualifying question, but it adds a step — and in competitive applicant pools, adding steps to the recruiter's job is rarely in your interest.
City and state removes that friction without exposing anything you'd rather keep private. It's the minimum viable location signal: enough to pass geographic filters, enough to answer the commute question, not enough to let a stranger find your front door. SHRM's guidance on resume screening consistently points to location as a standard contact-header field precisely because it serves a functional purpose that a blank field cannot.
What This Looks Like in Practice
For a standard applicant — local, not relocating, not in a privacy-sensitive situation — the formula is straightforward:
Morgan Chen morgan.chen@email.com | (617) 555-0294 | Boston, MA | linkedin.com/in/morganchen
No apartment number. No zip code. No street. Just enough to confirm geography and open a conversation.
Address on Resume for Remote Jobs: When Your Location Still Matters
Remote Jobs Are Not Always Location-Agnostic
The assumption that remote means location-free is one of the more expensive misunderstandings in modern job searching. Many remote roles are constrained by factors that have nothing to do with where you physically sit during a Zoom call. Tax nexus rules mean some employers can't legally employ workers in states where they don't have a registered entity. Licensing requirements in fields like law, healthcare, and financial services are jurisdiction-specific. Time zone overlap matters for teams that need synchronous collaboration across a defined window. And some roles marketed as remote still require quarterly travel to a headquarters or client site.
A recruiter at a remote-first software company explained the logic: "When I see a resume with no location at all for a remote role, my first question is always 'where are they?' Because it affects payroll, it affects whether we can even hire them in their state, and it affects whether they can make our team meetings." Location isn't irrelevant for remote work. It's just relevant for different reasons.
How to Format Your Location When You Work Remotely
The cleanest approach for a remote applicant is to include city and state exactly as a local applicant would, and add a parenthetical or brief note if the remote context is relevant. You don't need to make the header evasive or complicated. You need to give the recruiter enough to answer the jurisdiction and time zone questions without a follow-up email.
If you're explicitly targeting remote roles, adding "Remote" as a secondary note signals intentionality without obscuring your actual location.
What This Looks Like in Practice
For a fully remote applicant applying to roles in their own time zone:
Priya Nair priya.nair@email.com | (206) 555-0371 | Seattle, WA (Remote)
For a candidate applying across time zones who wants to flag availability:
Priya Nair priya.nair@email.com | (206) 555-0371 | Seattle, WA (PST — Open to Remote)
Both formats give the recruiter the location signal they need without requiring a separate conversation to establish basic eligibility.
Address on Resume If You Are Relocating or Keeping Your Search Private
Use Relocation Wording When the Move Is Part of the Story
Relocation is a legitimate variable in hiring, and trying to hide it usually backfires. If you're currently in Denver but applying for roles in Chicago, a recruiter who sees a Denver address will either assume you're not serious about relocating or flag you as a relocation cost they weren't budgeting for. The better approach is to name the move directly in the header so it reads as a deliberate choice, not a complication.
The phrasing matters. "Relocating to Chicago — available [Month Year]" is more credible than "Chicago area" when you're still physically in Denver, because the latter feels slightly misleading and recruiters notice. If you have a confirmed move date, use it. If the move is contingent on an offer, say "Relocating to Chicago" without a date. Either way, you're managing the recruiter's expectation instead of letting them discover the gap mid-process.
P.O. Boxes, Virtual Mailboxes, and Coworking Addresses Are Not the Same Thing
Some candidates in privacy-sensitive situations consider using a P.O. box or a virtual mailbox service as a substitute for a home address. This is worth thinking through carefully. A P.O. box signals privacy consciousness, which is fine, but it also signals that you don't want to be found — which can read as unusual in a professional context where nobody was planning to show up at your door anyway. A virtual mailbox tied to a coworking space or mail-forwarding service gives you a street address without exposing your home, but using it on a resume means you're presenting an address that isn't really yours, which creates its own awkwardness if it ever comes up.
The practical answer for most privacy-conscious candidates is simpler: just use city and state. It accomplishes everything a P.O. box accomplishes without the visual signal that something unusual is going on.
What This Looks Like in Practice
For a relocating candidate:
Sam Rivera sam.rivera@email.com | (303) 555-0148 | Relocating to Chicago, IL — Available March 2025
For a privacy-conscious candidate who wants to appear local without sharing a home address:
Sam Rivera sam.rivera@email.com | (303) 555-0148 | Denver, CO
For a candidate in an unstable housing situation who wants to keep location vague but still pass geographic filters:
Sam Rivera sam.rivera@email.com | (303) 555-0148 | Denver Metro Area
All three formats give a recruiter a usable location signal. None of them require a street address. The Equal Employment Opportunity Commission notes that candidates are not legally required to disclose a home address during the application process — the decision about how much location detail to share is yours.
The Recruiter-Tested Resume Header That Does the Job Without Oversharing
What Recruiters Actually Look For in the Contact Block
Ask a recruiter what they scan for in the first three seconds of looking at a resume, and the answer is almost always the same: name, title or function, and whether the person is reachable. The contact block needs to make those three things effortless to find. Name at the top, phone number and email on the next line, location right beside them. That's the entire job of the header.
Anything beyond that — a full mailing address, a fax number, multiple phone numbers, a second email — is noise. It doesn't improve the recruiter's ability to reach you or screen you. It just makes the block harder to scan. One recruiting operations lead at a staffing firm described her preference simply: "Name, phone, email, city and state, LinkedIn if it's current. That's all I need. Everything else slows me down."
Resume and LinkedIn Do Not Need to Match Character for Character
There's a reasonable consistency principle at play between your resume and your LinkedIn profile: both should tell the same basic story about who you are, where you're located, and what you're looking for. But they don't need to be identical in format. LinkedIn's location field is designed for a city or metro area — that's the standard on the platform, and LinkedIn's own career resources confirm that city-level location is what most recruiters filter by when sourcing candidates.
Your resume header can be slightly more formal. Your LinkedIn profile can be slightly less granular. What matters is that the two don't contradict each other in a way that raises questions — for example, listing Austin, TX on your resume while your LinkedIn shows Seattle, WA with no explanation.
What This Looks Like in Practice
A recruiter-friendly resume contact block:
Alex Thompson alex.thompson@email.com | (415) 555-0219 | San Francisco, CA | linkedin.com/in/alexthompson
The corresponding LinkedIn location field: San Francisco Bay Area
The resume is precise at the city level. LinkedIn uses the metro-area format native to the platform. Both tell the same story. Neither requires a street address, a zip code, or anything a recruiter wasn't going to use anyway.
FAQ
Should I put my full address, just my city and state, or no location at all on my resume?
City and state is the right default for most applicants. A full street address gives recruiters information they don't need and exposes your home location unnecessarily. Leaving location blank entirely creates friction — ATS filters may flag the omission, and recruiters will wonder whether you're local. City and state threads the needle: it satisfies geographic filtering, answers the commute question, and keeps your actual home address private.
If I'm applying for remote jobs, do I still need to include my location, and in what format?
Yes — and the reason is practical, not bureaucratic. Remote roles are often constrained by state tax law, professional licensing jurisdictions, or time zone requirements. City and state, optionally followed by "(Remote)" or your time zone, gives recruiters the information they need to confirm eligibility without requiring a follow-up email. Omitting location entirely on a remote application often prompts more questions than it avoids.
How should I show that I'm relocating without making my current location work against me?
Name the destination city directly in your header with a brief relocation note: "Relocating to Chicago, IL — Available March 2025." This frames the move as a decision you've already made, not a complication the employer has to solve. If you have a confirmed date, use it. If the move is contingent on the offer, just write "Relocating to [City, State]" without a date. Avoid listing your current city and hoping the recruiter doesn't notice the mismatch.
What is the safest professional way to share location if I want privacy but still need to look local?
City and state is the answer. It's the professional standard, it's what recruiters expect, and it tells them nothing about your specific home location. A P.O. box signals privacy concern in a way that can read as unusual. A virtual mailbox address presents a location that isn't really yours. City and state gives you full geographic coverage with zero personal exposure.
Will leaving my address off hurt me with ATS filters or recruiters?
Leaving off a full street address will not hurt you — ATS systems parse for a location signal, not a mailing address, and city and state satisfies that requirement. Leaving off location entirely is a different question: it can trigger a filter that's looking for geographic eligibility, and it creates uncertainty for recruiters screening high volumes of applications. The safest move is to include city and state even if you omit everything else about your physical location.
Should I use the same location format on my resume and LinkedIn profile?
The formats can differ slightly because the platforms are designed differently. LinkedIn's location field defaults to metro-area language ("San Francisco Bay Area" rather than "San Francisco, CA"), and that's fine — it's the platform norm. Your resume can be more specific at the city level. What matters is consistency in the underlying story: both should point to the same general geography, and neither should contradict the other in a way that prompts questions during screening.
How Verve AI Can Help You Prepare for Your Next Job Interview
Getting your resume header right gets you into the room. What happens in the room is a different problem — and the preparation gap there is usually not about knowing the right answers, but about delivering them under live pressure when the follow-up question wasn't on your prep list.
That's the structural problem Verve AI Interview Copilot is built to solve. It listens in real-time during your practice sessions, responds to what you actually say rather than a canned script, and surfaces the follow-up angles you hadn't thought to prepare for. If you blank on "tell me about a time you navigated a difficult stakeholder conversation," Verve AI Interview Copilot doesn't give you a template — it works with the actual memory you're trying to reconstruct and helps you build an answer that sounds lived-in rather than rehearsed. The difference is audible to any recruiter who's heard a thousand STAR answers in a row. Verve AI Interview Copilot stays invisible while it works, so the practice feels like the real thing rather than a coached performance.
The contact block gets you screened. Verve AI Interview Copilot helps you close.
Conclusion
The anxiety around the address on resume was never really about ATS algorithms or recruiter checklists. It was about not knowing which rule to follow when the rules kept changing. The answer turns out to be simpler than the myth suggested: give hiring teams a usable location signal, keep your home address off a document that circulates beyond your control, and don't add information that serves no one's practical interest.
Go audit your resume header right now. If it has a street address, delete it. If it has a zip code, delete that too. What should remain is your name, phone, email, city and state, and a LinkedIn URL if your profile is current. That's the complete contact block. Everything else was always dead weight.
Riley Patel
Interview Guidance
