A senior mobile developer applies to four firms on a Sunday. By Thursday she has a technical round booked at two and an offer from one. Your firm replies on Friday asking for a convenient slot next week. By then she has accepted. Nobody in your team lost the candidate through a poor interview. You lost her through the calendar.
Good developers rarely sit in one pipeline. The software development hub names this pattern. The fix lies in the hiring path, not only the offer.
How it shows up
- Candidates stop replying after the first call.
- The technical lead is the bottleneck: interview slots open only in the evening or on Friday.
- Feedback goes to HR on day three and to the candidate on day six.
- The offer comes with a pay figure but no band, no role scope and no joining date.
What it costs
An open requisition for a senior role can sit for months while the project slips or a junior is stretched. The cost shows in delivery dates, in the overtime of the existing team and in the recruiter's fee. A slow process also trains candidates to treat your firm as a backup. The recruitment process consulting service designs the path. A worked setting for custom software companies is also available.
A hiring path that holds candidates
- 1
Agree the role in one page
Stack, level, band, first project, reporting lead, interview panel. Share it with the recruiter.
- 2
Screen within two working days
A short call covering notice period, expected pay, location mode and the stack. Say the path and the decision date aloud.
- 3
Book the technical round at once
Use a reserved slot per week for the lead, so the round is not negotiated again.
- 4
Use a shared question bank and a score sheet
Two interviewers, same sheet, a pair-programming task or code review exercise that reflects real work.
- 5
Decide in a day
Panel huddle the same day. If yes, the offer goes out within twenty-four hours, with band, scope and joining date.
- 6
Keep touch until joining
A call from the lead before the joining date. Many offers fail between acceptance and the first day.
Selection quality, not only speed
Speed does not mean skipping rigour. Use the interview scorecard template so that each interviewer scores the same dimensions. A fast process with a fair scoring sheet beats a slow one with a gut call. Review rejected candidates after six months to see whether your questions predicted anything.
Where to begin
Take your last five hires. Count days from application to offer, and find the longest wait. Usually it is the technical round or the decision meeting. Fix that first. Then write the role page and send the path to recruiters. Once they accept, keep them with a first-week checklist.
What the candidate sees from the other side
A developer with three live processes keeps a private scorecard. Who replied within a day. Who named the interviewer in advance. Who gave a clear pay band. Who let her speak to the team lead rather than only HR. Whose coding round resembled the actual work, and whose was a puzzle about pirates and bridges. She is also checking the build and deploy practice: do they use pull requests, automated tests, a staging environment? Firms that are vague on these lose her to those who show their pipeline.
Offer content that wins
- Level and band, in writing, with the first project named.
- Stack and tools, including the code host, CI system and review practice.
- Work mode: office days, remote days, core hours, on-call expectations.
- Joining date, notice-period handling and any relocation help.
- A named buddy and a first-week plan, sent before acceptance.
Mistakes to remove from the path
- Three rounds of the same algorithm question by different interviewers.
- A take-home task that needs a weekend and gets no feedback.
- A salary question asked first and a band disclosed last.
- A silent gap between the last round and the offer.
A one-week calendar that works
Monday: screening call by HR. Tuesday evening: first technical round, a pair session on a real bug. Wednesday: second interviewer reviews a small pull request with the candidate. Thursday morning: panel huddle with the score sheet. Thursday afternoon: offer call by the hiring lead, letter by evening. Friday: buddy introduces himself by message. Few firms manage this, which is why those that do win the senior hires. Reserve the interviewers' slots in advance, since a lead who blocks two evenings a week removes the biggest delay.
Closing the gap between acceptance and joining
Offers fail in the notice period. The current employer counters, a rival calls, the candidate's family worries about the move. Keep a weekly touchpoint: a note from the buddy, an invitation to the team's demo day, the laptop courier tracking number. Ask openly whether anything has changed. A candidate who says the counter-offer is tempting on day twenty is easier to help than one who vanishes on day thirty.
