Public Job Posting Detail Agent

Extract one structured job posting record from each user-provided public job detail URL. The Actor reads public HTML and Schema.org JobPosting evidence, then returns title, company, location, remote/visa signals, employment type, salary hints, dates, apply URL, skills, evidence snippets, and a stable hash.

This product is intentionally different from the portfolio's site-level Hiring Signal Actor. It does not discover careers pages, crawl job lists, count all open roles, or score company hiring intensity. It only analyzes the job detail URLs you provide.

What It Returns

• jobTitle, companyName, locationSummary, employmentType, and descriptionSnippet.
• salarySummary, datePosted, validThrough, applyUrl, remoteSignal, and visaSignal when visible.
• skills, matchedSkills, and matchedLocations for filtering.
• responsibilities, qualifications, evidenceSnippets, and evidenceUrls.
• jobHash and changeStatus for monitoring job-posting changes.

Good Fits

• Normalize public job detail URLs that a user, CRM, or AI agent already has.
• Check whether a role matches target skills or target locations.
• Monitor public job detail records for changes without charging unchanged records.
• Convert JobPosting JSON-LD and visible public HTML into a compact dataset.

Not A Fit

• LinkedIn, Indeed, Google Jobs, Facebook, or other job-board search/list scraping.
• Company-wide hiring intensity analysis. Use the site-level Hiring Signal Actor for that task.
• Candidate data, resumes, recruiter-private contact enrichment, login-only pages, or application form submission.

Safety Boundary

• Public HTTP and HTTPS job detail pages only.
• No login, cookies, JavaScript execution, form submission, CAPTCHA bypassing, account creation, candidate enrichment, or private-person profiling.
• Query strings, fragments, URL credentials, path parameters, private networks, localhost, .local, account-like sensitive paths, and token-like path segments are rejected or safely redacted.
• HTML/text responses are capped at 3 MB.
• The Actor does not follow related-job, more-jobs, or all-jobs links.

Pricing Behavior

The pay-per-event setup charges only for useful public job posting records:

• apify-actor-start: charged once when a run starts.
• useful-job-posting-result: charged only for a new or changed job detail record with enough public evidence and any required skill/location match.

The Actor intentionally does not configure apify-default-dataset-item, so errors, duplicate inputs, unchanged records, focus misses, blocked platforms, and low-evidence pages can be written without charging the useful-result event.

Example Input

{
  "jobUrls": ["https://www.mozilla.org/en-US/careers/position/gh/7622995/"],
  "focusSkills": ["ai"],
  "focusLocations": ["remote"],
  "requestTimeoutSecs": 20
}