You find a name on LinkedIn, a title that matches what you're looking for, a company you want to get into. You write a good email, you send it, and nothing comes back. Not a reply, not an out-of-office, not even a bounce most of the time. The account is just quiet, because the person moved on eight months ago and nobody told the search result.
This is one of the most common, least talked-about reasons a cold email campaign underperforms. It's not the subject line and it's not the offer. It's that a meaningful share of the "current employees" a basic search surfaces don't currently work there at all.
Why this happens more than people think
A plain Google search for a job title and a company name, or an unfiltered LinkedIn search, returns anyone who has ever held that role at that company. Google's index and LinkedIn's own search don't always reflect a job change the moment it happens, and the people most likely to have moved recently are exactly the people you're trying to reach: early-career hires, recruiters, and anyone in a fast-moving function like sales or talent.
Two real numbers show why the odds aren't in your favor if you're not checking:
- According to the U.S. Bureau of Labor Statistics, the median time a worker aged 25 to 34 had been with their current employer was just 3.0 years as of January 2026, compared to 9.6 years for workers aged 55 to 64. If your list skews toward recent grads, recruiters, or junior hiring managers, a large share of any snapshot of "who works here" is already out of date by the time you read it.
- A Stanford-affiliated Revelio Labs study, reported on by Bloomberg, found that 19.7% of LinkedIn users retroactively edit a past job entry more than 60 days after actually leaving the role, with the behavior most common among younger workers, tech employees, and MBAs. Profiles don't just go stale when someone forgets to update them — a meaningful share update on a delay, so even a "current" tenure date on a LinkedIn profile can lag the real world by weeks or months.
Put those together and the picture is simple: the people you most want to reach, because they're closest to the hiring decision and the most likely to actually read a cold email, are also the people whose "current employer" field is least reliable.
What this actually costs you
A cold email to someone who left isn't a neutral miss. A handful of things happen, none of them good:
- It never gets read. Most companies route a departed employee's inbox to auto-forward, deactivate it, or let it sit untouched. You don't get a signal that anything went wrong.
- It can still bounce, and a rising bounce rate on your sending domain hurts every email after it, not just the one that failed. If you're not sure how a mailbox can look valid and still fail silently, what a catch-all domain does to a cold email list is the same underlying problem from a different angle: the inbox existing isn't the same as the right person reading it.
- It burns a contact you might need later. If that person moves to a company you actually want to reach in six months, a cold email to an address they abandoned isn't a great first impression if it ever does resurface.
- It wastes the one thing that actually matters in outreach: attention. Every email sent to a dead end is an email not sent to someone who could have replied, and it's also an email you can't follow up on later, since most replies to cold outreach come from the second or third message to a real, reachable person, not the first one to a dead inbox.
How to check before you send, not after
None of these require a paid tool, just a habit of checking before a name goes on your list.
- Look at the tenure line on the profile itself, not just the title. LinkedIn shows how long someone has been in their current role, in months or years. A role listed as started "3 years ago" with no recent activity nearby is a weaker signal than one updated in the last few months.
- Check for recent activity tied to the employer. A comment, a post, a reaction, or a mention in the last month or two is a much stronger "still there" signal than the profile's job title alone, since activity is harder to fake-stale than a static field.
- Cross-check against the company's own pages. A team page, an "about us" section, a recent press release, or a conference speaker bio naming the person and the company is a second, independent source. If a person's name shows up on the company's own site in the last quarter, that's better evidence than a search engine's cached copy of a LinkedIn profile.
- Use LinkedIn's own "People" tab on the company page, filtered to current employees, instead of a general search or a Google-indexed result. It's not perfect, but it's a narrower, more current slice than an open web search that can surface a profile LinkedIn itself hasn't recrawled.
- Treat a title you found through a company's own job posting or org chart differently from a title you found through an old article. A recent source beats an old one every time, and "recent" should mean weeks, not the publish date on a three-year-old company blog post.
- When volume matters, prioritize freshness signals over raw title matches. If you're building a list of dozens of names, not just one, the people worth reaching first are the ones with the strongest "currently there" evidence, not just the best-sounding title.
This is also the actual engineering problem behind finding a hiring manager's real email address: the hard part was never guessing an email format. It's confirming the person behind it is still the right person to write to.
Why this is worth building into your process, not just checking once
If you're sending a handful of emails a week, a manual check per contact is realistic. If you're trying to reach dozens of people across a job search, that manual check becomes the actual bottleneck, which is exactly why a basic name-and-title list from a search engine keeps producing bounces no matter how good the email itself is. The fix isn't writing a better email. It's filtering the list before you ever write to it, weighting current signals over whatever a search engine happened to index.
Hesper builds this check into the process instead of leaving it to a manual scan: it looks for people who currently have hiring power at a company actively hiring for the role you want, verifies the email is real before it's revealed, and sends from your own Gmail every weekday so you're not rebuilding this list by hand every time. If you're tired of a list that looks right on paper and bounces in practice, that's the problem it's built to fix.
No comments yet.