Company Careers Job Monitor

Find jobs from company careers pages and optionally monitor companies for new, removed, or changed roles.

This Actor is built for a profit-safe, predictable billing model. It uses simple HTTP requests, does not use a browser, and does not use proxies unless you enable them.

What You Get

• Job title
• Company domain
• Job URL
• Location when detected
• Department/team when detected
• Source system, such as Greenhouse, Lever, Ashby, SmartRecruiters, JSON-LD, or the careers page
• Optional monitoring changes between runs

Quick Start

1. Enter company domains or careers-page URLs, for example companycam.com or https://boards.greenhouse.io/embed/job_board?for=companycam.
2. Set Max jobs per company to the number of job rows you want.
3. Leave Proxy mode set to No proxy for the lowest platform cost.
4. Add job title or location filters only if you want a narrower dataset.
5. Turn on Monitor changes since last run when running the Actor on a schedule.

Result Limits And Billing

Apify pay-per-event result billing is based on rows written to the default dataset. This Actor keeps that simple:

• If Max jobs per company is 100, normal output writes up to 100 job rows per company.
• Monitoring snapshots and latest change details are stored in a named key-value store so scheduled runs can compare against previous runs.
• Monitoring does not double the normal dataset output.
• Change rows are written to the dataset only when Output only the changes is enabled.
• Empty or blocked companies are logged in the run status instead of written as paid result rows.

If you provide 5 companies and set Max jobs per company to 100, the maximum normal output is 500 job rows.

Proxy Strategy

Proxy use affects platform cost, so the default is intentionally conservative:

• No proxy: best margin, recommended first choice.
• Auto fallback to datacenter: tries without proxy first, then retries blocked requests with Apify datacenter proxy.
• Datacenter proxy: useful for moderate blocking.
• Residential proxy: strongest but most expensive; use only when the target company blocks other methods.

For most company careers pages, start with No proxy or Auto fallback to datacenter.

Monitoring Logic

When monitoring is enabled, the Actor:

1. Fetches current jobs for each company.
2. Applies filters and the selected job limit.
3. Compares the current jobs with the previous snapshot for that company.
4. Saves the new snapshot to a named key-value store.
5. Saves latest detected changes to a key such as changes-example.com.
6. Outputs either job rows or change rows, depending on Output only the changes.

Detected change types:

• new_job
• removed_job
• changed_job

Input Options

Company Websites Or Careers URLs

Company domains, websites, or direct career-page URLs.

Job Title Keywords

Optional filters matched against title, department, location, description, and URL.

Location Keywords

Optional filters for locations such as remote, london, or new york.

Max Jobs Per Company

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

Monitor Changes Since Last Run

Compares the current run with the previous saved snapshot for each company.

Output Only The Changes

Outputs change events instead of job rows. Use this for scheduled monitoring when you only want newly detected changes.

Proxy Mode

Controls whether Apify Proxy is used. Residential proxy can increase platform usage cost and should be reserved for blocked targets.

Storage

The Actor uses the named key-value store company-careers-job-monitor-state for monitoring state:

• snapshot-<company> stores the latest job snapshot.
• changes-<company> stores the latest detected changes.

Notes

• Careers systems such as Greenhouse, Lever, Ashby, and SmartRecruiters are supported directly when detected.
• Some company sites render jobs only in protected browser-only applications. Those may need a separate browser-based premium Actor.
• For best profit margin, keep proxy mode conservative and charge only for useful job rows.