Detect Job Changes Before Emailing: LinkedIn Verification

Roughly 18–20% of B2B contacts change jobs every year. If your sequences don't detect job changes before sending, you are emailing ghosts — paying reputation cost for every dead address, and missing the chance to follow a buyer to their new company where they might actually convert. This guide covers the detection patterns that work.

Why stale lists silently burn reputation

• The email address may still technically accept mail — it doesn't bounce immediately.
• It's often forwarded to someone who didn't sign up to hear from you.
• Engagement rate drops (nobody opens mail addressed to a person who left).
• Mailbox providers notice the pattern and downgrade reputation.

Related: Clean Contact Data Before You Reach Out: A Practical Checklist for Phone and Email Validation

How job changes are actually detected

1. LinkedIn profile check — real-time, not cached. Compare the contact's current employer in the profile to the employer in your record.
2. Tenure signal. Current tenure in role < 30 days? Congratulations sequence, not a cold pitch.
3. Role change within the same company. Different buying persona now — different messaging.
4. Auto-reply pattern matching. "I no longer work at X" / "please contact Y" replies classified automatically.
5. Outbound bounce history. Addresses that started bouncing in the last 30–90 days get flagged for re-verification.

What to do when a job change is detected

• Before the send: hold the address, don't dispatch. Flag for manual review or auto-look up their new employer via LinkedIn RTV. LinkedIn RTV.
• After the send (reply-based detection): pause sequence immediately, update CRM, re-enrol at new company if ICP match.
• If they moved to an ICP account: this is gold — trigger a congratulations + "I see you just joined X, would love to help" sequence.
• If they moved to a non-ICP account: archive the record.

Related: Google Is Becoming A Personalizing Mirror Before You Even Type A Query via @sejournal, @TaylorDanRW

A practical workflow

1. Weekly cron: LinkedIn real-time check across every contact scheduled to be sent in the next 7 days.
2. Stale contacts flagged before dispatch.
3. New-employer capture via LinkedIn.
4. Re-verify the new email via waterfall. Waterfall.
5. CRM record updated with both old and new data points.

Impact on bounce rate

Customers who run LinkedIn real-time verification before dispatch typically cut hard bounces by 40–55% on lists older than 90 days. That alone keeps the sending domain well below the 3% bounce rate that triggers throttling.

When to run the check

• Always, before a list's first send — even freshly sourced lists have 2–5% stale records.
• Before every resend on a 30+ day old list.
• On every CRM record older than 90 days.
• On every re-engagement campaign.

Turn on job-change detection

Start a trial and LinkedIn real-time verification runs automatically on every upload and every pre-send sweep.