# Wellfound Jobs Scraper (`romy/wellfound-jobs-scraper`) Actor

Scrape Wellfound (AngelList) startup jobs by role, location or both, remote-only, with optional full detail: description, structured salary, company website. No login, no browser.

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

## Pricing

from $0.78 / 1,000 job listings

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Wellfound Jobs Scraper

Scrape [Wellfound](https://wellfound.com) (formerly AngelList Talent) startup
jobs by role, by location, or both -- with optional full job detail
(description, structured salary, company website). Plain HTTP, no login, no
browser, no proxy needed for listings.

### Why

Wellfound has no public API. This reads its own server-rendered pages,
verified live from a home IP and from Apify's direct, datacenter and
residential IPs.

- **Any role or location works**, not just the ~12 roles / ~10 cities
  Wellfound links in its navigation. `backend-engineer`, `kubernetes`,
  `berlin`, `toronto`, `singapore` were all verified. Type a name; it is
  lowercased and hyphenated for you.
- **Role x location is a real combined filter** (Wellfound's own
  `/role/l/<role>/<location>` listing), not two searches intersected after
  the fact. Give both lists and every pair is scraped.
- **Remote-only is honest about what exists.** Wellfound has a remote listing
  per *role*, and a global remote feed -- but none per *location*. So
  `remoteOnly` works with roles alone, or with nothing else set (global feed),
  and is rejected with `locationSlugs` instead of silently ignored.
- **Detail is parsed from structured data**: every job page embeds a
  schema.org `JobPosting` block, so salary comes back as real numbers
  (currency / min / max / unit), not scraped text.
- **Duplicates are dropped** across sources, and `maxJobs` counts unique jobs.

### Input

| Field               | Type       | Default | Description                                                                                         |
| ------------------- | ---------- | ------- | --------------------------------------------------------------------------------------------------- |
| `roleSlugs`         | `string[]` | --      | Roles, e.g. `software-engineer`, `Product Manager`.                                                 |
| `locationSlugs`     | `string[]` | --      | Locations, e.g. `san-francisco`, `berlin`. Alone: all roles there. With `roleSlugs`: each pair.     |
| `remoteOnly`        | `boolean`  | `false` | Remote jobs only. Roles alone, or no lists (global remote feed). Not allowed with `locationSlugs`.  |
| `maxPagesPerSource` | `integer`  | `5`     | Listing pages per role/location (~30-50 jobs each; popular roles run 40-90+ pages).                 |
| `maxJobs`           | `integer`  | `100`   | Stop after this many unique jobs in total.                                                          |
| `scrapeJobDetail`   | `boolean`  | `false` | Also open each job for description, structured salary, date posted, industry, company website/logo. |

At least one of `roleSlugs`, `locationSlugs` or `remoteOnly` is required.

### Output

One dataset row per job.

Always: `id`, `slug`, `url`, `title`, `companyName`, `companySlug`,
`employmentType`, `salaryText`, `equityText`, `locationText`, `postedText`,
`source` (which role/location it came from), `sourcePage`.

`salaryText`, `equityText` and `locationText` are the strings Wellfound shows
(`"$100k – $180k"`, `"0.05% – 0.25%"`, `"Remote only • Canada + 3"`) and are
`null` when a job doesn't show that item. Enable `scrapeJobDetail` for
structured numbers.

With `scrapeJobDetail`: `description` (simple HTML), `datePosted` (ISO),
`industry`, `companyWebsite`, `companyLogo`, `locations`, `salaryCurrency`,
`salaryMin`, `salaryMax`, `salaryUnit`, and `detailError` (set, with the detail
fields `null`, if that job's page could not be read).

### Pricing

Pay-Per-Event, standard tiered ladder
(FREE/BRONZE/SILVER/GOLD/PLATINUM/DIAMOND = 100/92/85/78/72/68%):

| Event                                                | FREE tier |
| ---------------------------------------------------- | --------- |
| `job-listing-scraped` (per job row)                  | $0.001    |
| `job-detail-scraped` (per job whose detail was read) | $0.002    |

A job with full detail costs $0.003 at the FREE tier. A failed detail fetch is
not charged.

### Known limitations

- **No company profile data** (size, funding, about page): Wellfound returns
  403 for `/company/...` on every IP tier tested, including residential.
- **No salary / equity / experience / job-type filters**: they exist only in
  Wellfound's interactive search, which sits behind a Cloudflare challenge.
  Filter the output instead.
- Detail pages are sometimes refused (403) through Apify's *datacenter* proxy
  tier while working on direct and residential; the actor retries, and reports
  `detailError` if it still fails.
- Listing counts move as Wellfound updates; `postedText` is relative
  ("1 week ago") -- use `scrapeJobDetail` for an exact `datePosted`.

# Actor input Schema

## `roleSlugs` (type: `array`):

Role names/slugs, e.g. software-engineer, product-manager, devops-engineer. Any role works, not just Wellfound's featured ones (lowercase, hyphenated; spaces are converted). With locationSlugs, every role x location pair is scraped.

## `locationSlugs` (type: `array`):

City/country slugs, e.g. san-francisco, berlin, singapore, toronto. Global, not US-only. Alone: all roles in that location. With roleSlugs: each role x location pair.

## `remoteOnly` (type: `boolean`):

Only remote-eligible jobs. Works with roleSlugs alone (a role's remote listing) or with no roles/locations at all (Wellfound's global remote feed). Not available for locations: Wellfound has no remote filter there, so this is rejected with locationSlugs.

## `maxPagesPerSource` (type: `integer`):

Listing pages to read per role/location source (~30-50 jobs per page). Popular roles run 40-90+ pages.

## `maxJobs` (type: `integer`):

Stop after this many unique jobs across all sources (duplicates across sources are counted once).

## `scrapeJobDetail` (type: `boolean`):

Also open each job's page for the full description (HTML), structured salary (currency/min/max), date posted, industry, company website and logo. Slower and billed per detail.

## Actor input object example

```json
{
  "roleSlugs": [
    "software-engineer"
  ],
  "remoteOnly": false,
  "maxPagesPerSource": 5,
  "maxJobs": 100,
  "scrapeJobDetail": false
}
```

# Actor output Schema

## `dataset` (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 = {
    "roleSlugs": [
        "software-engineer"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("romy/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 = { "roleSlugs": ["software-engineer"] }

# Run the Actor and wait for it to finish
run = client.actor("romy/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 '{
  "roleSlugs": [
    "software-engineer"
  ]
}' |
apify call romy/wellfound-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,romy/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/d5Al1htvFcPUU5aXf/builds/kUreH8KdQWVL8nBvF/openapi.json