Behavioral Interview Questions: 40 Examples by Competency
Written by
Daniel Kunz
I
Published on
I
10
MIN
Behavioral Interview Questions: 40 Examples by Competency
Behavioral interview questions are the backbone of a good interview. They're the questions that ask candidates to describe something they've actually done, not something they think they might do one day. Past behavior predicts future behavior, hypotheticals predict almost nothing.
This article is a working bank of 40 behavioral interview questions, organized by the competencies they're designed to assess. Use it like a menu. Pick five or six that map to the competencies that matter most for your role, build them into a structured interview guide, and ask the same questions to every candidate so you can actually compare answers.
A quick framing note before the list. Every question below starts with "tell me about a time" or "describe a situation" for a reason. That phrasing forces specificity. If you rephrase these as "how would you..." you've converted a behavioral question into a situational one, and you've lost most of the predictive value. Keep the "time" or "situation" in the question.
For more on why behavioral questions work and how to structure them, see [Behavioral Interview Questions: How to Use Them (With Examples)].
Problem solving and analytical thinking
Use these when the role requires working through ambiguity, breaking down complex problems, or making decisions with limited information.
Tell me about a time you had to make a decision with incomplete information. What was the situation, and how did you decide?
Describe the hardest problem you've solved in the last year. What made it hard?
Tell me about a time the obvious solution turned out to be the wrong one. What did you do?
Walk me through a time you had to dig into a problem that wasn't originally yours to solve.
Describe a situation where you realized your initial approach was wrong halfway through. How did you handle it?
Tell me about a time you spotted a problem that nobody else had noticed. What happened?
Describe a time you had to balance competing priorities with limited resources. How did you decide?
What to listen for: Structured reasoning. Strong candidates walk you through how they defined the problem, what options they considered, what trade-offs they made, and what they'd do differently now. Weak candidates describe outcomes without showing their thinking.
Communication and collaboration
Use these when the role involves working closely with others, especially across functions, seniority levels, or personality types.
Tell me about a time you had to give difficult feedback to a colleague. How did you approach it?
Describe a situation where you had to work closely with someone whose style was very different from yours.
Walk me through a time you had to explain something complex to a non-technical audience.
Tell me about a time you disagreed with a teammate about something important. How was it resolved?
Describe a time you took the effort to understand someone else's perspective before pushing your own.
Tell me about a time you had to communicate a decision you didn't fully agree with.
What to listen for: Whether they take ownership of the communication itself, not just the outcome. Strong candidates describe what they specifically did, how the other person responded, and what they learned about working with different styles.
Ownership and accountability
Use these for any role where you need someone who takes real responsibility for outcomes, not just tasks.
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.
Tell me about a time you delivered something that didn't meet your own standards. What did you do?
What to listen for: Specifics. "We made a mistake" is not an answer. "I missed a deadline because I underestimated the complexity, and here's what I did to recover and prevent it happening again" is. Watch for candidates who blame circumstances or teammates without acknowledging their own role.
Prioritization and execution
Use these when the role demands judgment about what to do, what to cut, and what to ship.
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?
Describe a time you had to cut scope on a project. How did you decide what to remove?
What to listen for: Judgment. Senior candidates can articulate why they cut scope and what they traded off. Junior candidates often describe trying to do everything and burning out, which is also useful signal.
Learning and self-awareness
Use these to separate candidates who've actually grown from candidates who've just accumulated 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.
Tell me about a time you asked for help when you realized you needed it.
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, or they describe setbacks entirely caused by other people.
Handling pressure and conflict
Use these for roles involving stakeholders, deadlines, difficult conversations, or high-stakes moments.
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 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?
Tell me about a situation where you had to stay calm while things were falling apart.
What to listen for: Composure in the retelling, ownership of their role in the situation, and evidence they learned something rather than just survived.
Initiative and drive
Use these when you need someone who moves things forward without waiting to be asked.
Tell me about a time you saw something that wasn't working and fixed it without being asked.
Describe a project you started that nobody told you to start. What was the outcome?
Walk me through a time you went beyond your job description because you thought it was the right thing to do.
What to listen for: Evidence of genuine initiative, not just willingness to do extra work. Strong candidates can explain why they decided something was worth doing, not just what they did.
How to pick the right questions for your role
Don't ask all 40 questions. You'd be interviewing for three hours and none of your hiring managers would put up with it.
The goal is to pick five to eight questions that map to the three to five competencies that matter most for the role. Here's a rough guide for which questions to pick depending on the role type.
Individual contributors: Lean heavily on problem solving (1 to 7), ownership (14 to 19), and execution (20 to 25). One or two learning questions (26 to 31) round it out.
People managers: Add communication and collaboration (8 to 13), pressure and conflict (32 to 37), and at least one initiative question (38 to 40). You need all six categories covered.
Senior leaders: All six categories, with emphasis on ownership, pressure and conflict, and learning. Senior leaders should be able to tell stories about big mistakes and what they learned. If they can't, that's a red flag.
Early career candidates: Focus on learning (26 to 31), communication (8 to 13), and initiative (38 to 40). Go lighter on ownership and pressure questions, which often don't have the career length to draw on. Pair with a few situational questions if needed.
The follow-up questions that matter most
A behavioral question without follow-ups is only half the conversation. The first answer is rarely the most useful one.
The three follow-ups that unlock the most signal are:
"What did you specifically do?" When candidates describe "we" too much, this question separates the people who did the work from the people who were in the room.
"What was the result?" Strong answers include outcomes. Weak answers tail off without telling you what actually happened.
"What would you do differently now?" This is where self-awareness shows up. Candidates who've genuinely reflected on the situation have a thoughtful answer. Candidates who haven't either say "nothing" or give a non-answer.
One note. If a candidate consistently struggles to give specific, detailed answers even after follow-ups, that's signal too. Sometimes the issue isn't the question, it's that the candidate hasn't actually done the thing they're describing.
Build your interview guide
This list is a starting point, not a finished interview. The real work is picking the right questions for your role, writing down what a strong and weak answer looks like for each, and using the same guide for every candidate so you can score consistently.
The fastest way to do that is with a structured interview guide. See [How to Write an Interview Guide (With a Free Template)] for the full walkthrough, or jump straight into building one.
