Greenhouse, Lever & Ashby Jobs Scraper avatar

Greenhouse, Lever & Ashby Jobs Scraper

Pricing

$1.90 / 1,000 greenhouse, lever & ashby jobs scraper records

Go to Apify Store
Greenhouse, Lever & Ashby Jobs Scraper

Greenhouse, Lever & Ashby Jobs Scraper

Scrapes open job postings, salary ranges, remote flags, and tech stack keywords directly from Greenhouse, Lever, and Ashby boards. Accepts mixed company slugs in one run and outputs flat JSON or CSV for Clay and n8n.

Pricing

$1.90 / 1,000 greenhouse, lever & ashby jobs scraper records

Rating

0.0

(0)

Developer

Kim SungHyun

Kim SungHyun

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

8 hours ago

Last modified

Features

Limited permissions

Share

Pulls live job listings straight from public Greenhouse, Lever, and Ashby career boards without spinning up a headless browser. Give it a list of company board slugs (vercel, linear, cloudflare) and it resolves whichever of the three ATS platforms each company uses, normalizes the postings into a single schema, and tags mentioned tools and compensation ranges.

I built this mainly for outbound lists in Clay and n8n where you have a column of SaaS company slugs and want to see who is actively hiring security engineers, data engineers, or enterprise AEs before sending outreach.

How ATS auto-detection works

When atsProvider is set to "auto", each slug is checked against the public JSON endpoints in order:

  1. Greenhouse (boards-api.greenhouse.io/v1/boards/{slug}/jobs?content=true)
  2. Ashby (api.ashbyhq.com/posting-api/job-board/{slug}?includeCompensation=true)
  3. Lever (api.lever.co/v0/postings/{slug}?mode=json)

If you already know every slug in your batch belongs to one provider, set atsProvider to "greenhouse", "ashby", or "lever" to save the extra lookup requests. Dead slugs or 404 boards return zero rows and cost nothing.

Input example

{
"companySlugs": ["vercel", "linear", "cloudflare"],
"atsProvider": "auto",
"departmentFilter": "",
"maxJobsPerCompany": 20
}

Set departmentFilter to a plain substring like "security", "data", or "sales" if you only want roles matching a specific team. Because billing is per extracted row, filtering inside the actor is cheaper than pulling all 300 roles at a big company and filtering downstream.

Output sample

{
"company_slug": "vercel",
"ats_platform": "greenhouse",
"job_id": "5419284004",
"job_title": "Staff Security Engineer",
"department_raw": "Security",
"department_category": "Security_Compliance",
"location": "Remote - US",
"is_remote": true,
"compensation_summary": "$196,000 - $294,000",
"tech_stack_signals": ["AWS", "Go", "Kubernetes", "Next.js", "SOC2", "TypeScript"],
"company_open_roles_total": 48,
"hiring_intent_score": 0.89,
"job_url": "https://job-boards.greenhouse.io/vercel/jobs/5419284004",
"published_at": "2026-11-10T18:22:11-05:00",
"description_excerpt": "We are looking for a Staff Security Engineer to own cloud infrastructure security..."
}

Pricing and edge cases

Billing uses Pay-Per-Event at $1.90 per 1,000 extracted job rows ($0.0019 per job-signal-extracted event), with no start fee.

A few practical things worth knowing before running big batches:

  • A company's ATS board slug does not always match its domain name (for instance, getdbt vs dbtlabs). If a slug 404s across all three providers, check the URL of their careers page once.
  • Greenhouse embeds raw HTML entities inside its JSON content field; the parser strips tags before scanning for the 35+ stack keywords (Snowflake, Databricks, dbt, Kubernetes, Terraform, Salesforce, HubSpot, SOC2, HIPAA, etc.).
  • Personal webmail addresses (gmail.com, yahoo.com, naver.com, etc.) and national ID patterns found inside job text are automatically redacted so downstream CRM imports stay clean.