Question 1

Why does it return the full job description when other Wellfound scrapers need an extra enrichment step?

Accepted Answer

Because of where the data is read from, not because of any trick. Wellfound is a Next.js site and every search page embeds its entire Apollo cache in the HTML — the job description, job type, normalised role, the employer's headcount bucket, tagline, logo and badges are all sitting in that blob already. This Actor parses the blob rather than the rendered page, so those fields cost no extra request. Scrapers that read the visible listing cards instead have to fetch each job's detail page to fill them in, which is why they expose it as a separate, extra-cost option. Measured 2026-09-08 against the category leader on the same query: description, job type, role title, company size and company tagline were empty on its default run and populated on all of ours.

Question 2

Can I search for remote jobs?

Accepted Answer

Yes — with the 'Remote jobs only' switch, not by typing 'remote' as the location. Wellfound has no remote index: the URL /role/l/<role>/remote redirects to the plain nationwide role page, which is a much broader search than the one you asked for and nothing in the response tells you it happened. For 'data scientist' that is the difference between 396 jobs and 4,981. This Actor refuses 'remote' as a location and says why, then filters on Wellfound's own remote flag when you use the switch.

Question 3

How many jobs can I actually get for one search?

Accepted Answer

Wellfound serves at most 15 pages of search results per search — roughly 500 to 600 jobs — however many matches it reports on the page. If you ask for more than a search can reach, the run returns everything it can and adds one free row saying so, with Wellfound's own stated total. To go deeper, narrow the search: a role plus a city reaches a different, smaller set than the role alone, and running several cities in one run is the intended way to cover more ground.

Question 4

Should I turn the proxy on?

Accepted Answer

No, and switching one on is the most likely way to break a run. Measured from inside an Apify run on 2026-09-08: the container's own address answered 200 with the full page, and Apify's datacenter proxy pool was served a Cloudflare 403 on the same request in the same run. Residential also works but buys nothing today. The input is left available in case your own runs are ever refused, and it defaults to off.

Question 5

Does it return candidate or applicant data?

Accepted Answer

No. Everything here comes from public job postings and public company profiles — the job, its pay range, its description, and the hiring company. No candidate profiles, no applicant information and no personal contact details are collected.

Question 6

What happens when a search returns nothing, or Wellfound refuses the request?

Accepted Answer

You get a free, unbilled row that says which. A search that genuinely matched nothing returns a 'no_results' marker; a refusal returns 'blocked'; a page whose structure no longer parses returns 'source_changed'. That distinction matters on a jobs feed, because zero rows otherwise reads as 'nobody is hiring' when the real answer may be that the source did not answer.

Field	Type
`title`	string\|null
`company_name`	string\|null
`compensation`	string\|null
`job_type`	string\|null
`locations`	array\|null
`remote`	boolean\|null
`posted_date`	string\|null
`company_size`	string\|null
`hiring_badges`	array\|null
`actively_hiring`	boolean\|null
`role`	string\|null
`years_experience_min`	integer\|null
`company_tagline`	string\|null
`company_url`	string\|null
`description`	string\|null
`matched_by`	string\|null
`requested_role`	string\|null
`requested_location`	string\|null
`source_url`	string\|null
`notice`	string\|null

Field	Type	Req	Default	Description
`role`	string	no	`"software engineer"`	A job role, e.g. 'software engineer', 'product designer', 'data scientist'. Type it normally — spacing and capitals do not matter. Kept forever alongside 'Roles' because saved tasks and API callers send it.
`roles`	array	no	`[]`	Pull several roles in ONE run, e.g. software engineer and product designer. Combined with 'Role' if you fill both. Every role is searched in every location, and 'Maximum results' applies to each role+location pair, so adding one can never truncate the others.
`location`	string	no	`"san francisco"`	A city, e.g. 'san francisco', 'new york', 'london'. Leave it out to search the role nationwide. Do NOT type 'remote' — Wellfound redirects that to the nationwide page and silently widens the search; use 'Remote jobs only' below instead.
`locations`	array	no	`[]`	Pull several cities in ONE run. Combined with 'Location' if you fill both. Roles and locations combine as a product: 3 roles across 4 cities is 12 searches in one run.
`remoteOnly`	boolean	no	`false`	Keep only jobs Wellfound flags as remote. This filters the search results rather than changing the search, because Wellfound has no remote-only index.
`maxResults`	integer	no	`100`	Cap on the number of jobs returned PER role+location pair, not per run — so adding a city cannot silently truncate the ones before it. Wellfound serves at most 15 pages of search results (roughly 500-600 jobs) per search whatever total it reports; the run says so on the row when you ask for more than it can reach.
`proxyConfiguration`	object	no	`{"useApifyProxy":false}`	Leave OFF. Measured 2026-09-08: Wellfound answers Apify's plain egress normally and serves the datacenter proxy pool a Cloudflare 403, so switching a proxy on is what breaks this actor. Residential also works if your own runs ever start getting refused.