# Wellfound Remote Jobs & Compensation Scraper (`shawnle204/wellfound-jobs-scraper`) Actor

Scrapes remote startup job listings, salary ranges, and equity ranges from Wellfound (formerly AngelList).

- **URL**: https://apify.com/shawnle204/wellfound-jobs-scraper.md
- **Developed by:** [Shawn L](https://apify.com/shawnle204) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Wellfound Remote Jobs & Compensation Scraper

Extract **remote** startup job listings from [Wellfound](https://wellfound.com) (formerly AngelList Talent) — including **salary ranges, equity ranges, and remote eligibility** — as clean, structured data ready for comp benchmarking, lead generation, or market research.

### Why use this Actor

Wellfound is one of the few job boards where startups routinely publish real salary *and* equity ranges — and it runs a dedicated, fully paginated remote-jobs search covering every role. That makes it a uniquely valuable dataset for:

- **Compensation benchmarking** — build salary/equity bands for remote roles, by role or region.
- **Sales & recruiting leads** — find actively-hiring remote-friendly startups.
- **Market research** — track remote-hiring trends across the startup ecosystem over time.

This Actor reads Wellfound's own structured job data (the same JSON that powers its website) rather than scraping visible text off the page, so fields like salary and equity come back exactly as Wellfound reports them — no fragile guesswork.

### What you get

Each result is one job listing with these fields:

| Field | Description | Example |
|---|---|---|
| `job_title` | Job title | `"Senior Software Engineer"` |
| `company_name` | Hiring company | `"Oklo"` |
| `remote_status` | `Remote`, `Hybrid`, or `On-site` | `"Remote"` |
| `location` | Remote eligibility, then base location | `"Remote (United States) • Santa Clara"` |
| `salary_range` | Reported salary range | `"$120k – $160k"` |
| `equity_range` | Reported equity range | `"0.1% – 0.5%"` |
| `posted_date` | Date the listing went live | `"2026-08-12"` |
| `job_url` | Direct link to the job listing | `"https://wellfound.com/company/oklo/jobs/4579450-software-engineer"` |
| `company_url` | Company's Wellfound profile | `"https://wellfound.com/company/oklo"` |

`location` leads with where the role can be worked *from* (Wellfound's own UI convention) rather than the company's home city, since that's the fact that actually matters once a job is remote.

### How it works

Wellfound's job pages are server-rendered with Next.js and hydrated from an internal Apollo GraphQL cache that ships embedded in the page HTML (`<script id="__NEXT_DATA__">`). This Actor:

1. Opens each start URL with a headless, residentially-proxied browser (Wellfound puts a Cloudflare bot-check in front of plain HTTP requests, so real browser rendering is required for reliable access).
2. Reads the embedded JSON payload directly — the same structured data Wellfound's own frontend uses — instead of parsing visible page text with CSS selectors. This makes extraction robust to visual redesigns.
3. Follows Wellfound's built-in `?page=` pagination on search pages until it hits the page limit or your `maxItems` cap.
4. Pushes one normalized record per job listing to the dataset.

Images, fonts, and stylesheets are blocked during rendering to keep runs fast and light on proxy bandwidth.

#### Scope: remote by default

The default start URL, `https://wellfound.com/remote`, is Wellfound's own remote-jobs search — every role, fully paginated (thousands of listings). `https://wellfound.com/role/r/<role>` narrows to one role and is also remote-filtered. The one supported pattern that is **not** remote-filtered is `https://wellfound.com/role/l/<role>/<location>` — an in-person search scoped to a specific city. Only add one of those yourself if you deliberately want on-site/hybrid results mixed in too.

### Input

| Field | Type | Required | Description |
|---|---|---|---|
| `startUrls` | array | Yes | Wellfound URLs to crawl. Defaults to `https://wellfound.com/remote`. See "Scope" above for which URL patterns stay remote-only vs. not. Avoid the plain `https://wellfound.com/jobs` homepage as a volume source — it only returns Wellfound's small, curated "featured jobs" selection (~47 listings, no pagination, the same fixed set every run, mixing remote and on-site). |
| `keywordSearch` | string | No | A remote role keyword (e.g. `"Product Manager"`) that gets slugified into a Wellfound remote role-search URL and added to the crawl. Wellfound organizes listings by role taxonomy rather than free-text search, so this is a best-effort convenience, not a full-text search. |
| `maxItems` | integer | No | Hard cap on the total number of job listings returned. Default `200`. |
| `proxyConfiguration` | object | No | Defaults to the Residential Proxy group, required to reliably pass Wellfound's Cloudflare bot-check. |

#### Example input

```json
{
  "startUrls": [
    { "url": "https://wellfound.com/remote" },
    { "url": "https://wellfound.com/role/r/product-manager" }
  ],
  "maxItems": 500
}
```

### Proxy

This Actor requires an [Apify Residential Proxy](https://apify.com/proxy) group to reliably pass Wellfound's bot detection. Running without a paid proxy plan will result in a high rate of blocked requests.

### Compliance note

This Actor only requests publicly accessible Wellfound pages that are not disallowed by [wellfound.com/robots.txt](https://wellfound.com/robots.txt). You are responsible for using the scraped data in accordance with Wellfound's Terms of Service and any applicable data protection laws in your jurisdiction.

### Support

Found a field that stopped mapping correctly, or a page shape this Actor doesn't recognize yet? Wellfound occasionally changes its internal data shape — open an issue with the URL you tried and we'll take a look.

# Actor input Schema

## `startUrls` (type: `array`):

Wellfound job pages to crawl. Defaults to https://wellfound.com/remote - Wellfound's own remote-jobs search, covering every role and fully paginated (thousands of listings). To narrow to one remote role, use https://wellfound.com/role/r/software-engineer instead (also remote-filtered). The one exception is location pages like https://wellfound.com/role/l/software-engineer/new-york - these are NOT remote-filtered (in-person, scoped to a city), so only add one if you deliberately want on-site/hybrid results too. Avoid the plain https://wellfound.com/jobs homepage as a volume source - it only returns Wellfound's small, curated 'featured jobs' selection (~47 listings, no pagination, same fixed set every run, mixing remote and on-site).

## `keywordSearch` (type: `string`):

Optional remote job-role keyword, e.g. 'Software Engineer' or 'Product Manager'. It is slugified and added as a Wellfound remote role-search start URL (https://wellfound.com/role/r/<slug>) alongside Start URLs. Wellfound organizes listings by role taxonomy rather than free-text search, so this is a best-effort mapping - check the Wellfound site for the exact role slug if results look sparse.

## `maxItems` (type: `integer`):

Maximum number of job listings to scrape across all start URLs, applied as a hard cap on top of Wellfound's own pagination.

## `proxyConfiguration` (type: `object`):

Defaults to the Residential Proxy group, which is required to reliably pass Wellfound's Cloudflare bot-check. Switch to a Datacenter group only for testing/debugging - it's far more likely to get blocked and isn't recommended for real runs.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://wellfound.com/remote"
    }
  ],
  "maxItems": 200,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `jobListings` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "startUrls": [
        {
            "url": "https://wellfound.com/remote"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("shawnle204/wellfound-jobs-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "startUrls": [{ "url": "https://wellfound.com/remote" }] }

# Run the Actor and wait for it to finish
run = client.actor("shawnle204/wellfound-jobs-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "startUrls": [
    {
      "url": "https://wellfound.com/remote"
    }
  ]
}' |
apify call shawnle204/wellfound-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,shawnle204/wellfound-jobs-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/21WZhMMS6Rgu7z54S/builds/KpKqqlYEdyxZMcEG4/openapi.json