LinkedIn Jobs Monitor - New, Changed & Closed Roles

"That role was open for two months, then vanished. Did they hire, or did they give up?"

Job boards only show what is currently open, so the underlying hiring story is deleted as it happens. Recruitment teams, sales reps, and competitive strategy teams need to track job postings as they appear, change, and close to read market signals accurately.

Track job postings over time as they appear, change, and close, emitting active days open, repost flags, and modified fields mapped to stable jobId identifiers.

⬇️ Input

The actor accepts job search query objects specifying keywords and location filters.

Field	Type	Description
queries	Array	List of search query objects containing keywords and location filters.
maxItems	Integer	Maximum number of job postings to fetch in a single run.
proxyConfiguration	Object	Proxy settings to rotate IPs per request.

⬆️ Output

Outputs structured records directly to the default dataset. Each row describes a single job posting indexed by its stable per-row identifier (jobId).

• jobId (Numeric LinkedIn job posting ID)
• daysOpen (Active days open across observed runs)
• closedWithoutRepost (Flag indicating role closed without being reposted)
• Derived status and modified field attributes.

How it works

1. Job Extraction: Queries LinkedIn guest job search endpoints without login requirements.
2. Card Parsing: Extracts posting ID, title, company, location, salary text, and posting timestamps.
3. Change Tracking: Compares postings across repeated runs to calculate active days open and detect closed or modified listings.
4. Resilient Rate Budgeting: Integrates proxy rotation to prevent rate limiting and ensure stable data streams.

❓ FAQ

How does job closure tracking work?

By monitoring job IDs across sequential runs, the actor detects when a posting disappears from search results, marking its closure date and calculating total active days open.

Why do daysOpen and closedWithoutRepost return null on first run?

Tracking how long a role stays open requires observing the posting over time across multiple runs. On the first run, the actor returns null with a clear reason field rather than guessing.

💬 Your feedback

Need custom role filters, company tracking lists, or dataset integrations? Contact reapxdev@proton.me.

---

Unofficial - not affiliated with LinkedIn. Collects only data visible without logging in. reapx · reapx.dev · reapxdev@proton.me