Remote Job Feed Aggregator — Remotive, Himalayas, Arbeitnow, We Work Remotely & HN

One search across five public remote-job feeds, deduplicated into a single schema. No API keys, no proxies, no login.

Running five separate scrapers and merging their output by hand is the usual way to do this. This Actor does the merging — including collapsing the same job when two boards both carry it.

What it does

Input	Optional keywords, location and date filters
Output	One row per job, identical fields across every feed
Sources	Remotive · Himalayas · Arbeitnow · We Work Remotely · Hacker News "Who is hiring"
Speed	4 feeds × 3 pages finishes in well under a minute

Use cases

• Run a job board or newsletter for a niche (Python, design, EU-timezone) without maintaining five integrations.
• Job hunting at scale — schedule a daily run with postedWithinDays: 1 and get only what is new.
• Labour-market research — who is hiring remotely, for what, at what salary, over time.
• Feed an LLM or a RAG index with fresh, structured, permissively-sourced job text.

Input

{
  "keywords": ["python", "data engineer"],
  "sources": ["remotive", "himalayas", "arbeitnow", "weworkremotely"],
  "locationKeywords": ["Europe", "Worldwide"],
  "postedWithinDays": 14,
  "excludeKeywords": ["senior manager"],
  "includeDescription": false,
  "deduplicate": true,
  "maxItems": 200,
  "maxPagesPerSource": 3,
  "requestDelaySeconds": 1
}

Leave keywords empty to pull everything the feeds currently publish.

hackernews is off by default: it reads the current Ask HN: Who is hiring? thread, which is free-text rather than structured, so titles are the comment's first line and company names are best-effort.

Output

{
  "source": "himalayas",
  "jobId": "https://himalayas.app/companies/netomi/jobs/software-development-engineer-in-test-i",
  "title": "Software Development Engineer In Test - I",
  "companyName": "Netomi",
  "companyLogo": "https://cdn-images.himalayas.app/...",
  "url": "https://himalayas.app/companies/netomi/jobs/...",
  "applyUrl": "https://himalayas.app/companies/netomi/jobs/...",
  "locationText": "India",
  "locationRestrictions": ["India"],
  "employmentType": "Full Time",
  "category": "Developer",
  "tags": ["SDET", "QA-Automation-Engineering"],
  "seniority": "Mid-level",
  "salaryText": null,
  "salaryMin": null,
  "salaryMax": null,
  "currency": null,
  "postedAt": "2026-09-09T14:12:17+00:00",
  "descriptionText": null,
  "isRemote": true,
  "alsoSeenOn": ["remotive"],
  "scrapedAt": "2026-09-10T10:31:02.884000+00:00"
}

alsoSeenOn lists the other feeds that carried the same job when deduplicate is on. RUN_SUMMARY in the key-value store records how many rows each feed returned and any feed that failed.

Honest limitations

• Field coverage differs by feed. Salary comes mostly from Himalayas; employmentType is missing from We Work Remotely; Hacker News has no structured fields at all. Fields a feed does not publish are null, never guessed.
• Keyword filtering is client-side. The feeds are fetched first and filtered after, so a narrow keyword with a low maxPagesPerSource can return very little. Raise maxPagesPerSource before you conclude there are no matches.
• Deduplication is heuristic — normalised company + title. Two genuinely different roles with the same title at the same company will collapse into one row; turn deduplicate off if that matters.
• Remote-only by nature. These are remote-job boards. Arbeitnow carries some on-site European roles (isRemote is false for those); the rest are remote by definition.
• Feed depth is finite and varies a lot by feed. Remotive returns its whole current list in one request — and that list is small (it was 17 jobs on 2026-09-10). Himalayas serves 20 jobs per page, Arbeitnow 250, We Work Remotely one RSS file per category. So maxPagesPerSource buys you very different amounts of data per feed. This is a current openings tool, not a historical archive.
• These feeds are free services. They can rate-limit or change shape. The Actor retries with backoff and records feed errors in RUN_SUMMARY instead of failing the whole run.

Sources and attribution

• Remotive — remotive.com/api/remote-jobs, the public API Remotive publishes for third parties. Jobs sourced from Remotive keep their original url; please credit remotive.com when you republish.
• Himalayas — himalayas.app/jobs/api, public JSON API with cursor pagination.
• Arbeitnow — arbeitnow.com/api/job-board-api, public job-board API.
• We Work Remotely — the public per-category RSS feeds.
• Hacker News — hn.algolia.com/api/v1, the official public HN search API.

robots.txt was checked for every host; none of these paths are disallowed. There is no login, captcha solving, proxy rotation or browser automation anywhere in this Actor.

Changelog

See CHANGELOG.md.

Support

Found a bug, or need a field this Actor does not return yet? Open an issue on the Actor's Issues tab, or email pablodevigoalertas@gmail.com. Issues are read first.