Only 22.6% of U.S. workers describe themselves as actively looking for a new job, down from 33.4% in 2021 — the other 51.1% call themselves passively open.

Just 22.6% of workers are actively job hunting (Workable, 2023) — the rest are passive. Here's what to track beyond the 'Open to Work' badge in 2026.

Passive Candidate Signals: What to Track Beyond 'Open to Work' in 2026

Recruiting Intelligence Editors

Datamagnet Team

Datamagnet

Home

Blog

Recruiting Intelligence

Passive candidate signals are behavioral and employer-level data points — like tenure length, content engagement, profile updates, and company layoffs or funding events — that indicate someone may be open to a new role even though they haven't marked themselves 'Open to Work.' Only 22.6% of workers are actively job searching (Workable, 2023), so these signals cover most of the addressable talent pool.

What are passive candidate signals?

Yes, but as a lagging confirmation rather than a starting point. LinkedIn's own data shows candidates with the badge respond to InMails at a 37% higher rate (LinkedIn Talent Blog, 2022), so it's still worth prioritizing — it just shouldn't be your only filter, since it misses the majority of people who'd respond to the right outreach.

Is the 'Open to Work' badge still useful?

Most teams find two or more independent signals within a 30-day window is a reliable threshold — a single signal like one profile update is too noisy on its own. Combining an employer-level trigger with an individual signal tends to produce the highest-confidence shortlist.

How many signals should trigger outreach?

Manually, yes, for a shortlist of a dozen or so candidates — but it doesn't scale. Once you're tracking more than a handful of accounts, an automated Person Engagement Signal or Company Engagement Signal monitor removes the manual profile-checking entirely.

Can I track these signals without a dedicated tool?

Job-change monitoring is a related but distinct discipline — it watches people who've already moved, useful for re-engaging alumni or tracking champions who switch companies, rather than net-new passive sourcing.

How does this connect to job-change tracking?

Only 22.6% of workers are actively job hunting. Learn 6 passive candidate signals recruiters can track instead of waiting for the badge.

How to Track Passive Candidate Signals Beyond 'Open to Work' (2026)

Seventy-six percent of technology employers say they can't find the skilled talent they need (ManpowerGroup, 2025 Talent Shortage Survey, 2025). If your technical recruiting team is still manually scrolling LinkedIn every morning...

76% of tech employers can't find skilled talent (ManpowerGroup, 2025). Build a signal dashboard that flags job changes and engagement before competitors do.

How to Build a Talent Sourcing Signal Dashboard for Technical Recruiters

Recruiting Intelligence Editorial Team

A minimum viable version with one signal type, basic scoring, and a simple queue UI typically takes one to two weeks for a small internal tooling team. A full version with five signal types, company-level data, and a polished UI usually takes four to six weeks.

How long does it take to build a talent sourcing signal dashboard?

Yes, with tradeoffs. Tools like Retool or Streamlit can wrap API calls into a usable internal dashboard without deep front-end work, but you still need someone comfortable configuring webhooks and writing basic scoring logic.

Can I build this without an engineering team?

Build a health check that flags when signal volume for a given monitor drops to zero unexpectedly, since that usually means a broken webhook, an expired API key, or a paused monitor rather than an actual quiet period.

What if a signal source stops sending data?

Add role- and team-based filtering so each recruiter sees only relevant signals, and add a claim/assign mechanic so two recruiters don't reach out to the same candidate. At larger scale, make scoring weights configurable per team.

How do I scale this for a larger recruiting team?

They solve different problems. An ATS search finds candidates matching static criteria among people already in your database, while a signal dashboard finds people who just became more reachable. Stack Overflow's 2025 Developer Survey found 45.6% of developers describe themselves as 'not looking,' meaning most technical talent isn't sitting in an ATS at all.

Is a signal-based approach better than a traditional ATS search?

A step-by-step guide to building a sourcing signal dashboard that flags job changes, engagement, and hiring freezes for technical recruiters.

Build a Talent Sourcing Signal Dashboard for Technical Recruiters (2026)

Your best hire this quarter isn't wearing the green Open to Work ring. In 2026, roughly 75% of the global workforce counts as passive - not actively job hunting - while only 25% is openly searching.

75% of the workforce is passive, not job hunting (LinkedIn). Track 6 passive candidate signals - tenure, instability, engagement - to source them first.

Passive Candidate Signals: What to Track Beyond 'Open to Work'

Data & GTM Research

A passive candidate signal is any behavioral or company-side data point that indicates someone might be open to a new role without them explicitly saying so - tenure stagnation, employer instability like layoffs or leadership churn, LinkedIn engagement shifts, and profile or skill updates all qualify. None of these require the candidate to flip on Open to Work.

What counts as a passive candidate signal?

Generally no. A single weak signal, like one skill added or one profile edit, has too high a false-positive rate on its own. Stack at least two signals, or one strong trigger like a company layoff, before sending a personalized message - it dramatically improves reply rates and avoids wasting outreach on people who aren't actually receptive.

Is it worth reaching out based on a single signal?

Layoffs sharply increase receptiveness among survivors, not just people directly cut. Employers announced over 1.2 million job cuts in 2025, up 58% year over year, and job applications from affected sectors spiked nearly 150% within weeks. Move fast once you spot the signal.

How do layoffs affect passive candidate receptiveness?

Most of it can. Job change, company engagement, and person engagement signals can all be registered against target accounts and candidates, with matches delivered via webhook so a recruiter isn't manually re-checking profiles every week.

Can passive candidate signal tracking be automated?

The badge only surfaces the 25% of the workforce actively searching. Signal-based sourcing tracks tenure, employer instability, and engagement shifts across the other 75%, letting you reach candidates before they've decided to search publicly - and before every other recruiter sees the same green ring you do.

How is signal-based sourcing different from just using the Open to Work filter?

The Open to Work badge only shows 25% of the market. Here are 6 passive candidate signals recruiters should track instead - with data on why they matter.

Passive Candidate Signals: What to Track Beyond 'Open to Work' (2026)

> **Disclosure:** Datamagnet publishes this article. Product capabilities described below are based on public documentation, retrieved July 19, 2026. Collect and process public profile data in line with LinkedIn's terms, GDPR, and CCPA, and confirm your own compliance posture before you run any monitoring workflow.

# How to Monitor Talent Entries and Exits at AI Labs in Real Time

A talent map of frontier AI labs is out of date the moment you finish building it. Someone on your spreadsheet already left for a competitor, and someone who just joined isn't on your radar at all. Between OpenAI, Anthropic, Google DeepMind, Meta's Superintelligence Labs, and xAI, researchers move constantly — and a static list can't keep up.

This guide isn't about building a better spreadsheet. It's about replacing the spreadsheet with a watcher: one system that tracks the named researchers and executives you already care about, plus a second lane that surfaces people you've never heard of the moment they join or leave a lab you're watching.

> **TL;DR**
>
> - B2B contact data decays roughly **2% a month** — about 22.5% a year — so any hand-built AI-lab roster is already wrong by the time you finish it ([HubSpot, Database Decay Simulation](https://www.hubspot.com/database-decay), retrieved 2026-07-19).
> - Median U.S. employee tenure sits at just **3.9 years**, and it runs shorter in high-demand technical roles like AI research ([U.S. Bureau of Labor Statistics, Employee Tenure Summary](https://www.bls.gov/news.release/tenure.nr0.htm), retrieved 2026-07-19).
> - SignalFire's 2025 research found **retention gaps of 10+ points** between top AI labs, meaning some labs bleed talent to rivals far faster than others ([SignalFire, State of Talent Report 2025](https://www.signalfire.com/blog/signalfire-state-of-talent-report-2025), retrieved 2026-07-19).
> - Build two lanes: a **known-names watchlist** for people you already track, and a **discovery lane** that catches new entrants and exits you didn't know to look for.
> - Route both lanes through a [job-change signal](https://docs.datamagnet.co/api-reference/endpoints/signal-create) with [webhook](https://docs.datamagnet.co/api-reference/webhooks) delivery so a move reaches your team in minutes, not at your next quarterly refresh.

![A radar-style watcher dashboard showing researcher profile cards moving between AI lab building icons with entry and exit arrows](https://cdn.sanity.io/images/mmp5yyqj/production/133e027e4a469d14681b130122d28be831df50b7-1376x768.jpg)

## Why Do Hand-Built AI Lab Talent Maps Fall Apart So Fast?

Hand-built talent maps fall apart because the underlying data decays continuously, not in one big break. B2B contact records go stale at roughly 2% every month — about 22.5% a year — as people change roles, titles, and employers ([HubSpot, Database Decay Simulation](https://www.hubspot.com/database-decay), retrieved 2026-07-19). Map 200 AI researchers into a sheet today, and a meaningful chunk of those rows will be wrong before your next review.

Tenure compounds the problem in research roles specifically. The U.S. Bureau of Labor Statistics put median employee tenure at 3.9 years in its January 2024 release, and turnover tends to run faster in competitive technical fields where compensation and mission both shift quickly ([U.S. Bureau of Labor Statistics, Employee Tenure Summary](https://www.bls.gov/news.release/tenure.nr0.htm), retrieved 2026-07-19). Isn't it strange that teams still track this kind of movement in a spreadsheet nobody remembers to open?


Most talent-mapping efforts treat a researcher's employer as a fixed fact instead of a timestamped observation. That's the root error. A row that says "works at Lab X" is only ever true as of the day someone typed it. Once you start treating every employer field as "true as of [date]" instead of "true," the fix becomes obvious — you need a system that re-checks the timestamp constantly, not a person who remembers to.

## What Does "Watching Entries and Exits" Actually Mean?

Watching entries and exits means treating a job change as two distinct events, not one. An **exit** is when a tracked researcher leaves a lab you're monitoring — a signal that they're newly reachable, or that the lab just lost expertise. An **entry** is when someone joins a lab you're watching, whether it's a name you already tracked or a completely new one. Read separately, each event tells you something different.

Why split them at all? Because the action you take is different for each. An exit from a competitor lab might be a recruiting opportunity or a warning that a rival is about to ship something new. An entry into a lab you track might mean that lab just closed a hiring push in a specific research area — a market signal you'd otherwise only learn about from a press release, weeks after the fact.

![Two building icons connected by a curved arrow, one labeled Exit with a person icon leaving and one labeled Entry with a person icon arriving](https://cdn.sanity.io/images/mmp5yyqj/production/1e6acce1e9afab901b0de9b82bdc13436668f25e-1376x768.jpg)

According to a Datamagnet [signal](https://docs.datamagnet.co/api-reference/endpoints/signal-create), a `job_change` event fires the moment a tracked profile's current company field changes — which is precisely the raw material for detecting both directions. The same event is an exit relative to the old employer and an entry relative to the new one. You just need to read it from both angles.

## How Do You Build a Watchlist for Researchers You Already Know?

You build the known-names lane by registering a job-change signal over a saved list of profiles. This is the same mechanic Datamagnet documents in its [Champion Tracker cookbook](https://docs.datamagnet.co/cookbooks/champion-tracking), which tracks power users and decision-makers for job changes so a team can re-engage them at their new company — the mechanics transfer directly to a list of researchers, founders, or lab executives you want to keep eyes on.

Set it up once with the [Create Signal endpoint](https://docs.datamagnet.co/api-reference/endpoints/signal-create), which registers a monitor that tracks LinkedIn profiles for job changes, new posts, or engagement events. From there, use the [Update Signal endpoint](https://docs.datamagnet.co/api-reference/endpoints/signal-update) to add or remove names as your watchlist evolves — a new hire announcement, a conference talk, a paper author list are all reasons to add someone mid-quarter. Every active monitor is auditable through the [List Signals endpoint](https://docs.datamagnet.co/api-reference/endpoints/signal-list), so nothing runs silently without your team knowing it's there.

![A saved watchlist of researcher profile cards feeding into a single monitor icon labeled Known-Names Lane](https://cdn.sanity.io/images/mmp5yyqj/production/4c60ed8e752c60ecdc9c967152b05d2789a4e110-1376x768.jpg)

**Citation capsule:** A job-change signal turns manual profile-checking into a passive feed. Instead of opening 200 LinkedIn profiles every Monday to check for updates, one monitor watches the whole list and only notifies you when a tracked person's employer field actually changes — cutting a weekly task down to zero recurring effort.

## How Do You Catch New Entrants You've Never Tracked?

You catch new entrants with a repeatable search, not a static list — because you can't watch a name you don't know yet. Run a scheduled query against your target labs using the [ICP People Search endpoint](https://docs.datamagnet.co/api-reference/endpoints/icp-people-search), which finds people by job title, seniority, function, company, and location without requiring internal IDs. Compare each run's results against the last one, and anyone new is, by definition, a fresh entrant.

The [People Search DB endpoint](https://docs.datamagnet.co/api-reference/endpoints/people-search-db) sharpens this further with include and exclude filters on company LinkedIn URLs. Exclude the labs you've already fully mapped and include only the ones you're watching for growth, and each run surfaces just the people who showed up since the last query — no need to re-review names you've already seen.


The exclude filter is the part teams underuse. Run the identical ICP query on a weekly cadence and exclude every company you sourced from last time. What's left over isn't a random sample — it's the exact set of people who moved into your target companies since your last check. You've effectively converted a search endpoint into a change detector, without writing any custom diffing logic yourself.

For company-level context on *why* a lab might be hiring, pair people search with company data. The [ICP Company Search endpoint](https://docs.datamagnet.co/api-reference/endpoints/icp-company-search) filters targets by industry, headcount, and technology, and the [Funding Rounds endpoint](https://docs.datamagnet.co/api-reference/endpoints/funding-rounds) shows a company's Crunchbase funding history — a fresh raise often precedes a hiring wave, so the two signals read well together.

## How Do You Read an Exit as a Signal Instead of Just an Alert?

An exit is worth more than a notification if you treat it as a prompt to ask why. A single departure could be routine. A cluster of departures from the same team, in the same quarter, usually isn't. SignalFire's 2025 research found retention gaps of more than 10 percentage points between top AI labs over a two-year window, meaning some labs consistently lose researchers to rivals at a much higher rate than others ([SignalFire, State of Talent Report 2025](https://www.signalfire.com/blog/signalfire-state-of-talent-report-2025), retrieved 2026-07-19).

That gap is exactly the pattern a watcher should surface on its own, rather than something your team notices only after reading an industry newsletter. When your known-names lane flags three exits from the same research group inside a month, that's not three isolated alerts — it's a single, higher-priority signal worth escalating.

![A bar chart-style icon showing one lab with a tall stack of exit arrows and another lab with a short stack, illustrating uneven retention between labs](https://cdn.sanity.io/images/mmp5yyqj/production/e33b65b5d98bac8664da701fd6befa186bd710f7-1376x768.jpg)

**Citation capsule:** Retention varies sharply between AI labs — SignalFire measured double-digit percentage-point gaps in two-year retention among leading labs in its 2025 report. A watcher that groups exits by employer and time window turns that kind of industry-level finding into an operational alert your team can act on the same week, not months later.

Pair exit data with executive-specific monitoring for the people who matter most to your strategy. Datamagnet's [Executive Intelligence cookbook (the VIP Engagement Radar)](https://docs.datamagnet.co/cookbooks/executive-intelligence) is built to flag the moment a high-value prospect or executive posts, and a [Person Engagement signal](https://docs.datamagnet.co/api-reference/endpoints/signal-person-engagement) can watch a specific researcher's posts and mentions even before any formal job-change field updates — often the first public hint that someone is moving.

## How Do You Turn a Wave of Moves Into a Market Signal?

A wave of moves becomes a market signal once you stop reading events one at a time and start reading them as a group. Track entries and exits by lab, by month, and by research area, and patterns surface that a single alert never would: a lab quietly rebuilding its safety team, or a rival suddenly staffing up around a specific model architecture.


Watching this play out over several hiring cycles, the clearest tell isn't any single high-profile move — it's the follow-on entries in the weeks after. A well-known researcher joins a lab, and within a month, two or three former colleagues follow the same path. Tracking only the headline move misses that entire second wave, which is often more useful than the first for understanding where a lab's roadmap is actually headed.

The [Company Posts endpoint](https://docs.datamagnet.co/api-reference/endpoints/company-posts) helps here too — pulling a lab's recent posts, including hiring announcements, gives context for why an entry wave started. And Datamagnet's own product roadmap reflects this same shift toward pattern-level signals: the [July 2026 changelog](https://docs.datamagnet.co/changelog/july-2026) adds new company insights covering interests, similar profiles, recommendations, and headcount and hiring trends — built for exactly this kind of aggregate reading rather than one-off lookups.

## How Fast Should Alerts Reach Your Team?

Fast enough that you're not the last team to know. A researcher who just left a competitor lab is fielding outreach from every recruiter and account team with a working alert system within days, sometimes hours. A watcher that reports moves on a weekly digest is a watcher that consistently loses the reach-out race.

Delivery is what makes speed real, not detection alone. Register a [webhook](https://docs.datamagnet.co/api-reference/webhooks) and Datamagnet posts the job-change event to your endpoint the moment it's detected, complete with signature verification and retry handling, so you're not polling profiles on a timer and hoping you didn't miss one. From there, routing to Slack or your CRM is a short integration, not a new project.

Why should a human check 200 profiles by hand every week when a signal checks them continuously and only interrupts your team when something has actually changed? That's the entire case for a watcher over a spreadsheet, stated as plainly as possible.

## Build the Watcher Instead of Refreshing the Map

Every AI lab talent map goes stale the same way: quietly, continuously, and faster than anyone expects. Stop refreshing it manually. Register your known names to a job-change signal, run a scheduled discovery query against the labs you track, and route both lanes through a webhook so entries and exits reach your team the day they happen. For a deeper look at scoring the people this watcher surfaces, see how [recency-aware candidate sourcing](https://www.datamagnet.co/post/real-time-intent-signal-apis-job-changes/) ranks fresh moves over old resumes. **[Start a job-change watcher](https://www.datamagnet.co/signal-api/) and see who's entering or leaving your target labs this week.**

## Frequently Asked Questions

### How do you track when someone joins or leaves an AI lab?

Register their LinkedIn profile to a job-change signal through the [Create Signal endpoint](https://docs.datamagnet.co/api-reference/endpoints/signal-create), which fires an event the moment the tracked profile's employer field changes. Pair it with a [webhook](https://docs.datamagnet.co/api-reference/webhooks) so the event reaches your team immediately instead of waiting for a manual check.

### What's the difference between an entry and an exit signal?

They're two readings of the same job-change event. An exit is the move viewed from the old employer's side — a researcher leaving a lab you track. An entry is the same move viewed from the new employer's side — someone joining a lab you track, known or unknown. Reading both separately clarifies which action, recruiting outreach or competitive analysis, actually applies.

### How do I find new AI lab hires I've never heard of before?

Run a scheduled query with the [ICP People Search endpoint](https://docs.datamagnet.co/api-reference/endpoints/icp-people-search) or [People Search DB endpoint](https://docs.datamagnet.co/api-reference/endpoints/people-search-db), filtered to your target labs. Exclude companies you've already mapped from prior runs, and anyone new in the results is, by definition, a recent entrant you hadn't tracked before.

### Why do AI labs lose talent to each other so often?

Research roles carry short average tenure to begin with — the U.S. Bureau of Labor Statistics put overall median tenure at 3.9 years in its January 2024 release ([BLS](https://www.bls.gov/news.release/tenure.nr0.htm), retrieved 2026-07-19) — and SignalFire's 2025 research found some labs run over 10 percentage points behind rivals on two-year retention ([SignalFire](https://www.signalfire.com/blog/signalfire-state-of-talent-report-2025), retrieved 2026-07-19), meaning cross-lab movement is uneven, not random.

### Is monitoring public AI lab hiring moves compliant?

Datamagnet collects data from public sources and supports GDPR- and CCPA-aligned handling, but your specific obligations depend on jurisdiction and how you use the data. Review your own compliance posture and the [security and data practices](https://www.datamagnet.co/security/) behind any monitoring workflow before you scale it, and treat every signal as a prompt to verify, not automatic permission to contact someone.

## Sources

- HubSpot, Database Decay Simulation, retrieved 2026-07-19, https://www.hubspot.com/database-decay
- U.S. Bureau of Labor Statistics, Employee Tenure Summary (January 2024 release), retrieved 2026-07-19, https://www.bls.gov/news.release/tenure.nr0.htm
- SignalFire, State of Talent Report 2025, retrieved 2026-07-19, https://www.signalfire.com/blog/signalfire-state-of-talent-report-2025
- Datamagnet, Create Signal endpoint, retrieved 2026-07-19, https://docs.datamagnet.co/api-reference/endpoints/signal-create
- Datamagnet, Changelog: July 2026, retrieved 2026-07-19, https://docs.datamagnet.co/changelog/july-2026
- Datamagnet, Webhooks, retrieved 2026-07-19, https://docs.datamagnet.co/api-reference/webhooks

A talent map of frontier AI labs is out of date the moment you finish building it. Someone on your spreadsheet already left for a competitor, and someone who just joined isn't on your radar at all.

B2B contact data decays about 2% a month, so a hand-built AI lab talent map is wrong within weeks. Build a live watcher that flags every entry and exit.

How to Monitor Talent Entries and Exits at AI Labs in Real Time

Register their LinkedIn profile to a job-change signal through the Create Signal endpoint, which fires an event the moment the tracked profile's employer field changes. Pair it with a webhook so the event reaches your team immediately instead of waiting for a manual check.

How do you track when someone joins or leaves an AI lab?

They're two readings of the same job-change event. An exit is the move viewed from the old employer's side. An entry is the same move viewed from the new employer's side. Reading both separately clarifies which action, recruiting outreach or competitive analysis, actually applies.

What's the difference between an entry and an exit signal?

Run a scheduled query with the ICP People Search endpoint or People Search DB endpoint, filtered to your target labs. Exclude companies you've already mapped from prior runs, and anyone new in the results is a recent entrant you hadn't tracked before.

How do I find new AI lab hires I've never heard of before?

Research roles carry short average tenure to begin with, and SignalFire's 2025 research found some labs run over 10 percentage points behind rivals on two-year retention, meaning cross-lab movement is uneven rather than random.

Why do AI labs lose talent to each other so often?

Datamagnet collects data from public sources and supports GDPR- and CCPA-aligned handling, but obligations depend on jurisdiction and use case. Review your compliance posture before scaling a monitoring workflow, and treat every signal as a prompt to verify, not automatic permission to contact someone.

Is monitoring public AI lab hiring moves compliant?

Hand-built AI-lab talent maps decay in weeks. Build a watcher that tracks known researchers and surfaces new entrants and exits automatically.

Track AI Lab Talent Entries and Exits in Real Time

Custom Recruiting Tools

Real-Time People Data API

Candidate Sourcing

Modern recruiting rewards speed, and most off-the-shelf applicant tracking systems (ATS) weren't built to deliver it. You get generic workflows, limited integrations, and a recruiter stuck reconciling stale candidate data by hand instead of talking to people.

Technical roles cost $28,000 per hire on average. Learn the 3-Layer Sourcing Stack for building custom recruiting tools with real-time people data APIs.

Build Internal Recruiting Tools with Real-Time People Data

The Datamagnet team builds real-time people and company data APIs for B2B sales and recruiting teams. We publish research on sales intelligence, data enrichment, and pipeline efficiency.

Recruiting

Datamagnet is a strong choice for real-time people data in recruiting tools, with sub-500ms latency, on-request scraping for fresh data, and 75+ data points per profile. It's built for accuracy on recent job changes and offers a developer-friendly API for integration.

What is the best API for real-time people data in recruiting tools?

Costs include API fees (Datamagnet starts at $39/month; enterprise solutions can run $15,000-$50,000+ annually), development time for an MVP, and hosting. Reduced cost-per-hire and higher recruiter productivity often offset this within the first year (Cleanlist, 2026).

How much does it cost to build a custom recruiting tool with people data APIs?

Define a lawful basis such as legitimate interest and run a balancing test before processing. Practice data minimization, give candidates a clear opt-out, and support erasure requests within one month, as GDPR Article 12(3) requires (Cleanlist, 2026).

How do I ensure GDPR compliance when enriching candidate data?

For active candidates or competitive roles, event-based re-enrichment via job-change webhooks works best. For passive candidates or large talent pools, a monthly refresh of core fields balances accuracy and cost, since people change jobs every 2.8 years on average (HeroHunt.ai, 2026).

How often should candidate data be refreshed in a custom recruiting tool?

It's worth it for high-volume specialized hiring — 10+ technical roles per quarter — with in-house development resources. Off-the-shelf ATS still wins on deployment speed and predictable ROI for standard hiring (Chambers Talent, 2026).

Is it worth building a custom recruiting tool versus buying an ATS?

https://www.datamagnet.co/images/blog/build-internal-recruiting-tools-real-time-people-data-hero.png

A recruiter's dashboard showing candidate profiles being enriched in real time with employment history and contact data

A 3-Layer Sourcing Stack for building custom recruiting tools on real-time people data APIs — architecture, cost, and a 5-step build guide.

Build Internal Recruiting Tools with Real-Time People Data (2026)

> **Disclosure:** Datamagnet publishes this article. Product capabilities described below are based on public documentation, retrieved July 19, 2026. Collect and process public profile data in line with LinkedIn's terms, GDPR, and CCPA, and confirm your own compliance posture before you run any sourcing workflow.

# Social-Post Engagement as a Hiring Signal for Subject-Matter Experts

Every technical post on LinkedIn quietly builds you a candidate list. When a company ships a deep post about vector databases, RLHF, or GTM data infrastructure, the people who stop scrolling to like it, argue with it, or reshare it are self-selecting on the exact topic you're hiring for. That crowd is a hiring signal — you just have to read it.

Most sourcing ignores it. Recruiters keyword-search job titles and skills, then cold-message strangers who never showed any interest in the work. Engagement-first sourcing flips that. You start from a post about the problem, pull the people who engaged, and rank them by how well they fit the role. This guide shows how to do it with a real, working API call — and how to turn a one-off pull into an always-on watcher.

> **TL;DR**
>
> - The people who react and comment on a topic-specific post are a self-selected pool of subject-matter experts — LinkedIn has long estimated about **70% of the workforce is passive talent** you'd never reach through job-board applies ([LinkedIn Talent Solutions](https://business.linkedin.com/talent-solutions), retrieved 2026-07-19).
> - Not all engagement is equal: Datamagnet scores a **comment at 1.0 and a like at 0.7** on intent, because writing a reply takes more conviction than tapping like ([Datamagnet, Webhooks](https://docs.datamagnet.co/api-reference/webhooks), retrieved 2026-07-19).
> - One [Post Reactions](https://docs.datamagnet.co/api-reference/endpoints/post-reactions) call returns every reactor's profile for **1 credit**, and a matching [Post Comments](https://docs.datamagnet.co/api-reference/endpoints/post-comments) call returns each commenter.
> - Enrich the engagers with the [People Profile endpoint](https://docs.datamagnet.co/api-reference/endpoints/people), filter to your ICP, and rank the list by fit.
> - Automate the whole thing with a [Company Engagement signal](https://docs.datamagnet.co/api-reference/endpoints/signal-company-engagement) so new experts land in Slack or your ATS as they engage.

![A LinkedIn-style social post card with like, comment, and repost icons flowing out to candidate profile cards tagged as subject-matter experts](https://cdn.sanity.io/images/mmp5yyqj/production/a14c8a119b7f326e9acedcb8d332fb6d97ebc61b-1376x768.jpg)

## Why is social-post engagement a hiring signal?

Engagement is a hiring signal because it's self-selected interest. LinkedIn has long estimated that about 70% of the global workforce is passive talent — people not actively job-hunting, so they never show up in your applicant pool ([LinkedIn Talent Solutions](https://business.linkedin.com/talent-solutions), retrieved 2026-07-19). But when a passive expert comments on a post about your exact problem, they've just told you they care about it.

Think about who reacts to a genuinely technical post. Not the whole market — the sliver of people who understood it, had an opinion, and chose to say so publicly. That filter is doing free work for you. A keyword search returns everyone who once listed "machine learning" on a profile; a post's comment section returns people actively thinking about it this week.


Here's the part most teams miss: engagement is a *topic* signal, not a job-title signal. Titles lie — they're inflated, out of date, or vague. Someone titled "Software Engineer" who writes a sharp comment about retrieval pipelines has shown you more real expertise than a "Senior ML Engineer" title ever could. Reading engagement lets you source on demonstrated interest instead of self-reported labels, which is exactly where title-based search falls apart.

## Which engagements actually point to expertise?

Not every reaction carries the same weight, and the scoring reflects it: Datamagnet scores a comment at **1.0** and a like at **0.7** on intent, because leaving a reply takes more thought than tapping a button ([Datamagnet, Webhooks](https://docs.datamagnet.co/api-reference/webhooks), retrieved 2026-07-19). A repost with commentary sits higher still — the person put their own name behind your content.

![An intent ladder staircase showing Like as a light signal, Comment as a stronger signal, and Repost as the strongest, rising with hiring intent](https://cdn.sanity.io/images/mmp5yyqj/production/c9ac1a82a17696f3a6b15def02bf95208c4265ad-1376x768.jpg)

Treat engagement as a ladder. A like is a light nod — worth noting, easy to give. A comment is a real signal, especially a substantive one that adds a point or pushes back. A repost is a public endorsement: the person chose to broadcast the topic to their own network. The higher up the ladder, the stronger the read on genuine expertise and interest.

![A two-bar comparison chart showing a like scored at 0.7 and a comment scored at 1.0 on signal score](https://cdn.sanity.io/images/mmp5yyqj/production/9c3206fa3fc8eb6df995b9d13086cf5828ad899a-1376x768.jpg)

That's why you pull comments *and* reactions, then weight them. A commenter who explained a tradeoff belongs at the top of your list. A silent liker is a warm name for later. You can retrieve both with the [LinkedIn Posts API](https://www.datamagnet.co/linkedin-posts-api/) — content, reactions, comments, and the people behind each one — and score them the same way a lead system would.

## How do you pull the people who engaged with a post?

You pull them with one API call per interaction type. The [Post Reactions endpoint](https://docs.datamagnet.co/api-reference/endpoints/post-reactions) takes a LinkedIn post URL and returns every reactor's profile for **1 credit per request**, and the [Post Comments endpoint](https://docs.datamagnet.co/api-reference/endpoints/post-comments) does the same for commenters. No scraping, no proxies — a URL in, structured JSON out.

Here's the real, working call. First, authenticate with a bearer token (see [Authentication](https://docs.datamagnet.co/api-reference/authentication)), then POST the post URL to the reactions endpoint:

```bash
curl -X POST https://api.datamagnet.co/api/v1/linkedin/post/reactions \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://www.linkedin.com/posts/username_slug-activity-7430615551086850048-XXXX",
    "page": 1
  }'
```

The response gives you each reactor's name, headline, profile URL, and reaction type — everything you need to judge fit at a glance:

```json
{
  "message": {
    "reactions": [
      {
        "name": "Priya Menon",
        "description": "Staff ML Engineer · Retrieval & RAG systems",
        "profile_url": "https://www.linkedin.com/in/priya-menon-example",
        "reaction_type": "PRAISE"
      },
      {
        "name": "David Osei",
        "description": "Applied Scientist, NLP",
        "profile_url": "https://www.linkedin.com/in/david-osei-example",
        "reaction_type": "LIKE"
      }
    ]
  },
  "cursor": 2,
  "credit_used": 1
}
```

![An API pipeline diagram: a post URL feeds a POST /post/reactions endpoint that returns a stack of engager profile cards](https://cdn.sanity.io/images/mmp5yyqj/production/5139cad405e83f71ed1e6b12677f863df17a5aff-1376x768.jpg)

To get the full audience, paginate. Make the first call without a `page`, read the `cursor` in the response, and keep requesting until `cursor` comes back `null` — the same loop works for reactions, comments, and reposts:

```python
import requests

url = "https://api.datamagnet.co/api/v1/linkedin/post/reactions"
headers = {"Authorization": "Bearer YOUR_API_KEY"}
page, engagers = 1, []

while page is not None:
    resp = requests.post(url, json={"url": POST_URL, "page": page}, headers=headers)
    data = resp.json()
    engagers.extend(data["message"]["reactions"])
    page = data.get("cursor")

print(f"Pulled {len(engagers)} engagers")
```

Not sure which post to start from? Use the [Company Posts endpoint](https://docs.datamagnet.co/api-reference/endpoints/company-posts) to list a target company's recent posts with engagement counts, then pull reactors from the one that's most on-topic for your role.

## How do you turn engagers into a ranked SME shortlist?

You enrich the raw list, filter it to your ICP, then rank what's left. A reaction gives you a name and a headline; that's not enough to decide who to contact. Run each engager through the [People Profile endpoint](https://docs.datamagnet.co/api-reference/endpoints/people) to pull current company, full role history, skills, and location, so "Staff ML Engineer" becomes a full picture instead of a one-line label.

![A funnel diagram taking everyone who engaged, applying enrich and ICP filter, and outputting a ranked SME shortlist scored 3, 2, 2](https://cdn.sanity.io/images/mmp5yyqj/production/99e398306c9472c919ebf2a218c193c6171a742d-1376x768.jpg)

Then filter. Most engagers won't fit — wrong seniority, wrong location, wrong function, or they're already at a competitor you can't poach. Score the survivors the way an intent system does: Datamagnet's lead score runs 1 to 3, where `composite = 0.5 × icp_score + 0.5 × signal_score` blends how well someone fits your profile with how strongly they engaged ([Datamagnet, Webhooks](https://docs.datamagnet.co/api-reference/webhooks), retrieved 2026-07-19). A senior person who left a thoughtful comment scores a 3; a junior liker scores a 1.


The scoring math is why comments matter more than raw reach. Because signal weight splits evenly with ICP fit, a perfect-fit person who only liked the post (signal 0.7) still lands below a strong-fit person who commented (signal 1.0). In practice, that pushes the people who *engaged with substance* to the top of the shortlist — which is exactly the crowd worth a personal message first. You're not ranking by follower count; you're ranking by demonstrated interest plus fit.

## How do you run this continuously instead of one post at a time?

You wire it to an engagement signal so the pulling never stops. A one-off reactions call is a snapshot; a [Company Engagement signal](https://docs.datamagnet.co/api-reference/endpoints/signal-company-engagement) is a live feed. It monitors the LinkedIn posts of companies you choose, captures everyone who likes or comments, filters them against your ICP, and scores each engager 1 to 3 automatically — no manual URL-pasting.

![A continuous monitoring pipeline: company and topic posts feed an engagement signal with a refresh loop, delivering leads via webhook to Slack and an ATS](https://cdn.sanity.io/images/mmp5yyqj/production/379f28311a2eadb505af97aedfaa779edefa7872-1376x768.jpg)

Pick the lens that matches how you hire. Watching one company's thought leadership? Use company engagement. Hiring around a topic regardless of who posts? A [Keyword Engagement signal](https://docs.datamagnet.co/api-reference/endpoints/signal-keyword-engagement) surfaces experts who engage with posts matching terms like "inference optimization." Sourcing across a whole sector? An [Industry Engagement signal](https://docs.datamagnet.co/api-reference/endpoints/signal-industry-engagement) covers companies in your target industries. The [Competitor Hijack cookbook](https://docs.datamagnet.co/cookbooks/competitor-hijack) shows the same mechanics aimed at a rival's audience.

Delivery is what makes it real-time. Register a [webhook](https://docs.datamagnet.co/api-reference/webhooks) and each qualified engager is POSTed to your endpoint with name, headline, engagement type, the post they interacted with, and a lead score — signed and retried. From there it's a short hop to Slack or your ATS. Why check a post's comments by hand every week when a signal can watch a dozen posts and only ping you on the people who fit?

## Is engagement-based sourcing compliant?

Engagement-based sourcing uses public activity, but public doesn't mean unlimited. Everything here reads data people chose to make visible — a public like or comment on a public post. Datamagnet collects from public sources and supports GDPR- and CCPA-aligned handling, and it standardizes only what LinkedIn already exposes.

Still, your obligations depend on your jurisdiction, your outreach channel, and how you store the data. Treat every engagement as a reason to *research and personalize*, not as blanket permission to mass-message. The whole point of engagement-first sourcing is relevance — a note that references the actual post someone engaged with beats a scraped-list blast on every metric that matters. See how teams operationalize this on the [recruiting intelligence page](https://www.datamagnet.co/recruiting/).

## Start sourcing from the audience you already have

Your best next hire may have commented on your last technical post. Stop cold-searching titles and start reading engagement: pull the reactors and commenters on the posts about your problem, enrich and rank them by fit, then set a signal so new experts arrive automatically. It's demonstrated interest instead of guesswork. **[Start an engagement signal](https://www.datamagnet.co/signal-api/) and see who's already raising their hand.**

## Frequently Asked Questions

### Why is post engagement a good hiring signal?

Because it's self-selected topic interest. When someone comments on a post about a specific technical problem, they've shown they understand and care about it — unlike a keyword search that returns anyone who once listed the skill. With about 70% of the workforce passive ([LinkedIn Talent Solutions](https://business.linkedin.com/talent-solutions), retrieved 2026-07-19), engagement reaches experts who never apply.

### How do I get the list of people who reacted to a LinkedIn post?

Send the post URL to the [Post Reactions endpoint](https://docs.datamagnet.co/api-reference/endpoints/post-reactions), which returns every reactor's profile for 1 credit per request, and the [Post Comments endpoint](https://docs.datamagnet.co/api-reference/endpoints/post-comments) for commenters. Paginate using the `cursor` field until it returns `null` to capture the full audience of a high-engagement post.

### Are comments a stronger hiring signal than likes?

Yes. Datamagnet scores a comment at 1.0 and a like at 0.7 on intent, because writing a reply takes more conviction than tapping a button ([Datamagnet, Webhooks](https://docs.datamagnet.co/api-reference/webhooks), retrieved 2026-07-19). A repost with commentary is stronger still. Weight commenters higher when you build your shortlist, and treat silent likers as warm names for later.

### How do I rank engagers by how well they fit a role?

Enrich each engager with the [People Profile endpoint](https://docs.datamagnet.co/api-reference/endpoints/people), then filter by seniority, function, and location. Datamagnet's lead score blends fit and intent as `composite = 0.5 × icp_score + 0.5 × signal_score`, producing a 1-to-3 rank so strong-fit commenters rise to the top of your outreach list.

### Can I monitor engagement automatically instead of pulling one post at a time?

Yes. A [Company Engagement signal](https://docs.datamagnet.co/api-reference/endpoints/signal-company-engagement) continuously watches a company's posts, captures every engager, scores them against your ICP, and delivers qualified experts via [webhook](https://docs.datamagnet.co/api-reference/webhooks). Keyword and industry engagement signals do the same around a topic or sector instead of a single company.

## Sources

- LinkedIn Talent Solutions, Passive Talent Research, retrieved 2026-07-19, https://business.linkedin.com/talent-solutions
- U.S. Bureau of Labor Statistics, Employee Tenure Summary (January 2024 release), retrieved 2026-07-19, https://www.bls.gov/news.release/tenure.nr0.htm
- Datamagnet, Post Reactions endpoint, retrieved 2026-07-19, https://docs.datamagnet.co/api-reference/endpoints/post-reactions
- Datamagnet, Post Comments endpoint, retrieved 2026-07-19, https://docs.datamagnet.co/api-reference/endpoints/post-comments
- Datamagnet, Webhooks (lead scoring), retrieved 2026-07-19, https://docs.datamagnet.co/api-reference/webhooks
- Datamagnet, Company Engagement Signal, retrieved 2026-07-19, https://docs.datamagnet.co/api-reference/endpoints/signal-company-engagement

Every technical post on LinkedIn quietly builds you a candidate list. The people who stop scrolling to like it, argue with it, or reshare it are self-selecting on the exact topic you're hiring for.

People who like and comment on a technical post have raised their hand. Turn engagement into a ranked shortlist of subject-matter experts with one API call.

Social-Post Engagement as a Hiring Signal for Subject-Matter Experts

Because it's self-selected topic interest. When someone comments on a post about a specific technical problem, they've shown they understand and care about it — unlike a keyword search that returns anyone who once listed the skill. With about 70% of the workforce passive, engagement reaches experts who never apply.

Why is post engagement a good hiring signal?

Send the post URL to the Post Reactions endpoint, which returns every reactor's profile for 1 credit per request, and the Post Comments endpoint for commenters. Paginate using the cursor field until it returns null to capture the full audience of a high-engagement post.

How do I get the list of people who reacted to a LinkedIn post?

Yes. Datamagnet scores a comment at 1.0 and a like at 0.7 on intent, because writing a reply takes more conviction than tapping a button. A repost with commentary is stronger still. Weight commenters higher when you build your shortlist, and treat silent likers as warm names for later.

Are comments a stronger hiring signal than likes?

Enrich each engager with the People Profile endpoint, then filter by seniority, function, and location. Datamagnet's lead score blends fit and intent as composite = 0.5 x icp_score + 0.5 x signal_score, producing a 1-to-3 rank so strong-fit commenters rise to the top of your outreach list.

How do I rank engagers by how well they fit a role?

Yes. A Company Engagement signal continuously watches a company's posts, captures every engager, scores them against your ICP, and delivers qualified experts via webhook. Keyword and industry engagement signals do the same around a topic or sector instead of a single company.

Can I monitor engagement automatically instead of pulling one post at a time?

Who reacts to a company's technical posts is a self-selected pool of experts. Pull the engagers with one API call, enrich, and rank them by fit.

Post Engagement as a Hiring Signal for SMEs (2026)

> **Disclosure:** Datamagnet publishes this article. Product capabilities described below are based on public documentation, retrieved July 19, 2026. Collect and process public profile data in line with LinkedIn's terms, GDPR, and CCPA, and confirm your own compliance posture before you run any sourcing workflow.

# Recency-Aware Candidate Sourcing: Stop Surfacing 15-Year-Old Relevant Experience

A candidate's most "relevant" experience on paper is often the oldest thing on their profile. Search by keyword and you'll happily surface someone whose big, matching project shipped 15 years ago — while the person who moved into that exact role three days ago never shows up. That's the trap of keyword-first sourcing: it rewards buried history, not what someone is doing right now.

Recency-aware sourcing flips the priority. Instead of ranking a static map of names by how well old experience matches, you watch for movement and score people by how fresh their signal is. This guide shows how to build that watcher — one that tracks the known names on your list and catches the new movers you've never heard of, especially in fast-churning markets like AI research labs.

> **TL;DR**
>
> - Hand-built talent maps decay fast — B2B contact data goes stale at roughly **2% a month**, so a spreadsheet built this quarter is wrong by next ([HubSpot](https://www.hubspot.com/database-decay), retrieved 2026-07-19).
> - Keyword search over-weights old experience; **recency-aware** sourcing scores people by how recently they moved, posted, or changed roles instead.
> - Build a **two-track watcher**: one lane monitors known names for job changes, the other scans for new movers matching your ICP.
> - Wire it to a [job-change signal](https://docs.datamagnet.co/api-reference/endpoints/signal-create) with [webhook](https://docs.datamagnet.co/api-reference/webhooks) delivery so a move reaches your team in minutes, not on your next manual refresh.
> - AI-lab talent churns between employers constantly — SignalFire found retention gaps of 10+ points between top labs, so a static map is out of date almost immediately ([SignalFire](https://www.signalfire.com/blog/signalfire-state-of-talent-report-2025), retrieved 2026-07-19).

![Talent map of researchers moving between company and AI-lab profile cards, with one move lighting up a live radar watcher](https://cdn.sanity.io/images/mmp5yyqj/production/f8193b9a24e1c75dfab4e08fd0fb6b1271da6925-1376x768.jpg)

## Why do hand-built talent maps go stale in weeks?

Hand-built talent maps decay because the underlying data does. B2B contact records go stale at roughly 2% every month — about 22.5% a year — as people change jobs, titles, and companies ([HubSpot, Database Decay Simulation](https://www.hubspot.com/database-decay), retrieved 2026-07-19). Map 300 researchers into a spreadsheet today, and dozens of those rows are wrong before your next quarterly review.

Tenure makes it worse in tech. In its January 2024 release, the U.S. Bureau of Labor Statistics put median employee tenure at just 3.9 years — and it runs shorter in high-demand technical roles ([U.S. Bureau of Labor Statistics, Employee Tenure Summary](https://www.bls.gov/news.release/tenure.nr0.htm), retrieved 2026-07-19). Short tenure means constant movement. Constant movement means any static map is a photograph of a moving crowd.

![Side-by-side comparison of a stale hand-built spreadsheet talent map labeled "last updated weeks ago" versus a fresh live watcher feed of new job-change events](https://cdn.sanity.io/images/mmp5yyqj/production/06dc14e6377a1305e641b23efefac72bfb984848-1376x768.jpg)


Here's the part most teams miss: a stale map doesn't just lose people, it actively misleads you. When a row is outdated, you email the wrong company, pitch the wrong role, or skip someone who just became a perfect fit. The cost isn't a blank cell — it's a confident, wrong action. A live watcher fixes this by never claiming to be a snapshot. It's a feed. To keep this current in your own systems, you can re-enrich any profile on demand through the [People Profile endpoint](https://docs.datamagnet.co/api-reference/endpoints/people) instead of trusting a cached row.

## What does "recency-aware" candidate sourcing actually mean?

Recency-aware sourcing means ranking candidates by how fresh their signal is, not just how well their history matches a keyword. A profile's relevance decays over time — a project from week one is worth more than the same project from 12 weeks or 12 years ago. So you score for freshness first, then match on fit.

Think of every candidate's signal as moving through three states: **fresh**, **aging**, and **stale**. A move you detected this week is fresh and worth acting on now. A signal from last quarter is aging. And "15 years of relevant experience" with no recent activity? That's stale — interesting context, but not a reason to reach out today.

![Relevance-decay curve showing a candidate signal moving from fresh to aging to stale across weeks, with an old "15-year-old experience" tag sitting at the stale end](https://cdn.sanity.io/images/mmp5yyqj/production/ce74adc039f7e64a29ca353f8a5a8ce8e034b225-1376x768.jpg)

In practice, recency comes from three things you can actually measure: the date of a job change, the timestamp on recent activity, and how recently the profile itself was verified. According to Datamagnet's documentation, activity like a candidate's recent posts and engagement is retrievable per profile through the [Person Activity endpoint](https://docs.datamagnet.co/api-reference/endpoints/people-activity), so "recent" is a field you can sort on — not a guess ([Datamagnet, People API](https://www.datamagnet.co/people-api/), retrieved 2026-07-19). That turns recency from a vibe into a sortable number.

## How do you build a two-track watcher for talent moves between AI labs?

A good watcher runs two lanes at once, because you need to cover both the names you know and the ones you don't. The top lane watches a saved list of known people for job changes. The bottom lane scans the wider market for new movers who match your profile. One central monitor feeds both.

The **known-names lane** is a job-change signal over your watchlist. You save the researchers and engineers you already care about, and the monitor tells you the moment any of them changes employer. That's exactly the pattern in Datamagnet's [Champion Tracker cookbook](https://docs.datamagnet.co/cookbooks/champion-tracking), which uses `job_change` signals to catch when tracked people move — built for revenue teams, but the mechanics are identical for a recruiter's shortlist.

![Two-track watcher diagram: a saved watchlist feeds a central watcher that splits into a top lane tracking known names and a bottom lane surfacing new movers](https://cdn.sanity.io/images/mmp5yyqj/production/463c7acfc650604e7e04b9272a8946a3ed02b252-1376x768.jpg)

You set the whole thing up with one call. The [Create Signal endpoint](https://docs.datamagnet.co/api-reference/endpoints/signal-create) registers a monitor that tracks LinkedIn profiles for job changes, and you can pause, resume, or edit that list later through the [Update Signal endpoint](https://docs.datamagnet.co/api-reference/endpoints/signal-update). One monitor covers your entire watchlist — you don't poll each profile by hand. Why check 300 profiles every Monday when a signal can check them for you and only ping you when something actually changed?

## How do you catch new movers you've never heard of?

You catch new movers with search, not with a watchlist — because you can't save a name you don't know yet. The bottom lane of the watcher runs a repeatable ICP query for the roles, seniorities, and companies you care about, then flags anyone new since your last run. That's how a researcher who just joined a frontier lab surfaces even though they were never on your map.

Two endpoints do the heavy lifting here. The [ICP People Search endpoint](https://docs.datamagnet.co/api-reference/endpoints/icp-people-search) finds decision-makers and specialists by job title, seniority, function, company, and location — no internal IDs required. And the [People Search DB endpoint](https://docs.datamagnet.co/api-reference/endpoints/people-search-db) queries Datamagnet's own store of enriched profiles with include and exclude filters on company URLs, so you can say "AI research roles, at these labs, not at that one" in a single query.


The exclude filter is the quiet power move for recency. Run the same ICP query on a schedule and exclude the companies you already sourced from — what's left is, by definition, people who moved *into* your target set since last time. You've turned a search endpoint into a change detector. The new movers fall out automatically, ranked by how recently they appeared, ready to enrich and score.

## Why does a recency score beat a keyword match?

A recency score beats a keyword match because it answers a sharper question: not "who once did this?" but "who is doing this now, and just moved?" A scored candidate record puts current company, previous lab, seniority, and location up front — and pushes decade-old experience to the bottom, where it belongs. The headline is the move itself: "moved 3 days ago."

![Scored candidate record card showing a "Moved 3 days ago" flag, current company, previous AI lab, seniority, and location, with old previous experience struck through and a recency score](https://cdn.sanity.io/images/mmp5yyqj/production/9ddcd69139d9818a43499faf8a3c801c68131a17-1376x768.jpg)


This matters most in markets that never sit still. In its 2025 State of Talent Report, SignalFire found that top AI labs poach heavily from one another, with two-year retention varying by more than 10 points between the leading labs — Anthropic held onto the largest share of the technical talent it hired, well ahead of some rivals ([SignalFire, State of Talent Report 2025](https://www.signalfire.com/blog/signalfire-state-of-talent-report-2025), retrieved 2026-07-19). When people move between labs that fast, the name that matched your keyword search last month may already sit at a competitor. A recency score catches that; a static keyword map never will.

## How fast does the watcher need to be?

Fast enough that you reach out before everyone else does. In recruiting and sales alike, the first credible contact after a move wins an outsized share of the response — and a candidate who just switched labs is fielding messages from every recruiter with a keyword alert. Speed is the edge. A watcher that tells you next Monday is a watcher that tells you too late.

![Speed pipeline diagram: a job-change flag on a profile triggers a webhook, fires an alert, and prompts a "reach out first" action, labeled minutes not weeks](https://cdn.sanity.io/images/mmp5yyqj/production/f8c14f8625b87f1b65ebaa953cb9df145477d4b5-1376x768.jpg)

The delivery mechanism is what makes this real-time. Instead of polling, you register a [webhook](https://docs.datamagnet.co/api-reference/webhooks) and Datamagnet posts the job-change event to your endpoint the moment it's detected, with signature verification and retry handling built in. From there it's a short hop to Slack or your ATS. You can list and audit every active monitor through the [List Signals endpoint](https://docs.datamagnet.co/api-reference/endpoints/signal-list) so nothing runs silently in the background.

This is the whole promise of a [job-change signal API](https://www.datamagnet.co/signal-api/): monitor movement continuously, filter it to your ICP, and get pinged in minutes. Pair it with a recruiting workflow and you've replaced the quarterly map refresh with a live feed. See how teams wire this into sourcing on the [recruiting intelligence page](https://www.datamagnet.co/recruiting/).

## Start watching moves instead of mapping names

Stop maintaining a spreadsheet that's wrong by the time you save it. Save your known names to a job-change signal, run a scheduled ICP query for new movers, and score everyone by recency instead of buried keywords. You'll surface the person who moved this week — not the one whose best work shipped 15 years ago. **[Start a job-change watcher](https://www.datamagnet.co/signal-api/) and see who just moved.**

## Frequently Asked Questions

### What is recency-aware candidate sourcing?

Recency-aware sourcing ranks candidates by how fresh their signal is — a recent job change, recent activity, or a recently verified profile — rather than by how well old keywords match. It exists because B2B data decays about 2% a month ([HubSpot](https://www.hubspot.com/database-decay), retrieved 2026-07-19), so freshness is a better relevance signal than history.

### Why do hand-built talent maps go out of date so fast?

Because the people in them keep moving. Median employee tenure was just 3.9 years in the January 2024 BLS release, and it's shorter in tech ([U.S. Bureau of Labor Statistics](https://www.bls.gov/news.release/tenure.nr0.htm), retrieved 2026-07-19). Combined with ~2% monthly data decay, a static map built this quarter carries dozens of wrong rows within weeks.

### How do I track when specific people change jobs?

Save the profiles to a job-change signal monitor. Datamagnet's [Create Signal endpoint](https://docs.datamagnet.co/api-reference/endpoints/signal-create) registers one monitor across your whole watchlist and pushes an event via [webhook](https://docs.datamagnet.co/api-reference/webhooks) the moment anyone moves — the same pattern as the [Champion Tracker cookbook](https://docs.datamagnet.co/cookbooks/champion-tracking). No manual polling required.

### How do I find new movers I've never heard of?

Run a scheduled ICP query and flag anyone new since last time. The [ICP People Search endpoint](https://docs.datamagnet.co/api-reference/endpoints/icp-people-search) filters by title, seniority, and company, and the [People Search DB endpoint](https://docs.datamagnet.co/api-reference/endpoints/people-search-db) supports company include/exclude filters — so excluding already-sourced companies leaves only fresh movers.

### Is monitoring public profile moves compliant?

Datamagnet collects data from public sources and supports GDPR- and CCPA-aligned handling, but compliance depends on your use case. Review the terms for your jurisdiction and outreach channel before you act. Treat every signal as a prompt to verify, not as automatic permission to contact someone.

## Sources

- HubSpot, Database Decay Simulation, retrieved 2026-07-19, https://www.hubspot.com/database-decay
- U.S. Bureau of Labor Statistics, Employee Tenure Summary (January 2024 release), retrieved 2026-07-19, https://www.bls.gov/news.release/tenure.nr0.htm
- SignalFire, State of Talent Report 2025, retrieved 2026-07-19, https://www.signalfire.com/blog/signalfire-state-of-talent-report-2025
- Datamagnet, LinkedIn Signal API, retrieved 2026-07-19, https://www.datamagnet.co/signal-api/
- Datamagnet, People API, retrieved 2026-07-19, https://www.datamagnet.co/people-api/

A candidate's most relevant experience on paper is often the oldest thing on their profile. Search by keyword and you'll happily surface someone whose big, matching project shipped 15 years ago.

B2B contact data decays about 2% a month, so hand-built talent maps rot in weeks. Build a recency-aware watcher that tracks AI-lab moves in minutes, not weeks.

Recency-Aware Candidate Sourcing: Stop Surfacing 15-Year-Old Relevant Experience

Recency-aware sourcing ranks candidates by how fresh their signal is — a recent job change, recent activity, or a recently verified profile — rather than by how well old keywords match. It exists because B2B data decays about 2% a month, so freshness is a better relevance signal than history.

What is recency-aware candidate sourcing?

Because the people in them keep moving. Median employee tenure was just 3.9 years in the January 2024 BLS release, and it's shorter in tech. Combined with about 2% monthly data decay, a static map built this quarter carries dozens of wrong rows within weeks.

Why do hand-built talent maps go out of date so fast?

Save the profiles to a job-change signal monitor. Datamagnet's Create Signal endpoint registers one monitor across your whole watchlist and pushes an event via webhook the moment anyone moves — the same pattern as the Champion Tracker cookbook. No manual polling required.

How do I track when specific people change jobs?

Run a scheduled ICP query and flag anyone new since last time. The ICP People Search endpoint filters by title, seniority, and company, and the People Search DB endpoint supports company include/exclude filters — so excluding already-sourced companies leaves only fresh movers.

How do I find new movers I've never heard of?

Datamagnet collects data from public sources and supports GDPR- and CCPA-aligned handling, but compliance depends on your use case. Review the terms for your jurisdiction and outreach channel before you act. Treat every signal as a prompt to verify, not as automatic permission to contact someone.

Is monitoring public profile moves compliant?

Hand-built talent maps rot in weeks. Build a two-track watcher that tracks known names and catches new movers between AI labs — in minutes, not weeks.

Recruiting-intelligence