The call comes late on a Thursday. It is a no, but an odd one: you were a close second, the team really liked you, and they would love to stay in touch. You are left holding a sentence that could mean a job in three months or could mean nothing at all.
Both readings are plausible, which is the annoying part. Recruiters say this to people they fully intend to call back, and they say it to soften a rejection they feel bad about delivering. You do not have to guess. There is a simple test, and then about a week of small actions that decide whether the line stays open.
The test: does the message name anything?
Read the email again, or replay the call, and look for nouns. A genuine offer to stay in touch nearly always names one concrete thing. A formula names nothing.
Three things count:
- A timeframe. "We are opening a second headcount in the first quarter", or "the budget is confirmed in January". A date is expensive to say when it is not true, because you will come back on that date.
- A specific upcoming role. Not "future opportunities" but "the Leeds team is hiring for the same profile", or "a senior version of this job is being scoped".
- A person. "I would like to introduce you to Karen, who runs the other team", or "write to me directly, here is my number". A named human with a way to reach them is the strongest of the three.
Compare that with the template: "We were very impressed and will keep your CV on file for future opportunities." No date, no role, no person. That sentence goes out unchanged to every finalist, and probably to a few people who were not finalists. It is not a lie. It just commits nobody to anything.
If the message names a date, a role or a person, treat it as an open door. If it names none of them, treat it as good manners, and reply well anyway.
Reply the same week and accept out loud
Most runner-up candidates either do not reply or send one line of thanks. Both leave the offer hanging in the air, where it evaporates. They said "let's stay in touch", and the only way that becomes a fact is if you say yes in writing, so that a thread with your name on it exists and can be found later.
Timing matters more than polish here. Within the week, the interviewers still know which candidate you were. A month later you are a row in a spreadsheet. If you are still stinging, give it a day or two; "How to Handle Job Rejection (And Use It)" covers that side, and this piece will not repeat it.
Keep the reply short. Something like this:
Hi Marc, thank you for telling me directly, and for the time the team gave me. I am disappointed, naturally, but I enjoyed the process and I would like to take you up on staying in touch. You mentioned a second role may open in the spring, and I would be glad to be considered for it. May I check in with you in March? One question, if you have two minutes: what would have made the difference between me and the person you chose?
That note does four jobs. It thanks without grovelling, it admits the disappointment in four words, it accepts the offer explicitly, and it repeats the concrete thing they named with a date attached. If they named nothing, this is the place to ask: "Is there a role or a timeframe you had in mind?"
Their answer completes the test for you. A real offer produces a date or a name. A formula produces "we will reach out if anything comes up", and now you know where you stand without having burned anything.
Ask the one question worth asking
"Do you have any feedback?" gets you fog. You were great, it was very close, it was a tough decision. Someone asked for general feedback worries about sounding critical, or about saying something that comes back on the company, so they say nothing.
"What would have made the difference?" is a different question. It is about the gap between two people rather than about your flaws, and that makes it far easier to answer honestly. The usual answers are plain: the other person had already run this exact migration, managed a larger team, came from the sector, was an internal candidate, or could start sooner.
The value is in learning whether the gap can be closed. Ten more years in the industry is not something you fix by spring. A certification, a tool, or a sharper account of one project is. And sometimes the answer shows the decision had little to do with you, which is useful in its own way: an internal move, a salary band. Either way you find out whether applying again makes sense.
Ask once. If nobody answers, do not chase. Plenty of companies forbid their teams from commenting on a rejection, and that silence says nothing about you.
Keep a light contact with the hiring manager, not only the recruiter
The recruiter runs the process. The hiring manager holds the memory of you and hears about the next opening before anyone else does. Recruiters change accounts, leave agencies, and move on to forty other vacancies. The manager is the one who says "what about the person we nearly hired?" on the day somebody resigns.
After that, one message a quarter. Not "any news?", which hands them a chore. A good quarterly note carries something: a result you have had since, a piece of reading that relates to the problem you discussed, congratulations on a launch. For example: "Saw the new pricing tiers went live, congratulations. On my side, I have just closed the migration we talked about in May. Still watching what you publish." Three or four lines, and no question that demands a reply.
The real cost is about fifteen minutes a quarter, so an hour a year per company. That is cheap for the two or three employers you actually liked, and too much if you turn it into a campaign of ten. Stop after a year of silence, or sooner if the replies cool. A light touch is welcome; a monthly nudge is pressure.
Apply to a named role instead of waiting for the call
The most common mistake is waiting. "We will keep you in mind" assumes somebody remembers and then goes looking. Sometimes the database does that job, and "Talent pool ATS: how old job applications get looked at again" explains that side. On the human side, people forget, change jobs, and the new recruiter has never heard your name.
So watch the careers page and set an alert. When a role appears that fits, apply through the normal channel and write to the manager the same day: "I saw the product lead role go up and have just applied. I was runner-up for the project manager job in June and would be glad to pick the conversation back up." You are giving them an easy action, which is forwarding your note to the recruiter with "look at this one".
Before you apply, update your CV with what has changed since the interview and with what the difference question taught you. A tool such as Postulit rebuilds a CV from your LinkedIn profile in a few minutes, so start by updating the profile. The second round has its own dynamics, and "Reapplying to the Same Company: How the Second Interview Differs" deals with those.
What to expect, honestly
Most of these go nowhere. The headcount is frozen, the manager leaves, the person they hired works out fine. Nobody can give you odds, and anyone quoting a percentage is making it up. Do not pause your search for it.
Still, the cost is low and the cases that do come through tend to be good ones. You skip stages, and the team already knows you. Hires also come undone in the first months: a probation period that does not work out, a counter-offer from the old employer, a relocation that falls through. When that happens, the runner-up who replied well is the first call.
So this week: reply, accept in writing, ask the difference question, and put a check-in date in your calendar. Then go back to your other applications.