# Career Site Jobs Search: Greenhouse, Lever, Ashby, Workable (`greyledger/career-site-jobs-search`) Actor

Search open jobs by keyword, location, remote and whether pay is published, across thousands of company job boards on Greenhouse, Lever, Ashby and Workable, read from their public job-board feeds and refreshed weekly. Or read the boards you name, live.

- **URL**: https://apify.com/greyledger/career-site-jobs-search.md
- **Developed by:** [GreyLedger](https://apify.com/greyledger) (community)
- **Categories:** Jobs, AI
- **Features:** Limited permissions
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.40 / 1,000 job returneds

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

### What does Career Site Jobs Search do?

It searches job postings on company career sites that run on **Greenhouse, Lever, Ashby and Workable**. Jobs come from the public feed each provider offers for publishing a company's jobs. Each result links to the job page on the employer's board and, where the board gives one, to its application form (on Greenhouse, the job page itself).

You can use it two ways:

- **Search the index.** Filter about 390,000 job postings from about 11,000 company job boards by title keywords, location, remote, whether pay is published, posting date and company. The index is rebuilt every week.
- **Fetch named boards live.** Give job-board URLs (for example `https://jobs.ashbyhq.com/openai`) and the actor reads those boards at the moment you run it, including boards that are not in the index. Your other filters and **Maximum results** still apply.

### Who it is for

- Job boards and newsletters that want listings straight from employers' own boards.
- Recruiters and sales teams tracking which companies are hiring for which roles.
- Researchers studying pay, remote work and hiring by role or city.
- AI agents that need current job data through the Apify API or the Apify MCP server.

### What you get for each job

Example, from a real Ashby posting on 9 November 2026:

| Field | Example |
|---|---|
| `title` | Technical Program Manager, Compute Infrastructure |
| `company` | OpenAI |
| `location` | San Francisco |
| `isRemote`, `workplaceType` | false, hybrid |
| `department`, `employmentType` | Technical Program Management, FullTime |
| `salaryMin`, `salaryMax`, `salaryCurrency`, `salaryInterval`, `salaryText` | 207000, 285000, USD, 1 YEAR, "$207K – $285K • Offers Equity" |
| `postedAt` | 2026-11-05T02:20:02Z |
| `updatedAt` | empty here: filled only where the board gives an update time (Greenhouse) |
| `firstSeenAt` | when the job first appeared in the index |
| `url`, `applyUrl` | the job page and, where given, the application form (on Greenhouse, the job page) |
| `ats`, `companySlug`, `jobId` | ashby, openai, 8fb1615c-34bf-47c4-a1d1-b7b2f836bbd3 |
| `descriptionText` or `descriptionHtml` | the job description, when the board provides one |

Pay fields are filled only when the board's feed carries a pay range: Ashby's compensation field, Lever's salary range, and Greenhouse's pay ranges. Workable's feed has no pay field, so its pay, where an employer gives it, is only in the description. On Ashby and Lever, `salaryInterval` uses the provider's own wording (for example `1 YEAR` on Ashby, `per-year-salary` on Lever). Greenhouse gives no interval field, so it is read from the range's title: `hour`, `month` or `year` when the title says so, `year` for any other title that mentions salary (for example "Salary Range"), and empty otherwise. Some Greenhouse boards publish several ranges (for example by region); the first fills the number fields and all of them are listed in `salaryText`.

### How to use it

1. Enter title keywords, for example `data engineer`. Leave empty to get the newest jobs.
2. Optionally add locations (`London`, `UK`, `New York`), a remote filter, **Only jobs with a salary**, or companies.
3. Set **Maximum results**. Results are sorted newest first.
4. Run, then download the results as JSON, CSV, Excel or another Apify export format, or read them through the API.

To follow new postings, schedule a weekly run with **New in the last (hours)** set to 168. It returns indexed jobs that first appeared in the index in the last 168 hours (seven days), up to **Maximum results**; boards you fetch live by URL are not limited by this filter. The index started on 9 November 2026, and a board added later counts all its jobs as new in its first week, so the first run of such a schedule can return far more than a week's new jobs: set **Maximum results** to what you want to pay for.

#### Input example

```json
{
    "keywords": ["data engineer", "analytics engineer"],
    "excludeKeywords": ["intern"],
    "locations": ["London", "Remote"],
    "onlyWithSalary": false,
    "postedWithinDays": 14,
    "maxResults": 200
}
```

#### Matching rules

- Keywords match whole words in the job title, in any case. `engineer` matches "Data Engineer" but not "Engineering Manager". Turn on **Also match keywords in job descriptions** to search for skills such as `kubernetes`.
- Locations match the location text the employer wrote. `UK` also matches United Kingdom, England, Scotland, Wales, Northern Ireland, Great Britain and London; `US` matches United States, USA and U.S., and locations written as a city, a comma and a capitalised US state code ("Austin, TX"). `London` matches every London except one followed by ", ON" or ", Ontario".
- **Only jobs with a salary** keeps jobs with a published pay range or pay text; it does not filter by amount.
- Remote uses the board's own field where it has one (Lever's and Ashby's workplace type, Workable's remote flag, Ashby's remote flag when no workplace type is given). Otherwise a job counts as remote when its location mentions "remote", "anywhere", "work from home" or "WFH".

### Pricing

| Event | Price |
|---|---|
| Job returned | $2.00 per 1,000 jobs on the Free plan; $1.80 on Starter, $1.60 on Scale, $1.40 on Business and above |
| Run start | $0.002 per run, per GB of memory (default 1 GB) |
| Description search | $0.01 per run, charged only when **Also match keywords in job descriptions** is on and keywords are given |

You are not charged for jobs filtered out, and this pay-per-event Actor does not charge for platform usage on top. **Maximum results** caps the number of jobs charged; you can also set a maximum cost per run in Apify (at least $0.02 for this Actor).

#### Billing and refunds

Apify bills your runs under its [General Terms](https://docs.apify.com/legal/general-terms-and-conditions), which make fees non-refundable (section 7.4) and provide the platform for business use only, so there is no consumer cancellation period. If a run fails or returns wrong results, open an issue on the **Issues** tab with the run ID: we will ask Apify to compensate the run, and Apify credits compensation as platform usage ([how compensation works](https://docs.apify.com/actors/monetize/compensation-requests)).

### Coverage and freshness

- The index holds job boards found in public web-crawl data. A board that is not in the index can still be fetched live by URL.
- The index is rebuilt weekly, on Mondays. For jobs as they are now, fetch the boards you need live by URL. A job that closes is dropped when its board is next read. If a board errors or does not answer during a rebuild, its jobs from the last successful read are kept until it can be read; a board that answers "not found" is dropped and checked again at the next weekly rebuild.
- Live fetches read the board when you run the Actor; boards that cannot be read are reported: up to five in the run's status message, and all of them in the run's `SUMMARY` record.
- Requests to Lever's feed are spaced at least one second apart, as api.lever.co's robots.txt asks.

### Data and responsible use

The jobs are public postings that employers publish on their job boards. The Actor reads the providers' public job-board feeds, and the board page's title for Lever and Ashby company names. It collects no candidate data. Job descriptions remain the employers' content; check your own use against the terms of anywhere you republish them.

This Actor is independent and is not affiliated with or endorsed by Greenhouse, Lever, Ashby or Workable.

### Questions and problems

Open an issue on the **Issues** tab with your input and what you expected.

# Actor input Schema

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

Return jobs whose title contains any of these words or phrases (whole words, any case). Example: "data engineer", "product manager". Leave empty for all jobs.

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

Drop jobs whose title contains any of these words or phrases. Example: "intern", "senior".

## `searchDescriptions` (type: `boolean`):

Match keywords against the full job description as well as the title, for skills such as "kubernetes" or "dbt". Slower.

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

Keep jobs whose location mentions any of these places. Example: "London", "Berlin", "UK", "United States". Common short forms (UK, US, NYC, SF, Bay Area, EMEA) are expanded.

## `remote` (type: `string`):

Remote jobs only, non-remote only, or both.

## `companies` (type: `array`):

Limit to these companies. Give a company name as listed on its board ("Stripe"), or a job-board URL (https://job-boards.greenhouse.io/stripe, https://jobs.lever.co/palantir, https://jobs.ashbyhq.com/openai, https://apply.workable.com/acme/) to fetch that board live, even if it is not in the index.

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

Only jobs posted in the last N days (or first seen in the last N days when the board gives no posting date).

## `newWithinHours` (type: `integer`):

Only jobs that first appeared in the index in the last N hours. Run weekly with 168 to get each week's new jobs. Live board fetches have no first-seen date and are not limited by this.

## `onlyWithSalary` (type: `boolean`):

Keep only jobs whose board publishes a salary range or pay text.

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

Limit to some providers: any of greenhouse, lever, ashby, workable. Leave empty for all.

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

Add the full job description to each result. Turn off for smaller, faster output.

## `descriptionFormat` (type: `string`):

Plain text, HTML as published, or both.

## `maxResults` (type: `integer`):

Stop after this many jobs (newest first). You pay per job returned.

## Actor input object example

```json
{
  "keywords": [
    "data engineer"
  ],
  "searchDescriptions": false,
  "locations": [
    "London"
  ],
  "remote": "any",
  "onlyWithSalary": false,
  "includeDescription": true,
  "descriptionFormat": "text",
  "maxResults": 50
}
```

# Actor output Schema

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

The matching jobs, newest first.

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

Index build time and size, jobs matched and returned, and boards that could not be read.

# 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": [
        "London"
    ],
    "maxResults": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("greyledger/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": ["London"],
    "maxResults": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("greyledger/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": [
    "London"
  ],
  "maxResults": 50
}' |
apify call greyledger/career-site-jobs-search --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,greyledger/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/mlnKBINOql2EP8YkE/builds/Rux5bOeHwQgw0P5oX/openapi.json
