# Career Site Jobs by Keyword: 19,000+ Company Job Boards (`pistachio_implementation/career-site-jobs-search`) Actor

Search open jobs by keyword across 19,883 company career sites on Greenhouse, Lever, Ashby, Workable, SmartRecruiters and Recruitee. No company list needed. Title, company, location, remote, salary, posted date, apply link and description as JSON. $2 per 1,000 jobs.

- **URL**: https://apify.com/pistachio_implementation/career-site-jobs-search.md
- **Developed by:** [Hay Equipos](https://apify.com/pistachio_implementation) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.25 / 1,000 job saveds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Career Site Jobs Search: keyword search across Greenhouse, Lever, Ashby, Workable, SmartRecruiters and Recruitee

Type a job title and get matching open jobs from thousands of company career sites, without knowing which companies to look at. The actor holds an index of 19,883 public company job boards on six applicant tracking systems, picks the boards that have matching roles, and reads them live, so every job you get is open at the time of the run.

Each job comes in one clean schema: title, company, location, remote flag, salary range when the company publishes it, posted date, job link, apply link and the full description as plain text.

No login, no cookies, no proxies, no browser. Only the public job board APIs that these systems publish so companies can show their jobs on other sites.

### Who uses it

- **Job seekers and job boards** looking for every open "product designer" or "data engineer" role at companies that hire through modern applicant tracking systems.
- **Recruiters and staffing agencies** finding which companies are hiring for a role right now.
- **Sales teams** using hiring as a buying signal, for example every company hiring a "Head of RevOps" this month.
- **Analysts and newsletters** tracking demand for a skill or a city.
- **AI agents** that need a structured list of open roles for a query.

### How it works

1. **The index.** A list of public job boards built from the Common Crawl URL index (a free, public archive of web addresses at commoncrawl.org), where every address on `boards.greenhouse.io`, `job-boards.greenhouse.io`, `jobs.lever.co`, `jobs.ashbyhq.com`, `apply.workable.com`, `jobs.smartrecruiters.com` and `*.recruitee.com` was read and turned into a company board name. Every candidate was then checked against that system's public API; only boards that exist are kept. For each board the index stores the company name, the open job titles and the locations at build time.
2. **The search.** Your keywords and locations are matched against the index, and the boards with the most matching titles are read live, first to last, until your limit is reached.
3. **The output.** Live jobs are filtered again on the real, current titles, locations and dates, so closed roles never appear. Descriptions are fetched only for the jobs you keep.

#### Coverage, honestly

Index built 14 Oct 2026 from Common Crawl crawls of 2024 to 2026:

| System | Boards in the index | Boards with open jobs | Open jobs at build time |
|---|---|---|---|
| Greenhouse | 5,443 | 4,823 | 182,690 |
| SmartRecruiters | 1,461 | 1,461 | 182,626 |
| Workable | 5,653 | 2,778 | 112,031 |
| Ashby | 3,631 | 3,322 | 60,905 |
| Lever | 1,729 | 1,384 | 47,850 |
| Recruitee | 1,966 | 1,732 | 27,996 |
| **Total** | **19,883** | **15,500** | **614,098** |

What this means for you:

- **It is a large sample, not every company.** Companies that use these systems but never appeared in Common Crawl are missing. If you know a company you want, add its board in **Extra boards** and it is searched too.
- **Workday, iCIMS, Taleo, SuccessFactors, LinkedIn and Indeed are not covered.** Large enterprises often use those, so this actor leans toward startups, scaleups and mid sized companies.
- **New roles at a company that had no similar title at build time are skipped by default.** Turn on **Also check boards with no match in the index snapshot** to read every board in the index (slower, and charged per extra board, see Pricing).
- **The index is rebuilt from time to time**, and its build date is in every run's `RUN_SUMMARY`. Jobs themselves are always read live.

### Input

| Field | What it does |
|---|---|
| **Job title keywords** | One phrase per line. A title matches when it contains the phrase at a word start, with any ending on the last word: `data engineer` finds "Senior Data Engineer" and "Data Engineering Lead" but not "Data Center Engineer". Join words with `+` to require them anywhere in the title: `engineer + kubernetes`. |
| **Exclude titles with** | Drop titles that match any of these, for example `intern`, `senior`. |
| **Location contains any of** | For example `London`, `Germany`, `United States`, `Remote`. |
| **Remote jobs only** | Only jobs the board marks remote or that say remote in the location. |
| **Posted within the last N days** | 0 keeps every open job. |
| **Applicant tracking systems to search** | All six by default. |
| **Company name contains** | Optional, limits the search to matching companies. |
| **Extra boards to include** | Optional boards outside the index: `https://jobs.lever.co/spotify` or `greenhouse:airbnb`. |
| **Also check boards with no match in the index snapshot** | Off by default. Reads every indexed board to catch roles posted since the index was built. |
| **Include full job description** | On by default. |
| **Maximum jobs per company** | Default 10, so one large employer does not fill the result. |
| **Maximum jobs in total** | Default 500. |

#### Example input

```json
{
    "keywords": ["data engineer", "analytics engineer"],
    "excludeKeywords": ["intern"],
    "locations": ["United States", "Remote"],
    "postedWithinDays": 30,
    "maxJobsPerCompany": 10,
    "maxJobs": 200
}
```

### Output

One row per job, the same fields for every system:

```json
{
    "source": "ashby",
    "companySlug": "snowflake",
    "company": "Snowflake",
    "jobId": "db1375f0-ea5d-404a-b640-259f94dbc995",
    "title": "Software Engineer - Database Engineering",
    "department": "Engineering",
    "team": "Engineering",
    "location": "US-CA-Menlo Park",
    "locations": ["US-CA-Menlo Park", "US-WA-Bellevue"],
    "country": "United States",
    "isRemote": false,
    "workplaceType": null,
    "employmentType": "FullTime",
    "postedAt": "2026-07-28T22:20:47.028Z",
    "salaryMin": 160000,
    "salaryMax": 230000,
    "salaryCurrency": "USD",
    "salaryInterval": "1 YEAR",
    "salaryText": "$160K - $230K",
    "jobUrl": "https://jobs.ashbyhq.com/snowflake/db1375f0-ea5d-404a-b640-259f94dbc995",
    "applyUrl": "https://jobs.ashbyhq.com/snowflake/db1375f0-ea5d-404a-b640-259f94dbc995/application",
    "matchedKeyword": "software engineer",
    "boardUrl": "https://jobs.ashbyhq.com/snowflake",
    "descriptionText": "Snowflake is about empowering enterprises to achieve their full potential...",
    "scrapedAt": "2026-10-14T19:31:25.105Z"
}
```

A `RUN_SUMMARY` record in the key value store gives the index date and size, how many boards matched, how many were read, jobs saved per system and any board that failed.

Download the results as JSON, CSV, Excel or HTML, or read them through the Apify API, webhooks, Make, Zapier or the Apify MCP server.

### Pricing

Pay per event, no subscription, no platform usage on top:

- **$0.002 per job saved** ($2.00 per 1,000 jobs).
- **$0.0001 per extra board checked**, only when you turn on "Also check boards with no match in the index snapshot" ($0.10 per 1,000 boards). Off by default.
- Apify discount tiers pay less per job: $1.75 per 1,000 on Bronze, $1.50 on Silver, $1.25 on Gold.
- No start fee. Boards that fail, jobs removed by your filters, and searches with no matches cost nothing.

Example: 200 data engineering jobs with descriptions cost 40 cents. Set a maximum charge per run in the Console and the actor stops when it is reached.

### Limits

- Six systems only (see Coverage).
- Salary appears only when the company publishes it: Ashby and Greenhouse often do, Lever and Recruitee sometimes, Workable and SmartRecruiters rarely through these APIs.
- Posted date is what the job board reports; Workable gives a date without a time, Lever gives the creation date.
- Location matching is plain text: `United States` will not match a job listed only as `New York, NY`. Add the cities or states you care about, or `US`.
- Company names come from each system; a few boards show a name built from the board address (for example "Acme Labs" for `acme-labs`).
- Workable and Recruitee slow down clients that send many requests, so runs that touch hundreds of their boards take longer.

### FAQ

**Is this legal?** The actor reads public job board APIs that each system publishes so jobs can be shown on other sites, plus the public Common Crawl index to find boards. It does not log in, does not bypass any protection, and collects no personal data about candidates or recruiters. You are responsible for how you use the data, including each job board's terms.

**Why not every company in the world?** No public list of every company on these systems exists. The index is built only from public sources and is honest about its size.

**A company I want is missing.** Put its job board link in **Extra boards**. For whole company lists, our sister actor ATS Jobs API takes any list of boards.

**Can I monitor new jobs?** Yes. Schedule the actor daily with **Posted within the last N days** set to 1 or 2, or compare `jobId` values between runs.

**Can AI agents call it?** Yes. The input is small, the actor uses limited permissions and is priced per event, so it works through the Apify MCP server.

# Actor input Schema

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

One keyword or phrase per line. A job matches when every word of any one phrase starts a word in its title, in any order, so "data engineer" also finds "Senior Data Platform Engineer" and "Data Engineering Lead". Case does not matter.

## `excludeKeywords` (type: `array`):

Drop jobs whose title matches any of these words or phrases, for example intern, senior, manager.

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

Keep only jobs whose location text contains one of these, for example London, United States, Germany, Remote. "Remote" also matches jobs the board marks as remote.

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

Keep only jobs marked remote by the job board or with remote in the location.

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

Keep only jobs first published in the last N days. 0 keeps all open jobs.

## `ats` (type: `array`):

Which systems to search. All six by default.

## `companyKeywords` (type: `array`):

Search only companies whose name or board slug contains one of these, for example stripe or bank. Leave empty to search every company in the index.

## `extraBoards` (type: `array`):

Boards to search in addition to the bundled index, for companies it does not hold yet: a job board URL (https://jobs.lever.co/spotify) or ats:slug (greenhouse:airbnb).

## `searchAllBoards` (type: `boolean`):

By default the actor reads live only the boards that had a matching title when the index was built, which is fast and cheap. Turn this on to also read every other board in the index, to catch roles posted since. Much slower (thousands of boards) and charged per extra board checked.

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

Adds the job description as clean plain text. Greenhouse and SmartRecruiters need one extra request per kept job for this.

## `maxDescriptionChars` (type: `integer`):

Descriptions longer than this are cut.

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

Stop after this many matching jobs from one company, so one big employer does not fill the whole result.

## `maxJobs` (type: `integer`):

The run stops after saving this many jobs.

## Actor input object example

```json
{
  "keywords": [
    "data engineer"
  ],
  "excludeKeywords": [],
  "locations": [
    "United States"
  ],
  "remoteOnly": false,
  "postedWithinDays": 0,
  "ats": [
    "greenhouse",
    "lever",
    "ashby",
    "workable",
    "smartrecruiters",
    "recruitee"
  ],
  "companyKeywords": [],
  "extraBoards": [],
  "searchAllBoards": false,
  "includeDescription": true,
  "maxDescriptionChars": 20000,
  "maxJobsPerCompany": 10,
  "maxJobs": 100
}
```

# Actor output Schema

## `results` (type: `string`):

All jobs the run saved to the default dataset.

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

The RUN_SUMMARY record: index date and size, boards read, jobs saved per system and any failures.

# 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 = {
    "keywords": [
        "data engineer"
    ],
    "locations": [
        "United States"
    ],
    "maxJobs": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("pistachio_implementation/career-site-jobs-search").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 = {
    "keywords": ["data engineer"],
    "locations": ["United States"],
    "maxJobs": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("pistachio_implementation/career-site-jobs-search").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 '{
  "keywords": [
    "data engineer"
  ],
  "locations": [
    "United States"
  ],
  "maxJobs": 100
}' |
apify call pistachio_implementation/career-site-jobs-search --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pistachio_implementation/career-site-jobs-search"
        }
    }
}
```

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/jOFM7K2E3SHkR8Sg9/builds/VPAhBboKnjIk44V6h/openapi.json