6 min read
Your aunt's 1998 template still has a line for street, city, state, and ZIP. You paste your full home address because it looks official, then wonder why recruiters in another state never call back. You're not doing anything wrong. You're following a format that stopped matching how files get screened years ago.
The mismatch is simple. Modern US hiring runs on location for logistics, not correspondence. If you're applying across state lines, a street address won't fix the filter. A clear city line and an honest relocation note will. Check your resume for free after you trim the header. You're confirming the parser still reads your phone and email when the address shrinks to two words.
If you're also updating outreach, the cover letter generator helps you restate location intent without repeating a street line in the letter body.
Below: what belongs in the header, rare exceptions, and copy-paste lines for remote and relocation cases.
Quick Wins
- Replace street with City, State or a metro label tonight.
- Add Open to Remote or a relocation month if the posting cares about location.
- Re-export PDF and confirm phone and email still parse in the ATS preview.
What recruiters actually need from your location line
Recruiters scan for market fit, not ZIP codes. Austin, TX tells me whether commute or relocation is realistic. A street name does not change that decision and can create bias I don't want influencing a screen.
ATS parsers treat the contact block as name, phone, email, and sometimes location. A long address line can wrap awkwardly in the imported profile or push email onto a second line in the preview.
Before: Header lists 742 Maple Street, Portland, OR 97209.
After: Header lists Portland, OR (Open to Remote).
Privacy matters too. Resumes get forwarded, downloaded, and stored in vendor systems you never see. Street-level detail is unnecessary at the application stage.
Should you include your address on a resume? Fix the header in three moves
Step 1: Delete the street line
Open your master DOCX. Remove street and ZIP from the contact block. Keep name, phone, email, and one location line. If you're using a Canva or Word template with a footer address, move contact info into the body text.
Step 2: Pick the right location format
Onsite roles: City, State or Greater Metro Area. Remote roles: City, State (Open to Remote). Moving: Relocating to [City, State] in [Month Year].
Copy-paste block: contact header
Alex Rivera [email protected] | (503) 555-0142 Portland, OR (Open to Remote)
Before: Location buried in a footer the parser skips.
After: Location on line three in the main body, plain text, no table cell.
Step 3: Re-upload and spot-check parsing
Export a text-selectable PDF. Paste into a plain editor and confirm order: name, email, phone, location. If anything scrambles, rebuild the header as stacked lines, not a two-column table.
I've screened stacks of these in Greenhouse, and the file that wins lists location in plain text on line three, not buried in a footer the parser skips.
When a full address still belongs on the file
Follow explicit instructions. If the posting or portal says provide full residential address on the resume, do it. Government, federal contractor, and some security-cleared roles fall here.
Otherwise, wait. Many employers collect legal address later in a background-check portal, not from a PDF you uploaded on day one. Adding it early rarely speeds anything up and creates a duplicate record that can disagree with your later form.
International applicants sometimes need more detail for visa sponsorship paperwork. Even then, city and country often suffice on the resume itself, with full address reserved for forms that require it.
Location lines that backfire
Listing a fake local address when you're not there yet. Background checks and LinkedIn will contradict it. Use Relocating to [City] instead.
Hiding all location on remote postings. Many employers still filter by state for payroll. City, State (Open to Remote) keeps you searchable.
Using a suburb name recruiters won't filter on. Nearest major metro is clearer for ATS keyword filters and human skim.
Read how to tailor your resume for remote roles when the posting mixes onsite and distributed language.
Confirm the trimmed header still parses
Run HireFlow's free ATS resume checker after you change the contact block. You're checking that email and phone still land in the right fields when the address line shortens.
Use the free resume builder if your template keeps re-inserting a full address in a header region. Single-column body contact is easier to keep clean across exports.
What to do now
Should you include your address on a resume? For most US applications, the answer is no at street level. City and state, metro, Remote, or an honest relocation note is enough.
- Delete street and ZIP from tonight's export.
- Add relocation or remote language if the posting filters on location.
- Re-scan the file before your next batch of applications.
Open your master file, trim the header, then run a free ATS check so the next upload still reads your contact block cleanly.
Read more
Frequently asked questions
No for most corporate and tech applications. Recruiters need to know whether you're in the hiring market, not where to mail a letter. City and state, a metro label, or Remote is enough. A full street address adds privacy exposure when files move through ATS vendors and job boards, and it does not improve how Workday or Greenhouse parses your contact block.
List your city and state plus Open to Remote, or Remote if the posting is fully distributed. Some employers still filter by state for payroll and tax reasons, so hiding all location can backfire. If the posting says anywhere in the US, City, State (Open to Remote) is the safest one-line format.
Only when the application instructions ask for it explicitly, or when a government form requires a residential address at the resume stage. Federal, state, and some contractor roles are the common exceptions. If the posting does not mention a street address, default to city and state and provide the full address later in a secure portal.
Add a relocation note on the same line as location: Relocating to Denver, CO in May 2026. Put the target city in the header or summary so keyword filters and human reviewers see intent. Do not list a fake local address. Honest relocation language beats guessing what the recruiter wants to see.
