Offer accepted, then no show: reducing drop-off between offer and joining for developers

A custom software company makes an offer to a backend developer on a Monday. She accepts by email on Tuesday and says she will join after her notice period. On the joining date, the laptop is ready, the buddy is booked, and she does not turn up. Her phone is off. The team lead asks the same question every hiring manager asks: what did we miss?

Drop-off between acceptance and joining is common for developers because good candidates hold several options. You cannot remove the risk. You can reduce it with a clear process and honest contact. Here is one.

A signed acceptance is a promise, not a start. During the notice period the candidate is still in a conversation with the current employer, who may counter with a raise or a new role. Other recruiters keep calling. Silence from your side gives the other conversations room to grow.

• The current employer makes a counter offer.
• A competing offer arrives during the wait.
• Nobody from your company has spoken to the candidate since acceptance.
• The offer left key questions unanswered, such as the team, the tools or the first project.
• The candidate heard something negative about the company and had no one to ask.

Notice period length is a matter between the candidate and the current employer. Your contract and any buy-out arrangement depend on the facts, so check them with your own qualified legal adviser. Do not promise anything about it in writing without that advice.

Much of the risk is settled before you send a letter. Ask early what the candidate is weighing, what the current employer may do and what would make them stay. A candidate who says they are open to a counter offer is telling you something useful. Ask what the notice period is and whether the current employer has ever released people sooner. Then talk through the offer in a call, not only by email.

1. 1

   Confirm in writing the day after acceptance

   Send a warm note with the joining date, the team lead's name and the first-week plan. Ask for questions.

2. 2

   Introduce the team lead

   Arrange a short call between the candidate and the person they will report to. Talk about the first project, not about paperwork.

3. 3

   Share something real

   Send access to a sample repository, an architecture overview or the tools list, if it is not confidential. It gives the candidate something to look forward to.

4. 4

   Stay in touch at fixed points

   Agree check-ins with the candidate, such as every week or two. Keep them short and genuine, and ask how the notice period is going.

5. 5

   Confirm logistics a few days before

   Send the joining time, location or remote setup, documents to bring and who will greet them.

6. 6

   Have a backup plan

   Keep the second-ranked candidate warm and tell your delivery lead that a no-show is possible, so the project plan does not depend on one person.

Vague offers breed doubt. State the role, the team, the reporting line, the pay structure, the joining date and what happens in the probation period. Explain variable pay in plain words with an example. If anything in the offer is conditional, say so up front. The more complete the offer, the fewer questions the candidate has to answer for the current employer or for family.

Talk about counter offers before they happen. Ask the candidate what would make them stay and whether they would consider it. If they do receive one, ask what is on the table without arguing. Sometimes the best outcome is an honest conversation about whether the move still makes sense. Do not match a counter offer by raising pay beyond your bands in a panic, because it will cause trouble with the existing team.

Candidate, role and team.
Offer date and acceptance date.
Agreed joining date and notice status.
Last contact date and who made it.
Open questions from the candidate.
Competing offers or counter offer signals.
Backup candidate and status.
Equipment and access ready: yes or no.

Try to reach them by phone and email once, politely. Do not assume the worst. Record what happened, close the role in your tracker, and note any pattern, such as the same source, the same stage or the same recruiter. Review each drop-off in a short note, so the next offer improves. Never publish a candidate's name or discuss them outside the hiring group.

Recruiters often run the process until acceptance and then step back. For developers, the hiring manager should own the relationship after the offer. The candidate wants to hear from the person they will work for. Block a short slot each week in the notice period for this contact. Use it to share what the team is building, ask about their questions and mention small news such as a release or a new hire. The aim is for the person to feel already part of the team, which makes a casual call from another recruiter less tempting.

Also prepare the first week before the person arrives. A laptop that is not ready, access requests that take days and a manager on leave all tell a new joiner that nobody was waiting. Prepare accounts, a buddy, a first small task and a lunch plan. Our offer and joining process work often starts with this checklist.

Pair this with the scorecard and skills test for hiring developers and the recruitment process consulting page, which covers redesigning offer and joining steps. For the type of team this applies to, see custom software companies.