Greenhouse ATS Scraper - Jobs From Hundreds of Company Boards

Extract job listings straight from Greenhouse, the applicant tracking system used by a large share of venture-backed and mid-market technology companies. Instead of scraping an aggregator, this pulls each company's own board, so the data is first-hand, complete and current.

Give it a list of company slugs and it walks them in parallel.

What you get per job

Field	Example
title	Staff Machine Learning Engineer
companyName, companySlug	Stripe, stripe
departments	["Engineering", "Infrastructure"]
offices	["San Francisco", "Remote - US"]
location	posting location as shown on the board
firstPublished, updatedAt	when the role went live and last changed
metadata	custom fields the company defined on its board
jobId	stable Greenhouse identifier
absoluteUrl	direct link to the posting

Input

• companySlugs - the Greenhouse board identifiers, e.g. ["stripe", "anthropic", "figma"]. The slug is the part after job-boards.greenhouse.io/ on a company's board URL
• includeContent - fetch the full posting text for every job
• maxConcurrency - how many company boards to fetch in parallel

Example input

{
  "companySlugs": ["stripe", "anthropic", "figma"],
  "includeContent": false,
  "maxConcurrency": 5
}

Use cases

• Competitive hiring intelligence - track headcount plans across a whole peer group, by department and office
• Investor and market research - use open roles as a growth signal across a portfolio or a sector
• Talent sourcing - watch a target list of companies and react the day a role opens
• Recruitment agency prospecting - spot companies hiring in your specialism before the role hits the aggregators
• Job aggregation - build a curated board from first-party sources rather than resold listings
• Organisational research - map how companies structure departments and offices from their own taxonomy

Why go straight to Greenhouse

Aggregators lag, drop postings and strip fields. A company's Greenhouse board is the source those aggregators copy from, published by the employer itself, with departments, offices and custom metadata intact. It is also stable: no anti-bot layer, no login, no rate-limit games.

Notes

• metadata varies per company because each board defines its own fields, for example employment type, seniority or visa sponsorship.
• A company that has moved off Greenhouse returns nothing for its slug; that absence is itself a useful signal.
• Turning on includeContent adds a request per job, so a run across many boards takes considerably longer.
• Roles listed in several offices appear once with all offices in the offices array.