# Company Careers Job Scraper (`seeb/company-careers-job-scraper`) Actor

Extract open roles from company career pages with job title, location, department, seniority clues, source URL, and hiring-intent lead signals.

- **URL**: https://apify.com/seeb/company-careers-job-scraper.md
- **Developed by:** [Techionik](https://apify.com/seeb) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Stats:** 18 total users, 4 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: No ratings yet

## Pricing

$25.00 / 1,000 results

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

## Company Careers Job Scraper

Company Careers Job Scraper extracts open roles from public company careers pages and supported applicant-tracking systems. It is built for recruiters, sales teams, market researchers, workforce analysts, and B2B lead-generation teams that need structured hiring data from company websites.

The actor detects jobs from Greenhouse, Lever, Ashby, SmartRecruiters, JSON-LD job postings, and conventional careers pages. It returns clean job rows with company, stable job ID, job title, location, department, source system, job URL, posted dates when available, and detection timestamp.

### What it extracts

- Company identifier from the submitted domain or job board
- Stable `jobId` for deduplication and monitoring
- `jobTitle` for the open role
- Location and department/team when visible
- Direct job URL
- Source system such as Greenhouse, Lever, Ashby, SmartRecruiters, JSON-LD, or careers page
- Posted and valid-through dates when available
- `detectedAt` timestamp for audit and refresh workflows
- Optional descriptions when enabled

### Supported source patterns

- Company websites with careers links
- Direct careers pages
- Greenhouse job boards and embedded boards
- Lever postings
- Ashby job boards
- SmartRecruiters company postings
- Pages exposing `JobPosting` JSON-LD

### Input options

- `companyUrls` - company domains, websites, direct careers URLs, or ATS board URLs
- `keywords` - optional role, department, or keyword filters
- `locations` - optional location filters such as `remote`, `london`, or `new york`
- `maxJobsPerCompany` - maximum job rows per company
- `monitorChanges` - compare against the previous saved snapshot
- `onlyChanges` - output only detected changes when monitoring
- `proxyMode` - direct, auto fallback, datacenter, or residential proxy strategy
- `includeDescriptions` - include trimmed job descriptions when needed

### Example input

```json
{
  "companyUrls": ["https://boards.greenhouse.io/companycam"],
  "keywords": ["engineer", "product"],
  "locations": ["remote"],
  "maxJobsPerCompany": 25,
  "monitorChanges": false,
  "proxyMode": "none"
}
```

### Example output

```json
{
  "company": "companycam",
  "jobId": "4fcb6a0a37ed834c",
  "jobTitle": "Senior Software Engineer",
  "location": "Remote",
  "department": "Engineering",
  "url": "https://boards.greenhouse.io/companycam/jobs/123456",
  "source": "greenhouse",
  "postedAt": "2026-08-01T12:00:00.000Z",
  "validThrough": null,
  "detectedAt": "2026-08-11T08:00:00.000Z"
}
```

### Use cases

- Build hiring-signal lead lists from target accounts
- Enrich account-based sales workflows with current open roles
- Monitor competitors or portfolio companies for team growth
- Track role categories across a market segment
- Feed recruiting dashboards, spreadsheets, or CRM workflows

### Reliability notes

The actor works with public careers pages and public ATS endpoints. Some company sites render jobs only in protected browser applications or block automated requests. In those cases, use direct ATS URLs when available, enable proxy fallback, or use a browser-based actor for protected sources.

# Actor input Schema

## `companyUrls` (type: `array`):

Company domains, websites, or direct careers-page URLs. Examples: companycam.com, https://boards.greenhouse.io/embed/job\_board?for=companycam

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

Optional keywords to match in job titles, departments, or descriptions. Leave empty to return all detected jobs.

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

Optional location filters. Examples: remote, london, new york, united states.

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

Maximum job rows to write per company in normal output mode. 0 = all detected jobs.

## `monitorChanges` (type: `boolean`):

Compare against the previous saved snapshot in a named key-value store and store new, removed, and changed jobs there. Normal job output still respects Max jobs per company.

## `onlyChanges` (type: `boolean`):

When change detection is on, output change events instead of job rows. Leave off for normal job output.

## `proxyMode` (type: `string`):

Use no proxy by default for best profit margin. Auto retries blocked requests with Apify datacenter proxy. Residential should be used only when necessary because it increases platform usage cost.

## `proxyCountryCode` (type: `string`):

Optional two-letter country code for residential proxy, for example US or GB. Used only when Proxy mode is Residential.

## `includeDescriptions` (type: `boolean`):

Include short job description text when detected. Keeping this off produces smaller, cheaper result rows.

## `maxRunSeconds` (type: `integer`):

Cost protection timeout for the whole run. The Actor stops before another company if the budget is nearly exhausted.

## Actor input object example

```json
{
  "companyUrls": [
    "companycam.com",
    "https://boards.greenhouse.io/embed/job_board?for=companycam"
  ],
  "keywords": [
    "sales",
    "engineer",
    "customer success"
  ],
  "locations": [
    "remote",
    "london"
  ],
  "maxJobsPerCompany": 100,
  "monitorChanges": false,
  "onlyChanges": false,
  "proxyMode": "none",
  "proxyCountryCode": "",
  "includeDescriptions": false,
  "maxRunSeconds": 300
}
```

# Actor output Schema

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

Normal runs contain job rows. When Output only the changes is enabled, rows contain change events.

# 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 = {
    "companyUrls": [
        "https://boards.greenhouse.io/embed/job_board?for=companycam"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("seeb/company-careers-job-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 = { "companyUrls": ["https://boards.greenhouse.io/embed/job_board?for=companycam"] }

# Run the Actor and wait for it to finish
run = client.actor("seeb/company-careers-job-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 '{
  "companyUrls": [
    "https://boards.greenhouse.io/embed/job_board?for=companycam"
  ]
}' |
apify call seeb/company-careers-job-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,seeb/company-careers-job-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/xXlltedzrmzSIlA7R/builds/XMGnwvxssucjMf8lx/openapi.json