LinkedIn Hiring Posts Scraper 🚀

LinkedIn Hiring Posts Scraper

Find public LinkedIn posts that announce hiring - "we are hiring", "join our team", "open role" - by hiring phrase, role, industry keyword and location. Get clean, deduplicated post rows with the author, company, role and hiring intent, ready for outreach.

What you get

One dataset row per hiring post found:

Field	Content
Post URL	Canonical link to the post
Company	Best-effort extraction of who is hiring
Posted by	The post author's name (and profile link when available)
Role	The role being hired (matched against your roles, a built-in catalog, or the post wording)
Snippet	The post text
Hiring intent	High (urgent), Medium (explicit hiring), Low (soft signal)
Hiring signal / role / industry / location	Which of your inputs this post matched
Post date	The date or age shown on the post

Job-seeker posts ("looking for opportunities", "open to work") are filtered out automatically - this actor finds employers, not candidates.

Inputs

• Hiring phrases - the phrases to watch for, grouped into one search. Example: we are hiring, looking for, join our team.
• Job roles (optional) - narrow to specific roles. Example: Software Engineer, Marketing Manager.
• Industry / tech keywords (optional) - one search runs per keyword. Example: SaaS, Fintech, React.
• Locations (optional) - one search per keyword runs per location; the location joins the search text. Example: United States, Dubai, London.
• Maximum posts - stop after this many unique posts (1-500).
• Search language - two-letter hint for the search pages.
• Deduplication - drop posts already delivered by an earlier search in the same run.
• Maximum search requests - budget for how many search requests the run may make across all searches. One request loads a small batch of posts, so 100 posts need roughly 34 requests.

Good to know

• Steady pacing. One request at a time with a randomized pause, and the run stops cleanly on any refusal or rate limit. Use a reasonable Maximum posts value.
• Availability, not guarantees. The actor finds what people actually post. A limit is a maximum - narrow searches can return fewer.
• Maintenance. LinkedIn changes its internal formats from time to time. If a run stops with a "response shape changed" message, the actor needs an update - contact us through the Apify store page.

Example output

{
  "postUrl": "https://www.linkedin.com/feed/update/urn:li:activity:7123456789012345678",
  "hiringCompany": "Acme",
  "recruiterName": "Jane Doe",
  "recruiterProfileUrl": "https://www.linkedin.com/in/janedoe/",
  "authorImage": "https://media.licdn.com/dms/image/v2/D4D03AQ.../profile-displayphoto-shrink_400_400/.../0/1696532987627?...",
  "hiringRole": "Software Engineer",
  "postImage": "https://media.licdn.com/dms/image/v2/D4E24AQ.../live-thumbnail-high/.../0/1792591444297?...",
  "postMediaType": "video",
  "postSnippet": "We are hiring a Senior Software Engineer at Acme! Join our team...",
  "hiringIntent": "Medium",
  "hiringKeywordMatched": "we are hiring",
  "jobRoleMatched": "Software Engineer",
  "industryKeyword": "SaaS",
  "locationKeyword": "United States",
  "postDate": "Oct 21",
  "timestamp": "2026-10-26T07:00:00.000Z"
}

authorImage is the author's profile photo. postImage is the post's media (image or video poster frame) with postMediaType telling them apart; both are null when the post has no media. hiringRole falls back to your matched search role when the post text does not name one.