How long tech hiring takes and what to do when it goes quiet

The Cvizo team2 min read

A typical engineering hire runs three to eight weeks from application to offer. The spread comes from how many stages there are and how many people have to agree, and the stage that ruins the average is the final decision rather than the interviews.

A hiring timeline with six stages, the longest wait drawn as a broken line

In short

  • Three to eight weeks is the normal range. The final approval, not the interviews, is what stretches it.
  • Interviews can be scheduled. A budget sign-off waits on somebody outside the hiring loop.
  • Silence is usually a stalled process rather than a decision that has already gone against you.
  • Follow up once, after the date you were given has passed, and ask for a new date rather than an answer.

Most of the strain in a job search comes from the waiting between interviews. It is the only stage you have no control over, and nobody tells you anything about it.

How long it actually takes

A typical engineering hire runs three to eight weeks from application to offer. Almost all of that spread comes from two things: how many stages there are, and how many people have to agree before anyone can be hired.

StageTypicallyWhat stretches it
Application review2 to 10 daysThe pile that built up over the weekend
Recruiter screen15 to 30 minutesMatching calendars, not the call itself
Technical interview1 to 2 weeks after the screenEngineer availability
Team interview3 to 7 days after the technicalHolidays, travel
Decision and offer3 to 14 daysBudget sign-off, comparison with another candidate

The stage that ruins the average is the last one. Interviews can be scheduled. A decision waits on somebody who has to approve a budget, and that person is almost never in the hiring loop.

Silence rarely means rejection

No answer for ten days after a good technical interview usually means the company is still talking to a second candidate and does not want to close any door. A rejection is cheap and quick to send. Limbo is what is left when no decision has been made.

So do not read silence as a verdict on you. It tells you where the process is on the other side.

When to follow up

One question, sent at the right moment, works. Three questions in a week work against you.

  • After applying: do not follow up. If nobody replied in two weeks, the application did not clear the filter, and an email will not reverse that.
  • After the screen: follow up after a week, if the recruiter gave you a date and the date passed.
  • After the technical: follow up after five working days. Keep it short, with one specific question about the next step.
  • After the final interview: ask for the decision date while you are still in the room. Then you are not guessing at all.

What this does not change

Tracking dates will not make a process shorter. It will shorten the stretch where you have no idea where you stand, and that is the part that actually wears people down. If you are running several processes at once, keep the stage dates in one place: by the third company you stop remembering who promised what, and when.

Common questions

How long should I wait before following up?

Until the date you were given has passed, then a few days. If you were given no date, a week after the last stage is reasonable. Following up before the date you were promised reads as impatience and tells the recruiter nothing they can act on.

Does a fast process mean they like me?

Sometimes, and often it just means a short approval chain. A four-person company can decide in a day because the person deciding was in the room. Six stages and a panel cannot, regardless of how strong you were.

Should I keep applying while waiting?

Yes. Nothing about a process in flight is a commitment until an offer is signed, and the waiting stage is the one where a full pipeline is worth most.

Keep every application in one place

Your applications, dates and interviews in one view. The status of five processes stops being something you hold in your head.

Start free