How long should your engineering interview process take?

Two to three weeks from application to offer. That is the target for engineering roles at every level below director. Every week you add to that timeline, you lose 10 to 15 percent of your candidate pool. Not because engineers are impatient, but because good engineers are already employed, already being spoken to by other companies, and already receiving offers.

The maths is straightforward. Start with 10 shortlisted candidates. Run a five-week process and you are down to five or six by the time you make an offer. One of those five will decline. You are now re-running the process from a depleted field.

What should the process look like by level?

An engineering interview process should run 10 to 14 days for graduate roles, 14 to 21 days for mid-level roles at 3 to 10 years of experience, 21 to 28 days for senior and principal engineers, and no more than six weeks from first conversation to offer at director level. Every week beyond that loses 10 to 15 percent of the shortlist.

Graduate and early-career roles should not exceed two stages. A structured CV screen or phone screen, followed by a single interview combining technical questions with a culture and fit conversation. Some teams add a short written exercise or technical test, which is fine provided it takes under 90 minutes of candidate time and you review it within 48 hours. Total elapsed time: 10 to 14 days.

Mid-level roles (3-10 years’ experience) typically need two to three stages. An initial screen, a technical interview with the hiring manager or a lead engineer, and an offer. If a third stage is genuinely necessary, it should happen in the same week as the second. Do not schedule interviews two weeks apart. Total elapsed time: 14 to 21 days.

Senior and principal engineer roles can accommodate three to four stages, but the stages need to run fast. A screen, a technical deep-dive with a senior engineer or technical lead, a panel or stakeholder interview, and an offer. The key is compressing the calendar, not cutting the rigour. Offer approval should be pre-agreed before the final stage, not initiated after. Total elapsed time: 21 to 28 days, with 21 as the target.

Director-level engineering roles are the exception where a longer process is acceptable. But even here, six weeks from first conversation to offer is the outside limit. Above that, you are testing the candidate’s patience, not their suitability.

The five bottlenecks and how to fix them

The five bottlenecks that stall engineering hiring processes are panel availability, technical test design, internal alignment on requirements, slow offer approvals, and feedback delays beyond 48 hours. Pre-approving salary ranges before the process starts reduces offer approval time from 10 days to 24 hours and prevents the most common late-stage candidate loss.

Panel availability. The most common reason processes stall. Two or three stakeholders who cannot align calendars push a two-week process to six. The fix: agree interview dates before you open the role. Block time in diaries at the start of the process.

Technical test design. Companies send homework assignments with no clear criteria, no time limit, and no feedback mechanism. Candidates invest four hours, hear nothing for two weeks, and accept another offer. The fix: design tests that take under two hours, mark them within 48 hours, and tell candidates what you are assessing.

Internal alignment on requirements. The hiring manager wants one thing, the engineering director wants another, and the HR brief says something else entirely. The candidate sits in the middle while the business argues. The fix: align before you brief any recruiter or post any advert. One document, agreed by everyone who has a vote.

Slow offer approvals. The hiring manager wants to make an offer. Finance needs to sign off. HR needs to grade the role. Legal needs to review the contract template. Two weeks pass. The candidate has accepted elsewhere. The fix: pre-approve the salary range before the process starts. The offer approval should take 24 hours, not 10 days.

Feedback delays. Candidates who do not hear back within 48 hours after an interview assume rejection and move on emotionally, even if they are still technically in the process. The fix: commit to 48-hour feedback at every stage. This is not optional and it is not difficult.

What does a slow process really cost?

A slow engineering interview process costs the visible price of lost offers and restarted searches, plus the invisible reputational cost that takes 18 months to rebuild. Starting with 10 candidates and running a five-week process leaves five or six by offer stage, with at least one decline, forcing a restart from a depleted pool.

The visible cost is the wasted time, the lost offer, and the need to restart the search. The invisible cost is larger. Engineers talk to each other. Word travels that your process is disorganised, that you go quiet after interviews, that you do not make decisions. That reputation takes 18 months to fix and costs you candidates you will never know you lost.

The companies that attract and retain the best engineering talent are not necessarily the biggest employers or the highest payers. They are the ones who treat candidates with the same professionalism they would want for themselves, and who make decisions at pace.

For more on how we support engineering recruitment from brief to offer, including process design and candidate management, see how we work with engineering employers. For a broader view of the UK engineering market including current demand signals and salary benchmarks, that context is on our engineering sector page.

If your process is taking longer than it should, we can help. Talk to us about where the friction is and what a tighter brief looks like.