getnewresume
Practical Playbooks · 13 min read

How to Write a Resume for an Out-of-State Job (Relocation Guide 2026)

Why recruiters default to local applicants, how ATS systems filter by ZIP, and 4 placement strategies for relocating candidates — Census + Jobscan data.

How to Write a Resume for an Out-of-State Job (Relocation Guide 2026) illustration

The hardest rejections are the ones you never see. You apply to a job in a different state, never hear back, and assume your experience wasn’t strong enough. Often that isn’t what happened. Your resume was screened out at the location step before a human ever read it — by an ATS filter, by a recruiter sorting candidates by ZIP, or by the four-second scan that decides "this candidate is 1,400 miles away, next."

Location is one of the four hardest knockout filters in modern hiring (alongside work authorization, license, and minimum-years-of-experience). Unlike the others, you can fix it. This is a playbook, not a tips list. We’ll walk through the data on why recruiters default to local, the ATS mechanics most candidates never see, four placement strategies for "willing to relocate," an honesty firewall on borrowed local addresses, three illustrative before/after pairs, and the failure modes to avoid.

43.4%

Of recruiters who use ATS filters use location as one of their filtering criteria. Out-of-state resumes that don’t signal local intent are filtered out before review.

Source: Jobscan, State of the Job Search 2025 (n=384 recruiters)

2.1%

Of Americans moved to a different state in 2024 — down from 2.3% in 2023. Cross-state moves are rare, which is exactly why recruiters discount distant applicants by default.

Source: U.S. Census Bureau, ACS 1-Year Estimates 2024

58%

Of companies had at least one employee decline a relocation in 2024. The withdrawal-risk number is the proxy for why recruiters discount distant candidates on first pass.

Source: Atlas Van Lines, 59th Annual Corporate Relocation Survey (n=558)

Why Recruiters Default to Local Applicants

Hiring is risk management. From a recruiter’s seat, an out-of-state applicant introduces several risks that a local applicant doesn’t — and most of them have nothing to do with whether you can do the job.

The first is time-to-start drift. A local hire can typically start sooner than someone who needs to pack up a household, end a lease, and move. For a role that’s already been open for weeks, that delay is a meaningful cost in the recruiter’s calculation. The second is withdrawal risk. Atlas Van Lines’ 59th Annual Corporate Relocation Survey, fielded with 558 corporate decision-makers between December 3, 2024 and January 15, 2025, found that 58% of companies had at least one employee decline a relocation in 2024. Recruiters who’ve watched a candidate drop out late in the process discount the next distant candidate accordingly.

The third is relocation budget. Even when companies offer assistance, those packages cost real money. A candidate who needs relocation support competes against a local who needs none. The fourth is interview logistics — onsite loops are harder, slower, and more expensive to coordinate across time zones. The fifth is retention perception. Whether or not the data says relocators churn faster in year one, the perception is in the room. That perception is what we’re working against.

None of these are about you. They’re about a recruiter optimizing for fewer dropouts and faster fills. That’s the surface area you’re working with — and it’s why a resume that signals "I am effectively a local applicant" outperforms one that signals "I would consider moving."

What ATS Systems Actually Do With Your Location

Before a recruiter sees your resume, the ATS has already classified you. Most modern systems — Workday, Greenhouse, Lever, iCIMS — extract a structured location string from your header (city, state, sometimes ZIP) and write it to the candidate record. Recruiters then filter the candidate pool from a dashboard. Per Jobscan’s State of the Job Search 2025 (n=384 recruiters surveyed February–March 2025), location is one of the top filters used by recruiters who run ATS searches — 43.4% of respondents named it as one of their criteria.

What happens to your location string

STEP 01

Parse

ATS extracts city/state from your header. Missing or ambiguous values default to the IP-address geocode of where you applied — often a coffee shop or VPN exit.

STEP 02

Normalize

"NYC", "New York, NY", and "10001" all collapse to the same metro tag. "Open to relocate" usually does not — most parsers can't structure free-text intent.

STEP 03

Filter

Recruiters apply a radius filter (e.g., "within 50 miles of Austin, TX"). Your record is in or out — there is no middle setting on most dashboards.

STEP 04

Rank

Within the filtered pool, location scoring is binary. Distance becomes a tiebreaker only after skills and years-of-experience criteria.

The practical implication: if you write "Phoenix, AZ" in your header and you’re applying to an Austin role, you almost certainly fail the radius filter — even if everything else matches perfectly. The job of the four placement strategies below is to keep you inside the filter without misrepresenting where you live.

The Four Placement Strategies

Pick exactly one. Mixing strategies — for example, listing the destination city in your header but then asking about relocation in your cover letter — produces noise, not clarity. Choose based on your relocation reality, not what reads best.

Strategy A · Header swap

Update your header to the destination city

Use your destination city and state in the header — but only if you have a firm move date and a real address arriving (signed lease, family home, temporary corporate housing).

WHEN: Firm move within 30–60 days. You will have a verifiable local address before any background check.

HEADER:

Tomás Reyes Austin, TX · (512) 555-0140 · tomas.reyes@email.com
Strategy B · Hybrid

Current city + relocating-by line

Keep your current city (so the parser still has a real value) and add an explicit relocation line. The ATS reads two location signals — recruiters read your intent.

WHEN: Move planned but not yet executed. You want the destination ATS to surface you, but you cannot claim a local address yet.

HEADER:

Astrid Lindholm Boston, MA · Relocating to Denver, CO · April 2026 (617) 555-0119 · astrid.lindholm@email.com
Strategy C · Summary

One sentence in the professional summary

Lead the summary with your value, then close it with a relocation statement that names the city, names the timeline, and names who pays for the move.

WHEN: Header is already crowded, or you are applying to multiple cities and do not want to rewrite the header for each.

SUMMARY (last line):

Relocating to the Denver metro by Q2 2026 at my own expense; available to start within two weeks of an offer.
Strategy D · Cover letter

One paragraph, not one parenthetical

Keep the resume location-neutral and put the relocation context in the cover letter. Best when the role is sensitive to address signals (federal, regulated industries) or when you want the cover letter to do work the resume cannot.

WHEN: Application requires a cover letter, or you want to explain the move (family, partner role, return to a region you grew up in).

COVER LETTER OPENER:

I am writing from Boston, where I am wrapping up a four-year senior analyst role; I will be relocating to Denver in April with no employer assistance required, and I am targeting [Company] specifically because…

The selection rule is straightforward. Strategy A only works if the move is real and imminent — a signed lease, family already at the destination, or a confirmed temporary corporate housing arrangement that survives a background check. Strategy B is the most common and the most underrated; it gives the ATS two valid location signals and the recruiter a clear timeline. Strategy C is for candidates running parallel searches across cities who don’t want a different header per application. Strategy D is the move when the cover letter needs to do the explaining the resume can’t.

The Honesty Firewall: What's Defensible, What Isn't

Every relocation playbook eventually meets the same temptation: borrow a friend’s local address, list it in the header, sort out the move later. Sometimes a recruiter even suggests it. Here is the line.

Defensible

An address you will actually use

A signed lease, a family member’s home where you will live during transition, or temporary corporate housing tied to a confirmed offer. The address has to survive a background check and an offer-letter mailing without ambiguity.

Risky

A friend’s address with no plan to move there

If a recruiter asks "are you currently living at this address?" and the honest answer is no, you have put yourself in the same trust posture as someone who lied about a credential. This blows up at offer stage, not at application stage — which is the worst time.

Do not

A fabricated address you have no claim to

Mail-drop services, virtual offices presented as residences, or fully invented addresses. Background-check companies cross-reference address history against credit and utility records; a fabricated address breaks the trust contract and creates real legal exposure during E-Verify or I-9 reconciliation.

The federal frame is straightforward: under EEOC guidance, address questions are not inherently discriminatory, but they must be applied uniformly and not used as proxies for protected characteristics. From the candidate side, the rule is simpler: every fact on your resume must be true on the day a background check is run. If it isn’t, withdraw the claim or reframe it (Strategies B, C, or D above) instead of doubling down. The cost of being caught isn’t a recruiter rolling their eyes at the application stage — it’s a withdrawn offer at I-9 reconciliation, after weeks of mutual investment.

The "Apply Anyway" Templates: Three Before/After Pairs

Three illustrative scenarios using fresh fictional names and roles. Each shows the resume signal a recruiter sees in the first three seconds. Names, employers, and details are illustrative — the structural changes are the point.

Example 01 · Strategy A · Tomás Reyes — Phoenix → AustinSelf-funded · firm date

Before — Phoenix header, vague intent

Tomás Reyes
Phoenix, AZ · (602) 555-0188 · tomas.reyes@email.com
linkedin.com/in/tomasreyes

SUMMARY
Senior Product Marketing Manager with 8 years of B2B SaaS experience. Open to opportunities anywhere in the U.S.

ATS classifies as Phoenix-based; "anywhere in the U.S." reads as a flag, not a commitment. Auto-filtered out of Austin radius searches.

After — destination header, scope-forward summary

Tomás Reyes
Austin, TX · (512) 555-0140 · tomas.reyes@email.com
linkedin.com/in/tomasreyes

SUMMARY
Senior Product Marketing Manager with 8 years of B2B SaaS experience launching pricing pages, partner programs, and developer GTM motions for Series B–D startups.

Header reflects new address. Lease + partner transfer + own move budget all back the claim. Resume passes Austin radius filter on first pass.

Example 02 · Strategy B · Astrid Lindholm — Boston → DenverPlanned move · self-funded

Before — generic relocation flag

Astrid Lindholm
Boston, MA · (617) 555-0119 · astrid.lindholm@email.com

SUMMARY
SOC analyst with 5 years of incident response experience. Willing to relocate.

"Willing to relocate" is generic and gets discounted. Recruiters reading this in Denver assume Boston preference and pass.

After — hybrid header, destination + date + cost

Astrid Lindholm
Boston, MA · Relocating to Denver, CO · April 2026
(617) 555-0119 · astrid.lindholm@email.com

SUMMARY
SOC analyst with 5 years of incident response experience across financial services and healthcare verticals. Self-funded relocation to Denver in April; available to start within two weeks of offer acceptance.

ATS tags both Boston and Denver. Recruiters see a destination, a date, and the candidate covering the move. No ambiguity about commitment.

Example 03 · Strategy A + cover letter context · Ekene Onyemachi — Atlanta-rooted, Seattle-residentAlready in temp local housing

Before — competing location signals

Ekene Onyemachi
Atlanta, GA · (404) 555-0167 · ekene.onyemachi@email.com

SUMMARY
Senior Data Engineer · Atlanta-based · Currently on contract in Seattle through May 2026.

Atlanta header + "currently in Seattle" creates two competing signals. Seattle ATS treats as out-of-state; Seattle recruiters get confused about commitment.

After — Seattle header, contract context disclosed

Ekene Onyemachi
Seattle, WA · (404) 555-0167 · ekene.onyemachi@email.com

SUMMARY
Senior Data Engineer with 7 years building real-time pipelines on AWS and GCP. Currently in Seattle on a 12-month contract through May 2026; targeting permanent roles in the Seattle metro and prepared to start without relocation costs.

Seattle is the truthful current address. Cover letter discloses contract context. Recruiters read this as a low-friction conversion, not a relocation gamble.

Three Failure Modes to Avoid

Failure 01

Vague "open to relocation anywhere"

What it looks like: A blanket "willing to relocate" line with no destination, no timeline, and no statement on cost. Reads as desperation rather than commitment, and ATS systems can't filter "anywhere" into any specific radius.

Why it fails: Recruiters interpret blanket relocation as “I’d take any job” — which signals the opposite of the targeted, role-specific candidate they’re trying to find. Pick a city, name a date, name who pays.

Failure 02

Hiding location entirely

What it looks like: Removing city and state from the header to "let recruiters ask." ATS systems then either default to your IP geocode (often a coffee shop or VPN exit) or kick the record into a low-priority bucket because the location field is null.

Why it fails: A missing location is treated as “unknown candidate” by most ATS dashboards. You don’t avoid the filter; you fail it silently. Always provide a real location string, even if you pair it with a relocation line.

Failure 03

Misrepresenting a local address

What it looks like: Listing a friend’s address, a P.O. box presented as a residence, or a virtual-office mailing service to fake local status — with no actual plan to move there.

Why it fails: This surfaces at the worst possible time, during the background check or I-9 reconciliation, when you’ve already invested in interviews and the company has already invested in evaluating you. Mutual sunk cost makes the unwinding ugly. Use Strategy B (hybrid) or D (cover letter) instead — both are honest and both work.

The recruiter doesn’t reject your resume because you’re far away. The filter rejects your resume because you read as far away — and the filter runs before the recruiter ever opens it.

How GetNewResume helps

Tailoring an out-of-state application is what our pipeline was built for.

The hardest part of relocating isn’t writing one resume — it’s writing twelve, each tuned to a different city, a different ATS, and a different relocation framing. Paste the job description, paste your resume, and the tool reads the location signals in the JD and adjusts the header, summary, and keyword density so each version passes the destination radius filter without you rebuilding from scratch.

AI Tailoring Pipeline

Detects city/state references in the job description and produces a header and summary aligned to the destination metro, with change tracking so you see every word that moved. Built for the relocator who needs the location signal to read as a fit.

Cover Letter Generator

The strategy step asks for relocation context — destination, timeline, who pays — and produces a Strategy D opener that reads as committed, not desperate. The cover letter does the work the resume cannot.

ATS Score Checker

A 0–100 match score with keyword audit and recommendations against any pasted JD. Confirms that the location keywords in the listing actually appear in your resume before you submit, so you know whether the radius filter will pick you up.

When to Skip Relocation Framing Entirely

Not every job needs a relocation line, and adding one to a fully remote posting is a small act of self-sabotage. If the job description says "remote, U.S.," "distributed," or "anywhere in the continental U.S.," location framing creates friction where none existed. The recruiter doesn’t care where you live; the ATS filter is set to a country, not a city. Adding "willing to relocate to anywhere your hub is" tells the recruiter you didn’t read the posting carefully.

The exception is hybrid roles dressed up as remote. If the JD says "remote, with quarterly travel to HQ" or "remote-flexible with monthly in-office days," the location filter is still on — just at a wider radius. In those cases, a Strategy C (one summary line) note about your willingness to be in-office on a defined cadence is useful. Otherwise, leave relocation language out of remote applications entirely. Your job is to read the posting accurately, not to import distance into a job that doesn’t have it.

Out-of-state job hunting feels punishing because the rejection comes before the conversation. You don’t get a no — you get nothing, which is harder to learn from. The fix isn’t a stronger resume in the abstract; it’s a resume that survives the location step before it ever reaches a recruiter’s screen.

The four strategies above cover the major relocation realities: a firm move (A), a planned move (B), a multi-city search (C), and a sensitive context (D). Pick the one that matches your situation. Be specific about the city, the date, and who pays. Avoid the failure modes — vague language, missing locations, and dishonest addresses. Then let the rest of your resume do the work it was meant to do.

Relocation is a signaling problem, not a worth problem. Most recruiters will give you the benefit of the doubt if you give them the information they need to do that. Make it easy.

Sources & References

  1. 1.Jobscan — "The State of the Job Search 2025." Source for: 99.7% of recruiters surveyed use ATS filters; 43.4% use location as a filtering criterion. Methodology: 384 recruiters surveyed February–March 2025. Other figures from the same report: 76.4% filter by skills, 59.7% by educational background, 55.3% by job title.
  2. 2.U.S. Census Bureau — "2024 State-to-State Migration Flows Statistics Now Available" (press release, 2026). Source for: 2.1% of Americans moved to a different state in 2024 (down from 2.3% in 2023); 11.8% of the population moved at any distance in 2024. Based on the American Community Survey 1-Year Estimates 2024.
  3. 3.U.S. Census Bureau — "Why People Move" (Census story, September 2023, with subsequent CPS ASEC updates). Background reading on the four general categories of reasons-for-moving in the Current Population Survey ASEC (housing-related, family-related, employment-related, other) and how the breakdown has shifted across recent years.
  4. 4.U.S. Census Bureau — Migration / Geographic Mobility data and tables hub (American Community Survey).
  5. 5.Atlas Van Lines — "59th Annual Corporate Relocation Survey: Family, Flexibility and the Economy Are Driving Relocation Decisions." Source for: 58% of companies had at least one employee decline a relocation in 2024; only 7% of declined relocations were due to insufficient financial support (down 10 points from 2023); top reasons employees declined included family obligations and housing/mortgage concerns. Methodology: 558 corporate decision-makers, fielded December 3, 2024 – January 15, 2025.
  6. 6.Atlas Van Lines — Corporate Relocation Survey: Employees Declining Relocation (data resource page).
  7. 7.Robert Half — "62 Percent Of Workers Would Relocate For A Job, Survey Finds" (press release, January 15, 2019). Source for the historical baseline on relocation willingness. Methodology: more than 2,800 U.S. workers 18 years of age or older employed in office environments, and more than 2,800 senior managers at companies with 20+ employees in 28 major U.S. cities. Conducted by independent research firms.
  8. 8.U.S. Equal Employment Opportunity Commission — "Prohibited Employment Policies / Practices." Source for: pre-employment questions must be applied uniformly and cannot be used as proxies for protected characteristics under Title VII, the ADA, the ADEA, and related statutes.
  9. 9.Indeed Hiring Lab — labor market and metro hiring data portal. Background reading on cross-metro hiring patterns and the local-vs-distant applicant economics.
  10. 10.Jobscan — "Should You Put Your Address on Your Resume in 2024?" Editorial context on ATS location parsing and the practical implications of the address field on the resume header.

Ready to stop sending the same resume everywhere? Get New Resume uses AI to tailor your real experience to any job description — with full change tracking so you always know what was adjusted and why. No fabrication. Just translation.

More articles

Want to go deeper?

Browse all articles