Multi-Board Job Deduplicator & Hiring Intelligence

Collect job postings from public Greenhouse, Lever, and Ashby career boards, normalize them into one clean schema, strip out cross-posted duplicates, and get an employer-level hiring score for every company you track. One row per real job — not per listing.

What you get

One dataset record per unique job posting:

• Job: title, department, location, direct apply URL, publish date, and the board's own job ID
• Company and source: which employer posted it and which board it came from (greenhouse, lever, ashby)
• Remote flag: postings detected as remote, so you can filter to remote-only in one click
• Deduplicated: the same role cross-posted to two boards, or listed twice under different IDs, collapses to a single record
• Employer hiring summary (in the key-value store): open roles, remote roles, departments hiring, and a 0–100 hiring intent score per company, ranked
• Export to JSON, CSV, Excel, or Google Sheets directly from the Apify console

Use cases

• Hiring intent and lead generation — companies staffing up are companies buying; rank your target list by hiring score
• Job board aggregation — power a niche job site or newsletter from dozens of company boards without duplicate listings
• Competitor and market intelligence — see which departments a competitor is scaling and where
• Recruiting and talent mapping — track open roles across a whole portfolio or industry in one dataset
• Remote job feeds — filter every board down to remote-only roles matching your keywords

How to use

1. Add your Career boards — one entry per company with company, source (greenhouse, lever, or ashby), and the board slug from its careers URL
2. Optionally add Title keywords to keep only matching roles (case-insensitive, matched anywhere in the title)
3. Optionally toggle Remote only
4. Run the actor — unique jobs land in the Dataset tab, and the employer summary in the Key-value store tab under SUMMARY

{
  "boards": [
    { "company": "Example", "source": "greenhouse", "board": "example" },
    { "company": "Acme", "source": "lever", "board": "acme" }
  ],
  "keywords": ["engineer", "designer"],
  "remoteOnly": false
}

The board slug is the last part of the public careers URL — boards.greenhouse.io/example, jobs.lever.co/acme, or jobs.ashbyhq.com/acme all give you example / acme.

Output format

Dataset — one record per unique job:

{
  "company": "Example",
  "source": "greenhouse",
  "jobId": "4012345",
  "title": "Senior Software Engineer",
  "location": "Remote",
  "url": "https://boards.greenhouse.io/example/jobs/4012345",
  "publishedAt": "2026-08-01T00:00:00Z",
  "department": "Engineering",
  "isRemote": true
}

SUMMARY key-value store record — one entry per employer, ranked by hiring intent:

[
  {
    "company": "Example",
    "openRoles": 24,
    "remoteRoles": 11,
    "departments": ["Engineering", "Sales", "Design"],
    "hiringIntentScore": 100
  }
]

FAQ

How are duplicates detected? Jobs are matched on company, title, and location after normalization, so the same role posted to two boards or re-listed under a new ID appears once.

Do I need a login or API key for the boards? No. Only public career boards are read.

What if one board fails? That board is skipped with a warning and the run continues — a single broken slug never costs you the rest of the results.

Where is the employer summary? In the Key-value store tab of the run, under the SUMMARY record. The dataset stays one-row-per-job so CSV and Sheets exports stay clean.

Can I run it on a schedule? Yes — run it daily to track how many roles each employer has open over time.