When "remote" isn't: how RemNavi scores the hybrid listings the rest of the industry hides

Most remote job boards fail this test before the user clicks. They aggregate listings from company career pages, apply a "remote" tag to anything that mentions the word, and present the result as a curated remote jobs feed. What they are actually presenting is an unaudited stream that conflates fully-distributed positions with hybrid arrangements that require you to live in Austin and come in three days a week.

We pulled every listing in the RemNavi corpus as of 2026-04-25 — 10,495 active roles aggregated from Jobicy, Remote OK, We Work Remotely, Greenhouse, Lever, Remotive, and Hacker News Who's Hiring. We ran each one through the work-mode classifier built for our Real Remote Score audit. Here is what came out:

• 41% are fully remote as advertised — no office requirement in the description.
• 36% say "remote" somewhere in the listing but require office time in the body — anywhere from one day a week to "flexible hybrid" near a specific city.
• 0% are onsite-only roles that were tagged remote because "remote-friendly" appeared in company boilerplate.
• The remainder are ambiguous enough that no classifier should pretend to know.

The problem with the hybrid bucket is not that hybrid is bad. Hybrid is a legitimate working arrangement that many people prefer. The problem is that these listings get filed under "remote" and then reveal — on page two, below the benefits section — that you need to be within commuting distance of a specific city. That is not a remote job. That is a local job with a marketing problem.

The Real Remote Score already handles the problem for fully-remote listings — it grades how genuinely remote a position is on five dimensions (compensation transparency, location openness, source credibility, listing clarity, and freshness). But the RRS was designed for fully-remote evaluation. A hybrid listing will score poorly on RRS by design — location openness collapses — which is the right call for a remote index but tells the candidate nothing about whether the employer disclosed what they need to make a decision.

We built the Hybrid Transparency Score as a parallel 0–100 metric specifically for listings our classifier identifies as hybrid. HTS does not penalise a listing for being hybrid — it grades whether the employer told candidates the things they need to know:

A fully-disclosed hybrid listing — days stated, city stated, schedule flexibility described, relocation terms addressed, sourced from the company's own ATS — scores 90–100 and earns the Exceptional tier. An opaque hybrid listing that says "hybrid role, some office time required" without specifying where or how much scores below 30 and lands in the Weak tier.

Full HTS methodology at /how-we-audit/#hybrid

We ran HTS against every listing the classifier identified as hybrid in our 10,495-listing corpus. The results:

The industry average on hybrid transparency is 25/100 — well into the Weak band. 66% of hybrid listings fail to disclose enough for a candidate to make an informed decision before clicking through. Exactly 0% score Exceptional.

This is the same pattern we found with the Real Remote Score: the platforms that aggregate listings do not grade them, so opacity travels undisturbed from the employer to the candidate. The candidate clicks, spends 20 minutes on the application, and discovers the commute requirement on page three of the interview process.

The aggregation model has a built-in opacity bias. Aggregators are measured on listing volume — the more listings, the more search traffic, the more clicks. Grading listings on transparency reduces apparent volume (Weak listings become less prominent) and requires infrastructure that pure aggregators have no incentive to build.

RemNavi's position is different: our value proposition is not listing volume, it is listing accuracy. A smaller corpus where every listing is graded and classified is worth more to a job seeker than a large corpus of undifferentiated results. HTS is the extension of that thesis into the hybrid category — the half of the market that RRS does not cover by design.

For candidates: HTS tells you, before you click through, whether a hybrid listing has disclosed what you need. A listing with HTS Weak means the employer has not told you how many days or which city. A listing with HTS Strong means the terms are disclosed. You decide whether the commute is acceptable; we make sure you have the information to decide at all.

For employers: the disclosure bar is low. Stating "3 days/week in our London office, Monday–Wednesday core hours" takes 12 words. Those 12 words move a listing from Weak to Strong and demonstrate that the employer respects candidates' time enough to be specific.

The HTS classifier and scorer are open and documented. The full methodology — including factor weights, tier thresholds, and edge-case handling — is published at /how-we-audit/#hybrid. The source code for the JavaScript scoring library is at frontend/src/lib/hybridScore.js in our public repository.

All corpus statistics on this page are drawn from live API endpoints. Reporters can reproduce them at any time using the curl commands above. The numbers will change as new listings enter the corpus and the HTS backfill extends coverage to older listings. If a number cited in a published piece differs materially from the live API, the live API is the authoritative source — not the snapshot at time of writing.

This piece is published under CC BY 4.0. You may reproduce, reuse, and build on it with attribution to RemNavi and a link to this URL.

Published by RemNavi Editorial Desk · DField Kft. · 2026-04-25 · Editorial policy · Audit methodology