
Job change signals on LinkedIn: two motions that beat cold outbound
When someone who already trusts your product lands in a new role, you have the warmest outbound target on LinkedIn. A job change resets three things at once: the person's budget authority, the tech stack they inherit, and the list of problems they now own. That combination converts far better than any cold list, which is why job change tracking has quietly turned from a data-hygiene chore into a real pipeline channel. The catch is that most vendors sell you a 90-day window that is really more like 30 to 60 days, and they attach an enterprise price tag to a signal you can read off a public profile. This guide covers the two motions worth running, an honest read of the timing, and how to track the whole thing without connecting anything.
What a job change signal actually is
A job change signal fires when a specific person in your world moves into a new role: a past champion who switches companies, an advocate promoted into budget authority, or a buyer hired into a seat that owns the problem you solve. It is a person-level event, read from a public profile update, not a company-level one.
That last distinction matters more than it sounds. A job change signal is not the same as a hiring signal. A hiring signal is a company posting a role, which tells you budget has been committed to a problem before anyone is in the seat. A job change signal is a named person landing in a seat, which tells you who now owns that budget and what they already believe. The two pair beautifully, but they trigger different plays, so it is worth reading the LinkedIn hiring signals guide alongside this one and keeping them separate in your head.
The two motions that turn a move into pipeline
Two motions turn job changes into pipeline. The first tracks your people: past champions, users, and advocates, because when one of them moves you arrive as the known-good option in a fresh buying window. The second tracks the buyer: the new role-holder who now owns the problem you solve, whether or not they have ever heard of you. The map below pairs each signal with the play that wins.
Motion 1: track your people when they move
This is the highest-converting outbound you will ever run, and most teams miss it because they track accounts, not people. When a former user, champion, or advocate moves, they carry three advantages into their new seat at the same time. They arrive with budget authority they may not have had before, they are rebuilding a stack from scratch, and they already trust you. You are not cold. You are the known-good option walking into a fresh buying window, and the prior relationship does the qualification for you.
The gap between warm and cold is not marginal. Belkins, drawing on millions of LinkedIn touchpoints across its client campaigns, found messenger campaigns aimed at people you are already connected to replying at 12.2%, against 7.9% for connector campaigns that open with a cold connection request (Belkins, 2026). A champion who just changed jobs is about as warm as an outbound target gets, because the warmth is a real prior relationship rather than a single click on a post. For why that gap holds across the funnel, see cold versus warm LinkedIn outreach.
The play is to acknowledge the move without making it strange, then connect your value to what they now own. A line like "you ran this with us at your last company, and the same gap tends to show up in a new team's first quarter" is a message only you can send, and it is worth more than any purchased list. The requirement is that you keep a watch list of the people worth tracking, which is the part manual monitoring always drops.
Motion 2: track the buyer moving into a role you sell to
The second motion needs no prior relationship. When a company hires a new VP of RevOps, a first Head of Customer Success, or any leader whose seat owns your category, that person arrives with a mandate to change something and a first quarter spent auditing the stack they inherited. They question incumbent vendors, look for early wins, and have not yet locked in the tools their predecessor never bought. You want to be in that audit.
This is where role-fit does the qualifying instead of relationship. You are not asking "do I know this person," you are asking "does this role, at this company, own the problem I solve." A new owner of an inherited stack feels no loyalty to a decision they did not make and every incentive to prove the reset was worth it, which makes them unusually open to a better option. The play is to position for the first-quarter audit directly, naming the gap the seat was created to close rather than pitching a feature list. For the broader taxonomy that sits around this, from engagement to funding, see LinkedIn intent signals without Sales Navigator.
The 90-day window is really a 30 to 60 day window
Treat 90 days as the outer edge of detection, not the buying window. Sales Navigator's own filter surfaces anyone who "Changed Jobs in the Last 90 Days" (LinkedIn Sales Navigator, 2026), and vendors quote that number as if it were the receptive period. It is not. The first weeks are onboarding, when the new hire is drinking from a firehose and buys nothing, and by month three the new stack is being locked, so the real sweet spot lands at roughly days 30 to 60.
Two things quietly shrink the window further. First, detection lag: a job change only becomes visible when the person updates their public profile, which often trails the actual start date by weeks. By the time you see it, part of your 90 days has already burned. Second, conversion decay: receptiveness peaks once onboarding ends and falls as decisions calcify. Put both together and the honest picture is a narrow, fast-closing window, not a comfortable quarter.
The practical resolution is to separate two clocks. Move fast on the research the moment a move surfaces, then let the actual sending pace itself under safe daily caps rather than firing a whole list at once. Firing dozens of connection requests the instant a job-change list lands is the fastest route to a restriction, well above the commonly cited ceiling of roughly 100 connection requests a week. See LinkedIn connection request limits for where the real caps sit.
How to track job changes without a session cookie
You can track job changes from public data alone, because a person's current employer lives in the public experience section of their profile. Keep a watch list of the people who matter, re-read their public profiles on a schedule, and diff for a new company. No connected account, no session cookie, and no paid seat is required to detect the move itself.
The method is different for each motion, and both stay on public pages:
- For Motion 1 (your people), build the list from who you already know: past customers, closed-lost champions, trial users, advocates. Snapshot each person's current employer, then re-read those public profiles periodically and flag anyone whose company changed. That diff is your job-change alert, produced without a subscription per name.
- For Motion 2 (the buyer), run a public people search for the target title across your target accounts, snapshot the result, and re-run it on a cadence. New names appearing in a role that was previously held by someone else are your incoming buyers. The free LinkedIn people search tool does this from public data, with no account and no browser extension, so you can find who currently holds a role before deciding whether to connect. Pair it with the free LinkedIn companies search tool when you want the account-level view first.
A server reads a public profile the same way a browser does, which is what lets the entire research step run before you connect anything. The move is public the moment the profile updates, so detection never needs your login.
Which job-change tracking approach fits you
Four approaches dominate job-change tracking, and they split hard on cost and lock-in. Sales Navigator bolts it onto a paid seat, UserGems and Champify sit on top of your CRM at enterprise prices, and cookieless public tracking reads the same moves from public profiles for a fraction of the cost. The table shows where each fits, with prices confirmed on each vendor's current pricing pages.
The read is straightforward. If your revenue team already lives in Sales Navigator and only needs moves among leads they have saved, the built-in filter is enough, though it caps discovery at 90 days and covers only your saved list. UserGems and Champify are strong at CRM-wide coverage for enterprise teams that can absorb five-figure annual contracts, with Champify leaning Salesforce-native. If you are a lean team, do not want CRM lock-in, or simply refuse to pay per name for a signal that is public, cookieless public tracking covers both motions from public data and only touches your account at the moment you send. Compare the full pricing at BeReach pricing.
Where the account boundary sits
The account boundary sits at exactly one place: the send. Detecting a move, qualifying the person against your ICP, and drafting the message all run off public pages with nothing connected. BeReach calls this cookieless until outreach, so you connect a LinkedIn session only at the moment you message, and every message is human-approved before it goes out. That last step then paces itself under account-safety caps, instead of a full job-change list firing the instant it lands.
Job change signals reward you for moving fast on the person and slow on the send. Get that split right, and the warmest lead in your pipeline is one you read off a public profile before anyone else acted on it. For the framework behind why a real signal beats raw volume every time, read signal-based selling on LinkedIn.
Every viral post is 100+ warm conversations waiting.
Tell your agent who you want to reach. It finds leads, qualifies them, sends personalized outreach, and follows up.
What is a job change signal?
A job change signal fires when a specific person moves into a new role: a past champion switching companies, an advocate promoted into budget authority, or a buyer hired into a seat that owns the problem you solve. It is a person-level event read from a public profile update, and it resets that person's budget, stack, and priorities at once, which is what makes it convert.
How do you track when a prospect changes jobs?
A person's current employer is public in the experience section of their profile, so you snapshot it and re-read the profile on a schedule, flagging anyone whose company changed. For a list of known champions this runs entirely on public pages, with no session cookie and no per-name subscription. Dedicated tools like UserGems or Champify do the same by syncing your CRM contacts instead.
How long is the window after someone changes jobs?
Shorter than the 90 days vendors quote. Sales Navigator surfaces anyone who changed jobs in the last 90 days, but the first weeks are onboarding and by month three the new stack is being locked. The receptive window is roughly days 30 to 60, and detection lag from delayed profile updates eats into even that, so move on the research quickly.
Is job change tracking the same as hiring signals?
No. A hiring signal is a company posting a role, which tells you budget was committed to a problem before anyone fills the seat. A job change signal is a named person landing in a seat, which tells you who now owns that budget and what they already believe. They pair well but trigger different plays, so read the hiring signals guide alongside this one.


