Robert Half's Q2 2026 posting analysis just made the math ugly: 87% of advertised roles are fully on-site, 10% hybrid, and 3% fully remote. Two quarters ago on-site was 65%. If your resume still opens with "Remote-first Senior Engineer, Boise, ID," you are optimizing for the smallest slice of the market while the biggest one filters you out at the location field.
This is a rewrite guide, not a lament. The fix is mechanical, and most of it happens in three lines at the top of the document.
The 22-point swing that broke the remote resume
Fully on-site postings jumped from 65% in Q4 2025 to 87% in Q2 2026, a 22-point swing in two quarters, per Robert Half's Demand for Skilled Talent report. Hybrid dropped from roughly 24% to 10% over the same window. Fully remote fell to 3%.
The Q1 2026 waypoint shows how fast this moved: 77% on-site, 19% hybrid, 4% remote. One quarter later, hybrid nearly halved. HR Stacks calls it the fastest single-year contraction in flexible availability since 2020.
Layer on the demand side and the squeeze gets sharper: 46% of professionals are already looking or plan to look in the second half of 2026. Half the workforce is chasing 3% of the postings if they filter for "remote."
On-site share of new postings moved from 65% to 87% in two quarters, per Robert Half.
Why this happened faster than anyone modeled
Two mechanisms compounded. First, 36% of employers reported increasing required on-site days over the past year, per Robert Half, so existing hybrid roles quietly converted into on-site roles at renewal. Second, the federal RTO order that took effect in January 2025 pulled the whole labor market's baseline: BLS data shows federal hybrid arrangements collapsed from 61% to 28% in one policy stroke. When the largest single employer in the country halves its hybrid share, private-sector job specs redraft themselves within a quarter.
The mismatch in Refolk's index: 220 remote SWEs, 41 hybrid
In Refolk's index of professional profiles, US software engineers who self-brand as "remote" outnumber those who self-brand as "hybrid" by 5.4 to 1. Postings run more than 3 to 1 the other way. That is the personal-branding mismatch this article exists to fix.
| Segment | Count in Refolk's index | What it tells you |
|---|---|---|
| All US Software Engineers | 335,227 | The pool you are competing inside |
| US SWEs with "remote" in headline | 220 | Self-branded for the 3% posting slice |
| US SWEs with "hybrid" in headline | 41 | Self-branded for the 10% posting slice |
| Ratio of "remote" to "hybrid" headlines | 5.4x | The mismatch in one number |
| Share of US SWEs tagging any work model | 0.078% | Most engineers say nothing, which is often the right move |
| Top employers of self-branded "remote" US SWEs | Google (4), Walmart (2), Amazon, Meta, JPMorganChase, Siemens | Where the rewrite problem is concentrated |
The takeaway is not that "remote" in a headline is fatal. It is that hybrid is the arbitrage: 3x larger than fully remote, ignored by candidates who filter for "remote," and reachable with a small, honest edit to your top three lines.
Hybrid is not a compromise in this market. It is the only bucket where the math works.
The location line is the ATS filter that eats you
Your city field is a bigger ATS filter than your work-model tagline, because recruiters and applicant tracking systems sort candidates on the structured location field, not free text further down. A remote worker in Boise applying to a Chicago on-site posting is dropped by the filter before a human reads the "open to relocation" note.
Fix it in this order:
- Set the city to the target market. If you are willing to move for a specific city, put that city on the resume. "Chicago, IL" beats "Boise, ID (open to relocation to Chicago)" because the filter reads the first field.
- Kill the state-only line. "Remote, US" or "United States" reads as a red flag on on-site postings. Recruiters searching by metro will not surface you.
- If you truly cannot relocate, target hybrid postings in a metro within commute range. Do not apply to on-site roles 2,000 miles away and hope the recruiter reads paragraph three.
- Drop "Remote-first" from the headline. For 87% of postings it is an anti-signal. Replace with the role and one stack cue: "Senior Backend Engineer, Go and Postgres."
- Mention relocation once, in the summary, in one sentence. "Relocating to Austin in Q1 2026." Specific date, specific city. Vague willingness reads as bluffing.
Also watch the contradictory signal: mixing "remote-first" and "open to relocation" in the same resume reads as confusion unless you explain the split (say, wanting remote work with quarterly on-site travel). If you are remote-only, say that clearly and skip relocation language entirely.
The remote-to-onsite bullet flip
Bullets written for remote-first roles emphasize distributed coordination: "Led a fully remote team of 12 across four time zones." That was the right brag in 2022. In a Q2 2026 on-site market it reads as "will need Slack workarounds."
Flip the emphasis without lying:
-
Before: "Managed a distributed team of 12 across four time zones using async standups and Loom."
-
After: "Managed a team of 12, including four engineers on-site in the Austin office and eight distributed across the US."
-
Before: "Ran remote onboarding for 34 new hires over 18 months."
-
After: "Ran onboarding for 34 new hires, including in-person weeks in NYC and remote follow-through."
-
Before: "Facilitated all planning via Miro and Notion."
-
After: "Facilitated quarterly planning in-person and drove week-to-week execution in Notion."
You are not inventing office time you did not have. You are naming the office time you did have, which remote-first resumes routinely omit because it felt like the boring part.
Tailoring every bullet like this per posting is grinding work, and it is the exact rewrite Refolk takes off you: paste the posting, get your own resume back with the location line, headline, and bullets rewritten to the work model that posting actually offers.
Which sectors still have real remote and hybrid volume
Marketing and creative is the only major sector where remote clears the 3% floor comfortably at 9%, per Robert Half's Q2 2026 sector split. Technology sits at 8% remote. Administrative and customer support is the hardest on-site skew at 87%.
| Sector (US, Q2 2026) | On-site | Hybrid | Fully remote |
|---|---|---|---|
| Marketing and creative | 70% | 21% | 9% |
| Technology | 74% | 18% | 8% |
| Finance and accounting | 76% | 19% | 5% |
| Healthcare | 85% | 6% | 9% |
| Administrative and customer support | 87% | 8% | 5% |
The read for a remote-experienced candidate: if you are in tech, your realistic pool is 26% of postings (hybrid plus remote), not 8%. Rewriting for hybrid roughly triples your addressable market inside your own sector. If you are in admin or support, hybrid is thinner than remote, and the honest move is to target on-site roles in one metro.
The RTO enforcement gap is your cover letter opening
61% of US companies have formal RTO policies, but only 37% actually enforce attendance, per Makerstations' 2026 hybrid tracker. Kastle Systems' Back to Work Barometer still puts average US office occupancy at roughly 50% of pre-pandemic levels. The mandate is loud. The turnstile data is quiet.
Practical implications for your return-to-office job search:
- Apply to on-site postings at loud-mandate employers. Amazon, JPMorgan, AT&T, and Dell are named in the Makerstations coverage. The posting says five days on-site. The actual expectation on many teams is three. You negotiate that after the offer, not before the application.
- Do not self-select out on the work-model line. Candidates who read "5 days on-site" and skip are handing the interview to candidates who applied anyway.
- In the cover letter, address on-site directly in one sentence. "I am based in Chicago and available for the five-day on-site schedule from day one." No hedging. No "open to discussing." Recruiters forward the unambiguous ones.
- Save the flexibility conversation for the hiring manager screen. That is where the 37% enforcement number becomes leverage, not on the application.
The counter-mandate reality nobody says out loud
Only 10% of workers want to work on-site, per a Gallup poll cited by Forbes, yet nearly half of companies will mandate at least four office days in 2026. That gap does not go away because you refuse to apply. It shows up as retention churn six months into the role, which is when the enforcement number quietly slips.
Your job as a candidate is to be in the room when that slippage happens. That means getting hired, not filtering yourself out at the location line.
The three-line rewrite, in order
Rewrite in this order because each line unlocks the next:
- Location line. Set to your target metro. If you have two target metros, run two versions of the resume.
- Headline. Drop "Remote," "Remote-first," and "Distributed." Keep the role and one stack or domain cue.
- Summary, sentence one. Name the metro, the on-site or hybrid availability, and the start date. Example: "Senior Data Engineer in Austin, available on-site or hybrid, starting January 2026."
The rest of the resume stays. Your projects, your metrics, your stack are already what they are. The rewrite is 40 words at the top.
The problem is you need a different 40 words for every posting, because "Austin, hybrid" is wrong for the Denver on-site role you find on Tuesday. That is where a matcher earns its keep: Refolk rewrites your top block per posting, scores how well the rest of your history actually fits the role, and drafts the cover letter with the on-site sentence in place. You review, send, move to the next one.
FAQ
Should I remove all mentions of remote work from my resume?
No. Remove "remote-first" and "distributed" from your headline, but keep specific remote accomplishments in the bullets if you reframe them. "Coordinated a team across three time zones, including weekly in-office days in Seattle" reads as range, not as a red flag. What kills you is the top-of-page branding, not the fact that you have done the work.
What do I put on the location line if I am genuinely willing to move anywhere?
Pick one target metro and put that on the resume, because ATS filters run on the structured city field and cannot parse "anywhere." Run a second version for a second metro if you need to. "United States" and "Remote" both sort you out of on-site metro searches, which is where 87% of Q2 2026 postings live.
Is it worth applying to fully remote postings at all in 2026?
Apply, but do not build your pipeline around them. With 3% of postings fully remote and 46% of professionals looking, the marginal remote application converts at near-lottery odds. Spend most of your effort on hybrid and on-site postings in one or two target metros, and a smaller share on remote roles where you have a genuine referral or unusually specific fit.
How do I handle a five-year fully remote stretch on the resume?
Name the office anchors you did have (client sites, offsites, quarterly weeks) in the bullets, and address on-site availability directly in the summary and cover letter. Recruiters are not scoring you on the last five years of location, they are scoring you on the next five. One clear sentence that says "available on-site in Chicago from January 2026" resolves the ambiguity the work history creates.