We Work Remotely Jobs Scraper

Scrape remote job listings from We Work Remotely (weworkremotely.com) into clean, structured data. Pull the whole live board or filter by category and keywords in bulk — one tidy row per job with the title, company, category, job type, location, skills, company website, apply URL, posted date and the full job description.

We Work Remotely is one of the largest remote-work job boards. This actor turns its listings into a spreadsheet/JSON dataset you can search, filter, dedupe and load anywhere — no login, no API key, no browser needed.

What you get (data fields)

Field	Description
title	Job title (e.g. "Senior Full-Stack Developer")
company	Hiring company name
companyLogo	Company logo image URL
category	We Work Remotely category (e.g. "Full-Stack Programming", "Design")
jobType	Employment type — "Full-Time", "Contract", "Part-Time"
region	Where the role is open — "Anywhere in the World" or a country/state
country / state	Country / state when the listing specifies one
skills	List of skills/tags the company tagged (when the listing provides them)
headquarters	Company headquarters location
companyUrl	Company website (when the listing provides one)
url	We Work Remotely job posting URL (apply here)
guid	Stable unique job identifier (used for de-duplication)
publishedAt	When the job was posted
expiresAt	When the listing expires
description	Full job description as clean plain text
descriptionHtml	Full job description as raw HTML
sourceCategory	The category feed this row came from (null = whole-board feed)
scrapedAt	Timestamp of the scrape (ISO 8601)

How it works

We Work Remotely publishes public RSS feeds — the whole-board feed and one feed per category — so the actor reads structured data straight from the source, never fragile page selectors. It fetches one feed per category you list plus the whole-board feed, then merges and de-duplicates by job, so a broad category list pulls essentially the entire active board in a single run and you're never charged twice for the same posting.

Note on field coverage: the whole-board feed and the individual category feeds carry the same fields, with one exception — the broad remote-programming-jobs feed is a leaner aggregate that omits jobType, skills, country/state and expiresAt. Those jobs still come through in full via the whole-board feed and the specific remote-full-stack-programming-jobs / remote-front-end-programming-jobs / remote-back-end-programming-jobs feeds, so keeping "Also scrape the whole-board feed" on (the default) guarantees every job gets the full field set. Separately, a handful of fields — companyLogo, companyUrl, skills, country/state — are only filled when the individual company provided them, so they're populated on some rows and empty on others regardless of which feed a row came from.

Input

Everything is optional — run it with the defaults to grab the whole board. Example:

{
  "categories": [
    "remote-programming-jobs",
    "remote-design-jobs",
    "remote-customer-support-jobs",
    "all-other-remote-jobs"
  ],
  "includeMainFeed": true,
  "searchTerms": ["senior", "react", "python"],
  "jobTypes": ["Full-Time"],
  "maxResults": 1000
}

• categories — category feeds to scrape (leave empty to scrape only the whole-board feed). Valid slugs: remote-full-stack-programming-jobs, remote-front-end-programming-jobs, remote-back-end-programming-jobs, remote-programming-jobs, remote-devops-sysadmin-jobs, remote-design-jobs, remote-customer-support-jobs, remote-sales-and-marketing-jobs, remote-management-and-finance-jobs, remote-product-jobs, all-other-remote-jobs.
• includeMainFeed — also fetch the whole-board feed of the newest jobs across every category (default true; guarantees the full field set even for jobs found only via the leaner remote-programming-jobs feed).
• searchTerms — optional keywords; a job is kept if it matches any term (case-insensitive) in its title, company, category, region or description.
• jobTypes — optional list, e.g. ["Full-Time", "Contract"].
• maxResults — cap on the number of unique jobs returned (billed per row).
• proxyConfiguration — Apify Residential proxy is used only as a fallback if a request is blocked.

Output sample

{
  "title": "Data Governance & Platform Manager",
  "company": "LawnStarter",
  "companyLogo": "https://wwr-pro.s3.amazonaws.com/logos/0171/5865/logo.gif",
  "category": "All Other Remote",
  "jobType": "Full-Time",
  "region": "Anywhere in the World",
  "country": null,
  "state": null,
  "skills": [],
  "headquarters": "Brazil",
  "companyUrl": "http://lawnstarter.com",
  "url": "https://weworkremotely.com/remote-jobs/lawnstarter-data-governance-platform-manager",
  "guid": "https://weworkremotely.com/remote-jobs/lawnstarter-data-governance-platform-manager",
  "publishedAt": "Fri, 17 Jul 2026 20:07:06 +0000",
  "expiresAt": "Sun, 16 Aug 2026 20:07:06 +0000",
  "description": "Headquarters: Brazil\nURL: http://lawnstarter.com\n\nAbout LawnStarter ...",
  "sourceCategory": null,
  "scrapedAt": "2026-07-20T00:00:00Z"
}

Use cases

• Job aggregators & niche boards — feed a curated remote-jobs site or newsletter with fresh listings.
• Recruiting & sourcing — monitor which companies are hiring remotely and in which categories.
• Market & hiring research — track remote-hiring trends, in-demand skills, employment types and company locations over time.
• Lead generation — build a list of companies actively hiring (with their websites) for outreach.

FAQ

Do I need an account or API key for We Work Remotely? No. The actor reads public RSS feeds — no login required.

How many jobs will I get? The feeds return We Work Remotely's live listings across the selected categories. Merged and de-duplicated, a full run pulls essentially the whole active board (typically a few hundred unique jobs). Use maxResults to cap it.

Why are skills, country/state or companyLogo sometimes empty? Those fields are only filled when the individual company provided them — not every listing does — so they appear on some rows and not others (this is the same on the whole-board and category feeds, it's a per-listing gap, not a feed limitation). Core fields like jobType, region and expiresAt are present on essentially every row; the one exception is the broad remote-programming-jobs aggregate feed, which is leaner — keep includeMainFeed on (the default) so those jobs still come through with the full data.

Can I filter to specific roles? Yes — add keywords to searchTerms (matches any term) and/or narrow jobTypes.

Is it billed per job? Yes — pay-per-result: you're charged once per unique job row returned. Duplicate postings across categories are removed before billing.