Remote Jobs Aggregator (RemoteOK, WWR, Hacker News) avatar

Remote Jobs Aggregator (RemoteOK, WWR, Hacker News)

Pricing

from $0.60 / 1,000 jobs

Go to Apify Store
Remote Jobs Aggregator (RemoteOK, WWR, Hacker News)

Remote Jobs Aggregator (RemoteOK, WWR, Hacker News)

Merge and de-duplicate remote job listings from RemoteOK, We Work Remotely and Hacker News' Who is Hiring thread into one clean row per job — title, company, salary, tags and apply link.

Pricing

from $0.60 / 1,000 jobs

Rating

0.0

(0)

Developer

Murat Uzun

Murat Uzun

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

16 days ago

Last modified

Categories

Share

What is Remote Jobs Aggregator (RemoteOK, WWR, Hacker News)?

Remote Jobs Aggregator is an Apify Actor that merges and de-duplicates remote job listings from three of the biggest public remote-work feeds — RemoteOK's JSON API, We Work Remotely's RSS feed and Hacker News's monthly "Who is hiring?" thread — into a single, clean dataset: one row per job, with title, company, location, salary, tags and a direct apply link. No API key, no login, no proxies. It can also fold in named Greenhouse and Ashby company boards so a recruiter's own target-company list rides in the same run. Runs on Apify's schedule, webhook and API infrastructure, so a daily "new remote jobs" digest is a five-minute setup.

Why use Remote Jobs Aggregator?

  • Job boards and newsletters pull a fresh, de-duplicated remote-jobs feed every morning instead of manually checking three different sites.
  • Recruiters and sourcers filter by keyword (e.g. python, staff engineer) across every feed at once, then add their own tracked companies via greenhouseBoards/ashbyBoards.
  • Labor-market researchers track hiring volume, salary ranges and remote-vs-hybrid language across RemoteOK, WWR and Hacker News month over month.
  • Job seekers building a personal tracker get one flat table instead of three tabs, ready to import into a spreadsheet or Notion.

How to use Remote Jobs Aggregator

  1. Leave Feeds to aggregate on all three (remoteok, weworkremotely, hackernews), or narrow it to just one.
  2. Optionally add Keywords (e.g. react, remote) to keep only matching jobs — matching checks title, company and tags.
  3. Set Max jobs and Posted within (days) to cap the result size and freshness.
  4. Optionally list Greenhouse boards / Ashby boards slugs to fold specific companies into the same run.
  5. Click Start and export the dataset as JSON, CSV, Excel or HTML from the Output tab.

Example input

{
"sources": ["remoteok", "weworkremotely", "hackernews"],
"keywords": ["python"],
"maxJobs": 100,
"postedWithinDays": 30
}

Example output

{
"source": "hackernews",
"jobId": "hn-49522903",
"title": "Senior Product Engineer",
"company": "Modash.io",
"companyUrl": null,
"location": "Remote (Europe)",
"isRemote": true,
"employmentType": "Full-time",
"salaryText": null,
"salaryMin": 75000,
"salaryMax": 110000,
"salaryCurrency": "EUR",
"tags": [],
"description": "Modash.io | Senior Product Engineer | Remote (Europe) | Full-time | €75k–110k | https://modash.io Modash helps brands find, manage, and pay creators…",
"applyUrl": "https://modash.io",
"postedAt": "2026-09-01T15:01:54.000Z",
"scrapedAt": "2026-09-14T01:17:03.392Z",
"error": null
}

Data table

Remote Jobs Aggregator extracts 18 fields per row:

FieldTypeDescription
sourcestringremoteok, weworkremotely, hackernews, greenhouse or ashby
jobId, title, companystringIdentifier, job title and hiring company
companyUrl, applyUrlstringCompany site (when the feed publishes one) and the direct apply/read link
location, isRemotestring, booleanFree-text location and whether the posting is explicitly remote
employmentTypestringe.g. Full-time, Contract, Internship, when the source states one
salaryText, salaryMin, salaryMax, salaryCurrencystring, number, number, stringSalary as published, plus parsed numeric range and currency
tagsarraySkills, categories or departments from the source
descriptionstringPlain text, HTML stripped, trimmed to 2000 characters
postedAtstringISO 8601 UTC, when the source publishes a date
errorstringSet when a whole feed or board failed, instead of a job
scrapedAtstringTimestamp of the run (ISO 8601 UTC)

Input parameters

ParameterTypeDefaultDescription
sourcesarray["remoteok","weworkremotely","hackernews"]Which feeds to merge
keywordsarray[]Case-insensitive filter on title, company and tags
maxJobsinteger100Max rows after merge + de-duplication (1-2000)
postedWithinDaysinteger30Drop jobs older than this; jobs with no known date are always kept
greenhouseBoardsarray[]Greenhouse slugs to fold in, e.g. stripe
ashbyBoardsarray[]Ashby slugs to fold in, e.g. ashby
maxConcurrencyinteger3Parallel requests for the Greenhouse/Ashby board list

Pricing

Remote Jobs Aggregator uses pay-per-event pricing: $0.001 per result row, plus a negligible actor-start fee. The default run (100 jobs across three feeds) costs about ten cents. Set Maximum cost per run and the Actor trims the work to what the budget covers instead of overspending.

Remote Jobs Aggregator vs. checking each site by hand

RemoteOK, We Work Remotely and Hacker News each publish jobs in a different shape — a JSON API, an RSS feed and a freeform comment thread — and none of them de-duplicate against each other, so the same YC-funded startup's opening can show up on all three. This Actor normalises all three into one row shape, strips duplicates on company + title + apply link, and adds a numeric salary range wherever the source states one, so a downstream spreadsheet or dashboard never has to touch three different formats.

Using Remote Jobs Aggregator with AI agents and MCP

Remote Jobs Aggregator is pay-per-event with limited permissions — the two requirements for an Actor to be callable through the Apify MCP server at mcp.apify.com. An agent passes a keywords list (or none, for everything) and gets back structured job rows — title, company, salary, apply link — ready to summarise "what remote Python jobs opened this week" without the agent having to parse three different websites itself.

FAQ

Does this need an API key or login? No. RemoteOK's /api endpoint, We Work Remotely's RSS feed and Hacker News's Algolia search API are all public and unauthenticated. Greenhouse and Ashby's board APIs are the same public JSON endpoints their own career pages use.

Why is company/title sometimes null for a Hacker News row? Hacker News "Who is hiring?" posts have no fixed format — most follow a Company | Role | Location | ... convention that this Actor parses, but a post written as plain prose has nothing reliable to extract, so those fields stay null while description still carries the full text.

Why are salaryMin/salaryMax null for most rows? Only RemoteOK's own numeric fields, Ashby's structured compensation block, and a Hacker News headline that names a currency are trusted — this Actor deliberately does not scan long job descriptions for numbers, since that produces false positives from unrelated figures like founding years or headcounts.

What happens if I give a wrong Greenhouse or Ashby slug? That board returns one row with error set (e.g. Greenhouse board "typo" not found (HTTP 404)) instead of failing the whole run.

How current is the Hacker News data? Each run finds that month's live "Who is hiring?" thread via Algolia search and reads its comments fresh — there is no cached or delayed copy.

What are the limitations? We Work Remotely's RSS feed only carries its current front page (no historical pages), and RemoteOK's own salary fields are the site's self-reported figures, not verified. A failing feed still produces a row, with the reason in error.

Is this legal to run? Yes. RemoteOK's API, We Work Remotely's RSS feed, the Hacker News Algolia API and the Greenhouse/Ashby job-board APIs are all public, unauthenticated endpoints published for third-party consumption, and no personal data is collected.

Part of the webdatatools web-intelligence suite — every Actor is pay-per-event, reads public data without a login, and returns one clean row per entity:

Browse the whole suite at webdatatools, or call ten of these Actors straight from Claude, Cursor or Cline with the webdatatools MCP server.

Website & domain intelligence

Content for AI, LLMs and RAG

Search, video and social

Leads, jobs and company data

Developer, app and research data