How to Re-Engage Past Candidates and Silver Medalists

What does candidate re-engagement actually mean?

Every company with a few years of hiring behind it has a database of people who applied, interviewed, and did not get an offer. Most of that database is treated as exhaust. Candidate re-engagement is the practice of working it like a sourcing channel: filtering it against a live role, deciding who is genuinely still a fit, and reaching out with a message that acknowledges the history instead of pretending it never happened.

It matters because the economics are unusually good. Someone in your ATS costs nothing to find. They have already been screened by a person, so you have real signal on them rather than a resume guess. They know what your company does, which removes an entire round of explaining. And if they got to a final stage, someone on your team already believed they could do the job.

The reason it rarely happens is not disagreement, it is friction. Nobody wants to open the ATS and manually re-read 400 old applications against a new job description, so the database sits there while the same team pays to source strangers.

Who is worth re-engaging, and who is not

Not everyone in the database is a candidate. Sorting by rejection reason is what makes the list workable.

The single most valuable thing you can do for future re-engagement is record why someone was rejected in a structured field, not in a free-text note. A database where every rejection reads "not a fit" is unsearchable, and unsearchable is the same as empty.

How do you re-engage a candidate who was rejected?

Lead with the truth. The message that works acknowledges the previous process directly, names the specific role and stage, and explains what has changed. The message that fails is a generic template that treats a person who spent six hours interviewing with you as a cold lead.

A structure that consistently gets replies: reference the exact role and roughly when, say one specific thing you remember about their background or their work, explain what is different now (a new team, a more senior scope, a compensation band that moved), and ask a low-commitment question rather than pushing them into an application. If they were a silver medalist, say so plainly. Candidates find it flattering rather than awkward, and it explains why you are writing.

Be careful about two things. Do not tell someone they were "almost hired" if they were not, because it is easy to disprove and it costs you the relationship permanently. And do not re-engage on a role that is clearly a step down from where they were headed. Both mistakes read as a database blast, which is exactly what you are trying not to look like.

If you are running the outreach at any real volume, treat it with the same discipline as any other sequence: sender reputation, sensible sending limits and genuine personalization per message rather than one merge field. The mechanics of keeping a personalized sequence out of the spam folder apply just as much to a talent database as to a sales list, and a re-engagement campaign that lands in spam is worse than not sending it, because you burn the contact quietly.

How often should you re-engage past candidates?

Tie it to a trigger, not to a calendar. The right moment to touch a past candidate is when a role opens that genuinely fits them, and nothing else. Quarterly newsletters to a talent pool feel like activity and produce very little, because the recipient has no reason to act on the day it arrives.

As a spacing rule, no more than two role-specific approaches a year to the same person, at least four months apart, and stop entirely after two clear declines. Anyone who explicitly asks not to be contacted goes on a do-not-contact list that your sourcing actually respects, which is both a courtesy and, under US state privacy laws, increasingly a requirement.

Where an agent changes the math

The reason silver medalist programs get announced and then quietly die is that the re-screening work is genuinely tedious. Doing it properly means reading every archived candidate against the new role's criteria, not just matching a job title, and no one has a spare afternoon for that in the week a req opens.

That is exactly the work an AI recruiting agent is built to do. Point it at a role and it evaluates candidates against the structured criteria you set, including people already in your ATS, ranks them into a shortlist and shows the evidence behind each score, so the past candidate who is genuinely a fit surfaces next to the newly sourced ones instead of being invisible. From there it drafts outreach that references their real history and books the interviews. A person still decides who to contact and who to hire.

Two related pages are worth reading if this is the problem you are solving: candidate outreach automation for how personalized sequences run at volume, and passive candidate sourcing for reaching people who were never in your database at all. If you are calculating whether the effort pays off, our breakdown of the cost per hire formula and benchmarks gives you the number to compare against.

Frequently asked questions

What is a silver medalist candidate?

A silver medalist is a candidate who reached the final stage of your hiring process and lost to one other person. They have been fully screened and interviewed by your team, which means you have real evidence on them rather than a resume guess. They are the highest converting group in any talent database and the first place to look when a similar role opens.

How long after a rejection can you contact a candidate again?

For a silver medalist, three months is reasonable if a genuinely similar role opens, and 12 to 24 months is the window where they are most likely to be open to a move. For someone who declined an offer, wait around 18 months, since the reason they declined usually needs time to change. Always tie the contact to a specific role rather than a calendar reminder.

Is it worth re-engaging candidates instead of sourcing new ones?

Do both, but check the database first because it is free and pre-screened. Past candidates cost nothing to find, reply at higher rates than cold outreach, and need less explaining about the company. The database will not cover every role, particularly new skill areas, which is when external sourcing takes over.

What should a candidate re-engagement email say?

Name the exact role and roughly when they applied, say one specific thing about their background that made them memorable, explain what has changed about the opportunity, and ask a low-commitment question instead of asking them to reapply. If they were a finalist, say so directly. Generic re-engagement templates get ignored because the recipient can tell they went to hundreds of people.