Remote OK Jobs Scraper

Scrapes Remote OK and returns only the jobs that are genuinely remote, with parsed salary, normalised regions and ghost-job risk scoring on every row.

What this does that a plain scraper does not

Remote OK's feed is not all remote jobs. Measured against their live API on 2026-08-15, 90 of 100 listings were not remote roles at all — a barber in Regina, a live-in nanny in Bermuda, store managers, a marine painter, a bell person — plus rows that are not job postings in any sense: Test Job Title, Title TBD, HYGPOOLOP, Looking for Job, Seeking a job.

A scraper that dumps the feed hands you all of that and calls it remote work.

This one requires positive evidence that a listing is actually remote: a blank location (the board's way of saying anywhere), an explicit remote word in any spelling including Remoto, or a country/continent-level region that states eligibility rather than an address. A named town is a desk until the board says otherwise.

The trade is deliberate and worth knowing before you buy: you get roughly 10 real remote jobs instead of 100 rows, most of which were never remote. If you want the raw feed including on-site roles, this is the wrong Actor.

---

What each row contains

Identity	stable id across runs, posting URL, direct applyUrl where published
The role	title, company, plain-text description, tags, employment type, seniority
Where	remote flag, the board's own location text, and normalised regions (worldwide / usa / canada / latam / uk / europe / apac / africa / middle_east)
Pay	min, max, currency and period as numbers, annualised on request
When	posted date, expiry where published, age in days
Trust	freshness 0-1, ghostRisk low/medium/high, and ghostReason explaining the verdict in plain words

The trust fields

Job boards are full of postings still published but no longer open — filled roles left up for pipeline, evergreen "talent pool" adverts, and listings nothing ever expires. Every row here carries a risk band and the reasons behind it:

{
  "title": "Senior Backend Engineer",
  "company": "Acme",
  "freshness": 0.71,
  "ageDays": 10.4,
  "ghostRisk": "low",
  "ghostReason": ["recent, and nothing contradicts it"]
}

Signals come from what the board actually publishes: age, its own expiry date where there is one, missing application links, and evergreen phrasing. Nothing is inferred by a model. Freshness decays on a 21-day half-life, and a posting with no date scores 0.5 rather than 1.0 — absence of evidence is not evidence of freshness.

Example input

{
  "query": ["golang", "backend"],
  "regions": ["usa"],
  "seniority": ["senior", "lead"],
  "maxAgeDays": 21,
  "maxGhostRisk": "low",
  "maxItems": 200
}

Everything is optional — run it empty and you get the whole board, best-first.

• Search terms are OR-ed. ["go", "rust"] returns jobs mentioning either.
• Worldwide jobs match every region filter, because a job open to everyone is open to you.
• minSalary is annualised first, so hourly and monthly rates compare correctly.
• maxItems is your cost ceiling — you are billed per job returned.

Output

One dataset item per job, ordered best-first: lowest ghost-job risk, then freshest. Export as JSON, CSV or Excel, or read it from the API like any Apify dataset.

How it fetches

Remote OK publishes a public, documented, unauthenticated feed and this Actor reads it — paced, budgeted, with an honest user agent. No HTML scraping, no bot-check evasion, no personal data. Job adverts only.

Want more than one board?

Remote Jobs Aggregator runs this same pipeline across six boards at once — Remote OK, Remotive, Himalayas, Arbeitnow, We Work Remotely and Jobicy — folding duplicates and recording which boards carry each job.

Measured while building it: those six boards barely overlap. Only 1 of 1,513 company+title pairs appeared on more than one. The aggregator is not about removing duplication — there is almost none — it is about getting six boards' worth of distinct jobs from one call.