The short answer
Often, yes. A strong runner up candidate already knows your product and your team, and you already know they are good, so they can be the fastest next hire you make. It only works if the first rejection was honest, the feedback was useful, and someone stayed in touch until the next role opened.
A good hiring process often ends with two people you would happily hire and one seat to fill.
You make the offer. The winner signs. The runner up candidate gets a polite email, and within a week they are forgotten.
A few months later the team needs another engineer, and the search starts again from zero.
That runner up is often the fastest hire you will ever make. They already know your product. They have met your team. You already know they are good.
You just did not have the seat.
Whether they are still available when you do depends almost entirely on what happens in the days after you say no.
Why most runners up are lost
None of this happens on purpose. It happens because nobody owns it.
The rejection goes out as a two line email, or not at all. The engineer leaves with no idea how close they came, or why it went the other way.
The founder is busy onboarding the person they did hire. Nobody is thinking about the one who missed out.
And most recruiters have no reason to stay in touch. A candidate who did not get the job does not earn anyone a fee that month, so they drop off the list.
The result is predictable. A strong engineer who liked your company walks away feeling like a number, and takes the next good offer that comes along.
What keeping a runner up warm actually looks like
It is not a nurture sequence or a talent community. It is three things done properly.
Tell them straight, and tell them quickly. The same week the decision is made, with the real reason. Silence is what turns a near miss into a closed door.
Give feedback they can use. What they did well, and where it came down to. I always give feedback at the end of a process and make sure the loop is closed, whatever the outcome.
Stay in touch honestly. Do not promise a role that does not exist. Keep them posted, keep asking what they want next, and keep looking for them.
An engineer who started a new role this month described it better than I could:
“When a process ended without an offer, he told me straight, kept looking, and kept me posted.”
That sentence is the whole method.
A seventh hire with no new search
I have worked exclusively with a hospitality technology scaleup since 2024. This summer they briefed me for one senior Elixir engineer.
Two candidates came through strongly enough that they hired both, a senior and a strong mid level engineer, off one brief.
A third engineer was a close runner up.
I told him straight. I gave him the feedback. I kept him posted.
Shortly after, the founder needed another Elixir engineer, and asked whether that runner up was still available.
He was. One short call, then an offer. He started on 1 October.
No advert. No new shortlist. No new search. He is the seventh engineer I have placed with that client.
It is not the first time a runner up has become the next hire in my career, and it will not be the last. It only works because the first no was handled properly.
When going back to a runner up does not work
It is not a guaranteed hire, and treating it like one is a mistake. Be honest about which of these applies.
They have moved on. Strong engineers do not stay on the market for long. The longer the gap, the less likely they are still available.
The role has changed. If the new headcount is a different job from the one they interviewed for, do not shoehorn them into it because it is convenient.
They were second for a reason that still matters. Close is not the same as right. If the gap was a skill the team still needs, a second process will not close it.
The first no was handled badly. If they heard nothing for three weeks and then got a template rejection, the door is probably shut. That one is fixable next time, not this time.
How founders can keep the door open themselves
You do not need a recruiter to do this, although it helps to have someone who owns it.
Decide before you send the offer. Ask yourself whether your second choice is someone you would hire if the seat existed. If the answer is yes, tell them that, in those words.
Own the feedback. Give it yourself, or make sure whoever ran the process does.
Write it down. Who they were, why it was close, and what they want next. Your memory of a candidate fades faster than you think.
Check before you advertise. When the next headcount is approved, get in touch with them before you write the job advert.
The cost is a few honest conversations. The return can be a hire made in days rather than weeks.
Questions this search answers
Can I go back to a candidate after rejecting them?
Yes, provided the original no was honest and someone stayed in touch. Engineers remember how a process ended. In the example in this article, the founder went back to a runner up from a process two months earlier and made an offer after one short call, with no advert and no new shortlist.
Should I keep in touch with candidates I did not hire?
With the ones you would have hired if you had the seat, yes. Keep it honest. Tell them where things stand, ask what they want next, and do not promise a role that does not exist yet. A short message every few weeks is enough to keep the door open.
How long does a runner up candidate stay available?
It depends on the engineer and the market, and strong engineers rarely wait. The longer the gap, the less likely they are still free. In the example in this article, the gap between the first process ending and the offer was around two months, and the engineer was still available.
What should rejection feedback include?
What they did well, where the decision came down to, and whether you would consider them again for a future role. Short and specific beats long and vague. Give it the same week the decision is made, because silence is what turns a near miss into a closed door.
If you have a strong runner up from your last hire and no plan for them, or your next role is already on its way, I can help.
Arjun Gillard
Founder, AG Talent
agtalent.co.uk
