The Silver Medalists Sitting in Your ATS

What happened to the person who came second in the search you ran last spring? Say it came down to two finalists. Both were qualified and both wanted the job. You picked one. Maybe she was slightly stronger, or maybe the spec shifted two weeks in and the other one fit the new version a little less well. The runner-up got an email saying you'd decided to move forward with another candidate, and nobody at your company has spoken to him since.

Now it's autumn and you're opening a similar role. At most companies, you post it and start sourcing from scratch, paying for job boards and outreach to find people you know less about than the one you already turned down.

Put that way it sounds strange, but it's what nearly everyone does. Every competitive search produces people like this, who came second for reasons that had more to do with timing than ability, and a company that has been hiring for a few years has probably collected hundreds of them. They already got through your process, so you know something about them, and they're sitting in a database nobody opens.

Why? The data is there. Each of them has a disposition status and, somewhere, qualification notes. But finding the right person from eight months ago, for the right role, at the right moment, means somebody has to go looking, and nobody goes looking when 300 fresh applications from the new campaign are waiting in the queue.

Even someone who does look won't find much. "Just search your ATS" sounds reasonable, but ATSs were built to take candidates in, not to find them again. Keyword search over unstructured text in Workday or Greenhouse was never meant to match today's requirements against a profile nobody has touched in fourteen months. The results are noisy and incomplete, and sorting through them takes manual review that nobody has time for in the middle of a campaign.

The deeper problem is that the most useful part of the record was never really recorded. What you learned about a candidate came from the screening conversation, and that lives in a recruiter's notes, if anyone wrote it down. Human phone screens don't produce anything consistent enough to query. You can search the resume, but you can't search what the candidate said when asked how they handled an underperforming direct report.

Search also favors people whose resumes happen to use this year's vocabulary. If someone was screened fourteen months ago under an older title for what is essentially the same job, a search on the new title will skip right past them. They're as qualified as they were. The words just moved.

So the silver medalists become a kind of inventory that grows with every hiring cycle and quietly goes stale. Someone who had a good experience with you six months ago will probably take your call. At eighteen months the window is starting to close. Most companies never try at all.

A few recruiting teams have started treating past candidates as a sourcing channel rather than an archive, and the case for it is easy to see. Someone who has already engaged with your company, knows the type of role, and passed an initial screen should be easier to bring to an interview than a stranger answering a cold message, and cheaper to hire. The hard part is doing it on every opening instead of now and then. Reviewing old applications against a new role isn't something a recruiter can absorb on top of a live campaign. It happens when someone has a spare hour and thinks to try, which is to say rarely.

That seems to me like a job for software, and it's one of the things we built Asendia to do. The limit here is calls. A recruiter can make only so many screening calls in a day, and when new applicants and old ones compete for those calls, the old ones lose every time. Software doesn't have to pick. The same system that calls new applicants can call past ones. When a role opens, it matches the requirements against earlier candidates in your ATS whose profiles fit, and each of them gets a call that mentions their earlier contact with you, explains the new opening, and runs a structured screen against what the current role needs. What comes back is a ranked shortlist of people your team has already vetted, who can go to a hiring manager without repeating intake. Because it runs alongside normal intake, nobody in the new applicant pile waits longer while the old names get their calls.

For an agency running high-volume campaigns, the difference is where each one starts. A team that has already talked to a hundred qualified past candidates before the new posting goes live is in a very different position from one that starts cold every time. Its first shortlist comes sooner, and the people on it are having a second conversation with you rather than a first, which should show up in their intent and in how often they decline offers. The post on offer rejection rates goes into where slowness in the pipeline costs the most.

My guess is that most teams have less of a talent shortage than a memory problem. They spend heavily at the top of the funnel and leave years of pre-qualified people untouched. The best person for your next role may have applied eight months ago, passed a screen, and lost out on timing. If nobody calls, they'll take a job somewhere else or stop looking, and you'll never know they were there.

Ready to transform your hiring strategy? Schedule a Demo with our founders today!