# Hiring Signal Jobs Scraper - Greenhouse & Lever API (`groupoject/hiring-signal-jobs-scraper`) Actor

Scrape live jobs from Greenhouse and Lever career pages, then score hiring signals by department, seniority, remote status, salary, urgency, and role category. No login.

- **URL**: https://apify.com/groupoject/hiring-signal-jobs-scraper.md
- **Developed by:** [Group Oject](https://apify.com/groupoject) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 jobs

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## B2B Hiring Signal Lead Generator - Greenhouse & Lever

Turn live Greenhouse and Lever openings into timely B2B sales leads. Every result explains what a company is investing in, who is likely to own that initiative, why the signal matters, and which public job URL proves it.

It uses public ATS JSON endpoints, so it does not need a browser, login, cookies, or a paid job-board account.

Use it as a jobs scraper, hiring-signal monitor, sales prospecting feed, competitor hiring tracker, or AI/MCP agent tool for company research.

### What You Get

- Live jobs from Greenhouse and Lever career pages
- Normalized job title, ATS source, company slug, locations, department, seniority, role category, URLs, and dates
- Plain-text job descriptions, with optional raw HTML
- Remote, hybrid, and location detection
- Salary range fields when the ATS exposes compensation data
- `hiringSignalScore` from 0 to 100
- `hiringSignalTier` as Low, Medium, or High
- Lead-generation tags such as `new-role`, `urgent-hiring`, `go-to-market-hiring`, and `strategic-technical-hiring`
- Likely business needs such as CRM, developer tooling, cloud infrastructure, security, data, marketing automation, or recruiting
- Suggested target buyer by department
- A concise, evidence-based outreach angle for personalized prospecting
- `signalEvidence` combining role, department, location, and the source URL
- Monitor mode for scheduled runs that mark new roles

### Common Use Cases

- Find companies actively hiring engineers, sales reps, marketers, or data teams
- Track startup hiring signals before outreach
- Build prospect lists based on department growth
- Monitor competitors and portfolio companies
- Feed job-change signals into a CRM, spreadsheet, data warehouse, or AI workflow

### Works well with MCP and AI agents

Apify Actors can be discovered and run from the Apify MCP server, which makes this Actor a useful building block for AI agents that need fresh hiring data. The output is compact JSON with evidence URLs, role categories, seniority, departments, locations, salary fields when available, and a scored `hiringSignalScore`.

Good agent workflows:

- **Sales lead agent** - find companies hiring for roles that imply budget, growth, or new tooling needs.
- **Recruiting market agent** - track remote, AI, data, engineering, and GTM openings across target companies.
- **Competitor intelligence agent** - monitor department growth and new strategic roles.
- **Weekly account research** - append fresh hiring signals into CRM notes before outbound or sales calls.

### Input Examples

Use full career URLs:

```json
{
  "careerUrls": [
    "https://boards.greenhouse.io/stripe",
    "https://jobs.lever.co/palantir"
  ],
  "keywords": ["engineer", "data", "sales"],
  "maxTotalJobs": 100
}
```

#### AI Agent Hiring Intelligence Feed

```json
{
  "companySlugs": [
    "greenhouse:anthropic",
    "greenhouse:databricks",
    "greenhouse:stripe",
    "lever:shieldai"
  ],
  "keywords": ["engineer", "sales", "partnerships", "security"],
  "maxTotalJobs": 100,
  "includeDescription": false,
  "monitorMode": true,
  "onlyNewJobs": false,
  "stateKey": "ai-agent-hiring-intel"
}
```

#### B2B Buying Signal Job Monitor

```json
{
  "companySlugs": [
    "greenhouse:stripe",
    "greenhouse:airbnb",
    "lever:gohighlevel",
    "lever:Flex"
  ],
  "keywords": ["sales", "account executive", "marketing", "growth", "customer success", "partnerships"],
  "departments": ["Sales", "Marketing", "Customer Success", "Growth"],
  "maxJobsPerCompany": 40,
  "maxTotalJobs": 100,
  "monitorMode": true,
  "onlyNewJobs": true,
  "stateKey": "b2b-buying-signal-jobs"
}
```

Or use provider-prefixed slugs:

```json
{
  "companySlugs": ["greenhouse:stripe", "lever:palantir"],
  "remoteOnly": true,
  "monitorMode": true,
  "onlyNewJobs": true,
  "stateKey": "remote-saas-hiring-signals"
}
```

### Output Fields

Each dataset item can include:

- `title`
- `companySlug`
- `sourceAts`
- `department`
- `roleCategory`
- `seniority`
- `location`
- `locations`
- `remoteType`
- `employmentType`
- `salaryMin`
- `salaryMax`
- `salaryCurrency`
- `postedAt`
- `isNew`
- `hiringSignalScore`
- `hiringSignalTier`
- `urgencyTags`
- `matchedKeywords`
- `matchedLocations`
- `matchedDepartments`
- `jobUrl`
- `applyUrl`
- `description`

### Pricing Tip

The default input is capped at 100 jobs so first-time users can test the Actor cheaply before running larger company lists.

### Notes

This Actor works with public Greenhouse and Lever job boards. It does not scrape LinkedIn, Indeed, or private applicant tracking systems.

# Actor input Schema

## `careerUrls` (type: `array`):

Public ATS career URLs, e.g. https://boards.greenhouse.io/stripe or https://jobs.lever.co/palantir.

## `companySlugs` (type: `array`):

Use provider:slug format, for example greenhouse:stripe or lever:palantir.

## `careerUrlsText` (type: `string`):

Paste one Greenhouse/Lever URL or provider:slug entry per line.

## `keywords` (type: `array`):

Only keep jobs matching any keyword in title, department, location, or description. Leave empty for all jobs.

## `locations` (type: `array`):

Only keep jobs matching any location text such as Remote, United States, London, New York, or Europe.

## `departments` (type: `array`):

Only keep jobs matching department, title, or description text. Useful for Engineering, Sales, Marketing, Product, or Finance.

## `seniorities` (type: `array`):

Optional seniority filters such as Entry, Mid, Senior, Leadership, Director, Principal, or Intern.

## `remoteOnly` (type: `boolean`):

Only output jobs detected as remote.

## `includeDescription` (type: `boolean`):

Convert job HTML to clean plain text.

## `includeHtmlDescription` (type: `boolean`):

Also include raw HTML job description.

## `maxJobsPerCompany` (type: `integer`):

Maximum number of jobs to read from each company career page.

## `maxTotalJobs` (type: `integer`):

Maximum number of jobs to save across all selected sources. Default is capped at 100 for affordable testing.

## `postedWithinDays` (type: `integer`):

Optional freshness filter based on posting or update date.

## `minHiringSignalScore` (type: `integer`):

Only output jobs with this hiring signal score or higher. Use 55+ for stronger lead signals.

## `monitorMode` (type: `boolean`):

Store seen job IDs across runs so scheduled runs can mark new jobs.

## `onlyNewJobs` (type: `boolean`):

When monitor mode is on, output only jobs not seen in previous runs.

## `stateKey` (type: `string`):

Optional stable key for dedupe state. Use a different key per saved task/search scope.

## `requestDelayMs` (type: `integer`):

Delay between company API requests. Increase this for very large source lists.

## `debugMode` (type: `boolean`):

Enable verbose logs for troubleshooting source URLs and filters.

## Actor input object example

```json
{
  "careerUrls": [
    "https://boards.greenhouse.io/stripe",
    "https://jobs.lever.co/palantir"
  ],
  "keywords": [
    "engineer",
    "data",
    "sales"
  ],
  "remoteOnly": false,
  "includeDescription": true,
  "includeHtmlDescription": false,
  "maxJobsPerCompany": 100,
  "maxTotalJobs": 100,
  "minHiringSignalScore": 0,
  "monitorMode": false,
  "onlyNewJobs": false,
  "requestDelayMs": 250,
  "debugMode": false
}
```

# Actor output Schema

## `jobs` (type: `string`):

One row per job with ATS source, title, company slug, location, department, seniority, hiring signal score, apply URL, and description.

## `summary` (type: `string`):

Counts, high-signal jobs, top departments, top locations, duration, and per-source run status.

## `sources` (type: `string`):

Per-company ATS API status, kept job counts, average hiring signal scores, and source errors.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "careerUrls": [
        "https://boards.greenhouse.io/stripe",
        "https://jobs.lever.co/palantir"
    ],
    "keywords": [
        "engineer",
        "data",
        "sales"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("groupoject/hiring-signal-jobs-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "careerUrls": [
        "https://boards.greenhouse.io/stripe",
        "https://jobs.lever.co/palantir",
    ],
    "keywords": [
        "engineer",
        "data",
        "sales",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("groupoject/hiring-signal-jobs-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "careerUrls": [
    "https://boards.greenhouse.io/stripe",
    "https://jobs.lever.co/palantir"
  ],
  "keywords": [
    "engineer",
    "data",
    "sales"
  ]
}' |
apify call groupoject/hiring-signal-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,groupoject/hiring-signal-jobs-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ahbTccvB2A8eM4ZRh/builds/ytbOIBl1cjStuUjSK/openapi.json