Refolk
10 min readMarkdown

Texas Postings Are Up to 15%. Only 59 of 419,977 Engineers Say Relocate

Dallas, Austin and Houston postings run 12 to 15% above 2020 while Seattle sits 30% below. Here's how to write a relocation line filters can match.

If you're job hunting from Seattle or San Francisco, job postings there are still about 30% below February 2020. Dallas, Austin and Houston are running 12 to 15% above that level, according to Indeed Hiring Lab and Glassdoor data published Nov. 18, 2026. Applying to the strong metros is the obvious move. The catch is that location filters can drop you as non-local before anyone reads your resume, and the city line on your resume is usually what sets them off.

Where postings have recovered, and where they haven't

Postings have recovered unevenly. Texas metros are 12 to 15% above pre-pandemic levels, New York and Los Angeles are about 15% below, and Seattle and San Francisco are about 30% below. That leaves a gap of roughly 42 to 45 percentage points between the strongest and weakest large metros.

MetricFigureSource
Dallas / Austin / Houston postings vs. Feb 2020+12% to +15%Indeed / Glassdoor
New York / LA postings vs. Feb 2020about −15%Indeed / Glassdoor
Seattle / SF postings vs. Feb 2020about −30%Indeed / Glassdoor
US software engineers and developers419,977Refolk's index
...with "relocate" in their headline59 (about 0.014%)Refolk's index

Measured more broadly, the market is getting better. Postings are above pre-pandemic levels in 299 of the 385 US metros analyzed. The share of local markets with more postings than a year earlier went from about 1 in 10 at the start of 2026 to 49% in September. Also in September, Indeed's Job Postings Index grew year over year for the first time since 2022.

Laura Ullrich, director of economic research at Indeed Hiring Lab, put it this way: "After years of very little movement, several metros are starting to turn the corner." The important word is several. The recovery is happening city by city, and the cities where most tech workers live are at the back of the line.

Why Seattle and San Francisco are still 30% down

The coastal tech metros are behind because software development postings are still down 20% or more from February 2020. Software also makes up nearly four times as large a share of postings in Seattle and San Francisco as it does nationally. A metro that depends on one shrinking category can only recover as fast as that category does.

That covers demand. Supply makes it worse. Through Aug. 18, layoff notices in King and other counties covered 9,027 workers, and 6,766 of them came from the information sector (reported by Axios). KUOW reported that software engineer openings saw the steepest drop, 56%. In October, Amazon's Washington WARN notice listed 121 roles, and 52 of them (43%) were software development engineers or applied scientists.

75%
Share of Seattle-area layoff-notice workers from the information sector

6,766 of 9,027 workers on notices in King and other counties through Aug. 18, 2026.

So both halves of the ratio are working against a Seattle engineer who only applies locally: fewer postings, and more people with the same resume chasing each one. There is some good news. Indeed says the September upturn came from software development, banking and engineering, which are the same fields that had been holding the index down. Waiting it out could work eventually. Applying out of state is the move you can make now.

Should you apply to Dallas, Austin, or Houston?

Apply out of state if you are senior and your experience matches what Texas employers are hiring for. If you are entry or mid-level, think harder, because those postings are shrinking everywhere. Seniority matters more than geography.

Senior-level postings are up 19.2% since January 2025, while entry-level and mid-level postings are each down about 4% (4 Corners Resources' 2027 outlook). Relocating means competing against a different set of people, but it doesn't create junior openings that aren't there. A mid-level engineer who moves to Dallas is still applying in a mid-level market that is contracting. If you're near the line, an earlier post on proving scope instead of years shows how to make a mid-level resume read as senior.

Applying out of state makes sense when most of these are true:

  • You're senior or above. That's where postings are growing.
  • Your work matches finance, insurance, or large-scale operations. That describes most of the Dallas employer base (more below).
  • You can name a month. "Sometime next year" doesn't count as a plan.
  • You'd take the job without a relocation package, or you've already worked out what a move would cost you.

If you want something more rigorous than a checklist, the Metro Target Score rates a city and tells you whether to move first, apply from where you are, or drop it.

Dallas is a finance engineering market, not "Texas tech"

Recruiting in Dallas is driven by banks and insurers, and consumer tech is a small part of it. These are the anchor employers:

  1. JPMorgan Chase: 12,000+ at its Plano campus.
  2. State Farm: 11,000+ in Richardson.
  3. Fidelity Investments: 6,000+ in Westlake.
  4. Goldman Sachs: roughly 4,600 already in Dallas, its largest US office outside New York, growing toward 5,000+ when a new campus opens in 2028.
  5. Morgan Stanley: more than $587 million for a permanent Dallas hub, with 3,800 employees planned by 2031.

Refolk's index points the same way. Out of the 59 US engineers whose headlines mention relocating, a sample of 25 profiles had 5 based in Texas (Dallas-Fort Worth, Dallas, Frisco, Melissa, Houston). Big banks came up again and again as their employers: JPMorganChase twice, plus Bank of America, Citi and Capital One. That sample is small, so read it as a direction, not a share.

This means a consumer-tech resume needs translating. A bullet about "growing weekly actives 30%" means less to a bank's platform team than one about uptime, audit trails, change control, or transaction volume. You're keeping the same work and describing it in terms the reader cares about. Refolk handles that translation: paste a JPMorgan or State Farm posting and you get your own history back, rewritten for reliability, compliance and scale, with nothing made up.

If Dallas finance doesn't suit your background, Austin is the other Texas market worth checking today.

How location filters drop you before a human reads

Applicant tracking systems and recruiter searches filter by location first. If your city line says Seattle or Remote, a search scoped to a radius around Dallas will never return you. A location filter is a search setting that limits results to candidates whose listed location sits inside a named city or ZIP-code radius.

The resume vendor ResumeXRays cites a 2025 recruiter survey in which 43.4% said they apply this filter, which makes it one of the most commonly used. The original survey couldn't be traced, so treat that number as directional. The mechanism doesn't depend on it, though. On hybrid roles, recruiters often filter by a ZIP-code radius around the office, and "Remote" doesn't register in those results. As an earlier post argued, writing "Remote" in your location line hides you from roles that want people in a seat.

A second filter shows up as a question on the form, something like "Are you currently located within 50 miles of Dallas?" Answer no without context and you can be auto-rejected. This is the same knockout question drop-down covered in an earlier post. Where the form has a follow-up, answer the relocation question directly with a date.

LinkedIn is the third filter, and it's where Refolk's index shows how open this lane is. Of 419,977 people in the US holding Software Engineer or Software Developer titles, only 59 mention relocating in their headline.

1 in 7,100
US software engineers who say "relocate" in their headline

59 of 419,977 in Refolk's index of professional profiles.

Here's the practical effect. A Dallas recruiter types "backend engineer" with the location set to Dallas-Fort Worth. A Seattle engineer who has been sending applications for weeks doesn't appear, because their profile names a city the recruiter isn't searching. From the engineer's side, that looks like silence: plenty of applications, no recruiter messages, and no idea which filter is responsible.

The flip side is that signaling a move is almost free differentiation. When only 1 in about 7,100 engineers does it, the ones who do stand out in exactly the searches that matter.

How to write your city line in all three places

Put the target city and a dated move everywhere your location appears: the resume header, the ATS location field, and LinkedIn. "Relocating to Dallas, TX (March 2027)" works better than "willing to relocate" because a filter can match the city and a recruiter can plan around the date.

Here's how each version of the line plays with a filter and a reader:

Location lineWhat a radius filter seesWhat a recruiter reads
Seattle, WASeattle, outside the radiusNon-local, would need relocation
RemoteNothing it can matchDoesn't want the office
Willing to relocateNo city to matchMaybe, someday, somewhere
Relocating to Dallas, TX (March 2027)DallasArriving on a known date

The four places to change it

  1. Resume header. Write the target city, state, and move month. Should you put your street address on your resume? No. City and state are all any filter or recruiter needs, and a street address only adds risk.
  2. ATS location field. If it's free text, write the target city plus the date. If it explicitly asks for your current address, give your real one and answer the relocation question with the same city and month that appear on your resume.
  3. LinkedIn location and headline. Set your job preferences to the target metro and add the move to the headline, for example "Backend Engineer | Relocating to Dallas, March 2027." Then check whether it's working. The profile findability log tracks weekly search appearances so you can tell whether to keep a headline change or revert it.
  4. Cover letter, first paragraph. Write one sentence covering the city, the month, and whether you need help with the move. The cover letter should say exactly what the resume header says. Refolk drafts the cover letter from the same history and posting it used for the resume, so the relocation sentence and the header can't drift apart between applications.

These four have to agree. A recruiter who sees Dallas on the resume, Seattle on LinkedIn, and "Remote" in the ATS field will read it as uncertainty, and an uncertain candidate is easy to pass over.

What to leave out

  • A friend's or relative's address. People in Glassdoor threads warn that recruiters react badly when a location turns out to be misleading, and it comes out the first time a screener asks "so you're in Plano?"
  • "Remote" on a hybrid posting. It won't match the office radius and it reads as resistance to coming in.
  • "Open to relocation" with no city. A filter can't match it and a recruiter can't act on it.
  • Asking for a relocation package in your first message. Raise it once there's an offer. The relocation lump sum teardown walks through pricing one to net cash.

FAQ

Should I put my address on my resume when applying out of state?

No. List city and state only, and when you're relocating, make that your target city with a move month, such as "Relocating to Dallas, TX (March 2027)." Street addresses don't help any filter. They also give away your current location in a way that can cause an early rejection, and they expose personal data for no benefit. If an application form explicitly asks for your current address, give your real one and use the relocation question to state your plan.

Is "willing to relocate" on a resume enough?

Rarely. Location filters match city names and ZIP radii, and "willing to relocate" contains neither, so it doesn't help you in a Dallas-scoped search. A recruiter reading it also can't tell when you'd start. Name the city and the month. Only 59 of 419,977 US software engineers in Refolk's index mention relocating in their headline, so a specific, dated line stands out.

What are the best cities for tech jobs in 2026?

Measured by postings recovery, Dallas, Austin and Houston lead the large metros at 12 to 15% above February 2020, according to Indeed Hiring Lab and Glassdoor. Seattle and San Francisco trail at about 30% below. Keep in mind that software development postings are down 20% or more from February 2020, so a Texas move does the most for senior engineers whose work fits finance, insurance, and large-scale operations.

The data behind this

Put this to work

Paste your career in once. Every application after that is written for you.

Drop a resume or a LinkedIn URL. I rank the live openings against it, rewrite the resume and write a cover letter for the best of them, and fill in the employer's form when you press the button. You read, you decide what goes out.

  1. 01Drop your resume

    A PDF or a LinkedIn URL. About a minute, once.

  2. 02I rank the openings

    Every weekday morning, the live catalog scored against your history. Up to 20 worth your time, not two hundred links.

  3. 03Each one is written up

    Resume rewritten for the posting, a cover letter, a fit score. Press send, or let me fill in the form.

  • New matches ranked and written before you are up.
  • Every bullet stays inside what your history supports. Nothing invented.
  • Queued, submitted, interviewing, offer: one screen, not a spreadsheet.

Free, no card. Up to 25 applications sent a week, and nothing is sent until you say so.

Keep reading