The Best Interview Questions to Ask Every Candidate

Most interviews have a handful of great questions hidden inside a lot of filler.

"Tell me about yourself" eats ten minutes and tells you what's on the resume. "What's your biggest weakness" gets a rehearsed answer. "Where do you see yourself in five years" gets a different rehearsed answer. By the time you've gotten through the warm-up questions, you have 20 minutes left and you still haven't asked anything that actually predicts whether the candidate will do the job well.

This article is a curated set of interview questions that actually tell you something useful. They're organized by what you're trying to assess, so you can mix and match depending on the role. Most of them are behavioral, a few are situational, and none of them are "if you were a tree, what kind of tree would you be."

A quick note before the list: the best interview questions only work inside a [structured interview]. Ask the same questions to every candidate for the same role, use a scoring rubric, and compare scores in a debrief. A great question asked inconsistently still produces inconsistent hiring decisions.

Questions to assess problem solving

These questions reveal how a candidate thinks through complexity. Listen for structured reasoning, the ability to break down ambiguity, and awareness of trade-offs.

• Tell me about a time you had to make a decision with incomplete information. How did you approach it?

• Walk me through the hardest problem you've solved in the last year. What made it hard?

• Describe a time when the obvious solution to a problem turned out to be wrong. What did you do?

• Tell me about a time you had to dig into a problem that wasn't originally yours to solve.

• Describe a situation where you had to balance competing priorities with limited resources.

What to listen for: Clarity of thought, ability to articulate the trade-offs they considered, and a sense of whether they actually solved the problem versus just described one.

Questions to assess communication and collaboration

These surface how candidates work with other people, especially under pressure or across differences.

• Tell me about a time you had to give difficult feedback to a colleague. How did you approach it?

• Describe a time you disagreed with a teammate about something important. How did it resolve?

• Walk me through a time you had to explain a complex topic to a non-technical audience.

• Tell me about a time you had to work closely with someone whose style was very different from yours.

• Describe a situation where you took the time to understand someone else's perspective before pushing your own.

What to listen for: Whether they take ownership of the communication, not just the outcome. Strong candidates describe what they did specifically, not what "the team" decided.

Questions to assess ownership and accountability

These separate people who do their jobs from people who take real responsibility for outcomes.

• Tell me about a mistake you made that had real consequences. What did you do?

• Describe a project where you took ownership of something outside your formal role.

• Tell me about a time a project you were leading went off track. How did you respond?

• Walk me through a situation where you realized you were wrong about something important.

• Describe a time you pushed back on a decision from someone more senior than you.

What to listen for: Specifics. "We made a mistake" is not an answer. "I missed a deadline because I underestimated X, and here's what I did about it" is.

Questions to assess prioritization and execution

These reveal whether a candidate can actually get things done, not just plan them.

• Describe a time you had significantly more work than you could realistically complete. How did you prioritize?

• Tell me about a time you pushed back on a request because it wasn't the right use of your time.

• Walk me through a time you had to ship something under a tight deadline. What trade-offs did you make?

• Describe a situation where you said no to something important in order to say yes to something more important.

• Tell me about a time you shipped something you knew was imperfect. Why did you decide to ship?

What to listen for: Judgment. Senior people know when to push back, when to cut scope, when to ship. Junior people often try to do everything.

Questions to assess learning and self-awareness

These separate candidates who've actually grown from candidates who've just accumulated job titles.

• Tell me about a time you received feedback that was hard to hear. What did you do with it?

• Describe a skill you've deliberately developed in the last year. What drove you to invest the time?

• Walk me through a time you were out of your depth. How did you handle it?

• Tell me about a time your thinking on something important changed. What changed it?

• Describe something you used to believe strongly about your work that you no longer believe.

What to listen for: Genuine reflection. Strong candidates can articulate what they got wrong, what they learned, and how they'd approach it differently. Weak candidates describe perfect trajectories with no real setbacks.

Questions to assess motivation and role fit

These go beyond "why do you want this job" and get at what actually drives the candidate.

• What drew you specifically to this role, as opposed to others you're looking at?

• Tell me about the work you've enjoyed most in your career. What made it so satisfying?

• Describe a project or role that drained you. What was it about it that didn't work?

• What do you want the next step in your career to teach you?

• If you joined this team, what's the first thing you'd want to understand?

What to listen for: Specificity. Candidates who've actually thought about this role give specific, grounded answers. Candidates who are applying broadly give generic ones.

Questions to assess high-pressure and conflict situations

These matter for any role involving stakeholders, deadlines, or ambiguity, which is most of them.

• Tell me about the most stressful work situation you've been in. How did you manage it?

• Describe a time you had to deliver bad news to someone. How did you handle the conversation?

• Tell me about a conflict you've had with a manager. How did it play out?

• Walk me through a time when a customer, client, or stakeholder was unhappy with you. What did you do?

• Describe a time you made a judgment call that others disagreed with. What happened?

What to listen for: Composure in the retelling, genuine ownership of their role in the situation, and evidence they learned something.

Questions to ask at the end of every interview

These aren't behavioral questions but they're often the most useful part of the conversation.

• What questions do you have for me?

• Is there anything I haven't asked that you think I should have?

• Is there anything about your background I should understand better?

• Based on what you know about the role now, what are your questions or concerns?

What to listen for: The quality of the candidate's questions. Strong candidates ask sharp, specific questions about the role, the team, and the challenges. Weak candidates ask generic questions they could have googled, or don't have any questions at all.

Questions you should stop asking

A quick list of questions that sound like interview questions but don't actually tell you anything useful.

• "Tell me about yourself." Eats time. The resume already answers this.

• "What's your biggest weakness?" Produces rehearsed non-answers.

• "Where do you see yourself in five years?" Same. Most candidates give the answer they think you want to hear.

• "Why should we hire you?" Tests how comfortable candidates are selling themselves, which isn't usually what the role requires.

• "If you were an animal, what would you be?" Nothing. It tests nothing.

If your interview is only 45 minutes, filler questions actively prevent you from asking the ones that matter.

How to use these questions well

A handful of practical points.

Don't ask too many. Eight to twelve minutes per question including follow-ups. For a 45-minute interview, four or five questions is plenty. Quality of answer beats quantity of questions.

Always follow up. The first answer is rarely the most useful one. "What did you specifically do?" "What was the result?" "What would you do differently now?" That's where the real signal comes from.

Use a scoring rubric. For every question, know what a strong answer versus a weak answer looks like. Without a rubric, scoring is just gut feel.

Map questions to competencies. Every question should assess something you actually care about for this role. If you can't articulate why you're asking a question, cut it.

For a deeper dive on how to set up structured interviews and evaluate answers consistently, see What Is a Structured Interview? (And Why It Makes Hiring Better) and How to Write an Interview Guide (With a Free Template).

Build your question set

The fastest way to go from "here's a list of good questions" to "here's our actual interview process for this role" is an interview guide. Pick the five or six questions from this list that best match the competencies for your role, write down what a strong answer looks like, and use the same guide for every candidate.