Remote job boards, ranked by whether you can reach the employer
We index seven aggregators and six ATS vendors, and we probed each one to see where its apply button actually goes. Four of the seven never hand you the employer's own page — here is the measurement, and why that is not a scandal.
- job-search
- boards
- research
Ranked on one axis only: when you press Apply, do you end up on the employer's own application form, or on the board's?
It is the axis that decides whether your application enters the system the hiring manager actually reads, and almost nobody ranks on it, because measuring it means following every apply link on every posting. We had to do that anyway. Numbers below are from our own index and our own probes, on 3 August 2026, across 6,507 live postings.
One disclosure before the ranking: 73 of those rows are seeded test fixtures of ours, which is why the per-source counts do not sum to the total.
Tier 1 — the employer's own board
Greenhouse (2,597 postings in our index), Ashby (960), Lever (317), SmartRecruiters (288), Rippling (69), Workable (30), Recruitee (12), Personio (3).
These are not job boards in the usual sense. They are the software the employer runs their hiring in, and each customer gets a public board. Applying there puts a row directly in the system the recruiter works out of. No intermediary, no forwarding, nothing to strip your details.
The move almost nobody makes: pick fifteen companies you would actually work for and bookmark their boards. job-boards.greenhouse.io/{company}, jobs.ashbyhq.com/{company}, jobs.lever.co/{company}. Those pages are the employer's live list of open roles, updated by the employer, with no ranking algorithm between you and it. It is the highest-signal job feed on the internet and it is free and unglamorous.
Watch for the vanity domain, though: 1,147 of the Greenhouse postings in our index apply on stripe.com/jobs, careers.airbnb.com or similar. Still Greenhouse, still Tier 1, and the gh_jid in the URL is the board's own posting id.
One caveat on SmartRecruiters. Its board is real and applying there reaches the employer, but its application form is gated behind an employer-issued key, so no third party can read its questions in advance. It is Tier 1 for reach and opaque for preparation.
Tier 2 — aggregators that hand you the employer
Hacker News "Who is hiring?" (217 postings). Each posting is a comment written by somebody at the company, usually with their own link and frequently their own email address. Roughly three in four of the comments we resolve carry a link to the employer. There is no board, no algorithm, no apply button, and it is one of the best sources of direct contact that exists. The destination is usually a careers page rather than an ATS, which is fine — it is the employer's page and it is what you wanted opened.
Arbeitnow (112 postings). Publishes <listing>/apply as a 302 to wherever the employer actually recruits, and it does it reliably: 74 out of 74 rows redirected when we probed every one of them. Where they land is the more interesting result, and it is worth stating precisely because our own build spec had it wrong:
- join.com — 48
- apply.workable.com — 10
- Recruitee subdomains — 7
- employer career domains — 9
- Greenhouse or Ashby — 0
So Arbeitnow always forwards you to the employer, and only 13.5% of the time to a board whose questions anybody can read ahead. It is a mostly-German board and its employers buy the German ATS market; join.com alone is two thirds of it. Good for reach, thin for preparation.
(If you are probing that redirect in bulk: faster than about one request every two seconds and Arbeitnow answers 429. Ours runs once per posting per month, which is nowhere near it.)
Tier 3 — boards that keep the relationship
These four do not hand you the employer's link. The reason is the same in each case and it is not sinister: the board's asset is the relationship with the employer, and a direct line spends it.
Himalayas — 1,072 postings, the largest single source in our index. Every one of those rows points at himalayas.app. The employer's link exists behind a Himalayas account. The listings themselves are good and the volume is real; you are just signing up.
We Work Remotely — 212. Handles the application itself. Long-running, well curated, genuinely worth reading; the application does not go where you might assume.
RemoteOK — 254. Hosts the application on its own site.
Jobicy — 253. Publishes no apply link at all in the feed.
Remotive — 38. The apply control is not a link.
We record all five as "unresolvable" with those exact reasons rather than working around them. They are deliberate access controls and somebody's business model, and routing around a wall is not something a tool should quietly do on your behalf.
What this actually changes for you
Not much about finding jobs. Tier 3 boards are frequently the best place to find a role — curation is real work and they do it.
It changes what "applied" means. On a Tier 3 board, applying is an event on that board, mediated by their integration with the employer. It is not the same event as a row appearing on the employer's Greenhouse. If you have ever had the experience of applying somewhere and finding no trace of it later, this is the most likely explanation, and it is worth knowing which kind of Apply button you just pressed.
The move that follows from all of it is boring and effective: find the role anywhere, apply on the employer's board. Search the company name plus the ATS domain, or open their careers page. Ninety seconds, and your application lands in the system of record.
What we do with each tier
Crossing indexes all of them and routes by tier rather than pretending they are equivalent. 3,976 of the 6,507 postings sit on one of the six vendors whose question sets we can read, which is where showing you the employer's real form filled in becomes possible. For the rest we open the employer's page and say plainly why we could not help — Himalayas wants an account first, SmartRecruiters requires an employer-issued key, this Personio board has retired.
That ratio moves daily as the index turns over, which is why we describe the behaviour rather than print a percentage on the homepage. Every capability, with what it actually does.