Career Page Job Scraper & Change Monitor

What this Actor does

Extract current jobs from public company career pages and public ATS-hosted boards, or run the same inputs on a schedule and return only newly added and removed roles.

The Actor prioritizes JSON-LD/schema.org JobPosting data, then optionally uses a conservative fallback for visible public job-card links. It normalizes fields, infers the company from public page metadata when available, deduplicates jobs, supports keyword/location/remote filters, and saves clean records to the dataset.

The prefilled Figma careers example is verified to return public job rows, so you can test the Actor immediately without assembling an input first.

Why this Actor is useful

Use one Actor for both full job snapshots and recurring hiring-change feeds. changesOnly mode stores only public job identifiers in the runner's Apify key-value store and reports new and removed jobs on later runs.

Pricing

This Actor uses simple pay-per-event pricing:

• $0.01 when a run starts.
• $0.005 for each structured job result saved to the dataset.

The Actor charges only for visible outputs and stops cleanly when the run's maximum charge limit is reached. A run returning 100 jobs costs $0.51, excluding any platform usage that Apify may show separately.

Who this is for

• Recruiters
• Staffing agencies
• Job boards
• HR tech founders
• Hiring intelligence teams
• Career newsletter operators
• B2B sales teams targeting hiring companies

Common use cases

• Track new openings across target companies
• Detect removed roles without comparing exports manually
• Feed job boards or hiring newsletters
• Find companies currently hiring for B2B sales outreach
• Monitor competitor hiring signals
• Build recurring hiring intelligence datasets

Input

• startUrls: Public company career pages or public ATS-hosted board URLs.
• maxItems: Maximum number of rows to save.
• maxConcurrency: Number of pages processed in parallel. The default is intentionally conservative.
• extractionMode: Use structuredDataOnly or structuredDataWithFallback. The default enables the safe public job-card fallback.
• monitorMode: Use snapshot for all current jobs or changesOnly for new and removed jobs relative to previous runs.
• monitorStateKey: Separates saved monitoring state for workflows that reuse the same URLs.
• keywords: Optional filters matched against title, company, department, employment type, and included description.
• locations: Optional location filters.
• remoteOnly: Keep only roles visibly identified as remote or distributed.
• includeDescription: Include public job descriptions from JobPosting structured data when available.
• includeRawStructuredData: Adds the original JSON-LD object for audit/debugging.
• requestTimeoutSecs: Maximum time to spend on a single page.
• proxyConfiguration: Optional Apify proxy configuration where permitted by your source review.

Output

• companyName: Hiring company from structured data or public page metadata when available.
• careerPageUrl: The career page or job page supplied or discovered as the source.
• jobTitle: Public job title.
• jobUrl: Public application or job detail URL.
• location: Job location as listed by the source.
• department: Department or team when available.
• employmentType: Employment type such as full-time, contract, or internship.
• remoteStatus: Remote or hybrid signal when available.
• postedDate: Posting date or valid-through date when available.
• detectedAt: Timestamp when this Actor extracted the row.
• sourceUrl: URL where the data was extracted.
• extractionMethod: structured_data for valid JobPosting schema, or fallback_public_job_card for visible public career-page job cards.
• confidenceScore: Heuristic confidence score based on structured data availability.
• missingFields: Output fields that were not available from the source page.
• changeType: snapshot, new, or removed.

Sample input

{
  "startUrls": [
    {
      "url": "https://www.figma.com/careers/"
    }
  ],
  "maxItems": 10,
  "maxConcurrency": 3,
  "extractionMode": "structuredDataWithFallback",
  "monitorMode": "snapshot",
  "monitorStateKey": "default",
  "keywords": [],
  "locations": [],
  "remoteOnly": false,
  "includeDescription": false,
  "requestTimeoutSecs": 30,
  "includeRawStructuredData": false
}

Sample output

{
  "companyName": "Figma",
  "careerPageUrl": "https://www.figma.com/careers/",
  "jobTitle": "Distribution Partner Manager",
  "jobUrl": "https://boards.greenhouse.io/figma/jobs/5813967004?gh_jid=5813967004",
  "detectedAt": "2026-07-24T16:07:46.280Z",
  "sourceUrl": "https://www.figma.com/careers/",
  "extractionMethod": "fallback_public_job_card",
  "confidenceScore": 0.72,
  "missingFields": ["location", "postedDate"],
  "changeType": "snapshot"
}

How to use

Run the verified prefilled example, then replace it with reviewed public career URLs. Export snapshots as JSON, CSV, Excel, or through the Apify API.

For change monitoring:

1. Select changesOnly.
2. Save the input as an Apify task.
3. Run it once to establish the baseline; current roles are returned as new.
4. Schedule later runs. Only new and removed jobs are returned.

Keep the same URLs, filters, and monitorStateKey for a continuous comparison series. Connect the resulting dataset to Google Sheets, Make, Zapier, a webhook, a CRM, or an internal dashboard.

Best practices

• Start with a small set of reviewed public URLs.
• Prefer pages with schema.org JSON-LD structured data.
• Use structuredDataOnly when you want the highest precision and can tolerate empty output.
• Use structuredDataWithFallback when reviewed public career pages show visible job cards but no JobPosting schema.
• Use a stable monitorStateKey for each scheduled workflow.
• Keep maxConcurrency low for smaller websites.
• Review source website rules before scheduling recurring runs.
• Keep includeRawStructuredData off unless you need audit details.

Compliance and responsible use

This Actor is for public data only. It must not be used to bypass logins, paywalls, CAPTCHAs, or security systems, collect private data, gather sensitive personal data, or support spam or abuse. You are responsible for following applicable laws and source website rules.

Limitations

• Output quality depends on public structured data available on the source pages.
• Fallback extraction is intentionally conservative and only looks for visible public job-card/link patterns. It does not claim universal career page support.
• Some fields may be empty when the source does not publish them.
• The Actor does not claim support for any specific third-party platform.
• Website markup and access policies can change.

Troubleshooting

• Empty snapshot output usually means the page exposes neither usable JobPosting data nor recognized visible public job cards.
• Empty changesOnly output means no new or removed jobs were detected since the previous successful run.
• Invalid URL errors mean one or more input URLs are malformed.
• Slow runs can usually be improved by lowering maxConcurrency.
• Missing fields are source-data limitations, not inferred values.

Changelog

• v0.3.0: Added persisted new/removed job monitoring, keyword/location/remote filters, public company-name inference, a verified first-run example, and stronger ATS/hiring-change positioning.
• v0.2.0: Added safe public job-card fallback, confidence metadata, pay-per-event charging, spending-limit handling, memory cost controls, and improved Store positioning.
• v0.1.0: Initial dry-run factory generated MVP.