# Wellfound Jobs Scraper — Startup Roles API (`noahadler/wellfound-jobs`) Actor

Scrape Wellfound (AngelList Talent) startup job listings by keyword and optional location. Title, company, salary label, remote flag, locations and job URL. HTTP-only via SEO role pages + Apollo **NEXT\_DATA**.

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

## Pricing

from $2.00 / 1,000 jobs

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?

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 Startup Jobs Scraper

**Wellfound** (formerly AngelList Talent) startup jobs scraper by **keyword / role** + optional **location**: title, startup name, **salary + equity**, remote flag, locations, and absolute job URL — one clean Dataset row per listing.

Built for **startup recruiting intel**, **equity benchmarking**, **lead gen**, and PPE-friendly exports. No browser automation — HTTP + Chrome TLS fingerprint against Wellfound SEO role pages (`/role/…`) and the embedded Apollo `__NEXT_DATA__` store.

> Wellfound SSR embeds Apollo entities (`JobListingSearchResult`, `StartupResult`) with compensation strings like `$120k – $200k • 0.01% – 0.15%`. This Actor GETs the public SEO landing pages with `curl_cffi` (`chrome124`), maps salary vs equity into separate fields, and paginates with `?page=N` until `maxJobs`. **Residential proxy is optional** (often works without proxy; use RESIDENTIAL if you hit Security Check).

**Why this Actor:** Startup + equity schema (not generic cheap jobs) · Remote / city SEO URLs · Clean salary/equity split · No Playwright · No email-harvesting claims · Cheap PPE-friendly alternative to bloated multi-board Actors · CSV / API / webhooks ready

**Store icon:** set the Actor icon in Apify Console (PNG not shipped in this repo; `assets/` reserved for later).

***

### Table of contents

1. [What this Actor does](#what-this-actor-does)
2. [What you get](#what-you-get)
3. [Features](#features)
4. [Input](#input)
5. [Output example](#output-example)
6. [Output fields](#output-fields)
7. [Quick start (API)](#quick-start-api)
8. [Use cases](#use-cases)
9. [Limitations](#limitations)
10. [FAQ](#faq)
11. [Keywords](#keywords)

***

### What this Actor does

| Step | Action |
|------|--------|
| 1 | Accept `keyword` + optional `location` / `maxJobs` |
| 2 | Map to SEO URL: `/role/{slug}`, `/role/r/{slug}` (Remote), or `/role/l/{slug}/{city}` |
| 3 | `GET` HTML with Chrome impersonate |
| 4 | Parse `__NEXT_DATA__` → Apollo `seoLandingPageJobSearchResults` |
| 5 | Expand `StartupResult.highlightedJobListings` → Dataset rows (salary + equity) |
| 6 | Paginate `?page=N` until `maxJobs` or last page |

**Input:** keyword, location, max jobs, proxy.\
**Output:** one Dataset row per job.

***

### What you get

**Job / startup**

- `jobId`, `title`, `jobType`, `jobUrl`
- `companyName`, `companySlug`, `companySize`, `companyHighConcept`, `companyLogoUrl`

**Compensation (equity angle)**

- `compensation` (raw), `salaryLabel`, `equityLabel`

**Location / remote**

- `location`, `locationNames`, `remote`, `remoteKind`

**Meta**

- `keyword`, `locationQuery`, `scrapedAt`, `error`, `errorMessage`

***

### Features

| Capability | Detail |
|------------|--------|
| **Keyword + location** | e.g. `software engineer` + `Remote` / `San Francisco` |
| **Equity-aware schema** | Splits Wellfound `compensation` into salary vs equity % |
| **No browser** | `curl_cffi` impersonate `chrome124` + `browserforge` headers |
| **Apollo SSR** | Reads embedded search results — no fragile CSS selectors |
| **Proxy-aware** | Optional Apify proxy (RESIDENTIAL if Security Check / 403) |
| **PPE-friendly** | Listings only — no email harvesting claims |

***

### Input

| Field | Required | Description |
|-------|----------|-------------|
| `keyword` | Yes | Role keyword (maps to Wellfound SEO slug) |
| `location` | No | `Remote`, city name, or empty for all |
| `maxJobs` | No | 1–200 (default 40) |
| `proxyConfiguration` | No | Default off; enable RESIDENTIAL if blocked |

***

### Output example

```json
{
  "jobId": "4716782",
  "title": "Software Engineer",
  "companyName": "Boom",
  "companySlug": "boom-app",
  "companySize": "SIZE_11_50",
  "companyHighConcept": "Modern rental financial services for property managers and renters",
  "location": "Austin",
  "locationNames": ["Austin"],
  "remote": false,
  "compensation": "$120k – $200k • 0.01% – 0.15%",
  "salaryLabel": "$120k – $200k",
  "equityLabel": "0.01% – 0.15%",
  "jobType": "full-time",
  "jobUrl": "https://wellfound.com/jobs/4716782-software-engineer",
  "keyword": "software engineer",
  "locationQuery": null,
  "scrapedAt": "2026-09-21T20:00:00Z",
  "error": false,
  "errorMessage": null
}
```

***

### Output fields

See Dataset schema in Console. Key fields: `title`, `companyName`, `salaryLabel`, `equityLabel`, `remote`, `jobUrl`. Soft-fail rows set `error=true` with an actionable `errorMessage` (403 / unknown role / parse failure).

***

### Quick start (API)

```bash
curl "https://api.apify.com/v2/acts/noahadler~wellfound-jobs/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"keyword":"software engineer","location":"Remote","maxJobs":20}'
```

***

### Use cases

- Startup / VC talent pipeline monitoring
- Equity + salary band benchmarking by role
- Remote-first hiring market scans
- Competitive hiring intel for niche roles

***

### Limitations

- Uses **public SEO role pages** only — arbitrary free-text that is not a Wellfound SEO role returns 404 soft-fail
- GraphQL live search is behind Security Check (not used)
- Equity / salary only when Wellfound publishes them on the card
- No full JD HTML or applicant PII
- Rate limits / Security Check may require RESIDENTIAL proxy

***

### FAQ

**Does this need a browser?** No — HTTP + `__NEXT_DATA__`.

**Remote vs city?** `location=Remote` → `/role/r/…`; city → `/role/l/{role}/{city}`; empty → all locations.

**Why equity fields?** Wellfound’s differentiator vs generic job boards is startup equity in the compensation string — this Actor splits it explicitly.

***

### Keywords

Wellfound, AngelList Talent, AngelList jobs, startup jobs scraper, equity jobs API, remote startup jobs, Wellfound scraper, Apify jobs actor

# Actor input Schema

## `keyword` (type: `string`):

Wellfound role keyword (e.g. software engineer, product manager, machine learning engineer). Mapped to /role/{slug} SEO landing pages.

## `location` (type: `string`):

Optional. Use Remote for remote-only (/role/r/…), or a city slug like San Francisco / New York (/role/l/{role}/{city}). Leave empty for all locations.

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

Maximum job rows to collect (1–200). Paginated via Wellfound ?page=N (~20 startups / page, multiple jobs each).

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

Optional. Wellfound SEO pages often work without proxy; RESIDENTIAL can help if you hit Security Check / 403.

## Actor input object example

```json
{
  "keyword": "software engineer",
  "location": "Remote",
  "maxJobs": 40,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `jobs` (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 = {
    "keyword": "software engineer",
    "location": "Remote"
};

// Run the Actor and wait for it to finish
const run = await client.actor("noahadler/wellfound-jobs").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 = {
    "keyword": "software engineer",
    "location": "Remote",
}

# Run the Actor and wait for it to finish
run = client.actor("noahadler/wellfound-jobs").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 '{
  "keyword": "software engineer",
  "location": "Remote"
}' |
apify call noahadler/wellfound-jobs --silent --output-dataset

```

## MCP server setup

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

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/nE0DqrHgumyMptOzz/builds/egfa75Q3Orgr1Uffw/openapi.json