Leading questions in interviews: 30 examples and neutral rewrites
On this page
- Why does question wording matter so much?
- Six wording faults at a glance
- Leading questions: 7 rewrites
- Assumptive questions: 5 rewrites
- Closed questions: 5 rewrites
- Double-barreled questions: 4 rewrites
- Answer built into the question: 4 rewrites
- Hypothetical when you meant past behavior: 5 rewrites
- When is a closed question the right one?
- Leading questions in reference checks
- How do you check your own questions for leading wording?
- Questions people ask
A leading question signals the answer the interviewer wants, such as "You're comfortable working under pressure, right?", so the candidate's yes tells you nothing. The fix is to take the answer out of the question and ask for a specific example: "Tell me about the last time you had to deliver under real time pressure. What did you do?" Leading questions are one of six common wording faults, alongside assumptive, closed, double-barreled, multiple-choice and hypothetical questions. Below are all six with 30 before-and-after rewrites and a quick test you can run on your own interview kit.
This page is about how questions are worded. Which topics are off-limits altogether, such as age, family or religion, is covered in illegal interview questions, and the wider list of interviewer habits is in common interviewer mistakes.
Why does question wording matter so much?
The wording of a question changes the answer. In a classic study, Loftus and Palmer (Journal of Verbal Learning and Verbal Behavior, 1974) showed people the same film of a car accident and found that asking how fast the cars were going when they "smashed" into each other produced higher speed estimates than asking about when they "hit" each other. Interviews are not eyewitness testimony, but the lesson carries over: a candidate answering a loaded question is partly answering your wording.
Leading questions also tend to come from interviewers who have already made up their minds. A field study of 79 recorded interviews by Dougherty, Turban and Callender (Journal of Applied Psychology, 1994) found that interviewers behaved in ways that confirmed their first impressions, and gathered less information from applicants they had viewed positively. Neutral wording is one of the few defenses against that.
Six wording faults at a glance
| Fault | What it sounds like | Why it fails | Fix |
|---|---|---|---|
| Leading | "…right?", "I'm sure you…", "So you'd say…" | The candidate hears the answer you want | Ask for an example |
| Assumptive | "How did you deal with your difficult manager?" | Presumes a fact the candidate never stated | Ask whether, then how |
| Closed | "Do you like working in teams?" | A yes or no is not evidence of a skill | Ask how, what or tell me about |
| Double-barreled | "How do you plan and prioritize, and what tools do you use?" | Candidates answer the easier half | One question at a time |
| Answer built in | "Would you escalate or handle it yourself?" | Offers a menu, often with a right option | Leave the options out |
| Hypothetical by mistake | "What would you do if a project slipped?" | Gets intentions when you wanted past behavior | "Tell me about a time…" |
Leading questions: 7 rewrites
| Before | After |
|---|---|
| 1. "You're comfortable with ambiguity, right?" | "Tell me about a project where the goal changed partway through. What did you do?" |
| 2. "I'm sure you've managed difficult clients before." | "Tell me about the most difficult client relationship you've managed." |
| 3. "So you'd say you stayed calm?" | "How did you respond in that moment?" |
| 4. "You'd agree attention to detail matters in this job?" | "Tell me about a time an error of yours reached someone else. How was it caught?" |
| 5. "We move fast here. You'd be fine with that?" | "Describe the pace at your last job. What worked for you about it, and what didn't?" |
| 6. "Great answer. And I bet the team loved it?" | "How did the team react?" |
| 7. "You left because of the restructuring, I assume?" | "What led you to leave that role?" |
Number 6 is the subtle one: praise between questions tells the candidate what is landing, and every later answer bends toward it. Keep reactions neutral until the interview is over.
Assumptive questions: 5 rewrites
| Before | After |
|---|---|
| 8. "How did you deal with your difficult manager?" | "Tell me about your working relationship with your last manager." |
| 9. "Why did your last project fail?" | "How did your last project turn out?" |
| 10. "What made you want to leave sales?" | "Tell me about the move from sales to operations. How did it come about?" |
| 11. "How much of the team's work did you end up redoing?" | "How did you check the quality of the team's work?" |
| 12. "When did you realize the role wasn't for you?" (about a short stint) | "Tell me about your time at that company and why it ended when it did." |
Short tenures attract assumptive questions more than anything else; neutral wording for those is in how to interview candidates with short tenures.
Closed questions: 5 rewrites
| Before | After |
|---|---|
| 13. "Do you like working in teams?" | "Tell me about a team you worked in that worked well. What was your part in that?" |
| 14. "Are you good with Excel?" | "What's the most complex thing you've built in a spreadsheet? Walk me through it." |
| 15. "Have you handled complaints?" | "Tell me about the last complaint you handled from start to finish." |
| 16. "Did the launch go well?" | "How did the launch go, and how did you measure it?" |
| 17. "Is feedback important to you?" | "Tell me about the most useful feedback you've had. What did you change?" |
Double-barreled questions: 4 rewrites
| Before | After |
|---|---|
| 18. "How do you plan and prioritize your work, and what tools do you use?" | "How did you decide what to work on first last week?" Then, separately: "What do you use to keep track?" |
| 19. "What were your strengths and weaknesses in that role?" | Two questions, with an example asked for in each. |
| 20. "Why did you choose that approach and was it successful?" | "Why that approach?" Then: "What happened?" |
| 21. "Tell me about your experience with budgets and forecasting and reporting." | "Tell me about the largest budget you were responsible for." Follow-ups on forecasting and reporting as separate probes. |
Answer built into the question: 4 rewrites
| Before | After |
|---|---|
| 22. "Would you escalate to your manager or handle it yourself?" | "What would you do?" (and let them choose) |
| 23. "Do you prefer leading or following?" | "Tell me about a time you took the lead without being asked." |
| 24. "Were you more on the strategy side or the execution side?" | "What did a typical week in that role involve?" |
| 25. "Is it collaboration or speed that matters most to you?" | "What makes a team effective, in your experience? Give an example." |
Hypothetical when you meant past behavior: 5 rewrites
| Before | After |
|---|---|
| 26. "What would you do if a project slipped?" | "Tell me about a project that slipped. What did you do?" |
| 27. "How would you handle a disagreement with a colleague?" | "Tell me about a recent disagreement with a colleague." |
| 28. "How would you give feedback to a peer?" | "Tell me about the last time you gave a peer difficult feedback." |
| 29. "What would you do if you made a mistake?" | "Tell me about a mistake you made and how you found out." |
| 30. "How would you deal with a heavy workload?" | "Tell me about your busiest month in the last year. How did you manage it?" |
Hypotheticals are not wrong in themselves. For candidates without relevant experience, a deliberately written scenario with anchors is the right tool; see situational interview questions with a scoring rubric. The fault is asking "what would you do" by accident when the candidate has done the work.
When is a closed question the right one?
- Confirming a stated requirement: "The role needs a commercial driver's license. Do you hold one?"
- Confirming the posted schedule: "The role includes two Saturday shifts a month. Can you work that schedule?" Ask it the same way for everyone, and do not ask why someone cannot.
- Checking a fact: "Were you there until 2024?"
- Checking understanding: "Let me check I have this right: you rebuilt the report yourself, and your manager presented it. Is that right?" A summary check confirms what you will write down; it is not a way to add evidence the candidate did not give.
Leading questions in reference checks
Referees are even more eager to agree than candidates. "She's very reliable, isn't she?" will get a yes from almost anyone. Ask "How would you describe her reliability? Can you give me an example?" and "What would she need from her next manager to do her best work?" More wording in the candidate reference call script.
How do you check your own questions for leading wording?
- Search the kit for tell-tale phrases: "right?", "isn't it", "I assume", "I'm sure", "so you'd say", "would you agree", "or".
- Apply the guessing test: could a candidate work out the "right" answer from the wording alone? If yes, rewrite it.
- Count the questions in each sentence. More than one question mark, or an "and" joining two asks, means a double-barreled question.
- Read your own transcript or notes. Follow-ups are where leading creeps in, especially after an answer you liked.
- Ask a colleague to sit in with a checklist; see interviewer shadowing and how to evaluate your interviewers.
Fixing the wording once, in a shared kit that every interviewer reads from, does more than any amount of individual training; that is the core of a structured interview.
Questions people ask
What is an example of a leading question in a job interview?
"You're comfortable managing difficult stakeholders, right?" is a leading question: it tells the candidate the answer you want, so a yes tells you nothing. A neutral version asks for evidence instead: "Tell me about a time a stakeholder pushed back hard on your work. What did you do?"
Why are leading questions bad in interviews?
They produce agreement instead of evidence. Candidates want to give the answer the interviewer seems to want, so the reply reflects the wording of the question rather than what the candidate has done. They also tend to come from an interviewer who has already formed a view, which turns the interview into confirming a first impression.
Are closed questions always bad in an interview?
No. Closed questions are right for confirming facts and stated requirements, such as whether the candidate holds a license the job requires or can work the posted schedule, as long as every candidate is asked the same way. They are the wrong tool for assessing skills or judgment, where you need an example.
How do you rephrase a leading question?
Remove the answer from the question. Replace "right?", "I assume" and "so you would say" with an open request for a specific example: "Tell me about a time…", "How did you…", "What happened when…". Ask one thing at a time, and ask about what the candidate did rather than what they would do when you want evidence of past behavior.