Methodology · Updated 2026-04-19
How we aggregate remote jobs
RemNavi is an aggregator. We don't post jobs ourselves — we collect listings from seven major remote job boards and ATS platforms, deduplicate them, normalise the fields, and present them under one searchable interface. This page explains exactly how we do it, what our data means, and where it doesn't apply.
01 — Sources
Where our listings come from
All listings come from publicly accessible job boards and ATS-hosted career pages. We never scrape behind a login, and we always link through to the source so the application happens at the employer.
- jobicy.com ↗Jobicy
Curated remote job board; transparent salary disclosure.
- remoteok.com ↗Remote OK
High-volume remote board with structured salary fields.
- weworkremotely.com ↗We Work Remotely
Long-running remote board; salary often free-text.
- remotive.com ↗Remotive
Remote-first board with strong SaaS employer coverage.
- greenhouse.io ↗Greenhouse
ATS — direct company career pages.
- lever.co ↗Lever
ATS — direct company career pages.
- news.ycombinator.com ↗Hacker News Who's Hiring
Monthly high-signal thread, parsed for structured fields.
02 — Cadence
How often listings refresh
Every source is polled on its own schedule — aggressive enough to catch new listings within hours, polite enough that we do not strain the origin.
Board-style sources with public APIs (Jobicy, Remote OK, Remotive) are ingested every 30 minutes. Greenhouse and Lever career pages are polled every 2 hours per employer — more frequent for the companies we cover as hubs. We Work Remotely and Hacker News threads are parsed daily.
A listing disappears from RemNavi when its source returns 404, when it has not been seen for 14 consecutive polling cycles, or when the employer marks it closed. The 14-cycle buffer guards against transient source outages producing false negatives.
03 — Deduplication
How we handle the same job on multiple sources
A listing that appears on three boards is the same listing. Counting it three times is how aggregators inflate numbers. We don't.
Every listing is keyed by a stable hash of normalised_company + normalised_title + region. When the same hash appears on multiple sources, we keep the canonical ATS (Greenhouse or Lever) if present, otherwise the earliest-seen source, and we record the other sources as alternates on the listing record.
Normalisation is case-insensitive, strips legal suffixes (Inc., GmbH, Ltd.), collapses whitespace, and maps common title variants (e.g. "Sr." → "Senior", "PM" → "Product Manager") through a small managed dictionary. The dictionary is open in the repo and reviewed manually on every change.
04 — Salary data
How the Remote Salary Index is built
The Salary Index surfaces only listings with transparent, structured compensation — we never fabricate ranges, infer them from proxies, or interpolate between employers.
A listing enters the Salary Index only if the source provides a numeric range or a single numeric figure. Free-text salary language ("competitive", "market rate", "DOE") is excluded. We convert every range to USD per year using a daily FX rate — we do not attempt to correct for cost of living at this layer (that's what the Salary Calculator is for).
We report median and range per role group and per seniority band. Groups with fewer than 5 listings in the current window are suppressed to avoid statistical noise. The published snapshot at /tools/salary-index is built at every release and exposes the row-level underlying data via CC BY 4.0.
Limitations we want you to know about. Our sample is biased toward employers who publish salary bands — in practice, that's US-headquartered SaaS, European remote-first companies, and European employers subject to the 2026 EU Pay Transparency Directive. US states with pay transparency laws (CA, CO, NY, WA) are overrepresented in the underlying data. Treat the medians as lower-bound signals of real compensation, not universal industry figures.
05 — Boundaries
What RemNavi is not
Clarity about what we do not claim is more useful than hedge-everything disclaimers.
- —We are not a job board. We do not accept paid postings from employers. All listings come from public sources and link through to the original employer page.
- —We are not a recruiting agency. We do not hold candidate profiles, we do not submit applications, we do not broker between candidates and employers.
- —Our salary figures are not a compensation benchmark. They are a live snapshot of what employers openly advertise — useful as a negotiation anchor, not as an authoritative industry rate.
- —Our "Real Remote Score" (coming soon) is an editorial rubric, not an endorsement. Employers cannot pay to influence their score.
06 — Licence
Using our data
The structured data underlying the Remote Salary Index is published under Creative Commons Attribution 4.0. Use it, cite us, link back.
The Salary Index snapshot (CSV + JSON) is available at /tools/salary-index. A broader Market Index — source, role, skill, company, geo, and seniority cuts — is at /market-index, with direct JSON and CSV download links. Every listing is also scored on the Real Remote Score rubric. Attribution for any of these: "RemNavi — https://remnavi.com". Commercial reuse is permitted under the same CC BY 4.0 terms.
Individual job listings remain the intellectual property of the source employer and posting platform. Our right to surface them is under fair use for aggregators; we do not store full job descriptions, only the metadata required for discovery and the canonical link back to the source. If you are an employer and would like a listing removed or a source excluded, write to hello@remnavi.com and we will action within 48 hours.
Transparency
Found something we got wrong?
We care about getting this right. If you see a duplicated listing, an outdated salary, or anything that contradicts the rules on this page, let us know and we will fix it.
hello@remnavi.com