The best interview questions do one thing well: they get candidates to show how they actually work. The exact wording matters far less than the follow-ups you ask and the way you score what you hear.
Search for interview questions and you'll find endless lists of clever prompts. Most aren't tied to any particular job, and a memorable answer can still be useless as evidence. A question earns its place once you can name the competency it tests, say what a strong answer would show, and agree how you'll score it before the candidate walks in.
So this piece runs the other way around. We take one question all the way through for a single role, from the competency to the follow-ups to the scoring anchors, then hand you a compact set to build the same way for your own roles. Decide what you're testing, write the anchors first, and hold every candidate to the same standard.
The Metaview interview questions library is a good place to grab role-specific prompts to start from.
Why most question lists fall short
Most lists collect questions that sound interesting on paper, and plenty of them are. An interesting conversation can still tell you almost nothing about whether someone can do the job.
Structured interviews work differently. The team defines the skills the role needs, asks comparable job-related questions, and scores the evidence against a shared rubric. Two things get better here, and hiring teams routinely blur them together. Scoring gets more consistent, so different interviewers land closer to the same read on the same answer. And the questions get more job-related, so the evidence points at the work the person will actually do. Published guidance on structured interviewing backs both.² ³
Neither of those tells you how someone will do once they're in the role. A more consistent, more job-related interview is fairer to compare and easier to defend, and that's the whole of what it buys you. No interview question has been shown to forecast how someone will do once hired, and this article doesn't pretend otherwise. Metaview's record stops at the offer. It covers what happens inside the hiring process and holds nothing about what happens after a hire, so the goal here is the reachable one: a fair, consistent read during the interview itself.
A structured interview can still feel like a conversation. Ask follow-ups, chase a vague answer, let the discussion wander where it wants. Just hold every candidate to the same set of competencies.
One question worked end to end
Here's one question built properly for a single role. Say you're hiring a customer success manager, and the competency you care about is keeping an account that's close to walking. The same five steps work for any competency: name it, write the question, plan the follow-ups, decide what good evidence sounds like, and set the scoring anchors before anyone sits down.
The competency: keeping an at-risk renewal on track. You want to see how the candidate spots trouble early, decides what to do with the time they have, and pulls in the people around them to change the outcome.
The question: Tell me about a renewal you thought you might lose. What did you do about it?
The follow-ups that turn a story into evidence:
- What first told you the renewal was at risk, and when did you notice?
- What did you decide to do about it, and what did you deliberately choose not to do?
- What were you working against here, whether that was the timeline, the budget, or the customer's own internal politics?
- Which parts did you handle yourself, what did other people such as the account executive or a product manager contribute, and how did you coordinate across them?
- How did the renewal end, and what would you do differently next time?
What good evidence sounds like: a specific account of what told them the account was slipping, the calls they personally made and why, an honest description of the constraints, and a credible split of the work between them and everyone else involved. You're listening for their reasoning and for what they personally contributed inside a team effort. A solo rescue with a tidy ending is usually the weaker answer. A renewal they lost but handled well can be stronger evidence than one they saved by luck.
How to score it, using the guide below:
- Weak: talks about the account in general terms and can't say what they personally decided or did.
- Partial: describes some actions, but the reasoning or their own part stays vague, or the whole account rests on one lucky save.
- Strong: names what told them the account was at risk, the calls they owned, the constraints they worked under, and a clear line between their work and their colleagues'.
- Exceptional: all of that, plus a trade-off they can defend and something they changed the next time.
Those follow-ups are doing specific work. They ask separately what the candidate owned, what other people contributed, and how the work got coordinated, so a strong collaborator doesn't get marked down for saying 'we' and someone claiming sole credit for a team effort has to account for it. That’s what turns a rehearsed story into evidence you can score.
Six more questions to build the same way
Build one question end to end and the rest follow the same pattern. Here are six more competencies, each with a question that tends to surface it and the evidence worth listening for. Treat them as a starting point: define the competency for your own role, plan the follow-ups that pin down decisions and contribution, and write the scoring anchors before the first interview.
| Competency | A question that surfaces it | What counts as evidence |
|---|---|---|
| Working without full information | Tell me about a decision you made without all the information you wanted. | The information they did use, the assumptions they named, and an honest read of the risk rather than a lucky result. |
| Learning from a setback | Describe a piece of work that fell short. What did you change afterward? | Their specific part in what happened and one concrete change they made next time, rather than blame pointed elsewhere. |
| Judgment on a real problem | Here is a problem this role runs into. How would you approach it? | The questions they ask first, the risks they check, and priorities that fit the constraints you describe. |
| Doing the actual work | Show me how you would handle one core task from this role. | A workable approach and sound judgment on the same task every candidate gets, scored against the same criteria. |
| Explaining to a non-expert | Explain something you know well to someone new to it. | An explanation pitched to the listener rather than a display of jargon. |
| Changing your mind on evidence | Tell me about a time new evidence changed your approach. | A real shift in reasoning and a clear account of what the new evidence changed. |
Pick three or four for the role and ask real follow-ups. That will usually tell you more than racing through all of them.
A simple scoring guide
A question is only useful if interviewers agree on what the scores mean. Write the anchors before the interviews start, then tailor them to the competency you're testing.
| Score | What it means | What the answer sounds like |
|---|---|---|
| 1 - Weak | Little useful evidence | Vague, hypothetical or unrelated. The candidate cannot explain their own actions. |
| 2 - Partial | Some evidence, but important gaps | A relevant example with limited detail, unclear reasoning or no clear result. |
| 3 - Strong | Meets the bar | Specific actions, sound reasoning and a result that connects to the competency. |
| 4 - Exceptional | Clear evidence above the bar | Strong evidence, thoughtful trade-offs and insight that goes beyond the basic requirement. |
Ask interviewers to score independently before the debrief. Go back to the evidence and the rubric when the scores land far apart. Averaging the disagreement away buries the thing you most need to look at.
Why documentation matters
Good questions usually break down in one of two places:
The scoring is inconsistent
Different interviewers apply different standards to the same answer. Fix this with clearer anchors and occasional calibration.
The evidence is missing
Notes arrive late, or the scorecard never gets filled in at all, and by the debrief everyone's working from memory.
A corpus of 5.2 million candidate interviews shows 31.2% with a scorecard attached, and that’s the industry’s normal state. A separate measure covering 296,555 advances recorded in connected ATS data found 41.9% with no submitted scorecard on file at the moment the advance was recorded.¹
Feedback may well have existed. The data only shows that the reasoning wasn’t visible in a submitted scorecard at the point measured. A clear interview scorecard gives that reasoning somewhere to live, and it makes the decision easier to review months later.
How Metaview helps
Metaview records the interviews your hiring team runs and organizes the notes around the questions and competencies in your own template. It can also draft the scorecard and link each piece of evidence back to the moment in the conversation it came from.
Metaview captures the evidence while recruiters and hiring managers make the judgment. The interviewer reads the draft, fixes anything it got wrong, and applies the rubric. The decision never leaves the hiring team.
It's unimaginable to go back to a time before Metaview where we'd have to take notes during interviews and rely on guesswork for improving our processes.”
How to put the questions to work
Start with one role and build from there. Agree on what good looks like, hand each interviewer a clear focus, and score the evidence while it’s still fresh. Get that working on one role and rolling it out to the rest is mostly repetition.
- Define four to six competencies: Use the intake call to agree on what each one means in practice.
- Choose one or two questions for each competency: Keep the core questions consistent and plan a few useful follow-ups.
- Give each interviewer a clear focus: One or two competencies per person is usually enough.
- Score while the evidence is fresh: Ask interviewers to submit their scores independently during the interview or immediately after.
- Review what’s working: Use talent calibration to tighten unclear scoring, and Metaview Reports to check whether questions are producing useful evidence across the team.
- Go deeper when a role needs it: Pair the question set with competency-based interviewing.
Don't drop a question just because most candidates score well on it. First check whether the bar is too loose, whether the applicant pool is unusually strong, or whether the competency is simply a baseline everyone in the field clears.
Keep the evidence and the scoring in one place.
Live notes, structured scorecards, and ATS sync across your hiring process.
Frequently asked questions
What interview questions predict job performance?
No specific wording has been shown to predict performance on its own. The published research on structured interviewing supports the method: job-related questions, asked consistently, with the evidence scored against anchors agreed in advance. A short work sample adds direct evidence of how someone approaches the work.
Do structured interviews work better than unstructured interviews?
Generally, yes. Research and assessment guidance find that structured interviews tend to produce more reliable and valid assessments. Structure means comparable job-related questions and a clear scoring method, and interviewers can still sound like themselves while they run it.
Should every candidate be asked exactly the same questions?
Use the same core questions for candidates applying to the same role and stage. Interviewers can still clarify answers and ask natural follow-ups, as long as everyone gets a fair chance to show the same competencies.
How many questions should an interviewer ask?
For a 30- to 45-minute interview, three or four core questions usually leave enough time for follow-ups. Across the full process, cover the role's most important competencies without making candidates repeat the same evidence several times.
How should interview answers be scored?
Define what weak, partial, strong and exceptional evidence looks like before the interview. Score each answer against those anchors and keep the previous candidate out of it, along with whatever general impression the interviewer walked away with.
Does Metaview score or reject candidates?
No. Metaview captures and organizes evidence from the conversation and can draft the scorecard. Recruiters and hiring managers review the draft, apply the rubric and make every decision.
Sources and methodology
¹ Metaview platform research, 2026: a corpus of 5,519,828 captured conversations, including 5,207,185 candidate interviews. The 31.2% figure is the share of those interviews with at least one scorecard attached. The 41.9% figure is a separate measure covering 296,555 advances recorded in connected ATS data, so the two have different denominators. This research covers what happens inside the hiring process. It doesn’t track how people do once they’re hired, so nothing here is an outcome study.
² U.S. Office of Personnel Management, “Structured Interviews”: official guidance.
³ Sackett, Zhang, Berry and Lievens, “Revisiting meta-analytic estimates of validity in personnel selection” (2022): research record | SIOP summary.
