Refolk
10 min readMarkdown

Remote Fell to 14%. Writing 'Remote' Hides You From the Other 86%

Remote tech jobs hit a record-low 14% in 2026. Here's what to put in your resume location line, ATS form, and cover letter so geography doesn't screen you out.

If you've been remote for years and the listings suddenly look thin, you're reading them correctly: only 14% of open tech roles now offer a remote option, the lowest on record, according to Lenny Rachitsky's State of the Tech Job Market report. The bigger risk is what happens when you apply to the other 86%. The city on your resume, or the missing city, can get you rejected before anyone reads your experience.

How far did remote tech jobs fall in 2026?

Remote options dropped from 21% of open tech roles in late 2022 to 14% in late 2026, and engineering fell the hardest, from 25% to 14%. The report draws on TrueUp, which tracks openings at more than 9,000 tech companies, and Live Data Technologies, which tracks hires, departures and promotions for 124 million US professionals.

The pace is the part people miss. In March 2026, Lenny reported that 19% of engineering roles had a remote option. Eight months later the figure was 14%. The previous 6-point drop took more than three years.

RoleLate 2022 remote shareMarch 2026Late 2026
All tech roles21%not reported14%
Engineering25%19%14%
Design34%not reported19%
Product managementnot reported25%21%
14%
Share of open tech roles offering a remote option, late 2026

A record low in TrueUp and Live Data Technologies data, down from 21% in late 2022.

Hiring is also concentrating in one place. There are now more open PM, engineering and design roles based in the Bay Area than remote roles anywhere in the world. Four years ago remote led by almost 2 to 1. One write-up of the charts puts it at 21.8% of PM/eng/design openings in the Bay Area versus 14.5% remote, and 14.9% of all open tech roles in the Bay Area, also a record.

What it means in practice: most of the roles you could get now come with an office address. Some of them sit in a metro you don't live in.

Why does "Remote" on a resume get you screened out?

Recruiters search by city or ZIP code radius, and a resume that says "Remote" instead of a city doesn't appear in those searches. Nobody rejects you. You just never show up in the results.

An applicant tracking system (ATS) is the software, such as Greenhouse or Lever, that stores your application and turns its contents into fields a recruiter can filter. Location is one of those fields, and 43.4% of recruiters use a location filter. For hybrid roles, the usual filter is a radius around the office ZIP code. "Remote" isn't a place, so it can't fall inside a radius.

Recruiters also filter on three separate things:

  • Where you live now.
  • Work arrangement. Remote, hybrid or onsite.
  • Relocation willingness.

A knockout question is a form question that rejects you automatically based on your answer. Work authorization, minimum years of experience and location are the common ones, and they run before a human reads any resume. One ATS guide says it plainly: the resume alone rarely overrides a hard location filter.

A hybrid recruiter searches for a ZIP code. "Remote" isn't a ZIP code, so you never show up.

What does Refolk's index show about how remote candidates list location?

Very few engineers put "remote" in their headline, and the ones who do usually drop their city as well. That's the habit that hides them. In Refolk's index of professional profiles, 352,694 US profiles hold the title "Software Engineer." Only 233 of them have "remote" in the headline, roughly 1 in 1,514.

1 in 1,514
US software engineers in Refolk's index with "remote" in their headline

233 of 352,694 profiles, so advertising remote is rare even among people who want it.

The location fields are more telling. A 25-profile sample from each group shows a pattern. The samples are small, so read the percentages as a direction, not as precise measurements.

Group (Refolk's index)Total US profilesSample in Bay Area metrosSample listing only "United States"
Software Engineers352,69432% (8/25)4% (1/25)
Software Engineers with "remote" in headline2334% (1/25)36% (9/25)
All roles with "open to relocation" in headline3,1204% (1/25, San Jose)12% (3/25)

In the sample, engineers who advertise remote were about 9x as likely as engineers overall to list only "United States" as their location. That makes sense from their side: if you'll work from anywhere, a city looks irrelevant. A recruiter running a radius search around a San Francisco office ZIP code sees it differently. A profile with no city can't be found in that search, and searches like it now cover most of the openings.

The relocation number is just as low. Across every role in the US, only 3,120 profiles in Refolk's index say "open to relocation" in the headline. Candidates who would move rarely say so openly, so a clear relocation line puts you in a small group.

Is remote still the safer bet in 2026?

No. Remote is the most crowded option in the market. In September 2025, fully remote roles were about 8% of paid US postings on LinkedIn but received 35% of applications, roughly 4x their share. Forbes reported a similar split: about 9% of US postings in July offered remote work, and those listings drew 37% of applications.

The reason is simple. A remote posting is open to every qualified person in the country, and everyone who wants remote is applying to the same shrinking set of listings. A hybrid role in a major metro only competes for people who already live there or are willing to move. It can have far fewer serious applicants, even after you count the commute or the move.

That's why remote-only candidates often send application after application and hear nothing. The silence doesn't mean their experience is weak. They're competing in the most crowded slice of the market while invisible in the slice that holds most of the openings.

Remote-first companies still exist. Coinbase operates remote-first, and Shopify stayed remote. They're a short list, though, and the 35% application share is a reason to apply to them alongside hybrid roles, not instead of them.

Should engineers, designers, and PMs play this differently?

Yes. The decline isn't the same across roles, so the advice shouldn't be either. Engineering went from 19% to 14% remote in eight months, while about one in five PM roles (21%) still offers remote. "Hold out for remote" is a defensible plan for one of those groups and a costly one for the other.

  • Engineers. Remote fell from 25% to 14%, and it's falling fastest here. Treat hybrid as your main market. Add a real city to every application and consider the Bay Area seriously, since that's where PM/eng/design openings now outnumber global remote ones.
  • Designers. Remote fell from 34% to 19%. That's the biggest drop in percentage points, but the share is still higher than engineering. Split your applications: remote where your portfolio is strongest, hybrid in your own metro for everything else.
  • Product managers. About one in five roles is still remote, though that's near record lows. Remote-first applications are still reasonable. Put your city on the resume anyway so hybrid searches can find you.
  • Analysts and operators. The report focuses on PM, eng and design, so there's no remote share for these roles. The same filtering applies, though: if a hybrid team searches by ZIP, you need a city that matches.

Should I put my location on my resume?

Yes. Put a real city and state on your resume, every time, even if you only want remote work. A city puts you inside radius searches. Leaving it off removes you from them, and "Remote" or "United States" fixes nothing.

This matters more now because office rules often depend on distance. Microsoft began requiring three days on site in February 2026 for employees within 50 miles of an office. Dell expects anyone within about an hour of an office to be on site five days a week. Instagram goes further: it has required US employees in the office five days a week since February 2, 2026. Your listed city tells the recruiter which rule applies to you, and a bare "Remote" leaves them to guess.

Five location lines, by situation

  1. You live in the metro. Oakland, CA. Nothing else is needed.
  2. You'll relocate for this role. Denver, CO · Relocating to SF Bay Area, available Q1. This is how to say "open to relocation" on a resume so it reads as a plan rather than a maybe.
  3. You live within commuting range but not in the city. Sacramento, CA (commutable to SF, hybrid). Use this only if you'd actually do the commute.
  4. You want remote but would take hybrid locally. Portland, OR · Remote or hybrid in Portland.
  5. Remote-first company only. Raleigh, NC · Remote (US, Eastern Time). Keep the city. The time zone answers the question the recruiter actually has.

Don't claim a city you don't live in and don't promise a move you won't make. Both come out in the first recruiter call.

You also won't use the same line for every application. The Bay Area hybrid role gets line 2 and the Coinbase application gets line 5. Retyping the header for each job is easy to forget, and Refolk handles it for you: paste the posting and you get your own resume back with the header and bullets tailored to that role's location and arrangement.

Applying to hybrid jobs out of state: how do you get past the form?

Make the form answers, your resume header and your LinkedIn location say the same thing. The form is checked first. If you tick "not within commuting distance" on a knockout question, the relocation line on your resume never gets read.

For an out-of-state hybrid application, go in this order:

  1. Read the form before you write anything. Location and relocation questions are often knockouts, so find them before you upload a resume.
  2. Answer the relocation question honestly and specifically. If there's a free-text box, use the same sentence as your resume: "Relocating to SF Bay Area, available Q1."
  3. Match the resume header to that answer. Same city, same timing, same wording.
  4. Update your LinkedIn location or headline. A recruiter who checks your profile and sees only "United States" may read the resume as aspirational.
  5. Put the logistics in the cover letter's first paragraph. One sentence: where you are, when you'll be local, and that you're planning around the role's on-site schedule. Don't wait until the closing paragraph.

The cover letter matters because it's the only place you can explain the move in your own words: why this city, why now, and that it's already planned. Refolk drafts the letter from the same posting and your own history, with the location line first, so it matches the header you send. And before you commit to an out-of-state pitch, Refolk's fit score shows how well your experience matches the posting, so you can save the relocation effort for roles where you're a strong fit.

FAQ

Should I put "Remote" as my location on my resume?

Not by itself. "Remote" doesn't match the city or ZIP-radius searches that hybrid recruiters run, and with only 14% of tech roles offering a remote option, those searches cover most of the market. Write your city and state, then add a remote preference if you have one, for example Raleigh, NC · Remote (US, Eastern Time).

How do I write "open to relocation" on a resume without sounding vague?

Name the destination and a date. "Open to relocation" alone doesn't tell the recruiter much. "Relocating to SF Bay Area, available Q1" tells them which office rule applies and when you can start. Only 3,120 US profiles in Refolk's index say "open to relocation" in the headline at all, so a specific version is rare.

Is it worth applying to hybrid jobs out of state?

Often, yes, especially for engineers. Remote engineering roles fell from 25% to 14%, and the Bay Area now has more PM/eng/design openings than remote roles worldwide. Remote listings draw about 4x their share of applications, so a hybrid role you're willing to move for may have a much smaller applicant pool. Just make sure your form answers say you'll relocate.

Are remote tech jobs coming back?

Nothing in the data points that way yet. Engineering fell 5 points in about eight months, after the previous 6 points took more than three years, and companies like Microsoft, Dell and Instagram have tightened on-site rules. Remote-first employers such as Coinbase and Shopify are still around, so keep applying to them, but don't make them your whole search.

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