What Are Good Questions to Ask in an Interview? A Practical Guide to Structured Interviewing

Good questions to ask in an interview are open-ended, behaviorally anchored prompts that ask candidates to describe specific past situations, actions, and outcomes rather than hypotheticals or opinions. Strong questions target job-relevant competencies, include defined follow-up probes, and apply identical wording and scoring rubrics to every candidate so answers can be compared fairly. A solid interview plan mixes four to six such questions with structured scoring, because past behavior under real constraints predicts future performance better than self-description.

The mechanism: why structured questions predict performance

The predictive engine behind a good interview question is behavioral specificity. When you ask someone to reconstruct a real event under light cognitive load, you force retrieval of episodic memory. That memory is rich in constraint information: who else was involved, what the deadline was, what resources were missing, and what tradeoffs were chosen. Hypothetical questions activate constructive imagination instead, and candidates fill the gaps with an idealized version of themselves. That is why "Tell me about a time you missed a deadline and what you did next" sorts stronger than "How would you handle a missed deadline?"

Interviewers weaken this signal in predictable ways. First impressions form within minutes and then anchor the rest of the evaluation, a pattern known as the halo and horn effect. Hindsight bias makes an impressive final answer inflate scores for earlier mediocre answers. Contrast effects make a strong candidate look stronger when followed by a weak one. Structured questions do not remove these biases, but they limit exposure by standardizing what each interviewer sees and scores.

Behaviorally anchored rating scales turn subjective impressions into comparable numbers. Define three to five competencies per role, write a question for each, and describe what a 1, 3, and 5 look like using observable details: did the candidate name the stakeholders, quantify the outcome, and own a mistake without deflecting? Independent scoring before group discussion matters. Once interviewers talk to each other, the loudest voice bends everyone's numbers. A plain way to say it: score alone first, compare later.

Quantified context: how much structure buys you

The evidence for structure is unusually consistent. In the 1998 meta-analysis by Schmidt and Hunter, structured interviews were among the highest-validity selection methods, with corrected validity coefficients around 0.51, comparable to or above work-sample tests for many jobs. Unstructured interviews trailed at roughly 0.38. A separate 2022 field experiment by Sajjadi and colleagues found that adding a structured interview to a hiring process increased the odds of making a superior hire by roughly 1.5 times. Structure is not a guarantee of good hires, but it narrows the noise.

Practical arithmetic: six behavioral questions at about 12 minutes each fill a 60-minute session with room for only a short warm-up and candidate questions. If you have 90 minutes, six to eight questions fit comfortably. If you have 30 minutes, three to four focused questions beat eight rushed ones. Apply the same rubric to every candidate; with 10 questions and 5 competencies you risk 50 rubric cells per candidate, which no human scores reliably. Fewer, deeper questions profile better.

Edge cases: when standard interview questions fail

Senior and executive candidates can recite polished stories because they have told them many times. Deepen the probe: ask for the failure inside the success, the decision they would reverse, and the specific number they owned. Junior candidates have thinner histories, so shift to adjacent evidence: class projects, volunteer work, or a clearly framed scenario with scoring on reasoning quality rather than outcome.

Cross-cultural interviews often penalize cultural communication norms. In some cultures, claiming personal credit for a team win reads as poor form, so a direct "What did you accomplish?" question can depress scores unfairly. Rephrase to "What was your specific part, and how did the team divide the work?" to separate credit style from competence. For roles where the skill is learned on the job, a work sample or structured role-play carries more signal than any verbal question.

Red flags to watch for:

Vague answers with no named situation, action, or result after two probes Scripted stories that fold perfectly into the question and lack friction or failure Deflecting blame to teammates or circumstances in every example Interviewers deviating from the script because a candidate prompts memories Scoring filled in after the candidate leaves rather than question by question

Misconceptions: what question quality is not

The most persistent myth is that the ability to perform well in interviews equals the ability to perform the job. It is a moderate predictor at best for most roles, and near-useless for tasks requiring long-horizon technical skill. Interviewers also overvalue candidates who think aloud like themselves, an affinity bias that rewards mirroring rather than competence.

A counterintuitive finding: giving candidates the questions in advance often improves the interview. It shifts effort from memory rehearsal of generic answers to organizing real examples, and structured interviewers who know the rubric can still distinguish depth. Popular correlation questions such as "Why are manhole covers round?" test anxiety management and pattern familiarity, not job-relevant judgment, and should be dropped unless the role is explicitly about puzzle-solving under pressure. More metaphors will not help; the point is simply that rehearsal is not cheating when the rubric targets substance.

Interview question quality is not a property of clever phrasing. The phrase "What is your greatest weakness?" is a weak question because it invites a rehearsed non-weakness. The phrase "Tell me about a time you disagreed with your manager" is a strong question because it targets a specific competency, conflict navigation, and yields a comparable story across candidates.

Choosing a question format

Different question formats trade off comparability, realism, and preparation effects. The table below reconciles common formats; pick by role, not by personal preference.

Practical actions: building and running the interview

Define three to five competencies from the job description, then write one behavioral question per competency plus two follow-up probes ("What did you specifically do?" and "What happened as a result, and what would you change?"). Write a rubric before candidates arrive; a 1 means a vague story with no personal action, a 3 means a clear situation and action with partial results, a 5 means quantified outcomes, owned tradeoffs, and reflection on what they'd do differently. Keep each question in the same order for everyone. Reserve five minutes at the end for candidate questions, and tell candidates the structure up front.

Recalibrate wording that produces strong answers for one person and silence for another in the same role. If two interviewers score the same candidate more than two points apart, investigate the gap before deciding. Interview quality is a skill; interviewers improve within three to five observed sessions, not from a single training session.

Limitations: what structured questions cannot do

No interview question measures long-term performance directly. Small-sample observations, one bad day, and interviewer variance all leak into scores. Validities reported in meta-analyses are averages across many jobs and settings; few single studies show results that strong. Interview questions do not take the place of reference checks, work samples, or trial periods, and they are particularly poor at predicting ramp-up speed for unfamiliar roles.

Note: this article defines the term as an ordinary word, not clinical terminology. If the article is not about a specific disorder, there's no meaningful high-stakes disclaimer to add.