Author: fhai

How many interview rounds are enough?

Use as many interview rounds as it takes to test each must-have once, and no more. For most roles that means two to three rounds: a short screen, one structured interview, and for some roles a work sample or a conversation with future colleagues. Add a round only if it tests something new, and remove any round that repeats what you already know.

Key takeaways

Count rounds by what they test, not by tradition or seniority.
Two to three rounds suit most roles. Entry-level roles may need two. Senior roles may need three or four with different focus.
Every extra round costs candidate time, your team’s time and the risk of losing the candidate.
Do not add more rounds when your scores are clear. Doubt about a must-have is a reason to test it, not to repeat the same questions.
Tell candidates the number of rounds and the timeline at the start.

The cost of one more round

Each round has a cost that is easy to miss. For you, there are the hours of interview time, the preparation, the notes and the debrief. For the candidate, there is time off work, travel or preparation, and stress. For both sides, there is a delay of days or weeks. Candidates with other offers may accept elsewhere while you wait. The cost of a round is not a reason to skip a useful one. It is a reason to ask what it gives you.

You can estimate the internal cost with simple arithmetic. Multiply the number of interviewers by the hours per interview, add 30 minutes each for preparation and notes, and multiply by the number of candidates. Then compare it with the information you gain.

Item	Example (fictional)	Hours
Interview length	1 hour	1
Interviewers per round	3	3
Preparation and notes, per interviewer	30 minutes	1.5
Debrief	30 minutes, 3 people	1.5
Total per candidate, per round		7
Candidates in the round	4	28 hours

In this invented example, one extra round for four candidates costs 28 hours. That is almost a full work week of staff time. If the round adds no new information, the cost buys nothing. If the round tests a must-have that the earlier rounds could not, the cost may be worth it. Use your own numbers.

How to decide: five questions

Which must-haves are still untested? If every must-have has evidence from at least one method, you may be ready to decide.
Which stage would test the missing one best? Pick the shortest method that gives real evidence, such as a 30-minute task.
Is the evidence conflicting? If interviewers disagree on a must-have, add one targeted check, not a full round.
Who needs to meet the candidate? Include a future colleague if team fit in specific behaviours matters. Do not add a person only for status.
Would a candidate see this stage as fair? If you cannot explain why the stage exists, remove it.

Use the coverage matrix in our interview plan guide to check these questions on one page.

Guide by role type

These are planning suggestions based on common practice and logic, not research findings. Adjust them for your context.

Role type	Suggested rounds	What each round tests	Notes
Entry-level or high-volume	2	1. Short screen for availability and basics. 2. Structured interview with a short task	Keep total candidate time under two hours
Individual contributor, mid-level	2 to 3	1. Screen. 2. Structured interview. 3. Work sample or colleague meeting	Run the work sample only for finalists
Specialist or technical	3	1. Screen. 2. Technical interview or task. 3. Interview on collaboration and context	Use a task that mirrors real work, with a made-up case
People manager	3	1. Screen. 2. Structured interview on managing people. 3. Panel or case with the team	Include a skip-level or peer, but only for stated reasons
Senior leader	3 to 4	1. Screen. 2. Structured interview. 3. Case or presentation. 4. Meetings with peers and the person they report to	Pay for substantial case work; keep each meeting different

For senior roles, the extra round often adds meetings with stakeholders. Do these as conversations with a clear purpose, not a repeat interview. If the purpose is only “to get to know them”, reduce it to a short call.

Signs you have too many rounds

Sign	What it means	Action
Interviewers ask the same questions	Rounds repeat	Merge rounds or change the questions
Scores do not change between rounds	No new information	Remove the later round
Candidates drop out between rounds	The process is too slow or long	Shorten the timeline, combine rounds
The team adds interviews “to be safe”	Fear of a wrong decision, not evidence	Define the open question; add a targeted check only
The decision is made but you plan another meeting	The meeting is symbolic	Make the offer
Hiring takes much longer than your plan	Delays	See how long hiring should take

Signs you have too few rounds

You cannot name evidence for one or more must-haves.
Only one person met the candidate and that person is unsure.
The decision depends on a “feeling”.
The role carries high risk, such as handling money or safety, and you have not run proper checks.
Interviewers disagree strongly and there is no way to settle it.

In these cases, add the smallest step that addresses the gap: a work sample, a reference call, or a 30-minute conversation with a future colleague focused on one must-have.

Combine rather than add

You can often reduce rounds by combining them. Examples:

Screen plus first interview. For roles with few applicants, a 45-minute structured call replaces two shorter calls.
Interview plus task. Include a 20-minute task in the interview, such as editing a short text or planning a schedule.
Panel in place of three single interviews. One panel with a clear question allocation can replace several meetings. Brief the panel and keep it small. See our upcoming guide on panels.
One day, several short sessions. For finalists, hold three 30-minute sessions on a single day, each testing a different must-have.

Combining reduces elapsed time, which helps with candidates who have other offers. It should not reduce the quality of evidence. Use the same questions and scoring in the combined session as in separate ones.

Fairness across rounds

More rounds can raise the risk of unfairness. Each round gives more room for informal impressions, and each step can drop people for different reasons. Keep the process fair with these habits:

Define what passes each round, in writing, before you start.
Use the same questions and time for all candidates in a round.
Record the reason for each decision to move on or end the process.
Offer adjustments in every invitation.
Check that candidates who are dropped have an equal chance to explain, for example by a follow-up question on unclear points.
Review, where the law allows, whether certain groups drop out at a particular round more than others. If so, check the round for barriers, such as time, location or a task that favours certain backgrounds.

For the legal duties on adjustments and non-discrimination, see Acas, the EEOC and your national equality body. See also how to reduce bias in resume screening, which also applies to later rounds.

A worked example (fictional)

This example is invented. A team plans to hire a financial analyst and considers four rounds: a screen, a technical interview, a case study and a meeting with the director. The hiring manager draws the coverage matrix and finds that the director meeting repeats the technical interview. She replaces it with a 30-minute conversation about how the analyst would work with the director, and moves it into the case study session as the last 30 minutes. The process now has three rounds. The total candidate time falls from five hours to three. The plan is shared in the invitation. Two of five finalists mention in feedback that they liked knowing the whole process from the start.

What to tell candidates

The process for this role has [number] steps:
1. A 20-minute call on [week].
2. A 50-minute interview on [week].
3. A 45-minute task or a meeting with the team on [week].
We expect to make a decision by [date]. If you need any adjustment, please tell us and we will arrange it.

A clear outline lets candidates plan their time and shows that you respect it. If the plan changes, tell them promptly and explain why.

A round-by-round checklist

Before adding a round, confirm	Yes / No
A named must-have is untested or in doubt
The new round uses a different method or a different assessor
The questions or task are written, with a scoring guide
Candidates are told the purpose, length and date
An adjustment offer is included in the invitation
The extra time is acceptable to the candidate and the team
The decision date is still realistic

If you answer “no” to the first item, do not add the round. If you answer “no” to the others, fix the gap before you proceed.

How to handle a request for “just one more meeting”

Stakeholders often ask for an extra meeting near the end. This is a normal request, but it is a risk to the timeline and to fairness. Reply with questions, not with a refusal.

“Which must-have are you trying to check?” If there is none, suggest a short call instead.
“What would you do differently if the meeting goes well or badly?” If the answer is nothing, the meeting is not needed.
“Can we do this as the last 30 minutes of an existing round?” This keeps the elapsed time short.
“Will every finalist have the same meeting?” If not, the process is not equal. Offer it to all or to none.

If the meeting goes ahead, give the person the scorecard and the questions. Collect their input in writing before the debrief. This keeps the new voice in the same structure as the others.

Measure your own process

After each search, record the number of rounds, the total hours and the days from first contact to offer. Compare them across roles. If one type of role regularly needs four rounds and ends with a good hire, keep it. If the later rounds rarely change a decision, cut them next time. Your own data will tell you more than any general guide, including this one.

Keep the outcome of this review short and visible. A one-page note with the number of rounds, the hours spent and the reasons for any change is enough. Share it with the hiring team at the start of the next search, and use it to set the plan before candidates apply. Teams that review their process after each search tend to cut waste quickly, because they can see which steps added information and which did not.

Official sources for this topic: EEOC: employment tests and selection procedures, Acas: recruitment. These pages are maintained by the authorities and may change, so check them for the current text.

Frequently asked questions

How many interview rounds are normal?

Two or three for most roles. Roles with high risk or high seniority may need more. There is no ideal number, so count what each round tests.

Should the CEO or director always meet the candidate?

Only if they have a clear role in the decision or the person will work closely with them. Otherwise a short call may be enough.

Can I make a decision after one round?

Yes, if you have evidence on every must-have and the scores are clear. This is common for entry-level and urgent roles.

Do more rounds reduce the risk of a bad hire?

Not by themselves. Better evidence reduces risk. Repeating the same questions adds time but little information.

What if my team wants another interview?

Ask which must-have is still in doubt and what would settle it. Add the smallest check that does so.

Related guides

This is general information, not legal advice.

Join the waitlist

October 13, 2026

How to reduce time-to-hire without lowering quality

To reduce time-to-hire without lowering quality, find the stage where candidates wait longest, then remove the waiting rather than the checking. Set response-time agreements, schedule interviews in blocks, run steps in parallel, use written criteria so decisions are quick, and keep candidates informed. Never cut references, legal checks or structured scoring to save days.

Key takeaways

Measure the days between stages first. The longest gap is usually waiting, not work.
Cut waiting with agreements on response times, fixed interview blocks, and a named decision maker with a date.
Run steps in parallel where possible, for example references while the offer is prepared.
Keep the quality controls: written criteria, evidence, scorecards and legal checks.
Review the numbers after each search and fix one bottleneck at a time.

Speed and quality are not opposites

Most delays in hiring are not caused by careful work. They are caused by queues: a CV waits for a hiring manager, an interview waits for a free calendar, a decision waits for a second opinion. Careful work takes hours. Waiting takes days. If you remove the waiting, you speed up the process without touching the checks that protect quality.

The real risks to quality come from shortcuts: skipping the criteria, relying on gut feeling, or rushing the offer. A clear process lets you move faster because everyone knows what to do and when. See our guides on structured screening and the recruiter kickoff meeting for the foundations.

Step 1: Map your stages and measure the gaps

List every stage from role approval to start date. For your last five hires, record the date each stage began and ended. Calculate the days between them.

Stage	What to record	Questions to ask
Role approved to ad live	Dates	Is the brief ready? Who approves the ad?
Ad live to closing date	Dates	Is the ad period fixed? Are sources working?
Closing to shortlist	Dates	How long does screening take? Who reviews?
Shortlist to first interview	Dates	How long to schedule?
Last interview to decision	Dates	Who decides? Is there a meeting?
Decision to offer sent	Dates	Who writes the offer? Is pay approved?
Offer sent to accepted	Dates	Is the offer clear? Is there negotiation?
Accepted to start	Dates	What is the notice period?

Add up the gaps. In many processes, two or three of them hold most of the delay. Focus on those. If you do not have data yet, start recording it now. For definitions of the measures, see our upcoming guide on time-to-hire and time-to-fill.

Step 2: Remove the waiting

Agree response times in writing

Agree a service level with hiring managers: for example, review shortlisted CVs within two working days, give interview feedback within one working day, and decide within two working days of the last interview. Write it in the kickoff notes and track it. Our upcoming guide on recruitment SLAs gives a template.

Schedule in blocks

Ask hiring managers to reserve two or three interview blocks in advance, for example Tuesday and Thursday afternoons for three weeks. Invite candidates into those blocks. This replaces long email chains. Use a shared calendar link if you can, and give candidates a choice of at least three slots.

Run steps in parallel

Instead of	Do
Wait for all interviews, then start references	Ask finalists for referees at the final interview and start checks as soon as a preferred candidate is clear
Wait for the decision, then draft the offer	Prepare the offer letter and pay approval while interviews run
Screen all CVs at the end	Screen weekly so that early applicants move quickly
Book interviews one at a time	Offer the whole block to the shortlist at once

Name the decision maker and the date

Decisions slow down when no one owns them. At the kickoff, name the person who decides, the date and the evidence needed. Use a 30-minute debrief with scores submitted in advance. See how to run a debrief meeting.

Pre-approve the offer range

Agree the pay range and the offer terms before you start interviews. Waiting for an approval after the decision is a common source of a week or more of delay, and candidates may take another offer.

Step 3: Speed up screening safely

Use a screening sheet with yes, no and unclear for each must-have, and a CV passage for each yes. See screening at volume.
Screen in time-boxed sessions of 60 to 90 minutes. Take breaks.
Do a quick second review of a sample, not every application.
Send clear acknowledgements and outcome messages from templates.
Use tools that show evidence next to each requirement and leave the decision to people. Do not let tools auto-reject.

Faster screening should not mean less careful screening. The sheet, the evidence and the sample check keep quality high. Review our guide on how to reduce bias in resume screening if you worry that speed will add bias.

Step 4: Improve the candidate side of the clock

Candidates drop out when they wait. Reduce their waiting too.

Problem	Fix
No news after applying	Send an acknowledgement at once and a status update at set dates
Slow scheduling	Offer self-booking links with several slots
Unclear process	State the steps and the dates in the ad and the first message
Slow offer	Call the same day as the decision, send the letter within hours
Long notice periods	Ask early. Stay in touch during notice with short, useful messages

Keep the tone respectful. Do not pressure candidates with false deadlines. Speed is for the process, not a weapon against the candidate.

What not to cut

Control	Why it stays
Written must-haves	Fairness and quality; saves time later
Same questions for all candidates	Comparability; legal defence
Scorecards and notes	Evidence; decision quality
Legal checks such as right to work	Required by law
References for roles that need trust	Risk control
Feedback to candidates	Reputation and fairness

If someone proposes dropping one of these to meet a deadline, ask what risk they accept and who owns it. In most cases the saved time is small compared with the cost of a bad decision. For the cost side, see what a bad hire really costs.

A worked example (fictional)

This example is invented. A recruiter tracks five hires and finds these average gaps: 4 days from approval to ad live, 14 days of ad time, 5 days from closing to shortlist, 9 days from shortlist to first interview, 6 days from last interview to decision, 4 days from decision to offer. That is 42 days to an offer. She sees that waiting makes up most of 9 + 6 + 4 = 19 days. She introduces three changes: interview blocks booked in advance, a 30-minute debrief within two days after the last interview, and an offer range approved before the search. In the next search the gaps become 3, 14, 3, 3, 2 and 1 days: 26 days. The quality checks are unchanged. The hiring manager reports that the scorecards made the decision easier, not harder.

Your numbers will differ. The method is the same: measure, find the longest wait, remove it, and measure again.

Quality check after each change

To make sure speed does not hurt quality, track at least these four numbers: the share of hires that complete probation, the hiring manager’s rating of the hire at 90 days, the offer acceptance rate and the candidate experience rating. If any worsens after a change, review that change. Do not rely on one search. Look at several.

Measure	How to track	Warning sign
Probation completion	Share of hires who pass the review	Falls after a speed change
Manager rating at 90 days	Short form with a fixed scale	Lower than before
Offer acceptance	Offers accepted divided by offers made	Falls: offers may be unclear or slow
Candidate feedback	Two-question survey after the process	Complaints about rushing or silence

A 4-week improvement plan

Do not try to fix everything at once. Use four weeks, one focus per week.

Week 1: Measure. Collect dates for your last five hires. Calculate the gaps. Choose the two longest.
Week 2: Agree. Meet hiring managers. Present the two gaps and propose response times. Write them down and get a yes.
Week 3: Block and prepare. Book interview blocks for your next search. Pre-approve the offer range. Prepare templates for acknowledgement, invitation, hold and decline messages.
Week 4: Run and review. Use the changes on the next search. Track the new gaps. After the search, hold a 20-minute review with the hiring manager.

Share the result with the team: “Our average gap between the last interview and the decision fell from six days to two.” A concrete result makes it easier to keep the new habits and to ask for the next change.

Message templates that save time

Template	When to use	Key content
Acknowledgement	Within hours of the application	Thanks, closing date, next-step date
Invitation with slots	After screening	Three or more time options, length, format, adjustment offer
Hold	If a date slips	New date and reason
Decline with brief reason	After screening or interview	Clear result, thanks, one job-related reason for late-stage candidates
Offer call script	At decision	Terms, reply date, next steps

Store the templates in your email or tracking system. Review them twice a year. A good template cuts a five-minute task to a one-minute task. Across a hundred candidates that saves more than a day of work.

Using data without losing the human side

Track numbers to find bottlenecks, but do not turn people into numbers. A candidate who takes a week to reply may be changing jobs or caring for a family member. A hiring manager who delays feedback may be dealing with a customer crisis. When a gap is large, ask what caused it before you assign blame. The goal is to make the process work for people, so that speed comes from clarity and respect.

Where tools can help, and where they cannot

Software can speed up scheduling, reminders, tracking and the display of evidence. It cannot decide who fits the role. Choose tools that reduce waiting, such as self-booking links and status dashboards, and avoid any feature that ranks, scores or rejects people without a human decision. FastHire is being built on that principle: it shows each job requirement next to the exact CV passage that supports it, so a reviewer can check evidence quickly, while people make every decision. FastHire is coming soon.

Whatever you use, test it against your bottleneck list. If your delay is in decisions, a scheduling tool will not help. If your delay is in screening a large pile, a tool that shows the evidence for each requirement may help. Match the tool to the gap you measured, and review the numbers after three searches.

Start small. Pick one search, record the dates and discuss the result with the hiring manager this week.

Official sources for this topic: ICO: recruitment and selection, EEOC: small business guidance. These pages are maintained by the authorities and may change, so check them for the current text.

Frequently asked questions

What is a good time-to-hire?

It depends on the role, market and country. Compare with your own past hires first. Sources that publish averages define the measure differently, so check the definition before you compare.

Can I shorten the process without losing quality?

Yes, by removing waiting between steps, not by cutting criteria, scoring or legal checks.

What is the biggest cause of delay?

Usually scheduling and waiting for decisions. Measure the gaps to find yours.

Should I use software to speed up hiring?

Tools can help with scheduling, tracking and showing evidence. People should make the decisions. Check the data protection and AI rules in your country.

How do I get hiring managers to respond faster?

Agree response times at the kickoff, share a weekly status report and show the cost of delays in lost candidates.

Related guides

This is general information, not legal advice.

Join the waitlist

October 13, 2026

Time-to-hire vs time-to-fill: definitions and how to measure

Time-to-fill and time-to-hire both measure speed, but they start the clock at different points. In common usage, time-to-fill runs from when a job requisition is approved or the job is opened until the offer is accepted. Time-to-hire runs from when a specific candidate enters your process, usually the application or first contact, until that same candidate accepts. Definitions vary between companies, so write yours down.

Key takeaways

Time-to-fill measures how long a role is open. Time-to-hire measures how long a candidate takes to move through your process.
Definitions are not universal. State the start and end events in writing and use them every time.
Use the median as well as the average, because a few very long searches distort an average.
Track the gap between stages, not only the total. The gaps show where to act.
Do not compare your numbers with published benchmarks unless the definitions match exactly.

The two measures side by side

Measure	Common start event	Common end event	What it tells you	Who it helps
Time-to-fill	Requisition approved or job opened	Offer accepted (some use the start date)	How long the business waits for the role to be filled	Finance and operations leaders planning cover
Time-to-hire	Candidate applies or is first contacted	Same candidate accepts the offer	How fast your process moves a candidate	Recruiters improving the candidate journey
Time-to-start	Offer accepted	First day of work	How long notice and onboarding prep take	Hiring managers planning the work

These are common conventions, not official standards. Some teams count time-to-fill to the start date. Others count time-to-hire from the first interview. Pick one definition per measure and write it at the top of every report. When you read a number from another source, check how it was defined.

Why the difference matters

Time-to-fill includes the days before you speak to anyone: waiting for approval, writing the ad, choosing channels. If time-to-fill is long but time-to-hire is short, your problem is probably at the start, such as slow approvals or weak sourcing. If time-to-hire is long, the delay is in your process: screening, scheduling and decisions. Different problems need different fixes. See how to reduce time-to-hire without lowering quality for the fixes.

Pattern you see	Likely cause	Where to look
Long time-to-fill, short time-to-hire	Slow approval, late ad, thin sourcing	Kickoff, approvals, channels. See sourcing
Short time-to-fill, long time-to-hire	Good pipeline, slow process	Screening, scheduling, decisions
Both long	Both problems, or a very scarce skill	Start with the largest stage gap
Both short, but poor quality of hire	Rushed decisions	Check criteria, scorecards and reference steps

How to measure, step by step

Step 1: Write definitions

Create a one-page glossary: the name of each measure, the start event, the end event, the source of each date and who owns the data. Example: “Time-to-hire: days from the candidate’s application date in the tracking system to the date the candidate’s acceptance is recorded.”

Step 2: Capture the dates

For every role and candidate who reaches the offer, record these dates: requisition approved, job posted, application received, first screen, first interview, final interview, offer sent, offer accepted, start date. Use one sheet or your tracking system. Make the dates mandatory.

Step 3: Calculate

In a spreadsheet, use simple subtraction. If the offer accepted date is in column H and the application date is in column C, time-to-hire in days is H minus C. If the requisition date is in column B, time-to-fill is H minus B.

Column	Content	Example formula
A	Candidate or role ID
B	Requisition approved date
C	Application date
H	Offer accepted date
I	Time-to-fill (days)	=H2-B2
J	Time-to-hire (days)	=H2-C2
K	Time-to-start (days)	=Start date minus H2

Step 4: Summarise with the median and the spread

The average adds all values and divides by the count. One search that took 200 days will pull the average up. The median is the middle value when you sort the numbers, and it ignores extreme cases. Report both, plus the range. In a spreadsheet use AVERAGE and MEDIAN. A short report might read: “Time-to-fill: median 38 days, average 46 days, range 21 to 98 days across 12 roles.”

Step 5: Break it down by stage

Calculate the days between each pair of stages. The stage gaps show the bottleneck. Use a table like the one in the article on reducing time-to-hire.

A worked example (fictional)

This example is invented. A recruiter tracks one role. The requisition is approved on 1 March. The job is posted on 8 March. The chosen candidate applies on 12 March, has a screen on 20 March, an interview on 27 March, a final interview on 3 April, receives an offer on 8 April and accepts on 11 April. The candidate starts on 13 May.

Measure	Calculation	Result
Time-to-fill	1 March to 11 April	41 days
Time-to-hire	12 March to 11 April	30 days
Time-to-start	11 April to 13 May	32 days
Posting delay	1 March to 8 March	7 days
Application to screen	12 March to 20 March	8 days
Final interview to offer	3 April to 8 April	5 days

The recruiter sees that 7 days passed between approval and posting. That is 17 percent of the time-to-fill (7 divided by 41). The posting delay is the first problem to solve. The 8 days between application and screen is the second one. These facts guide the next change.

Common mistakes

Mistake	Effect	Fix
Mixing definitions between teams	Numbers cannot be compared	Publish the glossary
Counting only successful hires	Hides roles that failed or were cancelled	Track cancelled and open roles separately
Using only the average	Outliers mislead	Report the median too
Recording dates from memory	Errors	Use system timestamps or a shared sheet
Comparing with a benchmark that uses another definition	Wrong conclusion	Check the source definition first
Optimising for speed alone	Lower quality	Track quality measures too. See metrics

Which numbers to share with the business

Finance and operations leaders care about time-to-fill because it shows how long a seat stays empty. Hiring managers care about time-to-hire and time-to-start because they plan their work around them. Candidates care about the time between steps. Choose the right measure for the audience. A one-page report with one number per measure, the median, and one chart of stage gaps is enough. Add one sentence on what you will change.

Be careful with named benchmarks. Published figures about average hiring times come from different sources and use different definitions. If you quote one, link to the source, state the definition, and check that the sample matches your market and role. Otherwise, compare your numbers with your own past searches.

Data protection notes

The dates and outcomes you record relate to identifiable people, so data protection rules apply. In the UK and EU, the GDPR requires a lawful basis, limits on how long you keep data and transparency. See the ICO employment guidance. For reporting, use aggregated numbers without names. Keep individual records only as long as you need them. This is general information, not legal advice.

Median versus average: a small example (fictional)

Suppose five searches took 30, 32, 35, 38 and 120 days to fill. The average is (30 + 32 + 35 + 38 + 120) divided by 5, which is 51 days. The median is the middle value after sorting, which is 35 days. The one long search of 120 days pulls the average far above what happens in a typical search. If you only report 51 days, hiring managers may think the process is slow in general. If you report both numbers and explain the 120-day case, they see the real picture: a typical search takes about five weeks, and one search had a special problem.

Look into the outlier. Was the skill scarce? Did the approval stall? Did the hiring manager go on leave? Write a one-line reason beside each long search. Over time these notes show which causes repeat and which are one-offs.

A simple report layout

Section	Content	Chart or table
Headline numbers	Median and average time-to-fill and time-to-hire, number of hires, period covered	Four numbers at the top
Stage gaps	Median days between stages	Bar chart
By role family	Compare similar roles only	Small table
Open roles	Days open so far for roles not yet filled	List
Notes	One line per outlier	Text
Next action	One change to test	One sentence

Keep the report to one page. Share it monthly or after each search. If your team uses a tracking system, check that the reports use your written definitions. Many systems have default definitions that differ from yours.

Linking speed to quality

A fast number can hide a poor hire. Pair the time measures with at least one quality measure, such as the hiring manager’s rating at 90 days or the share of hires who complete probation. If time falls and quality falls too, the process is rushing. If time falls and quality holds, the changes are working. Define how you will rate quality before you change the process, so that you do not choose the measure afterwards to fit the result.

How to talk about the numbers with hiring managers

Start with the role they care about: “Your last role took 41 days to fill.”
Show the stage gaps, not blame: “Seven days passed before the ad went live, and eight days between application and screen.”
Ask what they see: “What made these steps slow from your side?”
Agree one change and a date to review.
Share the result after the next search.

This conversation works best when it is about the shared goal of getting the right person in the seat, not about who was slow.

Setting up the sheet in 20 minutes

Create a new sheet with one row per hire and the columns from the table above.
Format the date columns as dates, not text, so that subtraction works.
Add the formulas for time-to-fill, time-to-hire and time-to-start in the first row, then copy them down.
Add a second sheet for the summary, with MEDIAN and AVERAGE formulas for each column.
Add a column for “reason for delay” and fill it in for any role that took longer than the median by more than 10 days.
Protect the formula cells so that nobody types over them.

If a date is missing, the formula will show an error or a wrong number. Use a filter to find blank cells before you report. Fix missing dates at the source, so that the next search is complete from the start. A reliable sheet with five rows is more useful than a large sheet with gaps. Update it on the day each event happens, not at the end of the month, so that the dates are accurate.

Review the definitions once a year. If the business changes how it approves roles or how candidates enter the process, update the start events and note the date of the change in the glossary. A short change log lets anyone read an old report and understand which definition it used. This habit also prevents arguments in meetings, because everyone can see the rule behind the number.

Official sources for this topic: Acas: recruitment, Your Europe: human resources. These pages are maintained by the authorities and may change, so check them for the current text.

Frequently asked questions

What is the difference between time-to-hire and time-to-fill?

Time-to-fill starts when the role opens, or the requisition is approved. Time-to-hire starts when a candidate enters the process. Both usually end when the offer is accepted, but definitions vary.

Which measure is better?

Neither is better. They answer different questions. Use time-to-fill for business planning and time-to-hire for process improvement.

Should I include the notice period?

Track it as time-to-start. It is not under your control, but it affects planning.

How many hires do I need to get a useful number?

Even five searches show patterns. With fewer, look at the stage gaps rather than the totals.

How do I handle roles that were cancelled?

Record them separately with the date and reason. Do not mix them with filled roles.

Related guides

This is general information, not legal advice.

Join the waitlist

October 13, 2026

How to write a candidate update email cadence

Update candidates at every point where their status changes, and at least once a week when nothing changes during an active process. A good cadence has seven messages: acknowledgement, screening outcome, interview invitation, post-interview status, decision, offer or decline, and a final close-out. State the next date in every message, and send it on that date or earlier.

Key takeaways

Send a message whenever the status changes, and every five to seven days when it does not.
Put the next update date in each message, and keep it.
Use templates for speed and personal details for warmth.
Send a clear outcome to every candidate, including those who are declined early.
Track messages in your tracking system so that no one falls through the gap.

Why cadence matters

Candidates cannot see your process. They only see messages and silence. When there is silence, they guess: the role is filled, they were rejected or the company is disorganised. Regular short updates remove the guessing, even if the news is “no change yet”. They also reduce the number of status emails you receive, which saves your time.

A cadence is a plan for when you write, not a promise to share every detail. You decide the points in advance, and you tie them to dates. This is part of the candidate experience described in our candidate experience checklist.

The seven-message cadence

No.	Message	When to send	What to include
1	Acknowledgement	Within minutes or hours of the application	Thanks, closing date, next update date, how to ask for adjustments
2	Screening outcome	Within 2 working days of the screening date	Invite to the next step, hold or decline
3	Interview invitation	Same day as the decision to invite	Dates, format, people, length, preparation, adjustments
4	Post-interview status	Same or next day after the interview	Thanks, the date by which you will reply
5	Decision	On or before the promised date	Next step, offer, or decline with reasons for finalists
6	Offer or close-out	Same day as the decision	Call first for offers, then letter. For declines, a kind message
7	Final close-out	When the role is filled	Tell all remaining candidates that the role is filled; ask for consent to keep their details

This cadence fits most processes. Add a message if your process has extra steps such as a work sample or a panel. See how to give fast interview feedback for message wording after interviews.

The “no news” update

When nothing has changed, a short message still helps. Send it every five to seven days to candidates who are in the middle of a process. Do not send it to candidates who have received a clear outcome. A “no news” update has three parts: what is happening, what the candidate does not need to do, and the next date.

Hello [Name],

A short update on your application for [job title]. We are still [finishing the interviews / waiting for a decision]. There is nothing you need to do. We expect to contact you by [date]. If your situation changes, for example if you receive another offer, please let us know so that we can plan.

Best wishes,
[Name]

Do not add false urgency, and do not hint at an offer that you have not decided to make. Honest, calm updates build trust.

Template library

1. Acknowledgement

Hello [Name],

Thank you for applying for [job title]. We have your application. Applications close on [date]. We will contact everyone by [date] with a clear next step. If you need any adjustment to our process, please reply to this message.

Best wishes,
[Name]

2. Invitation to a screening call

Hello [Name],

Thank you for your application. We would like to arrange a 20-minute call to talk about the role. These times are available: [list]. Please reply with the time that suits you. The call will be by [phone/video]. If you would like any adjustment, tell us and we will arrange it.

Best wishes,
[Name]

3. Decline after screening

Hello [Name],

Thank you for your interest in [job title]. We reviewed your application against the requirements for the role. We will not move forward at this stage. We appreciate your time and wish you well in your search.

Best wishes,
[Name]

4. Post-interview thanks and date

Hello [Name],

Thank you for meeting us today. We enjoyed hearing about [specific point]. We are speaking to other candidates this week, and we will contact you by [date] with a decision.

Best wishes,
[Name]

5. Role filled

Hello [Name],

Thank you for your interest in [job title]. The role has now been filled. We valued your time and your application. If you would like us to keep your details for future roles, please reply “yes” and we will keep them for [period] and then delete them.

Best wishes,
[Name]

How to schedule and track

Add a “next update due” date for every active candidate in your tracking sheet or system.
Sort by date each morning. Send what is due.
Use mail merge or system templates for acknowledgement and decline messages, and personalise the first line.
Record the date and type of each message.
Review the sheet each Friday for candidates who have not heard from you in five days.

If you use an applicant tracking system, check whether it can set reminders and send templates. Keep control of the content. A human should approve declines for finalists. If you use automation, tell candidates that a status message is automatic and give a way to reach a person.

Common mistakes

Mistake	Effect	Fix
Updating only when there is good news	Candidates assume the worst	Send “no news” updates
Promising a date and missing it	Loss of trust	Promise only what you can keep; if you miss it, say so with a new date
Using the same wording for everyone, including finalists	Feels cold	Personalise finalists
Not telling candidates when the role is filled	Candidates wait for weeks	Send a close-out message
Including protected-trait comments	Legal risk	Keep to job-related facts
Sending messages at odd hours	Pressure	Schedule for working hours

A worked example (fictional)

This example is invented. A recruiter runs a search for a project manager. On Monday she posts the job and sets the closing date for the 21st. Every applicant receives message 1 within an hour. On the 22nd she screens and sends outcomes on the 23rd: 12 invitations and 38 declines. On the 24th and 25th she runs 12 calls. On the 26th she sends interview invitations to five people and declines to seven, each with a short reason for those who had a call. Interviews run on the 29th and 30th. After each interview she sends message 4 with the date of 3 November. On 2 November, with a day to spare, she sends a “no news” update to two people still waiting on a second round. On 3 November she calls the chosen candidate and sends the offer. She sends decline messages to the other four finalists the same day, with two specific reasons each. On 5 November the candidate accepts, and she sends message 5 to the remaining candidates. Total time spent on messages: about three hours across the search, because she used templates.

Data protection notes

Messages to candidates contain personal data. Keep them in your tracking system or a secure folder, delete them when no longer needed, and do not send sensitive information by unsecured channels. In the UK and EU, tell candidates how you use their data in your privacy notice. See the ICO employment guidance. If you keep candidate details for future roles, get consent and say how long you will keep them. This is general information, not legal advice.

Adjusting the cadence to your volume

The same plan does not fit every volume. Adapt it to the number of candidates and the time you have.

Volume	Approach	Notes
Under 20 applicants	Personal messages for every stage	Easy to keep warm; use templates for speed
20 to 100 applicants	Templates with a personal first line for finalists	Use mail merge in your email or tracking system
100 to 500 applicants	Automatic acknowledgement and outcome messages; personal messages for interviewed candidates only	Review the automatic text carefully. Include a way to reach a person
More than 500 applicants	Automated status page or messages for early stages; personal contact for shortlisted candidates	Plan the screening process first. See screening at volume

For high volume, set expectations in the ad: “Due to the number of applications, we will contact only those selected for an interview” is an honest sentence, but a better one is “We will send every applicant an outcome by [date]”. If you can send an outcome to all, do so. A short, courteous automatic message is better than nothing.

What to do when your timeline changes

Timelines slip. A manager gets ill, a decision waits for approval, an interview must be moved. When this happens, tell the candidates at once. Use three elements: what changed, the new date and a thanks for patience. Do not hide a delay until the date has passed. If the new date is unknown, say when you will next write, for example “We will write again on Friday with an update”. People accept delays when they are told in time.

Candidates who write to you

Some candidates will write to ask for news, even with a good cadence. Reply within one working day with the facts you have. If there is nothing new, say so and repeat the next date. Do not ignore the message, and do not give hints about internal discussions. Keep a log of questions you receive. If the same question appears many times, add the answer to your ad or to your acknowledgement message.

Review the cadence after each search

How many status enquiries did you receive? Fewer is better.
Did you miss any promised dates? Why?
Which messages did candidates mention positively in the survey?
Which step still leaves people without news?
What one change will you make for the next search?

Keep these notes with the role brief. After three searches you will have a cadence that fits your team, and it will be faster to run each time.

Ownership and backup

Name one person who owns the cadence and one person who covers when the owner is away. A cadence that depends on a single person fails during holidays and sick leave. Put the plan, the templates and the tracking sheet in a shared place, and give the backup person access. Agree what the backup does: check the “next update due” column each day and send what is due. This small step protects the promises you made to candidates and prevents silent gaps.

If you work with an agency or an outside recruiter, include the cadence in the briefing. Ask them to follow your dates and your tone, and to report the status of each candidate weekly. You remain responsible for the experience, even when someone else sends the messages.

Official sources for this topic: ICO: recruitment and selection, Acas: recruitment. These pages are maintained by the authorities and may change, so check them for the current text.

Frequently asked questions

How often should recruiters update candidates?

At each change of status, and every five to seven days during an active process even if there is no news.

What if I have no news?

Send a short message saying so, with the next update date. Silence is worse than “no news”.

Do I need to tell every applicant when the role is filled?

It is good practice. A short message ends the wait and keeps goodwill.

Can I automate updates?

Acknowledgements and status messages can be automatic. Tell candidates that they are automatic. People should write and send decisions about finalists.

What should a decline message include?

A clear result, thanks, and for later-stage candidates one or two job-related reasons. Avoid protected traits and comparisons.

Related guides

This is general information, not legal advice.

Join the waitlist

October 13, 2026

How to hire your first developer when you are not technical

To hire your first developer when you are not technical, define the problem and the outcome in plain words, choose the engagement type (employee, freelancer, agency or advisor-led), ask a trusted technical person to review the evidence, test with a small paid task, and set up ownership of code, accounts and data in writing from day one. You do not need to read code to judge communication, reliability and results.

Key takeaways

Describe what the product must do for users, not which technology to use. Let the developer propose the technology.
Pick the engagement type that fits the stage: freelancer for a defined build, employee for ongoing work, advisor for review.
Use a technical reviewer, even for a few hours, to check evidence you cannot judge.
Test with a small paid task and a short plan. Judge communication as well as code.
Own your accounts: repository, hosting, domains and data must be in your name.

What is different when you are not technical

A technical founder can read code and ask sharp questions. A non-technical founder has three risks: not knowing if the work is good, not knowing if the price is fair and not knowing if the developer is honest about time. You can lower all three with a clear brief, a reviewer and small steps with checkpoints.

You can judge more than you think. You can judge whether the developer asks good questions, explains in plain words, delivers on small promises, shows progress in working software and respects your budget and deadlines. These are strong signals of a good hire. A technical reviewer can then check quality in a few hours.

Step 1: Define the problem, not the technology

Write a one-page brief. Use the structure from the one-page role brief.

Part	Question	Example (fictional)
Users	Who will use it?	Clinic receptionists booking appointments
Problem	What is hard today?	Double bookings and phone calls take three hours a day
Outcome	What should be true in 3 months?	Booking page live; double bookings fall; receptionists use it daily
Must-haves	What must the first version do?	Show free slots; confirm by email; let staff edit bookings
Not now	What can wait?	Payments, mobile app, reports
Constraints	Budget, deadline, rules	Fixed budget; must handle personal data lawfully
Success measure	How will you know?	Number of bookings made online; fewer phone calls

A good developer will ask questions about this brief and may suggest changes. That is a positive sign. A developer who agrees with everything without questions is a warning.

Step 2: Choose the engagement type

Option	Fits when	Pros	Cons
Employee (full or part-time)	You have ongoing work and a roadmap for a year or more	Deep knowledge of your product; stable	Cost, notice and management time; hiring risk
Freelancer	A defined build or a set of features	Flexible; no long commitment	Availability; knowledge leaves when they leave; status rules apply
Agency or studio	You need a team (design, development, testing) for a project	Broad skills, process	Higher day rates; less control; handover risk
Technical co-founder or partner	Product is core to the business and you want shared ownership	Shared risk and commitment	Equity, legal and relationship complexity; take advice
Advisor plus junior developer	You want review by someone senior at low cost	Quality check at modest cost	Needs coordination

If you choose a freelancer, check the status rules in employee or contractor. If you choose an employee, use the cost worksheet to plan the full cost.

Step 3: Find a technical reviewer

A reviewer is a senior developer or technical lead who is not applying for the job. They can be a friend, a former colleague, a mentor or a paid consultant for a few hours. Ask them to do three things: read the brief and say if it is realistic, review the candidate’s past work or a test result, and join one interview to ask technical questions. Pay them a fair fee, and tell them that they are not responsible for the hiring decision. Give them the same scoring sheet as other interviewers.

Step 4: Write the ad and screen

Describe the product, the outcome, the stack only if you already have one, the working style, the hours and the pay range. Do not list every technology you have heard of. Pick three to five must-haves such as “has built and launched a web application used by real users” and “writes clear documentation”. See how to write a job ad that attracts the right applicants.

For screening, use evidence from the CV and links: live products, public code, a portfolio or a description of a past project with the candidate’s role. Ask the technical reviewer to look at a sample. Use a screening sheet. See structured screening.

Step 5: Interview with questions you can judge

Area	Question	What to listen for
Past work	Tell me about a product you built that real users used. What was your part?	Clear role, real users, honest account of problems
Communication	Explain to me, as if I am not technical, how you would build the booking page.	Plain words, steps, no jargon wall
Estimation	How would you estimate the time? What could make it slower?	Ranges, risks, questions
Trade-offs	What would you leave out of the first version, and why?	Focus, judgement
Quality	How do you test your work? How do you handle bugs?	A real method, such as tests and reviews
Collaboration	Tell me about a disagreement with a client or manager. How did it end?	Respect, facts
Maintenance	What happens after launch? Who fixes problems?	Awareness of ongoing work

Ask your reviewer to add three or four technical questions that they score on the same scale. Do not ask about protected characteristics. See what you can and cannot ask.

Step 6: Test with a small paid task

A small paid task reduces risk for both sides. Choose a task that takes four to eight hours, uses a made-up or non-sensitive problem, and has a clear outcome, such as “build a simple page that lists free slots from a data file and write a short README”. Pay a fair rate for the time, and tell the candidate how you will score: working result, clarity of explanation, code organisation as judged by your reviewer, and communication during the task. See how to assess skills with a work sample test for rules on pay and fairness.

Step 7: Set up ownership and security

Before work starts, put these in writing. This protects you and the developer.

Item	What to agree
Ownership of the work	Who owns the code and the designs. Employees often create work that belongs to the employer by default in many countries, but not everywhere. Freelancers usually need a written assignment or licence. Take legal advice for your country
Accounts	Repository, hosting, domain, app store accounts and analytics are created in your name or company name. The developer is added as a user
Access	Give the minimum access needed. Use separate logins, not shared passwords. Remove access when the work ends
Data protection	If the product handles personal data, agree the rules. In the UK and EU, GDPR applies. Check the ICO guidance and your national authority
Documentation	A README, set-up notes and a list of services used
Payment and milestones	Fee, milestones, review points and what counts as done
Ending	Notice, handover and return of access

This is general information, not legal advice. A short review by a lawyer is worth the cost for a contract that covers your core product.

Red flags and green flags

Red flag	Why it matters
Refuses to explain in plain words	You cannot manage what you do not understand
Promises very fast delivery for a low price without asking questions	Likely to miss scope
Wants all accounts in their own name	You could lose control
No examples of finished products	Cannot judge experience
Avoids a paid test but asks for full payment up front	Risk for you
Blames former clients for every problem	Pattern risk

Green flag	Why it matters
Asks many questions about users and goals	Cares about the outcome
Proposes a smaller first version	Understands risk
Shows working software early and often	Visible progress
Documents decisions	Reduces dependence on one person
Admits what they do not know	Honest

A worked example (fictional)

This example is invented. A non-technical founder of a small tutoring company needs a booking tool. She writes a one-page brief, asks a former colleague who is a senior developer to act as reviewer for four hours, and posts the ad. She screens eight applicants with a sheet and interviews four with the same questions. Two do a six-hour paid task. The reviewer says both solutions work, and one is better organised. The founder’s own scoring shows that one candidate sent a progress note after three hours and explained a choice clearly. The other sent nothing until the end. She hires the first as a part-time freelancer for three months with an assignment of the work in writing, accounts in the company name and two-weekly demos. At the three-month review, the booking tool is live and used by teachers. She then decides whether to extend or hire a part-time employee.

Your first 90 days with the developer

Period	Focus	Your actions
Days 1 to 14	Set up accounts, agree the first milestone	Share brief; give access; schedule demo every two weeks
Days 15 to 45	First version in test	Try it as a user; write down what is confusing; keep scope small
Days 46 to 90	Launch and learn	Release to a few users; track the success measure; decide next steps

Review progress with your technical reviewer once a month for the first quarter. Keep a log of decisions and changes. This record helps you if the developer leaves and a new person starts.

Questions to ask your technical reviewer

Stage	Question for the reviewer
Before the ad	Is the brief realistic for the budget and time? What is missing?
Screening	Which of these portfolios show real, working products? Which look copied or thin?
After the paid task	Is the code organised and readable? Are there tests? Could another developer take it over?
Before the offer	Did the candidate answer your technical questions with sound reasoning? Any concerns?
After three months	Is the product maintainable? What are the largest risks?

Ask for short written answers. Keep them with your decision record. Remember that the reviewer’s view is one input and that you decide.

What it may cost, and how to check

Rates for developers vary by country, skill and type of work. Do not rely on a single number from the internet. Ask for quotes from at least three people for the same written brief, and compare how they break down the work. A big difference between quotes often means the brief was understood differently, so ask each person to explain their assumptions. For employee costs, add employer taxes and contributions using the official sources for your country. See the cost of hiring an employee.

Official sources for this topic: GOV.UK: employing people, US Small Business Administration: hire and manage employees. These pages are maintained by the authorities and may change, so check them for the current text.

Frequently asked questions

Do I need a technical co-founder?

Not always. Many non-technical founders work with freelancers, agencies or employees and a technical reviewer. A co-founder involves equity and a long-term relationship, so decide carefully.

How do I know if the code is good?

Ask a trusted technical reviewer to check a sample. Also judge outcomes: working software, fewer bugs, clear documentation.

Should I hire a freelancer or an agency?

A freelancer suits a defined, small build. An agency suits a project that needs several skills. Compare cost, control and handover.

Who should own the code?

You or your company, by written agreement. Take legal advice for your country, especially for freelancers.

How much should I pay?

Compare local market sources and quotes for similar work. Do not accept the lowest or highest quote without a reason. Use the cost worksheet.

Related guides

This is general information, not legal advice.

Join the waitlist

October 13, 2026

Interview questions for managers: a bank for leadership hires

To interview for a manager role, choose four to six management competencies the job needs, such as setting direction, hiring and developing people, giving feedback, managing performance, working across teams and making decisions. Ask each candidate for specific past examples and, for a few questions, a realistic scenario. Score the answers on a written scale and check claims with references.

Key takeaways

Define what the manager must achieve through other people before you write questions.
Ask about real situations: what the candidate did, what the team did and what changed.
Include scenario questions to test judgement on situations the candidate has not seen.
Probe for results through others: team outcomes, development of people, retention of skilled staff.
Score on a scale, record evidence and check with references from people who reported to the candidate.

What makes a manager role different

Individual contributors are judged by their own output. Managers are judged by what their team delivers, how people develop and how the team works with others. A strong individual contributor may be a weak manager, and the reverse can be true. Questions about technical skill alone will not show management ability. Questions about leadership style in general terms, such as “what kind of manager are you?”, produce well-rehearsed answers. Ask for evidence.

Use a structured approach: the same questions for each candidate, a scoring guide and a debrief. See structured interviews, behavioural interview questions and the interview scorecard.

Step 1: Choose the competencies

Competency	What it means in practice	Weight for your role (low, medium, high)
Setting direction	Turns goals into clear priorities and tasks for the team
Hiring and building a team	Defines roles, interviews fairly, onboards well
Developing people	Coaches, delegates, gives growth opportunities
Feedback and performance	Gives clear feedback; handles poor performance fairly and early
Decision making	Gathers evidence, decides, explains reasons
Working across teams	Builds relationships, resolves conflicts, aligns work
Managing resources	Plans budget, time and workload
Change and resilience	Leads the team through uncertainty
Inclusion and fairness	Treats people equally, adjusts for needs, follows the law

Pick four to six that matter most for this job. Ask your own manager and the team members who will report to the new manager what they need most. Link the competencies to outcomes, for example “the team meets its delivery goals with less rework”. Use the one-page role brief.

Step 2: The question bank

Setting direction and priorities

Question	Follow-up probes	Strong answer shows
Tell me about a time you had to set priorities for your team with limited resources.	What did you drop? How did you explain it?	Clear criteria, communication, effect on results
Describe a goal you set for your team. How did you check progress?	What changed? What did you do when progress stalled?	Measures, regular reviews, adaptation
Tell me about a plan that failed. What did you learn?	What did you change afterwards?	Ownership and learning

Hiring and building a team

Question	Follow-up probes	Strong answer shows
Tell me about the last person you hired. How did you decide?	What criteria? What evidence? What did you do differently from before?	Written criteria, structured process, evidence
How have you helped a new team member succeed in the first 90 days?	What support? What was the result?	Plan, regular check-ins, outcomes
Describe a time you changed your hiring process.	Why? What was the result?	Learning, fairness, measurement

Developing people

Question	Follow-up probes	Strong answer shows
Tell me about someone you helped grow. What did you do?	What did they do? What happened to their career?	Specific coaching actions, shared credit
How do you decide what to delegate?	Give an example where it went well or badly.	Judgement, support, accountability
Tell me about a time a team member disagreed with you. What did you do?	Did you change your view?	Listening, openness, clear decision

Feedback and performance

Question	Follow-up probes	Strong answer shows
Tell me about a time you had to give difficult feedback.	How did you prepare? What did the person say? What happened next?	Specific, respectful, follows up
Describe a time a team member was not meeting expectations. What did you do?	How early did you act? How did you document it? What was the result?	Early action, clear standards, fair process, support, outcome
How do you recognise strong work?	Give an example.	Specific, timely, fair

Decisions, conflict and working across teams

Question	Follow-up probes	Strong answer shows
Tell me about a decision you made with incomplete information.	What did you do to reduce risk? What happened?	Evidence, options, reasons, review
Describe a conflict between two teams. What was your role?	What did you do to resolve it?	Facts, listening, agreement, follow-up
Tell me about a time you disagreed with your own manager.	How did you raise it?	Respect, evidence, professionalism

Fairness and inclusion

Question	Follow-up probes	Strong answer shows
Tell me about a time you adjusted how you managed to meet a team member’s needs.	What was the need? What did you change?	Flexibility, fairness, legal awareness
How do you make sure everyone on your team has an equal chance to contribute?	Give an example.	Concrete practices, not slogans
Describe a time you spotted unfair treatment in your team. What did you do?	What was the result?	Courage, process, escalation when needed

Do not ask about family plans, health, age, religion or other protected traits. See what you can and cannot ask.

Step 3: Scenario questions

Scenarios test judgement. Describe a realistic situation and ask what the candidate would do first, what they would check, and why. Use a made-up case.

Scenario (fictional)	What to listen for
Two senior team members refuse to work together on a key project. The deadline is in three weeks. What do you do in the first week?	Facts first, individual talks, shared goal, clear roles, follow-up, escalation if needed
A strong performer repeatedly misses team meetings. Others are starting to complain. What do you do?	Curiosity before judgement, a direct conversation, clear expectations, support, fairness
You inherit a team with low morale and high turnover. What do you do in your first 30 days?	Listening, data, quick wins, no blame, a plan with the team
Your budget is cut by 10 percent. How do you decide what to change?	Priorities, communication, fairness, impact on people

Do not expect a perfect answer. Look for structure, questions asked, awareness of people impact and a clear first step. Score on the same scale as the other questions.

Step 4: Scoring guide

Score	Meaning	Example for “gives difficult feedback”
1	No evidence or poor	Could not give an example, or described avoiding the conversation
2	Some evidence, gaps	Gave an example but did not follow up or explain the result
3	Good evidence	Clear preparation, direct conversation, follow-up, improved result
4	Strong evidence	All of 3, plus changed a team practice or coached other managers to do the same

Score each competency separately, and write the evidence. Do not let one strong answer cover weak ones. Compare candidates by competency in the debrief. See how to run a debrief meeting.

Step 5: Check with the right references

For a manager, ask for references from people who reported to them, as well as peers and their own manager. With permission, ask:

What was it like to work for this person? Give an example of how they helped you or the team.
How did they handle disagreement, pressure and mistakes?
How did they give feedback? Was it fair and clear?
What would you want a new team to know about working with them?
Would you work for them again, and why?

See how to check references for consent and data rules. Treat reference comments as one signal, and look for patterns.

Red flags and green flags

Red flag	Green flag
Uses “I” for every success and “they” for every failure	Credits the team and owns mistakes
Cannot name a person they developed	Names people and what they did
Speaks badly of former teams without examples	Describes problems with facts and what they changed
Only talks about technical work	Talks about outcomes through others
Avoids detail about poor performers	Describes fair, early, documented action
Gives general philosophy but no example	Gives specific examples and numbers they can explain

Use red flags as prompts for follow-up questions, not as proof. A single poor answer is not a verdict. Look at the pattern across questions and sources.

Interviewing a first-time manager

Candidates who have not managed before cannot answer questions about managing people. Ask about the building blocks instead: leading a project, mentoring a colleague, onboarding a new teammate, coordinating work across people, handling a disagreement and giving feedback to peers. Look at potential and willingness to learn. See our upcoming guide on interviewing for potential. Plan support: training, a mentor and regular check-ins in the first six months.

A worked example (fictional)

This example is invented. A company hires a customer support manager. The hiring manager chooses four competencies: setting priorities, developing people, feedback and performance, and working across teams. She writes two questions for each and one scenario. Three interviewers each score on a 1 to 4 scale and write evidence. Candidate A gives a vivid story about reducing response time by redesigning shifts, but cannot name a person they developed. Candidate B describes coaching a junior agent from a low score to a team-leader role, including what feedback she gave and how often. In the debrief, the scores for “developing people” are 2 for A and 4 for B. For “setting priorities”, A scores 4 and B scores 3. The group chooses B because developing people is the top-weighted competency for this role, and plans to give B coaching on priority setting in the first quarter. A reference from B’s former direct report confirms the story.

Structure of a 75-minute manager interview

Minutes	Part	Content
0 to 5	Welcome	Agenda, notes, adjustments
5 to 10	Role context	Team, goals, challenges, reporting line
10 to 55	Core questions	Six to eight questions on the chosen competencies, with follow-ups
55 to 65	Scenario	One realistic scenario with discussion
65 to 72	Candidate questions	Answer honestly, including about the team’s challenges
72 to 75	Close	Next steps and date

Be open about the real challenges of the role. A candidate who hears an honest description can judge fit, and a candidate who is misled may leave early. Describe the team size, the current performance, known problems and the support you can give.

What to avoid

Asking only about technical achievements.
Accepting stories where the candidate did everything alone.
Changing the question for each candidate.
Skipping the scoring because the candidate seems impressive.
Using the interview to compare with a former manager you liked.
Allowing a single interviewer to dominate the decision.

A manager hire affects everyone on the team, so the cost of a poor choice is higher than for an individual role. See what a bad hire really costs for a way to estimate that cost. Spend the time to prepare questions, brief interviewers and check references from people who worked under the candidate.

Official sources for this topic: EEOC: prohibited employment policies and practices, Acas: recruitment. These pages are maintained by the authorities and may change, so check them for the current text.

Frequently asked questions

What are the best interview questions for managers?

Questions that ask for specific past examples of setting priorities, developing people, giving feedback, making decisions and working across teams, plus a few scenarios. Score all candidates on the same scale.

How do I assess leadership if the candidate has never managed?

Ask about leading projects, mentoring, onboarding others and giving peer feedback. Look at potential and plan support.

Should I ask about management style?

You can, but ask for an example. Style labels are easy to rehearse.

How many questions should I ask?

Six to ten core questions in a 60 to 75 minute interview, plus follow-ups. Cover your chosen competencies.

Can I ask a manager candidate about their family plans?

No. Keep to job-related topics. Do not ask about family, health, age or other protected traits.

Related guides

This is general information, not legal advice.

Join the waitlist

October 13, 2026

How to interview for potential and not just experience

To interview for potential, define what potential means for the role in observable terms, such as learning speed, problem solving, adaptability and motivation. Then collect evidence with past examples of learning something new, a short learning exercise and a plan for support. Score on a written scale, and do not let “potential” replace the must-haves or become a label for people who look like you.

Key takeaways

Potential is not a feeling. Define it as behaviours you can observe: how the person learns, solves new problems and adapts.
Ask for examples of learning something hard, and run a short learning exercise where the candidate learns a task and applies it.
Keep a small set of true must-haves. Potential can replace experience only for skills that can be learned in your timeframe.
Guard against bias: “potential” is often given to people who resemble the manager.
Plan the support: training, a buddy, clear goals and regular feedback.

What potential means, and what it does not

Employers often say they hire for potential. The phrase is vague. It can mean learning ability, ambition, a good attitude or simply “I like this person”. To make it useful, translate it into behaviours that you can check. For many roles, these four are a practical starting point:

Dimension	What it looks like	Evidence you can collect
Learning speed	Picks up new tools, rules or domains quickly and applies them	Examples of learning a new area; a short learning exercise
Problem solving	Breaks down unfamiliar problems, asks useful questions, tests ideas	A case or scenario; examples of solving a new problem
Adaptability	Changes approach when facts change; handles uncertainty	Examples of changing plans; behaviour when the task changes during an exercise
Drive and persistence	Keeps going through difficulty and seeks feedback	Examples of long projects; how the person responded to failure

Potential is not a replacement for evidence. It is a different type of evidence. It also does not mean youth. Many experienced people change fields and learn fast. Link back to your role brief and decide what the person must be able to do on day one and what they can learn in three to six months.

Decide which requirements can be learned

Use a simple split. For each requirement in the role brief, ask: Can a capable person learn this within our onboarding time, with the support we can give? If yes, it can be a learnable item. If no, it is a day-one must-have.

Requirement (fictional example for a junior analyst)	Day-one must-have or learnable?	Reason
Basic spreadsheet use	Day-one must-have	Needed for the first task, and easy to test
Our specific reporting tool	Learnable	Training takes about two weeks
Clear written English	Day-one must-have	Reports go to clients from week two
Knowledge of our industry	Learnable	Reading and mentoring can cover it in three months
Statistics at graduate level	Day-one must-have for this role	The first project uses it

Be honest with yourself. If you list 12 learnable items, the person will need a lot of support, and you must plan time for it. See must-haves vs nice-to-haves.

Interview questions that show potential

Dimension	Question	Follow-ups	What a strong answer shows
Learning speed	Tell me about the hardest thing you learned in the last two years. How did you go about it?	How long did it take? How did you know you were improving?	A method (practice, feedback, resources), time scale and result
Learning speed	Tell me about a time you started a job or project where you had little experience. How did you get up to speed?	What helped? What would you do differently?	Active steps, asking for help, applying quickly
Problem solving	Describe a problem you had never seen before. What did you do first?	What did you check? What did you learn?	Structure, questions, testing ideas
Adaptability	Tell me about a time a plan changed at short notice.	How did you respond? What happened?	Calm, flexible, clear thinking
Drive	Tell me about something you stuck with despite setbacks.	What kept you going? What did you change?	Persistence with reflection
Feedback	Tell me about useful feedback you received. What did you do with it?	What changed?	Openness and action
Transferable skills	What skills from your previous work would help in this role? Give an example.	How would you apply them here?	Clear links between past and new tasks

Use the same questions for all candidates and a scoring guide. See behavioural interview questions. Do not ask about age, family or health, even to judge “energy” or “commitment”. See what you can and cannot ask.

A learning exercise

A learning exercise shows how a person learns now, which is stronger than a story about the past. It takes 30 to 45 minutes. It has four parts.

Teach. Give the candidate a short guide, a data set or a mini-lesson on something new to them (for example a simple rule set or a small tool). Allow 10 to 15 minutes to read it.
Apply. Give a task that uses what they read. For example, apply the rules to five cases.
Change. Mid-task, add a new fact or rule and see how they adjust.
Reflect. Ask: What was easy? What was hard? What would you ask if you could?

Criterion	Score 1	Score 3	Score 4
Understanding the new material	Misreads the main rule	Applies the main rule correctly	Applies it and spots an edge case
Applying it	Many errors	Few errors	No errors; checks own work
Adapting to change	Ignores the change	Adjusts after prompting	Adjusts at once and explains
Asking questions	No questions	Relevant questions	Questions that improve the approach

Use made-up material and tell candidates that you are not testing prior knowledge. Offer adjustments, extra time or alternative formats. Keep the exercise to the time stated. See how to assess skills with a work sample test for fairness and pay rules.

Guard against bias in “potential”

Potential is a judgement about the future, and judgements about the future are easily shaped by bias. Managers often see potential in people who resemble themselves: same school, same background, same style. Others may be judged on their “experience” and not on their capacity. Use these controls:

Define potential in writing before the interviews.
Use evidence, not labels. Write what the person said or did that shows the dimension.
Use the same questions and the same exercise for everyone.
Do not use age, years of experience as a proxy, or “energy” as a signal. Age discrimination law applies in many places. See Acas, the EEOC and the EU directives.
Include a second reviewer on a sample of scores.
Check the results by stage, where lawful, for patterns.

See also how to reduce bias in resume screening and the UK Equality Act guide. This is general information, not legal advice.

A scorecard for potential

Dimension	Evidence from interview	Evidence from exercise	Score (1 to 4)	Support needed
Learning speed
Problem solving
Adaptability
Drive

Combine this with the scores for your day-one must-haves. Do not allow a high potential score to cover a missing must-have. Do not allow a low potential score to hide strong day-one evidence. In the debrief, discuss each dimension and make the final decision using both sets of scores. See how to run a debrief meeting.

Plan the support before you hire

Support	Detail
Learning plan	A 90-day plan with milestones, reading, courses and tasks
Buddy or mentor	A named person who answers questions weekly
Clear goals	Three to five outcomes for each month
Regular feedback	Weekly 30-minute meeting in the first quarter
Review	A 30, 60 and 90-day review; adjust the plan
Budget	Time and money for training

If you cannot provide this support, reduce the number of learnable items or hire for more experience. Hiring for potential without support is not a strategy, it is a gamble that transfers risk to the new person. See the onboarding plan for a template.

A worked example (fictional)

This example is invented. A team hires a junior data analyst. The must-haves are spreadsheet skills and clear writing. The learnable items are the company’s reporting tool and the sector. Four finalists take a 40-minute learning exercise: they read a one-page guide to a simple pricing rule, apply it to five orders, then get a new discount rule and apply it to three more. Candidate A, a recent graduate, applies the rule carefully and asks two good questions. Candidate B, a career changer from retail, makes two errors in the first part, then corrects them and applies the new rule correctly. Candidate C, who has similar experience to the team, applies the rules quickly but does not check the new rule. The panel scores learning speed as 3, 3 and 2, and adaptability as 3, 4 and 2. The panel also checks must-haves: all have them. They choose between A and B on the interview scores and references, and make a plan for B’s support, because B had the stronger adaptability score and the interview evidence of learning a new field. They record the reasons.

What to say to candidates about the exercise

Hello [Name],

The next step is a 40-minute exercise. You will read a short guide on something that may be new to you, apply it to a few cases and then adapt when we add a new rule. We are not testing prior knowledge. We want to see how you learn and solve problems. You may take notes and ask questions. If you need extra time, a different format or any other adjustment, please tell us and we will arrange it.

Best wishes,
[Name]

A clear explanation lowers stress and gives a fairer picture of how people work. Candidates who know what to expect perform closer to their ability.

Evaluating career changers and returners

Potential is often most visible in people who have changed field, returned after a break, or learned on their own. Their CVs may not match the usual pattern. Look for transferable skills and the way they learned. For a career gap, ask neutral questions about what the person did and learned, not why they left. Do not assume anything about the reason. See our guide on reading career gaps and short stints fairly. Be careful not to treat people with a different background as a risk by default. Test their evidence with the same standards as others.

Check the outcome after hire

Track whether people hired for potential succeed. Set a simple check at 90 days and six months: did they reach the learning goals, how did the manager rate their results, and what support did they need? Compare with other hires. If the ratings are lower, review the support plan, the exercise and the must-have list before you conclude anything about potential itself. If ratings are strong, record what worked and reuse it. Over a few hires, you will see which of your questions and exercises relate to later performance, and you can drop the rest.

Official sources for this topic: EEOC: employment tests and selection procedures, Acas: recruitment. These pages are maintained by the authorities and may change, so check them for the current text.

Frequently asked questions

What does “hire for potential” mean?

It means choosing a person based on their ability to learn and grow into the role, not only on current skills. Define it in behaviours you can observe.

How do I assess potential in an interview?

Ask for examples of learning something hard, use a learning exercise, and score the evidence on a written scale.

Is potential just another word for age?

It should not be. Using age or years of experience as a proxy can be discriminatory. Focus on learning behaviour.

Can potential replace experience?

Only for skills that can be learned within your onboarding time. Keep real day-one must-haves.

What support does a high-potential hire need?

A learning plan, a mentor, clear goals, regular feedback and reviews.

Related guides

This is general information, not legal advice.

Join the waitlist

October 13, 2026

How to avoid bias in interviews: 12 practical controls

To reduce bias in interviews, use twelve practical controls: define job-related criteria first, use the same questions, ask for past examples, take notes, score each answer before you form an overall view, hide scores from other interviewers until yours are filed, use a diverse panel, plan adjustments, watch the first minutes, separate small talk from scoring, debrief on evidence, and check outcomes over time. No control removes bias alone, but together they make decisions fairer and easier to explain.

Key takeaways

Bias is normal human thinking. The aim is to make it harder for bias to change the decision.
The strongest controls are structural: same questions, written criteria, scoring before discussion, and records.
Interviewer habits matter: do not decide in the first five minutes, and keep small talk neutral.
Offer adjustments to everyone, and check the process for barriers.
Measure outcomes over time, where the law allows, and fix patterns you cannot justify by job-related reasons.

How bias shows up in interviews

Bias	What it looks like in an interview	Control that helps
First impression	Deciding in the first minutes, then looking for facts to support it	Scoring after each answer; set questions; delay overall judgement
Similarity	Preferring people with the same school, hobby, accent or style	Criteria first; evidence scoring; diverse panel
Halo and horn	One strong or weak trait colours everything	Score each competency separately
Confirmation	Asking leading questions that confirm a first view	Same questions for all
Contrast	Comparing a candidate with the previous one rather than with the criteria	Score against the scale, not against others
Stereotyping	Assuming skills or limits from age, sex, race, accent or disability	Job-related questions only; notes on evidence
Affect or likeability	Choosing the person you enjoy talking to	Evidence-based scorecard
Groupthink	The most senior voice sets the view in the debrief	Written scores first; speak in order

These tendencies affect everyone. They do not mean that interviewers are bad people. They mean that the process should not depend on perfect self-control. The law looks at what you did and at the effect, not only at your intent. See disparate treatment vs disparate impact.

The twelve controls

1. Write job-related criteria first

Decide the must-haves from the role brief before the first interview. Each criterion should link to a task. See the role brief and must-haves vs nice-to-haves.

2. Use the same questions in the same order

Differences in questions create differences in scores that have nothing to do with candidates. Use a structured guide. See structured interviews. Allow follow-up probes to clarify, but give each candidate a similar chance.

3. Ask for past examples and realistic tasks

Behaviour in the past and in realistic tasks gives more evidence than opinions about oneself. See behavioural interview questions.

4. Take notes of facts, not feelings

Write what the candidate said or did. Avoid words such as “good vibe”. Do not write about protected traits or appearance. Tell the candidate that you are taking notes.

5. Score each answer on a defined scale

Use a 1 to 4 scale with written anchors. Score after each answer or each block, not at the end. See the interview scorecard.

6. File your scores before you talk to others

Ask each interviewer to submit scores and evidence within two hours, before any discussion. This protects independent judgement and avoids anchoring on the loudest view.

7. Use a diverse panel where you can

Different interviewers notice different things. Include people from different teams, levels and backgrounds. Do not ask one person to be the “representative” of a group. Train all panel members equally.

8. Plan adjustments and access

Offer adjustments in every invitation. Make the room, the platform and the timing accessible. Use the same length and questions for all, with changes as needed. See the UK Equality Act guide and the EU equal treatment overview.

9. Do not decide in the first five minutes

Be aware of your own first impression, and treat it as a hypothesis to test. Write it down if it helps, then look for evidence that could prove it wrong. Start with the first question as if you knew nothing.

10. Keep small talk neutral

Small talk often drifts into family, age, home town and hobbies. Choose neutral topics, keep it short and do not score it. If the candidate shares personal information, do not follow up and do not use it. See what you can and cannot ask.

11. Debrief on evidence

In the debrief, read the scores first and discuss differences. Ask for examples. Speak in order from the most junior. See how to run a debrief meeting.

12. Check outcomes over time

Where the law allows, compare pass rates by stage and source. Look for patterns you cannot explain. Review what happened to hires at six months. See the four-fifths rule explained for a US method and note that other countries use different tests.

A one-page interviewer checklist

Before	During	After
Read the criteria and questions	Start with the first question as if no view yet	Score within 15 minutes
Read the CV for facts, not impressions	Ask the same questions; use probes	Write the evidence for each score
Offer adjustments	Take notes of facts	File scores before any discussion
Plan neutral small talk	Keep to job-related topics	Remove any notes on protected traits
Block time for notes	Let the candidate finish	Join the debrief with evidence ready

Training interviewers in 45 minutes

10 minutes: Explain the biases in the table above with a short example each.
10 minutes: Practise the notes sheet and the scale with a recorded or written example answer. Everyone scores it alone, then compare.
10 minutes: Practise rewriting five risky questions into safe ones.
10 minutes: Role-play the first five minutes and the small talk.
5 minutes: Agree the rules for the debrief.

Repeat once a year. Training alone may not change results. It tends to work best when the structure is in place: the guide, the scale and the scoring habits.

Limits and honest cautions

No set of controls can promise a bias-free interview. Controls reduce risk, and they can add work. Some, such as panels, add scheduling time. Some, such as strict scripts, can feel less natural. Balance structure with warmth: a structured interview can still be friendly. Also remember that the interview is only one stage. Bias can enter in the ad, the screening and the offer. See how to reduce bias in resume screening and the overview of blind CV screening.

A worked example (fictional)

This example is invented. A team notices that candidates who studied at a few well-known universities are more often chosen, though the role does not require a particular degree. The hiring manager adds controls: written criteria that remove “degree from a top university”, a question list, a scale with anchors, scores filed before discussion and a second reviewer on 20 percent of applications. After two searches, the team compares scores. They find that interviewers still give slightly higher scores to candidates who share their background in the first question, which is about motivation. They replace it with a question about a specific work example and score it with an anchor. The change is recorded and applied to all candidates in the next search.

Example question rewrites

Biased or risky question	Why it is risky	Better question
“Tell me about yourself.”	Open; invites personal details and rewards confident talkers	“Tell me about your most relevant work for this role. What did you do yourself?”
“Where do you see yourself in five years?”	Rewards rehearsed answers; may disadvantage people with caring duties	“What skills do you want to build in this role, and how would you go about it?”
“Are you a culture fit?”	Vague; rewards similarity	“Tell me about a time you worked in a team with different views. What happened?”
“Do you have any commitments outside work?”	May reveal family, health or religion	“The role needs these hours. Can you work them?”
“How old is your experience?”	Age proxy	“What recent projects show the skill?”

Rewrite your own question list this way. Ask a colleague who did not write the questions to review them. Keep the revised list in a shared place and version it with a date.

Handling bias you see in colleagues

If you notice a colleague asking a risky question or using biased language in a debrief, act early and calmly. Use a neutral prompt: “Which criterion does that relate to?” If it continues, speak to the person after the meeting and, if needed, raise it with HR. Keep a short note of what happened. In most cases the person did not mean harm and welcomes a quiet correction. Where a comment shows intent to discriminate, escalate to HR and take advice. Create a culture where anyone can say, “Let us check this against the criteria.”

Remote and phone interviews

Remote interviews bring their own risks. Sound quality, accents, lighting and home settings can colour the judgement. Decide in advance that you will ignore the background, the camera quality and the accent unless the job needs specific speech skills, and score only the content of the answers against the criteria. Give candidates the same time and the same tools. Allow captions. Ask whether a candidate needs a different format, such as a phone call. Offer a back-up plan for connection failures so that technical problems do not become a hidden filter.

Measure what happens

Question	Data to review	Action if the answer is “no”
Do interviewers use the same questions?	Question logs or checklists	Retrain; use a shared guide
Do scores differ widely between interviewers?	Score grid	Clarify anchors; calibrate on a sample
Do certain steps lose more people from one group?	Pass rates by stage, where lawful	Review the criteria and the step
Do hires succeed at six months?	Manager rating, probation outcome	Review criteria and questions
Do candidates report a fair process?	Short survey	Fix the issues they name

Calibration: practise scoring together

Before a big search, run a 30-minute calibration. Give all interviewers the same written example answer to one question. Ask each person to score it alone with the anchors. Compare the scores. If they differ by two points or more, discuss why and adjust the anchor wording. Repeat with a second example. After this, interviewers use the scale in a more similar way, and the scores in the debrief mean the same thing to everyone. Keep the examples for new interviewers. Calibration costs little and improves the quality of every later decision.

Finally, share a one-page summary of these controls with every new interviewer and ask them to confirm they have read it before their first interview. A short, signed-off page makes the rules visible, sets a shared standard and gives you a simple record that interviewers were briefed.

Keep the list of controls visible in the interview room or in your calendar invitation, so that the habits are in front of you when you need them. Habits become easier with repetition, and the second search will feel faster than the first.

Frequently asked questions

Can I remove bias completely from interviews?

No. You can reduce it with structure, evidence and checks, and you can make decisions easier to explain.

Does unconscious bias training work?

Training raises awareness, but results usually change more when the process changes: same questions, written criteria and scoring habits.

Should every interview have a panel?

Not always. A panel adds views, but it adds cost. Use at least two perspectives on important decisions, and share independent scores.

Is small talk a problem?

It can be if it drifts into protected topics or influences the score. Keep it short and neutral and do not score it.

How do I know if my interviews are fair?

Check consistency of questions and scoring, review outcomes where the law allows, and ask candidates for feedback on the process.

Related guides

This is general information, not legal advice.

Join the waitlist

October 13, 2026

How to interview when you are not trained to

If you have never been trained to interview, use a simple structure: prepare the criteria and five to seven questions, open clearly, ask each question the same way for every candidate, listen and probe for examples, take notes, leave time for the candidate’s questions and score straight after. This gives you most of the benefit of training in about 45 minutes of preparation.

Key takeaways

You can run a fair, useful interview with a short plan: criteria, questions, notes, scale.
Listen more than you talk. Aim for the candidate to speak about 80 percent of the time.
Ask for examples, then probe: what did you do, what happened, what did you learn?
Avoid questions about protected traits. Keep small talk neutral.
Score right after the interview and compare with the criteria, not with your mood.

You do not need a special talent

Many managers are asked to interview with no training. They worry about asking the wrong thing, running out of questions or being too friendly or too hard. Interviewing is a skill, but a simple method gets you most of the way. The method has six parts: know what you are looking for, plan your questions, create a calm setting, listen and probe, take notes and decide on evidence. This guide takes each part in turn. For a short template, see how to run a first interview.

Step 1: Know what you are looking for (15 minutes)

Write three to five must-haves for the job. Each should be something the candidate can show with an example. Use the role brief if you have one. If you do not, answer these questions in writing: What will the person do in the first three months? What skills or experience do they need on day one? What can they learn on the job?

Step 2: Plan five to seven questions (15 minutes)

For each must-have, choose one question that asks for a real example. Add one question about motivation and one about practical matters such as availability. Use the same questions for every candidate. You can copy from behavioural interview questions. Write them down, with a space for notes below each one.

Question type	Example	Why
Experience	Tell me about the most relevant work you have done for this role.	Starts with strength; shows fit
Skill example	Describe a time you [did the key task]. What did you do and what happened?	Past behaviour as evidence
Problem	Tell me about a problem you solved at work. How did you approach it?	Thinking and action
Learning	What is something you learned recently? How?	Growth
Motivation	Why does this role interest you?	Interest; expectations
Practical	Do the hours and the place work for you?	Fit; avoid personal questions

Step 3: Create a calm setting

Choose a quiet room or a stable video link.
Send the candidate the time, length, place, names and an offer of adjustments in advance.
Be on time and ready. Silence your phone.
Start with a warm welcome and a short outline of the meeting.

Thank you for coming. I will tell you a little about the role, then ask some questions, and leave time for yours. I will take notes so that I do not miss anything. The meeting will take about 40 minutes. Is that fine?

Step 4: Listen and probe

The most useful habit is to ask short, open questions and then be quiet. Silence feels long, but waiting three or four seconds often brings more detail. When an answer is vague, probe.

If the candidate says	You can probe with
“We did a lot of customer work.”	“What did you do yourself? Can you give an example?”
“I am good at planning.”	“Tell me about a time you planned something complex. What steps did you take?”
“It went well.”	“How did you know? What was the result?”
“It was a team effort.”	“What was your part in it?”
“I would do it differently now.”	“What would you change, and why?”
A very short answer	“Can you tell me more?” or “What happened next?”

Keep probes neutral. Do not lead. Do not finish the candidate’s sentences. Do not fill silence with hints. If you do not understand a term, ask. It is not a weakness to say, “Can you explain that for me?”

Step 5: Take notes and stay on track

Write facts and short quotes. Link them to the must-haves. Leave out protected traits and feelings. See how to take interview notes. If a candidate talks for too long, you can say, “Thank you, that is helpful. I want to make sure we cover everything, so let me move to the next question.” If the candidate goes off topic, bring them back with a friendly prompt.

Step 6: Close well

Leave five minutes for the candidate’s questions. Answer honestly, including about challenges. Explain the next step and the date. Thank the candidate. Do not promise a result. After the candidate leaves, score at once using the scale. See the interview scorecard.

What not to ask

Avoid questions about age, family plans, marital status, health, religion, ethnic origin, nationality of birth, sexual orientation and political views. They can lead to unfair decisions and legal risk. If the candidate raises such topics, do not follow up and do not note them. Rewrite risky questions to focus on the task. For example, instead of “Do you have children?”, say, “The role requires two weekend shifts a month. Can you work those?” See what you can and cannot ask.

Common mistakes of untrained interviewers

Mistake	Effect	Fix
Talking too much	Little evidence	Plan to talk 20 percent of the time
Making up questions on the spot	Unequal candidates	Write the list in advance
Deciding in the first five minutes	Confirmation bias	Score each answer; delay overall view
Friendly chat that drifts to personal topics	Risk and bias	Neutral small talk
Selling the job too hard	Candidates cannot judge fit	Be honest about challenges
No notes	Poor memory	Use a sheet
Skipping feedback	Poor candidate experience	Send an outcome by the date promised

Handling your own nerves

Prepare the sheet. Preparation lowers nerves.
Take a few slow breaths before the candidate arrives.
Remember that the candidate is also nervous. A warm start helps both.
If you lose your place, look at the sheet and say, “Let me check my notes.”
If you make a mistake, such as asking a risky question, pause, apologise briefly and move on. Do not use the answer. Tell HR if needed.

A 45-minute preparation plan

Minutes	Task
0 to 15	Write must-haves from the job tasks
15 to 30	Choose and write five to seven questions
30 to 40	Write the scale and prepare the note sheet
40 to 45	Read the CV, mark two points to ask about, plan the first five minutes

With this plan you can interview with confidence even without formal training. After the interview, ask a colleague who has experience to review your notes and scores, and ask for feedback on your questions. Improve the list for the next time. Consider a short course or a coaching session if you will interview often. Many professional bodies, such as CIPD in the UK, publish guidance on good recruitment practice.

A worked example (fictional)

This example is invented. A restaurant manager who has never interviewed before needs to hire a server. She spends 45 minutes writing three must-haves: works well in a busy team, communicates with customers and can work evenings. She picks six questions and a scale. In the interview she talks for five minutes, asks the questions in order, and probes twice with “What did you do yourself?” and “What happened next?”. She takes notes on the sheet and does not write about the candidate’s appearance. At the end she answers two questions about tips and shifts. After the interview she scores each question, writes three strongest points and one doubt, and compares with the other two candidates the next day. She offers the job to the candidate with the strongest evidence of working in a busy team and tells the others the outcome within two days.

Practice before the real interview

Ask a colleague to play the candidate for ten minutes. Ask your questions, take notes and score the answers. Then swap roles. You will find which questions are unclear, how long each takes and where you tend to talk too much. Practice also helps you notice your own habits: nodding too much, finishing sentences, or reacting more to answers you like. Fix them before the first candidate arrives. Ten minutes of practice often improves the real interview more than an hour of reading advice.

Keep the candidate at ease without losing the structure

Structure does not mean coldness. You can be warm and still ask the same questions. Smile, use the candidate’s name, thank them for their answers and show that you listen by summarising: “So you led the move to the new system and trained the team. Is that right?” Summaries show respect and check that you understood. They also give the candidate a chance to correct you. Avoid reacting differently to answers you like and to answers you do not like. Keep your tone steady, and save your judgement for the scoring.

If the interview is not going well

Situation	What to do
The candidate is too nervous	Slow down, offer water, repeat the question in different words, give time
The candidate is not suitable for the role	Complete the interview politely, using the same questions. Do not cut it short unless the candidate asks. Score at the end
The candidate dominates the conversation	Use a polite interruption and return to the questions
You feel a strong liking or dislike	Name it to yourself and return to the evidence. Score by the scale
The candidate raises a complaint about a former employer	Listen briefly, then ask for the facts that relate to the role
You run out of time	Prioritise the must-have questions and arrange a short follow-up call for the rest

If in doubt, take a short break, check your sheet and continue. The sheet is there to support you. Remember that a respectful interview is a good outcome for every candidate, whether or not they get the job.

After your first interviews

Hold a ten-minute review with yourself or a colleague. Which question gave the best evidence? Which gave none? Where did you talk too much? Which note was most useful when you scored? Write the answers in one short list and change your question sheet before the next candidate. Small improvements after each interview add up quickly. After five interviews your sheet will be better than any template, because it reflects your role, your team and your own style of listening.

Share your improved sheet with the next manager who has to interview. Teams that pass on their question lists and scoring guides build a common standard, so that candidates meet a consistent process whichever manager they see, and new managers do not start from zero.

Official sources for this topic: Acas: recruitment, EEOC: prohibited employment policies and practices. These pages are maintained by the authorities and may change, so check them for the current text.

Frequently asked questions

How do I interview if I have no training?

Use a simple structure: criteria, written questions, notes, a scale and a clear close. Prepare for 45 minutes and score straight after.

How many questions should I ask?

Five to seven main questions for a 40 to 45 minute interview, plus probes.

What if the candidate asks me a hard question?

Answer honestly, or say you will find out and reply by a date.

Should I tell the candidate I am new to interviewing?

You do not need to. Be clear, polite and prepared. If you want to say it, it is fine; honesty rarely harms.

How do I know if I interviewed well?

Check whether your notes give evidence for each criterion and whether another person could understand your scores. Ask for feedback from colleagues.

Related guides

This is general information, not legal advice.

Join the waitlist

October 13, 2026

How to avoid ghosting candidates: a simple service standard

To avoid ghosting candidates, publish a simple service standard and build it into your process: acknowledge every application, give every candidate an outcome, state a date for the next update, keep a “last contact” date for each active candidate and review it every week. Ghosting is mostly a workflow problem, not a character problem, so fix the workflow.

Key takeaways

Ghosting happens when a process has no owner for the silent moments: after the application, after an interview, and after the decision.
A service standard has five promises: acknowledge, update, decide, tell, close. Put dates on each.
Track “days since last contact” for every active candidate and review it weekly.
Use templates so a kind decline takes one minute.
Silence harms candidates and your reputation. Even a short, honest message helps.

What ghosting is, and why it happens

Ghosting means cutting off contact without an explanation. In hiring, employers ghost candidates when they go silent after an application or an interview. The cause is rarely bad intent. It is usually one of these: too many applicants, no template for declines, a hiring manager who has not decided, a recruiter who is overloaded, a role that is on hold, or a fear of awkward conversations.

Cause	What it looks like	Fix
Volume	Hundreds of applications and no time to reply	Automated acknowledgement and outcome messages; screening sessions on fixed days
Waiting for a decision	Hiring manager delays; recruiter has no news to share	“No news” update with a date; response-time agreement
Role on hold or cancelled	The process pauses; nobody tells candidates	Close-out message as soon as the status changes
Awkward conversations	Declines feel uncomfortable	Templates and a short script
No owner	Nobody is responsible for follow-up	Name an owner for each role and a backup
Tool gaps	Applicants sit in a system without prompts	Reminders and a weekly list

Silence costs more than it seems. Candidates tell friends and write reviews. Some will be future customers, partners or colleagues. Fairness also matters: a person who receives no outcome cannot move on or learn. A clear service standard is a modest investment with a high return. See our candidate experience checklist for the full journey.

The five-promise service standard

Promise	Standard (example)	Who owns it
1. Acknowledge	Every applicant receives an acknowledgement within one working day, with the closing date and the date of the next update	Recruiter or system
2. Update	Every active candidate hears from us at least every seven days, even if there is no news	Recruiter
3. Decide	We give an outcome within two working days of each interview or task	Hiring manager and recruiter
4. Tell	Every candidate receives a clear outcome, including those declined at screening	Recruiter
5. Close	When a role is filled, paused or cancelled, we tell all remaining candidates within two working days	Recruiter

Publish the standard on your careers page and in the ad. Choose times you can keep. Track performance. If you cannot meet a promise, change the promise or the process. A published standard also helps hiring managers understand what they must do. See candidate update email cadence for message timing.

Build the standard into the workflow

Give every application a status

Use a short list of statuses: received, screened, call, interview, task, finalist, offer, hired, declined, withdrawn, on hold. Each status has a rule for the next message.

Status	Message due	Maximum days in this status
Received	Acknowledgement (same day)	Until screening day, as stated in ad
Screened: declined	Decline within 2 working days of the screening date	2
Screened: invited	Invitation within 2 working days	2
After interview	Thank you and date within 1 day; outcome by the date given	As stated
Finalist	Update every 3 to 5 days	Until decision
On hold	Notice when put on hold; update every 7 days	Review monthly
Hired or role closed	Close-out to all remaining candidates	2

Keep a “last contact” date

For every active candidate, record the date and type of the last message. Add a column for “next update due”. Sort by this column each morning. Anything in the past is a risk of ghosting. A simple spreadsheet is enough for a small team. In a tracking system, use filters or tasks.

Hold a ten-minute weekly review

Every Friday, list active candidates with no contact for five days or more, roles with no activity for seven days and decisions that are overdue. Send the messages that are due. Ask hiring managers for decisions by the next working day. This review prevents most ghosting.

Put the deadline in the ad

Write “We will reply to every applicant by [date]” in the ad. Then do it. A public promise gives you a reason to prioritise it.

Templates for the hard moments

Decline at screening

Hello [Name],

Thank you for applying for [job title]. We reviewed your application against the requirements for the role. We will not move forward with it at this stage. We appreciate your interest and wish you every success.

Best wishes,
[Name]

Role on hold

Hello [Name],

We are pausing the search for [job title] while we review our plans. We do not yet know when it will restart. We will write again by [date] to tell you what has changed. If you would like us to withdraw your application, please reply and we will do so.

Best wishes,
[Name]

Role cancelled

Hello [Name],

We have decided to close the [job title] search. We are sorry for the late news and appreciate your time. If you agree, we will keep your details for [period] and contact you if a similar role opens. Please reply “no” if you prefer that we delete them.

Best wishes,
[Name]

After an interview with no decision yet

Hello [Name],

Thank you for your interview on [date]. We have not yet made a decision. We expect to contact you by [new date]. If your situation changes in the meantime, please tell us.

Best wishes,
[Name]

What to do when the volume is very high

If you receive hundreds of applications, you cannot write to each person by hand. Use automation with care. Send an automatic acknowledgement, then an automatic outcome message after screening. Write the text yourself and avoid cold language. Offer a way to reach a person. Do not let a system reject candidates without a person making the decision. See screening at volume. For legal context on automated decisions in the UK and EU, see our article on the EU AI Act and hiring tools and check the rules for your country. This is general information, not legal advice.

Working with hiring managers

Most ghosting at the interview stage comes from slow decisions. Agree response times in the kickoff meeting, share the service standard, and show the data. Say: “Our standard is two working days after an interview. This week we are at six days for two candidates. Can we decide by Thursday?” Offer help: a short debrief, a decision template or a call. See the recruiter kickoff meeting and how to run a debrief meeting. Make it easy for managers to say yes, no or “not yet, until [date]”.

Measure and report

Measure	How to calculate	Target (set your own)
Acknowledgement time	Hours between application and acknowledgement	Within one working day
Outcome rate	Candidates who received an outcome divided by all candidates	100 percent
Update gap	Days since last contact for active candidates	7 days or fewer
Decision time	Working days from interview to outcome	Within the promise
Complaints	Number of “I never heard back” messages	Falling over time

Report these to the hiring team each month. Celebrate improvements. If a number is poor, ask what blocked it. Do not use the numbers to blame individuals.

A worked example (fictional)

This example is invented. A recruiter of a mid-sized company discovers that 40 candidates have had no contact for more than two weeks after an interview. She sets up a status list, a “next update due” column and a weekly review. She writes five templates. In the first Friday review she sends 40 messages in about one hour: 25 declines, 10 holds with dates and 5 invitations. She publishes a service standard on the careers page. Over the next two months, the number of “I never heard back” emails falls from several each week to about one a month. She adds a line to the kickoff agenda about decision times and shares the monthly report with hiring managers.

A weekly review that keeps the standard alive

A service standard only works if someone checks it. Set a fixed 20-minute slot each week. The recruiter who owns the standard opens the applicant list for every open role and answers four questions. Does any applicant have no outcome and no message in the last seven days? Is any interviewed candidate waiting longer than the promised date for news? Are there hiring managers who owe feedback? Which messages are due this week?

Write the answers in a shared note, not in your head. Name each late item, the person who owns it and the day it will be fixed. If the same hiring manager appears on the list two weeks in a row, raise it with that manager directly and use the feedback guide linked below as a starting point.

Weekly check	Owner	Fix if late
Applicants with no acknowledgement	Recruiter	Send the acknowledgement today
Applicants past the promised screening date	Recruiter	Send a short update with a new date
Interviewed candidates with no outcome	Hiring manager and recruiter	Agree the decision or a new date within one working day
Declined applicants with no message	Recruiter	Send the decline message today
Offers waiting for a reply	Recruiter	Call the candidate and ask if they need anything

A short script for the hiring manager conversation

The hardest part of the standard is a manager who is busy and does not reply. Do not send a long complaint. Use a short, factual message, and offer a fix.

Hi Sam, three candidates interviewed last week are waiting for news. We told them they would hear by Friday.
Can you send your scorecards by noon tomorrow? If you need more time, I will tell the candidates the new date today.
If it helps, we can hold a 15-minute debrief tomorrow and decide together.

This message states the facts, names the promise to the candidate, gives a deadline and offers help. It does not blame. If the manager still does not reply, tell the candidates the truth: “We need a little more time and we will write again by Wednesday.” That is better than silence.

What to do when you have no news

Many ghosting cases start when a recruiter feels they have nothing to say. But “no news yet” is news. A candidate can plan around a clear date. They cannot plan around silence. Use this pattern: say what has happened, say what has not happened, give the next date, and give a contact.

Hello Priya, thank you for your patience. We have finished the interviews for the role, but the final decision is not made yet.
We will write to you by Thursday 17:00 with an outcome or an update.
If you accept another offer before then, please tell us so we can wrap up your application.

The last line respects the candidate. They may have other offers, and you are not asking them to wait with no information.

How to measure the standard without invented targets

You do not need industry statistics to measure this. Count your own numbers each month: the share of applicants who received an acknowledgement on the day, the share who received a final outcome, the number of days from interview to outcome, and the number of candidates who withdrew after waiting. Compare this month with last month. Set a target based on your own starting point, for example “reduce the number of interviewed candidates waiting more than the promised date by half”. Treat this as a planning target, not an external benchmark.

You can also ask every candidate one question at the end of the process: “How clear was our communication, from 1 to 5?” Keep the answers anonymous and read the free-text comments. They show where silence happens more clearly than any dashboard.

Common objections, and short answers

Objection	Short answer
We get too many applicants to write to everyone.	Use a template and your system’s bulk send. A two-line decline sent late is better than none. See the update email guide below.
Declining people will cause arguments.	Short, neutral messages with no reasons beyond “we chose candidates whose experience was closer to the requirements” rarely start debates. Do not give detailed scores or personal comments.
The hiring manager has not decided.	Send the “no news yet” message with a date. Silence is the worse option.
A decline might create legal risk.	Keep the message factual and consistent for every applicant, and keep records. For legal questions in your country, ask a specialist.

A calm, consistent standard protects your employer brand in a simple way: candidates who are treated with respect, even when they are declined, are more likely to speak well of you and to apply again later. That is a reasonable expectation, not a measured result, so judge it by your own repeat-applicant numbers over time.

Official sources for this topic: Acas: recruitment, ICO: recruitment and selection. These pages are maintained by the authorities and may change, so check them for the current text.

Frequently asked questions

What is candidate ghosting?

It is when an employer goes silent to a candidate, usually after an application or interview, without giving an outcome.

Why do employers ghost candidates?

Usually because of volume, slow decisions, unclear ownership or discomfort with giving bad news. It is a process problem that can be fixed.

Do I have to reply to every applicant?

It is good practice. A short automated acknowledgement and a clear outcome message take little time and protect your reputation.

What should I say if I have no news?

Say so, give the next date and thank the person. A short “no news” message is better than silence.

Can automation help?

Yes, for acknowledgements and status messages, if the text is clear and kind and a person makes decisions.

Related guides

This is general information, not legal advice.

Join the waitlist

October 13, 2026