When a strong candidate withdraws, the usual explanation is that they took a better offer. Sometimes true. More often, something in the process told them this was not a place worth joining, and the other offer simply arrived at the right moment.
These are the signals candidates read, in roughly the order they encounter them.
1. The job description tells them nothing
A specification listing fourteen requirements, three paragraphs of boilerplate about company culture, and no salary gives a candidate no reason to apply and no way to judge whether they would be any good at the job.
Strong candidates are usually employed and not desperate. They apply for roles that sound specific and interesting. A vague description filters for the people with the least choice.
What to change: describe what the person will actually do in their first six months. Cut the requirements to the ones that are genuinely requirements. Include the salary range.
2. The application takes more than ten minutes
Re-typing a CV into a form field by field is the most reliable way to lose candidates who have options. Every additional screen loses people, and it loses the employed, selective ones first — the people with the least patience for an unnecessary process.
What to change: ask for what you need to make a first decision. Everything else can come later, once there is mutual interest.
3. Nobody responds for two weeks
Silence after an application is read as rejection. Silence after an interview is read as rejection with discourtesy attached.
Candidates talk. A reputation for not responding costs you applications you will never know you lost.
What to change: acknowledge every application automatically. Give interview feedback within 48 hours, including to the people you are rejecting.
4. There are five interview stages
Each stage adds scheduling delay, and each delay is an opportunity for another process to finish first. By stage four a candidate is wondering whether an organisation that needs this many conversations to make a decision is one where decisions get made at all.
What to change: ask what decision each stage enables. Remove the ones that do not answer that. Combine what remains.
5. The unpaid task takes six hours
Work samples can be genuinely useful. A six-hour exercise is not a work sample, it is unpaid labour, and the strongest candidates — who are employed, in demand, and short of evenings — decline.
What to change: cap it at ninety minutes. If you need more than that, pay for it. Make sure the task actually resembles the job.
6. The salary conversation happens at the end
Reaching offer stage before discovering a gap wastes weeks and leaves the candidate feeling the process was not straight with them. Even when you can close the gap, you have started the relationship by making them ask.
What to change: publish the range, or establish it in the first conversation.
7. The offer takes a week to arrive
The gap between "we would like to make you an offer" and an actual document is where candidates reconsider. Enthusiasm fades, counter-offers arrive, and the delay suggests either disorganisation or hesitancy.
What to change: have the approval chain ready before you reach decision stage. The offer should go out within 48 hours.
What this costs
The visible cost is the role staying open. The larger cost is invisible: the candidates who withdrew without explanation, the ones who did not apply because someone told them about the process, and the ones who accepted elsewhere while you were still scheduling.
None of that appears in a time-to-hire report. It appears in the quality of who you end up hiring.
Where to start
Take your last five processes and note every point where the candidate was waiting on you. Not the total duration — the waiting. That list is your fix, in order.
Sizanid runs searches end to end, which includes keeping candidates warm through the gaps. If your process is losing people and you are not sure where, [we are happy to take a look](/find-talent).
