Monster Jobs Search Scraper

Extract complete public Monster.com job postings with bounded browser navigation. The Actor captures Monster's own structured search payload or current rendered result cards, validates title, company, location, description, and official job URL, deduplicates IDs, and stores only complete jobs.

Input

• query: required job keyword.
• location: optional US location.
• maxItems: 1 to 200 complete jobs.
• maxPages: 1 to 20 result pages.

{"query":"developer","location":"","maxItems":3,"maxPages":2}

Output and diagnostics

The Dataset contains only complete source-backed job records, marked recordType: "job" and sourceVerified: true. The records come from Monster's search payload or rendered listing; detailVerified is false because the Actor does not open separate detail pages. Diagnostics, access evidence, rejected candidates, and run counts are kept in the RUN_SUMMARY key-value record and are never written as Dataset rows. The Actor uses one ordinary direct browser route and does not accept proxy settings.

Apify's platform run status is separate from RUN_SUMMARY.resultStatus:

• SUCCEEDED / COMPLETE: eligible jobs were stored and the bounded search finished without a recorded limitation.
• SUCCEEDED / LIMITED: at least one awaited Dataset write succeeded, followed by a later error, confirmed barrier, or rejected incomplete candidate.
• SUCCEEDED / SKIPPED: a confirmed Monster access barrier was recorded and the Actor stopped without retrying or switching routes.
• SUCCEEDED / DEFERRED: the search returned no eligible jobs, but did not provide evidence that the result was genuinely empty.
• SUCCEEDED / NO_DATA: the first-party search response explicitly reports totalSize: 0 and an empty result list.
• FAILED / FAILED: a fatal runtime or storage error occurred before any eligible job was stored.

The summary's persistedRecords count includes only awaited successful Dataset writes. Unofficial search indexes are not used as a fallback.

Cost and responsible use

Browser requests are capped by maxPages, with one bounded crawl request and a 60-second handler limit. Start with the provided three-item input. The Actor reads public pages only and does not log in or bypass access controls. Follow Monster's terms and applicable privacy and data-use laws.

Local QA

npm ci --ignore-scripts --no-audit --no-fund
node --check src/main.js
node --check src/lifecycle.js
node --check src/access-policy.js
node --check src/scraper.js
node --check validate-datasets.js
npm test
apify validate-schema
apify run --input-file INPUT.json
npm run validate-dataset -- "<dataset-directory>" "<RUN_SUMMARY.json>"