7 min read
Time-to-hire under 30 days: how growing companies speed up recruiting
Stephanie Haller
Growing companies almost never lose time in recruiting on the candidate market. They lose it on themselves: on slow feedback loops, unclear role profiles and sluggish scheduling. A time-to-hire under 30 days is therefore a question of process discipline. It rarely takes more budget or more sourcing. Eliminate internal latency and structure the selection, and you fill roles faster and make better decisions.
Where the time actually goes
When people say the market is picked clean, the first place to look is not the market but the timestamps in the applicant tracking system. The picture there is almost always the same: the application sits untouched for four days. Interview feedback arrives after a week. Scheduling the next round takes ten days because five calendars have to be coordinated. Most of the elapsed time comes from internal waiting like this: time in which nobody is actively working on filling the role.
The most common time sinks:
- Unclear role profiles. If the manager and recruiting do not have the same role in mind, it becomes visible in the third interview, and the process effectively starts over.
- Interview rounds without a brief. Conversations in which nobody knows what exactly should be tested, spread over weeks, because nobody wants to decide who actually decides. Every additional round costs a week of calendar time on average.
- Feedback as recruiting’s job to chase. Recruiters run after interviews because feedback does not flow automatically within 24 hours.
- Scheduling as a black box. Without blocked interview slots, every appointment is negotiated individually.
And while nothing happens internally, a great deal happens externally: good candidates have two to four other processes running in parallel. A week of silence is not a pause. It is an exit.
Behind this sits almost always the same cause: managers see filling the role as recruiting’s job. They do not share their open roles in their own network, do not approach anyone directly, do not activate contacts, and leave applications sitting that are not convincing at first glance. The role is theirs, the team is theirs, they carry the consequence of a wrong hire, and yet the work sits somewhere else. Holding managers accountable is one of the biggest levers in the whole process, and it costs nothing.
The process, rethought
A 30-day process is built out of decisions made in advance. Everything that can be settled before the role goes live is settled before the role goes live.
The evaluation form exists before the first conversation. Before the role goes live, the manager and recruiting define together: the three to five results the person has to have delivered in twelve months, the capabilities needed for that, and the knock-out criteria. This form, often called a scorecard in recruiting, is the basis for assessing every interview. It ends the debate about the certain something being missing. The certain something is either on the form or it does not count.
The work sample comes first. A case, a coding test or a comparable task comes before the first conversation. It shows early whether the professional fit is there and how serious someone is about the role. The recruiting team stays personally available throughout.
The manager leads the first conversation. Half an hour in which the most important questions are settled first: is the professional competence there, and does the person fit the team? That applies to both sides, because the candidate is also checking whether she wants to work with this manager and this team. Only the manager really knows who she is looking for, and the process can already end after this conversation. That saves everyone involved a great deal of time.
Then a professional conversation. 30 to 45 minutes in which the work sample is discussed. This second conversation adds an independent professional assessment, because the manager understandably wants to fill the role at all costs. Both decide together who is invited to the interview day. Whoever is invited goes through all further conversations up to the decision.
An interview day with four conversations. Four conversations of 45 minutes each on one day, on site or by video, each with its own brief. What gets tested is what decides whether a hire succeeds or fails: whether someone can fulfil the tasks, whether the person fits the team and enriches it, and whether they are motivated to move something and to keep developing. Team fit is assessed by everyone who leads a conversation, from the manager to the last interview.
The briefs work best along your own company values, because all of these points are values at their core, and the values are the yardstick for everything else. Each conversation has its fixed set of questions, and for each role the same people always lead the conversations. That makes candidates comparable and shows that the team stands behind the hire. Along the way the candidate meets up to six people from the company and can better judge whether the role is right for her.
SLAs between the manager and recruiting. This is the single most effective lever I know: binding response times in both directions. New applications are reviewed within 48 hours. Interview feedback arrives within 24 hours, in writing and along the evaluation form. Managers block two fixed interview slots per week. Whoever breaks the SLAs loses their slot in the priority order. That sounds hard, but it is only honest: a role nobody has time for is evidently not urgent.
The 24 hours are not an arbitrary figure. After the conversation no further information arrives, because there is no further exchange with the candidate. Sleeping on it therefore produces no new insight, only a later answer. Anyone who cannot decide after 24 hours did not ask the questions in the conversation that would make an assessment possible. In case of doubt the answer is then a no, and for the next interview different questions belong in the guide.
Shape the candidate journey actively. No more than five working days pass between steps, and the candidate knows at any point where she stands and what comes next. The decision is made on the interview day itself, and the feedback comes directly, including with a rejection. Everyone who goes through the process tells others about the experience, on average to considerably more people than we would like.
The KPIs that count
You can only steer what you measure. But please, few metrics with clear targets, not a dashboard nobody reads. And put the definitions in writing once before you measure: I count time-to-hire from application received to offer accepted. Include the job going live or the first day at work and you arrive at entirely different numbers.
| KPI | Definition | Target |
|---|---|---|
| Time-to-hire | Application received to offer accepted | under 30 days |
| Quality of hire | Goal attainment after 6–12 months, assessed by the manager along the evaluation form | over 80 % meet or exceed expectations |
| Candidate NPS | Willingness to recommend among everyone in the process, including those rejected | over +30 |
| Probation exits | Separations during probation, either side | under 5 % |
| Feedback latency | Time from interview to written feedback | under 24 hours |
The most interesting metric is the combination: if time-to-hire falls while quality of hire stays stable and probation exits do not rise, the process works. If time-to-hire falls and probation exits rise, you cut in the wrong place.
What you must not shorten
Speed comes from eliminating waiting time. Two steps stay untouchable:
The work sample. A real problem from daily work, tackled together, shows how someone thinks, communicates and handles ambiguity. But it shows something else as well: motivation. Someone who genuinely engages with a task like that wants the job. Someone who visibly just works through it is also saying something about their interest.
The conversation about team and culture. Many managers are satisfied when someone can do the work. That is half the test. Someone who fits professionally but does not belong in the team blows up the whole structure in the end, and costs the organisation more than the vacancy would have.
The candidates are out there. The question is whether your process is fast enough to deserve them.
Frequently asked questions
What is a good time-to-hire for growing companies?
For most professional and leadership roles, 25 to 35 days from application received to offer accepted is realistic and competitive. What matters is fixing the definition first: some companies count back to the job going live, others forward to the first day at work, and then you are comparing numbers that have nothing to do with each other. Less decisive than the absolute figure is consistency: a reliable 30-day process beats one that takes 20 days once and 90 the next, because candidates move through it predictably instead of dropping out halfway.
Does hiring quality suffer if we speed the process up?
No, provided you speed up the right thing. In almost every process the time is lost to waiting rather than to care: applications left sitting, feedback dragged out, scheduling that takes weeks. Structured interviews with shared evaluation forms actually improve the hit rate, because everyone involved assesses against the same criteria rather than against their gut feeling.
Which recruiting steps should never be shortened?
Two: the work sample and the conversation about team and culture. The work sample shows motivation alongside professional fit. The culture conversation tests what many managers underestimate: someone who can do the job but does not belong in the team will blow up the whole structure in the end. Cutting here saves two or three days and risks a wrong hire that costs a multiple of an annual salary.