Tech Jobs Aggregator — Greenhouse, Ashby & Lever in one feed

Aggregate live job postings across companies' public ATS boards — Greenhouse, Ashby, and Lever — into one normalized, deduped feed. No login, no anti-bot: these boards are published by companies specifically to be consumed by aggregators. The value is the aggregation the raw endpoints don't give you.

Why this beats a single-board scraper

• One schema across three ATS shapes — company, title, location, remote, team, apply URL, posted date, description, all normalized.
• Auto-detects the ATS — give a company slug (e.g. notion) and it figures out whether they use Greenhouse, Ashby, or Lever. You don't need to know.
• Built-in company directory so search works out of the box across well-known tech companies; add your own with companies.
• Filter + dedupe — keyword, location, remote-only, de-duplicated across boards.

Modes

Mode	What it does
Search	Filter jobs by keyword / location / remote across the built-in directory (+ any companies you add)
Company	Pull all live jobs for the specific companies you list (ATS auto-detected)

Who it's for

Recruiters and talent-intelligence tools; sales prospecting (a company hiring is a growth & buying signal); job-board builders; and AI agents — as an MCP tool answering "who's hiring for backend roles?" or "is {company} hiring?".

Output

Flat JSON rows: company, ats, title, location, remote, team, url, published_at, description.

Input examples

{ "mode": "search", "keywords": ["engineer","backend"], "remoteOnly": true, "maxItems": 500 }

{ "mode": "company", "companies": ["stripe", "openai", "gopuff"], "maxItems": 1000 }

A slug is the last part of a careers URL: boards.greenhouse.io/stripe → stripe, jobs.ashbyhq.com/openai → openai, jobs.lever.co/gopuff → gopuff.

Use cases

• Recruiting & talent intelligence — a live feed of who is hiring, for which roles, where. Track competitors' engineering headcount growth from their own job boards.
• Sales prospecting & lead generation — a company posting backend/DevOps roles is a buying signal for dev tools, cloud services and recruiting agencies. Export hiring companies to CSV for outreach.
• Job boards & newsletters — power a niche remote-jobs board or a weekly "who's hiring" newsletter without writing three scrapers for Greenhouse, Ashby and Lever.
• Market research — salary-band, tech-stack and remote-work trends from thousands of live postings.
• AI agents — call this actor as an MCP tool so an agent can answer "is Stripe hiring engineers?" with live data.

FAQ

How do I get jobs from the Greenhouse job board API? Every Greenhouse board is public at boards.greenhouse.io/{company}. This actor reads those public endpoints for you, plus Ashby and Lever, and returns one normalized JSON schema — no API key required.

Can I scrape Lever and Ashby jobs without an API key? Yes. Companies publish these boards to be read. Give the actor a company slug (jobs.lever.co/gopuff → gopuff) and it auto-detects the ATS.

How is this different from scraping LinkedIn or Indeed? LinkedIn and Indeed aggressively block scrapers and their listings are ad-mixed. ATS boards are the source of truth the aggregators themselves read — cleaner data, zero anti-bot risk.

Can I export the jobs to CSV or Excel? Yes — every run's dataset downloads as CSV, Excel, JSON or XML from the Apify console or API, ready for spreadsheets or your ATS.

How do I keep a job feed continuously updated? Schedule the actor (e.g. every 6 hours) in Apify → Schedules, and read the dataset from your app, Zapier/Make, or a webhook.

Does it find remote-only jobs? Set "remoteOnly": true in search mode to keep only remote-friendly postings across all companies.

Legal

Reads companies' public ATS job-board APIs, which are published for aggregation. No login, no circumvention. Respect rate limits; link back to the original posting when republishing.

Pricing

Pay-per-event: a small actor-start fee plus a per-job charge — you pay for exactly the jobs you pull.