Guide 3 min read

Should you put your address on a resume?

Do not put your full street address on a resume. List city and state or city and country: Austin, TX. That satisfies recruiters checking location and time zone, feeds ATS location filters, and avoids handing your home address to every database your resume lands in. Add relocation or work-authorization notes only when they preempt a real doubt.

Updated September 1, 2026

Why the street address died

The full address was a mailing artifact — offers and rejections once arrived by post. Nothing in a modern hiring pipeline mails you anything until after an offer, at which point HR collects your address through a form. On the resume itself, the street and number add zero screening information while adding real costs: your home address sits in ATS databases, recruiter exports, and forwarded PDFs indefinitely, with security and privacy implications you cannot retract.

There is also a subtle bias surface. A street address encodes neighborhood, and commute-distance judgments happen informally — a recruiter deciding you are probably too far away is a decision you never get to argue with. City-level location gives them what the process legitimately needs and nothing it does not.

What to write instead

One fragment in your contact line: Austin, TX, or Dubai, UAE for international applications, alongside phone, email, and LinkedIn. This is not decoration — ATS location filters and recruiter searches genuinely run on it, and a resume with no location at all can drop out of geo-filtered searches or read as evasive. City plus region is the minimum that keeps you findable.

For remote roles, location still matters for time zone and employment law, so list it, optionally with a clarifier: Lisbon, Portugal, remote, UTC+0. If you are targeting a market you have not moved to yet, say so explicitly — relocating to London, March 2027 — because otherwise the mismatch between your location and the job's reads as an application mistake rather than a plan.

Relocation and authorization notes

Add a clarifying phrase only when the reader would otherwise assume wrongly. Open to relocation matters when applying out-of-market; authorized to work in the US without sponsorship matters when your history suggests otherwise; omit both when they answer questions nobody would ask. Every extra clause in the contact line dilutes the four things that must be instantly findable: name, phone, email, location.

Never fake a local address to game geo-filters. The lie surfaces at scheduling — interviews, notice periods, and onboarding paperwork all reference where you actually are — and it converts a solvable logistics question into a credibility problem. If distance is the objection, the honest relocation line plus a strong resume is the only play that survives contact with the process.

Frequently asked questions

Can leaving my address off hurt my application?

Leaving off the street address, no. Leaving off location entirely can — geo-filtered recruiter searches may skip you and readers wonder about time zone. City and state or city and country is the reliable middle ground.

What if I am applying to jobs in another city?

State it directly: current city plus relocating to target city and a date if you have one. Ambiguity gets you filtered as too far; a fake local address collapses at scheduling. A plan stated plainly is the credible option.

Should remote applicants list a location?

Yes. Remote employers still screen on time zone, tax jurisdiction, and legal ability to hire in your country. City and country, optionally with UTC offset, answers those questions without giving away a street address.


The free scorer checks your contact block for what recruiters and parsers need — and flags what should not be there.

Apply this to your role
More guides
How far back should a resume go?
The 10–15 year rule for resume work history, when older experience earns its place, and how to compress ancient roles without creating fake gaps.
Best fonts for a resume (ATS-safe and readable)
The fonts that survive ATS parsing and six-second recruiter scans: safe choices, sizes, and the decorative fonts that quietly cost you interviews.
Resume margins and spacing: the settings that scan well
Margin sizes, line spacing, and white-space rules that keep a dense resume scannable — and the cramming habits that make recruiters stop reading.
What to name your resume file
The resume file-name format recruiters prefer, why Resume_Final_v3.pdf hurts you, and how file names behave inside ATS databases and inboxes.
Resume as PDF or Word: which file format to send
PDF vs DOCX for resumes: what modern ATS parsers handle, when a posting genuinely needs Word, and the export mistakes that break both formats.
How many bullet points per job on a resume
The recency-weighted rule for resume bullets: how many each role deserves, why old jobs get fewer, and what to cut when a role has too many.
Resume action verbs that actually work
How to choose resume action verbs by function, the inflated verbs recruiters discount, and why the noun and number after the verb matter more.
Resume summary vs objective: which one to use
The difference between a resume summary and an objective, why summaries won, and the few cases where an objective line still earns its space.
How many skills should you list on a resume?
The right size for a resume skills section, how to group and order skills, and why a 30-skill wall reads as noise to recruiters and parsers alike.