How to Scrape Remote Jobs from Remote OK, We Work Remotely and More
How to Scrape Remote Jobs from Remote OK, We Work Remotely and More Remote job boards overlap a lot: the same role often appears on Remote OK, We Work Remotely, Himalayas, Jobicy or Arbeitno...
Résumé
How to Scrape Remote Jobs from Remote OK, We Work Remotely and More Remote job boards overlap a lot: the same role often appears on Remote OK, We Work Remotely, Himalayas, Jobicy or Arbeitnow. If you only subscribe to one board you miss roles; if you subscribe to all five you drown in duplicates. A small aggregator that de-duplicates across boards and writes one clean schema is usually the better setup. This guide shows how to build that export without writing five scrapers. You will use the Remote Jobs Aggregator on Apify. It reads several public remote boards in one run, applies keyword, region, date and salary filters, de-duplicates cross-board postings, and returns salary and a full description in a single schema. By the end of this article you will have a CSV or JSON file on your machine, and a short Python snippet you can rerun or schedule. The same Actor is also callable from JavaScript and from AI agents through the Apify MCP server. What you need An Apify account. The Free plan is enough to try a small run. A list of inputs for the Actor (URLs, IDs or search terms — details in the steps below). Optional: Python 3 with the apify-client package if you want to automate the run. No account on any of the boards is required. Start with one board and a low max jobs value, then turn the rest on. How to run it in the Apify Console Step 1: Open the Actor Go to https://apify.com/veenkes/veenkes-remote-jobs and click Try for free. Step 2: Pick boards Choose Remote OK, We Work Remotely, Himalayas, Jobicy and/or Arbeitnow. You can start with a single source. Step 3: Filter Add keywords, exclude words, a location or region, a posted since date, or salary only if you only want postings that publish a range. Set max jobs to 20 for a first look. Step 4: Export Run the Actor and download CSV or JSON. Keep include description on if you plan to search the body later; turn it off for a lighter file. De-duplication and source balancing are there so one noisy board does not dominate the file. You pay only for jobs that are saved after filters and de-duplication. How to run it from Python Install the official client and call the Actor by its Store id veenkes/veenkes-remote-jobs. Replace YOUR_APIFY_TOKEN with a token from Apify Console > Integrations. Do not commit the token to a public repository. pip install apify-client from apify_client import ApifyClient client = ApifyClient("YOUR_APIFY_TOKEN") run = client.actor("veenkes/veenkes-remote-jobs").call(run_input={ "sources": [ "remoteok", "weworkremotely", "himalayas" ], "maxJobs": 50, "includeDescription": True }) # Write every dataset item, then export from the Console or keep going in code. for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) The JavaScript client (apify-client on npm) uses the same Actor id and the same input object. You can also start the run with a plain HTTP POST to the Apify API if you prefer. Sample output Here is a shortened example of one dataset record (field values are illustrative of the schema, taken from a real sample run shape): { "source": "remoteok", "sourceName": "Remote OK", "jobId": "1137719", "title": "Patient Care Specialist I", "company": "Boston Scientific", "companyLogo": null, "url": "https://remoteOK.com/remote-jobs/remote-patient-care-specialist-i-boston-scientific-1137719", "applyUrl": "https://remoteOK.com/remote-jobs/remote-patient-care-specialist-i-boston-scientific-1137719", "location": "Worldwide", "remote": true, "employmentType": null, "seniority": null, "category": null, "tags": [ "design", "sys admin", "education" ], "salaryMin": null, "salaryMax": null, "salaryCurrency": null, "salaryPeriod": null, "publishedAt": "2026-11-11T08:00:08.000Z", "expiresAt": null, "descriptionText": "Additional Location(s): N/A\n\nDiversity - Innovation - Caring - Global Collaboration - Winning Spirit - High Performance\n\nAt Boston Scientific, we’ll give you the opportunity to h…", "scrapedAt": "2026-11-12T21:29:43.129Z" } Once the run has finished, open the dataset in the Console and use Export > CSV if a spreadsheet is your destination. JSON is usually better for code and for language models. What to use the data for Job seekers build a personal daily digest. Recruiters watch a niche (for example 'data engineer' plus a region). Analysts study which boards publish salaries and how often. A newsletter or Slack bot can run on a schedule and post only jobs newer than yesterday. Pricing Pay-per-result pricing starts at $1.20 per 1,000 saved jobs on the Apify Free plan, with lower unit prices on paid Apify plans, plus a small per-run start fee. Always check the live pricing on the Actor page, because plans and unit prices can change. For a first test, keep the input tiny so you can inspect the schema before you scale up. Scheduling and automations In the Apify Console you can schedule the Actor (daily or hourly) and leave the same input in place. For incremental jobs, prefer a "since" or "posted after" style filter when the Actor offers one, so you are not paying to re-collect old rows. When a run finishes you can send a webhook, or connect the Actor in Zapier, Make or n8n. AI agents can discover and call veenkes/veenkes-remote-jobs through Apify's MCP server using the same input. Good practices and limits Give credit to the original board when you reshare a posting, and do not republish a competing job site wholesale. Follow each board's terms. The Actor is not affiliated with Remote OK, We Work Remotely, Himalayas, Jobicy or Arbeitnow. If a run returns fewer rows than you expected, check the input caps, language or country filters, and the Actor log. A zero-row run is usually a filter or an unavailable source, not a silent crash — read the log before you increase limits. Next step Open the Actor and run a small job: Remote Jobs Aggregator: Remote OK, WWR, Himalayas & Jobicy. If you later want this on a schedule, save the input that worked, add a date filter where it applies, and export CSV automatically from the dataset or from the API snippet above.