How many questions should an interviewer ask? Enough to cover every competency the interview stage is there to assess: one planned core question for each, with time left to follow up on the answers. There’s no right total, because it depends on how many competencies the stage covers and how long it runs.
It’s still tempting to look for a number, and to judge interviewers by how many questions they ask. Fewer questions can look focused, and more can look thorough. But a count can’t tell you whether the questions were the right ones, whether every candidate heard the same ones, or whether the answers gave the interviewer enough to rate. That’s why my advice is to plan questions from competencies, ask the same core questions of everyone you interview for a stage, and judge an interview by whether every rating rests on something the candidate said.
This guide is for interviewers and hiring managers who plan and run interviews. It shows you how to work out what each stage assesses, how many questions to plan for it, and how to follow an answer without losing your plan. Then it covers how to check, once the first interviews are done, whether your questions are working.
Decide what each stage has to find out.
Before you write a single question, sit down with the hiring manager and everyone else who interviews for the role. Agree what the role needs and which stage will assess each part of it. Write down three things:
- the competencies the role needs, each described as something an interviewer can see or hear
- the stage that assesses each competency
- what a strong answer looks like for each one, so every interviewer rates against the same standard
Describe each competency so it can be tested. “Strong communicator” is too broad to assess. “Explains a technical trade-off clearly enough for someone outside the team to make a decision” gives the interviewer something to test, and tells them what a strong answer would contain. For help describing what a strong answer looks like, read the guide to interview rubrics.
Then look across the stages. Give every competency one stage, unless you want a second look on purpose. When two stages both cover a competency by accident, the candidate answers the same kind of question twice, and the time spent on it is time another competency doesn’t get.
How many questions should an interviewer ask at each stage?
Once each stage has its competencies, the number of questions follows from them. Work it out in four steps:
- List the competencies the stage assesses, and give each competency one core question. A core question is open and asks for a real example, such as “Tell me about a project where you had to make an important decision without all the information you wanted.”
- Leave room to follow up on every core question. The first answer rarely gives you enough to rate, so expect to spend most of the interview on follow-ups.
- Fit the core questions to the time you have. If the core questions and their follow-ups won’t fit, move a competency to another stage rather than rushing every answer.
- Write the core questions down and use them for every candidate at that stage. Follow-ups will differ with each answer. The core questions shouldn’t.
Two interviewers can ask very different numbers of questions and both run a good interview, as long as each covers the same competencies with the same core questions.
Use the table below when interviews don’t go to plan. Each row starts from something you can see in the interview and says what to change in your plan:
| What you see | What it usually means | What to change |
|---|---|---|
| Ratings rest on one short answer | There are too many core questions to follow any of them up | Hand a competency to a different stage so every core question gets its follow-ups |
| The interview ends early with little to rate | The core questions can be answered in a sentence | Rewrite them to ask for a real example |
| Two interviewers ask about the same thing | Two stages assess the same competency | Give the competency to one stage |
Ask the core question, then follow the answer.
A planned interview doesn’t have to sound like a script. Ask the core question, listen to the answer, and follow up on what it left out: what the candidate did themselves, why they chose that approach, and what happened next. The guide to follow-up interview questions covers the gaps to listen for and the follow-up that closes each one.
Stop following up when you have enough evidence to rate the competency against what you agreed a strong answer looks like. If the answer is still too thin when you need to move on, write down that there wasn’t enough evidence, rather than turning it into a confident rating. Then ask the next core question.
An answer can wander into another competency. Note what it showed, but still ask that competency’s core question when you reach it, so every candidate gets the same chance to answer it.
Where Metaview fits.
Once the interviews are done, you’ll want to check whether the plan held: did every candidate hear the same core questions, and does every rating rest on an answer? You can’t check that from memory. After a day of interviews, an interviewer rarely remembers which core questions they asked each candidate, or what each candidate said in reply. Checking needs a record of the interview.
Metaview is the Agentic Recruiting Platform. Where consent has been given, an interview is captured by the Metaview Notetaker, which records and transcribes it, then turns the conversation into structured notes. The recording captures every spoken word, so you can read back each question you asked and the answer it got.
With a transcript of each interview, the hiring team can read interviews for the same role and stage side by side and see whether every candidate heard the same core questions. James Lesner, Director of Talent Management at Catawiki, described what Catawiki found: “After bringing in Metaview, we were able to see that for the same role, we had interviewers asking very different questions. While some variety is good, it was to an extreme where the candidate experience heavily depended on the interviewer.” That’s what one written list of core questions for each stage, used by every interviewer, is there to prevent.
One candidate’s transcripts from every stage, read together, also show whether the stages covered every competency the role needs. No single interview has to cover everything. Shahriar Tajbakhsh, Metaview’s co-founder and chief technology officer, has put it this way:
One interview can’t get all of the signal needed to make a hiring decision, but the collection of all interviews for any given candidate must provide the necessary information.”
The record also helps with the ratings: the Notetaker drafts the interviewer’s scorecard from the conversation. The interviewer reviews the draft, adds their own ratings, and submits it. The interviewer makes every rating, and the hiring team makes every decision.
Check whether your questions are working.
A question plan can look right on paper and still not work in the room, so check it early. Once the first few interviews for a role are done, read back the notes or transcripts and run these four checks:
- Did every candidate at the stage hear the same core questions? Where one didn’t, find out why. An interviewer may have dropped a question, or the plan may not fit the time.
- Does every rating rest on an answer? For each competency, find the part of the interview the rating rests on. A rating with no answer behind it means the core question wasn’t asked, or the answer wasn’t followed up.
- Is the same competency always squeezed? If the last core question is always rushed, the plan is too long for the stage. Move a competency to another stage.
- Did two interviewers ask very different numbers of questions? Read both interviews: the count only tells you the conversations went differently, and reading them tells you whether each gathered enough evidence to rate.
These checks look at the core questions and the ratings. For a fuller check of whether interviewers followed the whole interview plan, read the guide to structured interview adherence.
You’ll know your plan is working when every rating rests on an answer and the candidates at each stage all heard the same core questions, however many follow-ups it took to get there. Whatever number of questions that comes to is the right number for that stage.
Read back the questions each candidate heard.
See how the Metaview Notetaker transcribes your interviews, where consent has been given, so you can read back the questions behind every rating.
Frequently asked.
Do the best interviewers ask fewer questions?
Not necessarily. A good interview covers every competency the stage assesses, with enough follow-up to rate each one. Some interviews get there with few questions and some need more, depending on how much the answers leave out. Judge an interviewer by whether each of their ratings is backed by an answer.
How many questions should you ask when you interview a candidate?
One core question for each competency the stage assesses, plus the follow-ups each answer needs. Make sure the core questions and their follow-ups fit the interview, and if they don’t, hand one competency to a different stage.
Should every candidate get the same interview questions?
Every candidate at the same stage for the same role should hear the same core questions, so their answers can be compared. Follow-ups will differ, because they depend on what each candidate says.
What’s the difference between a core question and a follow-up question?
A core question is planned before the interview and asked of every candidate to open a competency. A follow-up comes from the candidate’s answer and fills in what it left out, such as what they did themselves.
What should you do if you run out of time before your last question?
Write down that the competency wasn’t assessed rather than guessing at a rating, and cover it somewhere else, such as a later stage. If it keeps happening, the stage covers too many competencies for its time.