I once spent an entire Sunday night building a spreadsheet of 73 interview questions. Color-coded by category. Cross-referenced with competencies. Hyperlinked to Harvard Business Review articles I'd skimmed but not read. Monday morning I walked into a panel interview, forgot the spreadsheet existed, and asked the candidate "So, tell me about yourself" like every other unprepared interviewer in the history of hiring.
That spreadsheet is still on my Google Drive. Unopened since 2019. RIP.
Here's what I learned from that experience and about a dozen since: the best interview questions to ask candidates aren't the ones you collect. They're the ones you actually use, consistently, with a plan for how to score the answers.
Five questions asked the same way every time will outperform 73 color-coded questions asked differently to each person.
The problem with "best interview questions" lists
Google "best interview questions" and you'll get a wall of listicles. Fifty questions here. A hundred there. Organized by category if you're lucky. No context on when to use them, what a good answer sounds like, or how to compare answers across candidates.
These lists treat interviewing like a trivia game. Pick the cleverest question, and the right candidate will reveal themselves. But clever questions produce interesting conversations, not useful data. You need the same questions, asked the same way, every time.
Schmidt and Hunter's meta-analysis of 85 years of personnel selection research found that structured interviews are 2x more effective at predicting position performance than unstructured conversations. Structure explained the entire difference.
You know how this goes. Monday you have a plan. By Thursday afternoon, four phone screens deep, you're asking the basics just to get through the call in 10 minutes. Thirty screening interview questions on your list, no rubric for any of them. So you wing it. Every candidate gets a different version of you.
Most interview questions for employers fail because they're conversation starters with no scoring system behind them.
What makes an interview question actually useful
A good question does three things. It tests something specific. It produces comparable answers across candidates. And it reveals past behavior, not hypothetical thinking.
That last part matters most. "Tell me about a time you disagreed with your manager" forces someone to pull from real experience. "What would you do if you disagreed with your manager?" lets them perform. The behavioral version is harder to fake and easier to score. This is the foundation of behavioral interview questions that actually tell you something.
Here's a quick filter for bad questions. If the question is hypothetical, it tests imagination, not experience. If it's leading ("You're a team player, right?"), it tests compliance. If it's vague ("Tell me about your culture"), it tests storytelling ability. If it's a brain teaser ("How many golf balls fit in a school bus?"), it tests nothing relevant at all.
Good interview questions are boring. They sound the same every time. That's the point. The consistency is what makes the data useful. You're not looking for the most interesting conversation. You're looking for comparable evidence across candidates so you can make an actual decision.
The best interview questions to ask candidates (by what they test)
Most lists organize questions by format (behavioral, situational, technical). That's backwards. You should organize by what you're trying to learn. Here are the competency areas that matter for most positions, with questions that actually produce useful answers.
Problem-solving and critical thinking
Ask: "Tell me about a time you had to solve a problem with incomplete information. What did you do?"
Ask: "Describe a situation where you identified a problem before anyone else noticed it."
These test whether someone can reason through ambiguity, not whether they can recite a framework. A strong answer includes the specific constraints they faced and the tradeoffs they considered. Watch for red flags: candidates who only describe problems they solved perfectly, with no mention of uncertainty or mistakes. Real problem-solving is messy. Clean narratives are rehearsed ones.
If you're hiring for entry-level positions, you can adjust the scope. "Tell me about a time you figured something out without being taught" works for candidates without years of professional experience.
Collaboration and teamwork
Ask: "Tell me about a time you worked with someone whose approach was very different from yours."
Ask: "Describe a situation where a team project wasn't going well. What role did you play in turning it around?"
These reveal how someone actually operates in a group, not how they think they operate. A strong answer names the other person's perspective without dismissing it. The red flag: candidates who position themselves as the hero who saved the team from everyone else's mistakes. Every time.
Ownership and accountability
Ask: "Tell me about a time you made a mistake at work. How did you handle it?"
Ask: "Describe a project where the outcome didn't meet expectations. What would you do differently?"
Ownership questions separate candidates who learn from those who deflect. A strong answer describes the mistake clearly, without minimizing it, and explains what changed as a result. The red flag: "I can't really think of one" or blaming external factors for every outcome.
Communication
Ask: "Tell me about a time you had to explain something complex to someone without your expertise."
Ask: "Describe a situation where miscommunication caused a problem. How did you resolve it?"
Communication questions are especially useful for positions where the candidate will work across teams or interact with customers. A strong answer shows awareness of the audience. The red flag: long, rambling answers that ironically demonstrate the exact problem the question is designed to surface. You can also test communication directly through one-way interview questions where candidates record their responses on camera.
Role-specific motivation
Ask: "What specifically about this position caught your attention?"
Ask: "What's the most interesting problem you've solved in your last role that relates to this work?"
Motivation questions reveal whether someone has done their homework on your company or is just applying broadly. A strong answer references something specific about the position or team. The red flag: generic answers that could apply to any company in your industry.
Adaptability and resilience
Ask: "Tell me about a time your priorities shifted unexpectedly. How did you adjust?"
Ask: "Describe a period when you were under more pressure than usual. What did you do?"
These matter more now than they did five years ago. Roles change faster. A strong answer shows the candidate recognizing the shift, adjusting their approach, and not pretending the disruption didn't bother them. The red flag: "I thrive under pressure" with no supporting evidence.
Questions you should stop asking
Some interview questions have been around so long that nobody questions whether they work. They don't.
"Where do you see yourself in five years?" This tests rehearsal ability. Candidates who've prepped will give a polished non-answer. Candidates who haven't will fumble. Neither response tells you anything about their actual ambition or fit. Ask instead: "What kind of work do you want to be doing more of?" That's specific enough to produce a real answer.
"What's your biggest weakness?" Everyone has a canned response. "I'm a perfectionist" is the hiring equivalent of a laugh track. You already know it's coming. Ask instead: "Tell me about a skill you've had to actively work on improving." This gets at self-awareness without the theater.
"Why should we hire you?" This puts the candidate in sales mode. You learn who's good at pitching, not who's good at the position. Ask instead: "Based on what you know about this role, what would you focus on in your first 90 days?" This tests whether they've thought about the actual work.
"Tell me about yourself" (without framing). Too open-ended. Wastes the first three minutes of your interview while the candidate figures out what you're actually asking. Frame it: "Walk me through how you ended up in this line of work and what you're looking for next." Same spirit, better signal.
These are common interview mistakes that even experienced hiring managers make. Clearer questions fix all of them.
Structure matters more than the questions themselves
You could use every question in this article and still make bad hires if you skip the structure. Consistency is what changes everything. Same questions, same order, same scoring criteria for every candidate.
An interview scorecard changes the entire dynamic. Instead of walking out of an interview with a gut feeling, you walk out with ratings against specific criteria you defined before the first candidate showed up. As one recruiting lead we spoke with put it: "Structured screening reduces bias. Don't make it about DEI. Make it about consistency."
The stakes are real. The U.S. Department of Labor estimates the cost of a bad hire at 30% of first-year wages. SHRM puts average cost per hire at $4,700. And 75% of employers admit they've hired the wrong person. Most of those bad hires aren't from asking bad questions. They're from inconsistent evaluation. One interviewer loved the candidate's energy. Another thought they talked too much. Nobody scored against the same criteria.
This is where how to screen candidates effectively starts to matter. Tools like one-way interviews let you standardize screening at scale. Platforms like Truffle let you set your screening questions once, then have every candidate answer the same questions on their own time. AI transcribes and scores each response against your criteria, so you're comparing apples to apples instead of relying on memory from five back-to-back phone screens.
You can also layer in hiring assessments and candidate assessments to capture signals beyond what interview answers alone can provide. The goal is better evidence at each step, not more steps.
Frequently asked questions about interview questions
How many interview questions should I ask?
Five to seven per interview is the sweet spot. Enough to cover your key competencies. Few enough to actually listen to the answers. If you're asking 15+ questions, you're not interviewing. You're speed-running a checklist. Start with pre-screening interview questions to handle the basics before the live conversation, and save your structured questions for the deeper evaluation.
What's the difference between behavioral and situational interview questions?
Behavioral questions ask about past experiences: "Tell me about a time when..." Situational questions ask about hypothetical scenarios: "What would you do if..." Both have value, but behavioral questions are stronger predictors of future performance. Many interviewers evaluate behavioral answers using the STAR method (Situation, Task, Action, Result) or the similar SAR method (Situation, Action, Result) to check whether candidates give specific examples with clear outcomes. Use situational questions sparingly, and pair them with behavioral ones. See our guide to situational interview questions for examples.
Should I ask every candidate the same questions?
Yes. This is the single highest-leverage change you can make. Asking different candidates different questions makes comparison nearly impossible. You end up choosing based on vibes, not evidence. Same questions, same order, same rubric. Every time. Interview training for your hiring managers can help make this stick.
How do I evaluate interview answers consistently?
Build a rubric before you start interviewing. For each question, define what a strong answer includes, what an acceptable answer looks like, and what counts as a red flag. Score each answer on a 1-4 scale during the interview, not after. Waiting until later means you're scoring from memory, and memory is biased toward whoever you talked to last. Use knockout questions for must-have qualifications, and save nuanced evaluation for your structured interview questions.
Should I ask "why do you want to work here" and "what's your greatest strength"?
Both questions get rehearsed answers. "Why do you want to work here" usually produces a summary of your About page. "Greatest strength" gets "I'm a team player" or "leadership skills" with no supporting detail. If you want to understand motivation, ask candidates what they know about your company culture, work environment, or company values and what specifically appeals to them. If you want to assess strengths, ask for a specific example from their work experience where that strength made a measurable difference.
How should I ask about a candidate's previous position?
Candidates will narrate their current job or past job in the best possible light. Instead of "why are you leaving your previous job," ask what they wish they could change about their current role. This gets at real dissatisfaction without putting them on the defensive. You can also ask what part of the job description excited them most, which tells you whether they've actually read it and whether their experience at their last position maps to what you need.
Should I ask about career goals in an interview?
Career goals questions can be useful if you frame them well. "Where do you see yourself in five years" produces rehearsed answers about future goals and greater responsibility. "What does your ideal career path look like over the next few years" is slightly better because it invites honesty about career development instead of performance. The best version: "What kind of work do you want to do more of, and what do you want to stop doing?" This tells you whether the position actually fits their trajectory.
Should I ask about salary expectations?
Address salary range early. Ideally in a pre-screening interview or even the job description itself. Waiting until a final round to discover a mismatch on salary expectations wastes everyone's time. State your range, ask if it works. Move on. This isn't a question that benefits from clever phrasing.
What questions should I expect candidates to ask me?
Strong candidates will ask about management style, professional development opportunities, team structure, and next steps in the hiring process. If a candidate asks "do you have any questions for me" and gets silence back, that's a signal too. Prepare to answer questions about the day-to-day work environment and what success looks like in the first six months. The quality of a candidate's questions often tells you more than their answers to yours.
How should the interview process handle follow-ups and next steps?
Communicate the next step and timeline before the candidate leaves the interview. Candidates who've done a mock interview, prepared thoughtfully, and shown up ready deserve to know when they'll hear back. Send a brief thank you or acknowledgment within 24 hours, even if it's automated. A thank you letter from the candidate is a nice signal of professionalism, but don't use it as a screening criterion. Focus your evaluation on the structured scores, not the follow-up email.
.png)
