Greenhouse Job Keyword Evidence Report

Find jobs mentioning your chosen technologies or phrases on one public Greenhouse company board. Get a JSON report with the job title, location, source link and a short text excerpt for each matched keyword. Useful for agencies and researchers checking a known company's job descriptions without reading every posting.

This is a literal text scan, not a prediction of purchase intent or a verified technology installation. A mention may be a requirement, a comparison or a negated statement. Read the excerpt and original job before drawing conclusions.

Run a scan

Enter a board slug from a public Greenhouse careers URL and 1–10 keywords:

{"boardToken":"figma","keywords":["Salesforce","Snowflake"]}

Use the company's Greenhouse board slug, which can differ from its company name. For a URL ending in /figma, the slug is figma. URLs themselves are not accepted. The Actor reads the public Greenhouse Job Board API once. No login, browser, proxy, application submission or employer discovery is involved.

Matching is case-insensitive literal text with word boundaries: Java does not match JavaScript. Phrases match normalized whitespace; punctuation must match. Any supplied keyword can qualify a job. Each keyword has at most one excerpt per job, preferring its first title match, otherwise its first description match. HTML is converted to text. There is no stemming, synonym expansion, semantic classification, salary extraction, contact enrichment or cross-run history.

Output and price

One completed board scan costs USD0.01, including a scan with zero matches or an empty board. Platform run usage is included. There is no start charge and no per-job charge. Invalid input, source failures, exceeded limits or insufficient event budget create no report and no custom charge. Apify storage or export charges after the run can be separate under your platform plan.

The default Dataset contains one nested JSON report. Use JSON for the complete matches and evidence arrays; this is not a flat spreadsheet export. SUMMARY records completion, counts or the failure reason. The output links expose both.

Example synthetic match from a one-job source:

{
  "boardToken": "example-company",
  "jobsScanned": 1,
  "matchingJobs": 1,
  "keywords": ["Salesforce"],
  "scanComplete": true,
  "matches": [{
    "jobId": 123,
    "title": "Business Systems Engineer",
    "location": "Remote",
    "jobUrl": "https://example.com/jobs/123",
    "evidence": [{"keyword":"Salesforce","field":"description","snippet":"Maintain our Salesforce integrations."}]
  }]
}

Actual reports also include sourceUrl and a UTC observedAt timestamp. A complete scan means all jobs in the returned response were examined and its reported total matched the received count; it does not independently verify the employer's data.

Limits and interpretation

• One board, 1–10 keywords of up to 60 characters each per run.
• At most 2,000 source jobs, 20 MB decoded HTTP response and 500 matching jobs.
• 45-second total source-request timeout; redirects are not followed.
• Exceeding a limit fails the scan without a partial report. If too many jobs match, use narrower keywords; oversized boards are unsupported.
• Source postings can be stale, incomplete or unavailable. A job listing is not proof of an open hiring process, an installed product, a budget or buying intent.
• Greenhouse only. No Lever, Workday, LinkedIn or private recruiting data.

You supply the board; this tool does not find all companies using a technology. Repeated runs scan the current board again and are billed again. Scheduling and integrations are available through Apify; this Actor itself sends no messages.