Free Calculator

How Long Will This Hire Really Take?

From the day the posting goes live to the day someone actually sits down and works. Most managers plan for the interviews and forget the latency between them, the offer dance, and the notice period. Here is the honest math, with your projected start date.

1 2 weeks 6

Posting live until enough real candidates

1 3 rounds 5
2 5 days 10

Scheduling latency, the silent killer

0 2 weeks 8

US standard is 2, senior roles run longer

Posting to first day of work

0 days

If you post today

estimated first day

Sourcing phase

0d

pool + screening

Interviews + offer

0d

rounds, debrief, negotiation

Notice period

0d

outside your control

Your Process vs a Tight Process

A tight process keeps the same rounds and the same rigor, but batches interviews and schedules the next stage before the current one ends, cutting stage latency to about two days. Same quality bar, fewer wasted weeks.

Your timeline

0 days

at 5 days between stages

Tight process

0 days

batched, pre-scheduled

What This Number Means for You

Every week on this timeline has a price tag.

The seat stays empty while the process runs: work undone, colleagues covering, opportunities waiting. The cost of empty seat calculator prices each week, and multiplying it by your timeline is the budget case for a tighter process.

Speed loses candidates last, latency loses them first.

Good candidates run parallel processes, and the slowest pipeline loses by default. You do not need fewer rounds or lower standards. You need the next stage scheduled before the current one ends. If this is your first hire, the full process is walked through in the guide to hiring your first employee.

The timeline does not end at the start date.

Day one starts the ramp, not the productivity. Budget the onboarding explicitly with the onboarding timeline calculator, and the money side with the cost per hire calculator.

About the numbers: Timeline = sourcing weeks + 5 days of screening + (rounds × days between stages) + 2 days of debrief and decision + 5 days of offer and negotiation + notice period. The tight-process comparison keeps your rounds and sourcing but cuts stage latency to 2 days. The projected start date adds the total to today's date. The model assumes no restarts: a declined offer or an empty final round adds weeks that no calculator can predict, which is one more argument for a pipeline with more than one finalist. Planning estimates, not a promise.

Where Hiring Timelines Actually Go to Die

Ask a manager how long a hire takes and they count the interviews: three rounds, maybe four hours of actual conversation. Then the process takes ten weeks anyway, and everyone is mystified. The missing time is not in the interviews. It is between them: the four days to find a slot, the weekend in the middle, the panelist who was traveling, the debrief that waited for Friday. Latency multiplied by rounds is the real timeline, and it is invisible on every plan because no single delay looks like a decision.

The second killer is the restart. A process built around one favorite candidate has no floor under it: if they decline the offer, you are back at the sourcing phase with two months gone. Keeping two or three live finalists costs a few extra interviews and removes the single most expensive failure mode in recruiting.

The Three Fixes That Compress Everything

Batch the interviews. One or two half-days per candidate instead of a round per week. Candidates prefer it, panelists remember the person better, and it deletes latency at the multiplier. Schedule forward. Book the next stage before the current one happens; cancelling is easier than finding a slot. Debrief same-day. A decision made while impressions are fresh takes twenty minutes. The same decision a week later takes a meeting, a re-read, and someone asking to see the candidate again.

Frequently Asked Questions

Is this timeline realistic or optimistic?
Realistic, assuming you actually run the process. The model adds up the phases most managers underestimate: building a real candidate pool, the calendar latency between interview stages (which quietly dominates everything), offer negotiation, and the notice period. What it does not model is drift: the week the posting sits unapproved, the round nobody scheduled, the hiring manager on vacation. Commonly cited benchmarks put average time-to-fill at roughly six weeks, and most of the gap between fast and slow processes is scheduling discipline, not candidate supply.
Why do days between interview stages matter so much?
Because they multiply by the number of rounds, and because candidates do not wait. Five days of latency across three rounds adds two weeks to your timeline, and every one of those days is a day your best candidate is interviewing somewhere faster. Batching interviews into one or two days per candidate is the single highest-leverage fix in recruiting, and it costs nothing but calendar courage.
Can I skip rounds to go faster?
Sometimes, and carefully. Below two rounds you are hiring on vibes, and a bad hire costs far more than the weeks you saved (run the cost of bad hire calculator if you want that number). The better lever is not fewer rounds but denser ones: same interviews, compressed into batch days, with a debrief scheduled the same afternoon instead of "when everyone is free."
What about the notice period? I cannot control it.
True, and that is exactly why the controllable phases matter more. Two weeks of notice is standard in the US, senior roles often carry four or more, and some candidates have relocation on top. You cannot compress their notice, so compress your own latency: the phases before the offer are the only part of the timeline you own outright.
What does the empty seat cost me while I run this process?
Usually more than the recruiting itself. Every week of the timeline is a week of work not getting done, colleagues covering, and opportunities slipping. The cost of empty seat calculator prices exactly that, per week, and pairing the two numbers is the strongest argument for fixing your scheduling latency today.
Should I start sourcing before the role is fully approved?
If there is any legal and political room, yes. Sourcing runs in parallel beautifully: warming up the network, drafting the posting, lining up the interview panel. Teams that treat approval day as posting day save one to two weeks against teams that treat it as the starting gun for thinking about the posting.

The Seat Is Empty Either Way. Choose for How Long.

Batch the interviews, schedule forward, debrief same-day. Same rigor, weeks faster, and your best candidate is still available when the offer goes out.

Related: Cost Per Hire → Related: Onboarding Timeline →

← All Calculators