# Careers & Jobs Scraper - Company Job Board Extractor (`samer-samaha/careers-jobs`) Actor

Scrape job listings from company career pages: title, department, location, URL, and new-posting flags. Export to CSV/JSON.

- **URL**: https://apify.com/samer-samaha/careers-jobs.md
- **Developed by:** [Sam S](https://apify.com/samer-samaha) (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 $3.00 / 1,000 result delivereds

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/platform/actors/running/actors-in-store#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

## Careers & Jobs Scraper

Returns every open job listing from a company's careers page: title, department, location, direct apply URL, and whether it's newly posted. Built for recruiters, sales teams, and job seekers who need structured job data instead of scrolling career pages by hand. No API keys, no config files — paste a company careers URL and run.

### Sample output

```json
[
  {
    "id": "stripe-7922618",
    "title": "Account Executive, Existing Business, Platforms",
    "url": "https://stripe.com/jobs/search?gh_jid=7922618",
    "company": "stripe",
    "department": "Acquisitions & Other / PERM / Global Operations",
    "location": "New York, NY",
    "isNew": false
  }
]
```

### Input

| Field | Type | Description | Default |
|---|---|---|---|
| companyUrls | array | List of company career page URLs to scrape | required |
| maxJobsPerCompany | integer | Cap on listings returned per company | 0 (no limit) |
| onlyNew | boolean | Only return listings flagged as newly posted | false |

### Use cases

- **Sales & recruiting intel**: track which companies are hiring for which roles to spot growth signals, budget expansion, or new market entry.
- **Competitive hiring analysis**: monitor competitor job postings to infer product direction or team investment.
- **Job seekers & career coaches**: build a personal feed of openings at target companies without checking each site manually.
- **Market researchers**: aggregate hiring trends by department, location, or company across an industry.
- **ATS migration/QA**: verify job board data integrity after a company switches applicant tracking systems.

### Pricing

Pay-per-result at **$0.003 per listing returned**.

Worked example: scraping 5 companies with an average of 150 open listings each returns 750 results, costing **$2.25** total. Running this weekly to track hiring trends across those 5 companies costs roughly **$9/month** — far cheaper than a manual check or a dedicated intelligence subscription.

### FAQ

**Is this legal?** Yes. This actor extracts publicly listed job postings from company career pages, which is standard practice for aggregators, recruiters, and market researchers. It does not access any private or authenticated data. Always review the target site's terms of service if you plan to redistribute scraped data commercially.

**Does it work on any company's careers page?** It's built and tested against common ATS platforms (Greenhouse, Lever, and similar structured career pages) plus several major company sites. Highly custom or JavaScript-heavy in-house career pages may need a config tweak — open an issue and we'll usually add support within days.

**Does it detect closed or removed listings?** No — it returns a snapshot of currently live postings only. Run it on a schedule to track changes over time.

**Can I filter by location or department?** Filter the output after scraping, or use the `onlyNew` input to only capture newly posted roles between runs.

**How fresh is the data?** Real-time — each run fetches the live careers page at execution time.

### Changelog

- **v1.2** — Added `isNew` flag to detect newly posted listings between runs.
- **v1.1** — Added `maxJobsPerCompany` input and department field parsing.
- **v1.0** — Initial release supporting Greenhouse-based career pages.

# Actor input Schema

## `searchTerm` (type: `string`):

Keyword to match against job titles and locations (e.g. 'software engineer').

## `searchTerms` (type: `array`):

Optional list of keywords; if provided, jobs matching any of these are included.

## `location` (type: `string`):

Preferred office/location text (best-effort filter; Greenhouse does not always expose this server-side).

## `sites` (type: `array`):

Greenhouse company slugs to search, e.g. 'stripe' for boards.greenhouse.io/embed/job\_board?for=stripe.

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

Maximum number of job postings to return in total.

## `isRemote` (type: `boolean`):

If true, best-effort filter for remote-labelled roles.

## `jobType` (type: `string`):

Employment type filter (e.g. full-time, part-time, intern). Not always available on Greenhouse boards.

## `hoursOld` (type: `integer`):

Only return jobs posted within this many hours, if that data is available.

## `countryIndeed` (type: `string`):

Present for cross-actor input compatibility; not used by Greenhouse.

## `googleSearchTerm` (type: `string`):

Present for cross-actor input compatibility; not used by Greenhouse.

## `distance` (type: `integer`):

Present for cross-actor input compatibility; not used by Greenhouse.

## `offset` (type: `integer`):

Number of results to skip before returning (used together with maxResults).

## `easyApply` (type: `boolean`):

Present for cross-actor input compatibility; not used by Greenhouse.

## `linkedinFetchDescription` (type: `boolean`):

Present for cross-actor input compatibility; not used by Greenhouse.

## `linkedinCompanyIds` (type: `array`):

Present for cross-actor input compatibility; not used by Greenhouse.

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

Format hint for downstream consumers (markdown/html/text). Not used for parsing here.

## `enforceAnnualSalary` (type: `boolean`):

Present for cross-actor input compatibility; not used by Greenhouse.

## `userAgent` (type: `string`):

Custom User-Agent header to use for requests.

## `caCert` (type: `string`):

Optional custom CA certificate for requests, if required by your proxy.

## `proxyConfiguration` (type: `object`):

Apify proxy configuration to use for requests.

## Actor input object example

```json
{
  "searchTerm": "software engineer",
  "searchTerms": [],
  "location": "",
  "sites": [
    "stripe"
  ],
  "maxResults": 100,
  "isRemote": false,
  "jobType": "",
  "countryIndeed": "",
  "googleSearchTerm": "",
  "distance": 25,
  "offset": 0,
  "easyApply": false,
  "linkedinFetchDescription": false,
  "linkedinCompanyIds": [],
  "descriptionFormat": "markdown",
  "enforceAnnualSalary": false,
  "userAgent": "Mozilla/5.0 (compatible; CareersJobsBot/1.0; +https://apify.com)",
  "caCert": "",
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

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

All records found in this run.

# 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 = {
    "searchTerm": "software engineer"
};

// Run the Actor and wait for it to finish
const run = await client.actor("samer-samaha/careers-jobs").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 = { "searchTerm": "software engineer" }

# Run the Actor and wait for it to finish
run = client.actor("samer-samaha/careers-jobs").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 '{
  "searchTerm": "software engineer"
}' |
apify call samer-samaha/careers-jobs --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,samer-samaha/careers-jobs"
        }
    }
}

```

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/f2aCUTkFqTudlUSDI/builds/9BymPcXIyGue0GmCG/openapi.json