Greenhouse & Lever Job Scraper

Scrape open roles straight from company career boards

Pull job openings from the Greenhouse and Lever feeds that sit behind a company's own "Careers" page - the source of truth, not an aggregator's copy of it. Give the actor a list of company boards and it returns every open role as clean, flat JSON.

Each record carries title, employer, location, department, workplace type, employment type, first-seen date and a direct apply URL. No login, no API key, no CAPTCHA.

Get your first results in about 30 seconds: press Start with the prefilled input. It returns 100 roles from the two example boards. Then swap in your own companies and add filters.

Boards are read in the order you list them and the run stops as soon as maxResults is reached, so a large employer at the top of the list can fill the whole result set on its own. Set Max results per company when you want even coverage across every company you are tracking.

Your $5 of free Apify credit is worth roughly 1,000 job records on this actor.

What you get per role

Field	Description
id	Stable id, provider-prefixed - e.g. greenhouse:stripe:7954688
provider	greenhouse or lever
company	Employer display name
companySlug	The board token you supplied
title	Job title
location	Location as the employer wrote it
department	Department or team, exactly as the board records it. Greenhouse often prefixes an internal id - 1654 Account Executives (AI) - so match on a substring rather than equality
workplaceType	onsite, remote, hybrid - Lever only, null on Greenhouse
employmentType	Commitment as the company words it, e.g. Regular Full Time (Salary) - Lever only
tags	Commitment and team labels, where the board publishes them
salaryMin, salaryMax	Reserved - neither feed publishes salary
url, applyUrl	The public posting and its apply page
publishedAt	ISO 8601 date the role was published or last updated
teaser	First 300 characters of the description, HTML stripped

Sample record

{
  "id": "greenhouse:stripe:7954688",
  "provider": "greenhouse",
  "company": "Stripe",
  "companySlug": "stripe",
  "title": "Account Executive, AI Sales (Grower)",
  "location": "San Francisco, CA",
  "department": "1654 Account Executives (AI)",
  "workplaceType": null,
  "employmentType": null,
  "tags": [],
  "salaryMin": null,
  "salaryMax": null,
  "url": "https://stripe.com/jobs/search?gh_jid=7954688",
  "applyUrl": "https://stripe.com/jobs/search?gh_jid=7954688",
  "publishedAt": "2026-07-27T11:17:30-04:00",
  "teaser": "Who we are About Stripe Stripe is a financial infrastructure platform for businesses. Millions of companies use Stripe to accept payments, grow their revenue, and accelerate new business opportunities..."
}

Finding a company's board slug

Look at the company's careers URL and take the last path segment:

• boards.greenhouse.io/stripe becomes greenhouse:stripe
• jobs.lever.co/leverdemo becomes lever:leverdemo

Many companies host the board on their own domain but still run one of these two systems underneath - check the careers page's network requests, or try the company name as a slug. A slug that does not exist is reported in the run summary and skipped; it never sinks the run.

Filters

Input	What it does
companies	The boards to scrape, as provider:slug. Add as many as you like
maxResults	Stop after this many roles. Your cost control
keywords	Keep roles containing ALL of these words, e.g. senior engineer
titleOnly	Match those keywords against the job title alone
excludeKeywords	Drop roles containing ANY of these words, e.g. intern manager
location	Keep roles whose location contains this text
remoteOnly	Keep only remote roles
department	Keep only a matching department or team
employmentType	Keep only roles whose commitment contains this text
postedWithinDays	Keep only roles published or updated in the last N days
maxPerCompany	Cap how many roles any one company contributes
proxyConfiguration	Standard Apify proxy input. Datacenter proxies are fine here

Neither Greenhouse nor Lever offers a server-side search on these public feeds - each endpoint returns that company's current openings in full. Every filter above is therefore applied to the roles after fetching, not sent as a live query. That costs you nothing extra: the request per company is the same either way, and filtering before results are written means you are only charged for the roles you asked for.

Example

{
  "companies": ["greenhouse:stripe", "greenhouse:gitlab", "lever:spotify"],
  "keywords": "engineer",
  "excludeKeywords": "manager director",
  "remoteOnly": true,
  "maxPerCompany": 20,
  "maxResults": 100
}

What it costs

Pricing is pay-per-event on Apify's built-in per-result event: you pay per role returned and nothing at all for a run that finds no matches. There is no per-run start fee, so watching twenty companies in twenty small runs costs the same as one big one.

A worked example: Stripe's board carries about 550 open roles. Pulling all of them costs roughly $2.75. Monitoring ten mid-size companies for engineering roles only, at around 300 matches a day, is about $1.50 a day.

Typical uses

• Recruiting and talent intelligence - track exactly who a target company is hiring, by team and location.
• Job boards and aggregators - source listings from the system of record instead of re-scraping another aggregator.
• Competitive and market research - headcount direction, which teams are growing, which locations are opening.
• Sales prospecting - hiring signals are budget signals, and the department tells you which budget.

Your feedback

If a provider is missing, a field is wrong, or you need something these boards publish that this actor does not yet return, please open an issue on the Issues tab. Requests get read and acted on, and a short review helps other people find the actor.

Disclaimer

This is an unofficial scraper. It is not affiliated with, endorsed by, or sponsored by Greenhouse Software, Inc. or Lever, Inc. It reads only data that those boards publish publicly, with no login and no access to private accounts.

Personal data in the output

Results may contain personal data (for example a named contact on a job posting). Personal data is protected by regulations such as the GDPR in the EU and the CCPA in California. You should not scrape or process personal data unless you have a legitimate reason to do so; if you are unsure whether your reason is legitimate, consult your lawyers.