LinkedIn Hiring Posts Scraper

Discover public LinkedIn posts mentioning hiring. Search by hiring phrase, job role, industry keyword and location, then export the available details as JSON, CSV or Excel.

Input

{
  "hiringKeywords": ["we are hiring", "looking for", "join our team"],
  "jobRoles": ["Software Engineer"],
  "keywords": [],
  "locations": ["United States"],
  "maxResults": 100,
  "maxSearchRequests": 20,
  "language": "en",
  "deduplicateResults": true
}

Hiring phrases are required. Roles, keywords and locations are optional. The Actor keeps the supplied search criteria and does not substitute unrelated searches when results are unavailable.

Limits

Plan	Maximum posts per run
Free	10
Paid	500

Paid discovery uses a shared budget of 20 search requests by default, including retries. Set maxSearchRequests (1–500) to control that budget. It reviews query variants before moving to later pages. The same record limit and deduplication apply across every query, and discovery stops when the selected limit is reached. A lower platform result limit takes precedence. These limits are maximums, not guaranteed result counts.

Output

Each record includes the post URL, available hiring company, author name, inferred hiring role, search snippet, hiring-intent level, matching hiring phrase and scrape timestamp.

jobRoleMatched, industryKeyword and locationKeyword describe the search criteria that surfaced the post. They do not independently verify the post's role, industry or location. hiringKeywordMatched contains a requested phrase only when it appears in the available result text.

hiringIntent is inferred from wording: High for urgency, Medium for direct hiring invitations and Low for softer recruiting signals. Clear first-person job-seeking posts are excluded. Search snippets are incomplete, so classification and author/company extraction can still be imperfect.

Missing fields remain null. postDate is populated only when a date hint appears in the snippet; the scrape timestamp is not the publication date. Results are indexed public search hits, not a guarantee that a vacancy is still open. The Actor does not fetch full post text or private contact details.

Reliability

A temporary search failure is retried once, within the same request budget. There are no additional recovery sweeps. Seed queries scan through empty gaps; individual phrase/role queries stop after two genuinely empty pages. Failed or duplicate-only pages do not stop later pages. Per-query logs show results received, parsed, added and saved toward your selected target. Successful records are retained when some pages remain unavailable. The key-value store's RUN_REPORT reports completion, partial results or failure, plus available search totals and requests used. budget_limited means discovery stopped at the request limit with the available records retained.

Authentication errors and runs in which every search page fails are reported as failures. Unrelated website URLs are skipped while later search pages continue. A run with only unusable results is reported as a failure rather than a genuine empty search. If no posts were saved and pages remain unresolved, the run fails rather than claiming there were no matches. A successful empty search returns zero records. No LinkedIn login or cookies are required.