If your search filter is set to "Remote" and your inbox is quiet, that's not just bad luck. Huntr's Q3 2026 Job Search Trends Report found remote-only applications got interviews 3.4% of the time, against 5.3% for hybrid-only and 5.3% for onsite-only. Remote has come in last every quarter this year. The fix costs you very little flexibility. It starts with the one line most remote seekers deleted from their resume: their city.
Are remote jobs harder to get?
Yes. Across 2026, remote-only applications have converted to interviews at the lowest rate of any work arrangement, and it isn't close. Huntr's tracked applications show the same pattern in all three quarters reported so far:
- Q1 2026: remote-only converted at 3.63%, 37% lower than onsite-only.
- Q2 2026: 6.07% of hybrid-only applications and 5.86% of onsite-only reached an interview, against 3.53% of remote-only.
- Q3 2026: remote-only 3.4%, hybrid-only and onsite-only 5.3% each.
The strongest version of the stat is the one that holds the applicant constant. Among 6,793 job seekers, the same people got interviews on 5.5% of their hybrid-only or onsite-only applications and 3.4% of their remote-only ones. So it's not just that weaker candidates pile into remote listings. One person with one resume gets fewer callbacks the moment the job says "remote."
Same people, same resumes. The work arrangement alone moved the outcome. (Huntr, Q3 2026)
Run the numbers and you can see the cost. At 3.4%, five interviews take roughly 147 applications. At 5.3%, it's roughly 94. That's about 50 extra applications for the same five conversations.
Why the remote vs hybrid job interview rate gap exists
The most likely cause is competition: a small share of postings offers remote work, and it draws a far larger share of applicants. LinkedIn data cited by Forbes in September put it starkly: about 9% of U.S. job postings in July offered remote work, and those listings drew 37% of all applications.
Huntr raises the same possibility in its own caveat: it can't see how many people applied to each vacancy, so competition alone could produce the gap. Put that next to the 9% vs 37% split and competition is the simplest explanation. Your resume is the same on a remote application and a hybrid one. What changes is how big the pile is when it lands, and a recruiter with a bigger pile filters harder.
How much it hurts depends on your role
Remote competition isn't the same across job families. Jobgether's September Remote Work Index, which tracked 200,043 new remote postings first published between August 1 and September 30, 2026, estimated applications per posting relative to the platform average:
| Remote role family | Applications per posting vs average |
|---|---|
| Software engineering | 2.26x |
| Administration and executive support | 2.22x |
| Banking, investment and insurance | 0.20x |
| Healthcare and life sciences | 0.19x |
These are platform estimates, not the whole market, but the spread is more than tenfold. A remote healthcare or insurance role is lightly contested. A remote software engineering role is among the most crowded on the platform. Going remote-only is a defensible strategy in the bottom two rows and a hard one in the top two.
The hidden geography catch: "remote" usually has a border
Most remote jobs are only remote within a set region. Jobgether found just 4% of new remote postings were open worldwide, and each of those drew an estimated 8.8 times the average number of applications.
That changes how you read a listing. Canonical posts a lot of software roles as "Remote from EMEA," which means you need to live and work inside Europe, the Middle East or Africa. Zyte's "Remote from Anywhere" software engineer listing is the rare global exception, and global exceptions get buried in applicants.
Here's why this matters for your resume. If nearly every remote role has a location requirement, a resume that hides your location doesn't look flexible. It looks like an unanswered question. A recruiter hiring "remote, US only" or "remote, Eastern time zone" has to guess whether you qualify, and with a crowded pile, they won't bother guessing.
The real lever is location, not work mode
Being near the job matters more than the hybrid-or-remote label. For non-remote jobs, Huntr found the same people got interviews at 6.1% when the job was in the state or region on their resume, against 4.9% when it was somewhere else.
That's a 1.2-point lift just from the address matching, with the work arrangement held constant. Huntr also reports 6.2% for in-country roles versus 4.0% for roles abroad, but that figure comes from just 199 job seekers, so treat it as a hint rather than a finding.
Why would location matter for a job that's only in the office part of the week? Because recruiters filter on it whether or not the job strictly needs it. A recruiter searching for candidates within a set distance of Austin, or located in Texas, is matching against the location on your resume. A resume that says only "Remote" or "United States" doesn't match that search. It isn't rejected. It just never shows up.
A resume that says only Remote can't match a search for candidates near Austin. It isn't rejected. It just never shows up.
Refolk's index: the engineers who say "remote" are the ones hiding their city
Engineers who advertise "remote" in their headline are far more likely to leave their city off: 40% in my sample, against 4% of everyone else. In a 25-profile sample of US engineers with "remote" in the headline, 10 listed only "United States" as their location, with no city. In a general software engineer sample and a "hybrid" sample of the same size, it was 1 of 25 each.
Both groups are small to begin with. In Refolk's index, 353,073 US profiles have "Software Engineer" in the title. Only 237 put "remote" in their headline, and only 47 put "hybrid." Remote advertisers outnumber hybrid advertisers about 5 to 1.
| Signal (US software engineers) | Remote headline | Hybrid headline | All SWEs |
|---|---|---|---|
| Profiles with keyword in headline | 237 | 47 | 353,073 total |
| Share of all US SWEs | 0.067% | 0.013% | n/a |
| Country-only location, no city (25-profile sample) | 40% | 4% | 4% |
Versus 4% of hybrid-headline and general software engineers. Small samples, so read this as directional.
The samples are small, so read this as a direction, not a precise rate. Still, the pattern fits the Huntr data: the people most committed to remote work are the most likely to strip out the one field that location filters check.
One more detail is worth noting. The employers that showed up most often in the remote-headline group were Google (3), Walmart (2) and JPMorganChase (2), not remote-first startups. These are large employers that also hire for offices, which is exactly the kind of local hybrid search a city line would get these engineers into. They've hidden it.
Should I put my location on my resume?
Yes. Put your city and state (or region) in the header, plus a short line saying which work arrangements you'll take. It costs almost nothing on remote applications, since most of them require a location anyway, and it gets you into the local hybrid and onsite searches that convert better.
Here's a header that works:
- Line 1: Name
- Line 2: Austin, TX (open to roles across the Austin metro) · email · LinkedIn
- Line 3: Open to remote (US), hybrid, or onsite in Austin
Each piece does its own job:
- City and state. This is what matches radius and state filters. If you're near a bigger metro, use the metro name recruiters actually search for.
- Commute radius. A commute radius is the maximum distance you'll travel to an office, written as miles or a metro area. It tells a hybrid recruiter you've already thought about the commute.
- Work-mode line. This tells remote recruiters you qualify for "remote, US" and tells everyone else you're not remote-only.
- Time zone, for remote-heavy targets. If you're mostly applying to distributed teams, "Eastern time" answers their first question.
- Relocation, only if it's true. "Relocating to [city], [month]" gets you into that city's searches before you have a lease.
The work-mode line is the part to adjust per application. For a hybrid role in your metro, lead with the city and drop the remote language. For a "Remote from EMEA" role, lead with country and time zone. That per-posting rewrite is the kind of work Refolk takes off your plate: paste the posting and you get your own resume back with the header, summary and bullets rewritten for that role.
How to find hybrid jobs near me without giving up flexibility
Search by place first, then filter by arrangement. If you start from "remote," you only see the most crowded 9% of listings. If you start from your metro, you see the hybrid and onsite roles that convert at 5.3%, and the remote ones too.
A practical setup:
- Set your job alerts to your city plus a radius, and allow remote, hybrid and onsite. Don't filter down to remote only.
- Don't assume remote-friendly means startup. The remote-headline engineers in Refolk's index were working at Google, Walmart and JPMorganChase. Large employers with local offices belong on your hybrid list.
- Check the location line on every remote posting. "Remote, US" and "Remote from EMEA" are location requirements. Only apply where you qualify.
- Weight your remote applications by role family. If you're in healthcare or banking, investment and insurance, where remote postings draw about a fifth of the average applications, remote-only is reasonable. In software engineering at 2.26x, mix in local hybrid roles.
Remote job search not getting interviews? Send fewer, better ones
Sending more applications makes the rate worse. Huntr found users with more than 100 applications had a 2.4% interview rate, against 8.0% for users who sent 11 to 20. Sam Wright, Head of Career Strategy at Huntr, put it simply in Forbes: "Getting interviews isn't a numbers game."
The better approach is to apply to fewer roles where you clearly fit, with a resume written for each one. Before you apply, check whether you actually match the role's must-haves, location included. Refolk scores your fit against each posting before you send it, so you can skip the remote listing where you're one of a crowd with a missing requirement and spend that time on the hybrid role in your metro that you match line by line.
Part of the 100-application number is selection: people who aren't getting interviews keep applying. But it's also a trap. With 9% of postings drawing 37% of applications, the easiest way to hit 100 applications is to keep clicking one-click apply on remote listings. Each one competes with a crowd, each one gets the same untailored resume, and silence follows. Weeks of that, mostly while holding down a current job you can't let find out about the search, is how people burn out on a search that was never set up to work.
FAQ
Should I put my location on my resume if I only want remote work?
Yes. Only 4% of remote postings on Jobgether were open worldwide, so nearly every remote role screens on country, region or time zone. A city and state, plus "Open to remote (US)," answers that screen up front. Leaving it blank doesn't make you look flexible. It makes you harder to place.
Does a full street address help?
No. City, state and a commute radius are enough to match recruiter location filters, and they're the parts that matter. Huntr's finding that same-state or same-region jobs interviewed at 6.1% versus 4.9% elsewhere is about region matching, not street-level detail. Leave your street address off for privacy.
Is remote-only ever the right strategy?
It depends on your field. Jobgether estimated remote healthcare and life sciences postings drew 0.19 times the average applications, and banking, investment and insurance drew 0.20 times, so remote-only can work in those fields. In software engineering (2.26 times) or administration and executive support (2.22 times), add local hybrid roles to your search or expect to send far more applications per interview.