Behavioral questions are the single most predictive category of interview question. They cut through rehearsed answers and polished resumes by asking 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.

That said, most teams ask behavioral questions badly. They ask vague versions that produce vague answers, they don't follow up, and they rate responses on gut feel rather than evidence. Here's how to use them properly.

What is a behavioral interview question?

A behavioral interview question asks a candidate to describe a specific past situation, what they did in it, and what the outcome was. The format usually starts with "Tell me about a time when..." or "Give me an example of..."

The logic is simple. If you want to know whether someone can handle conflict, you don't ask them how they would handle conflict. You ask them to describe a specific time they did. The answer tells you far more, because they're describing something real that already happened.

A good behavioral question is specific enough to generate a concrete story, not a generic talking point. "Tell me about a time you had to give difficult feedback" is better than "Are you good at giving feedback?"

Why behavioral questions work

Three reasons.

First, they generate evidence. Hypothetical questions produce opinions. Behavioral questions produce stories with specifics you can evaluate.

Second, they're harder to fake. A candidate can rehearse generic answers about their "biggest strength" all day. It's much harder to invent a detailed, specific story about a time they actually did something, especially when you probe for follow-up details.

Third, they map directly to competencies. If you want to assess problem solving, you ask them to walk through a specific problem they solved. If you want to assess communication under pressure, you ask about a specific high-pressure communication. Every question connects to something you actually care about.

The STAR format (and why it matters)

Good behavioral answers follow a structure called STAR: Situation, Task, Action, Result.

Situation: the context, briefly
Task: what they needed to accomplish
Action: what they specifically did
Result: what happened because of it

You don't need to teach candidates this framework. Strong candidates tend to use it naturally. But you do need to listen for it. Answers that skip the Action section, or that slide into "we did this" instead of "I did this," are red flags. The candidate might have been in the room, but that's not the same as actively contributing.

When you're evaluating an answer, ask yourself: do I know what they specifically did? Not the team. Them. If the answer is vague, probe until it isn't.

How to write a good behavioral question

Three things separate a strong behavioral question from a weak one.

It targets a specific competency. Every behavioral question should connect to something in your [interview guide] that you actually need to evaluate. Don't ask about "a challenging situation" unless you know exactly why.

It asks for specifics. The word "time" is doing a lot of work in "tell me about a time when." Keep it. Avoid "Have you ever..." or "Do you usually..." which invite generic yes or no answers.

It's open enough to generate a real story. Questions that are too narrow restrict good candidates to weak examples. "Tell me about a time you gave difficult feedback" is better than "Tell me about a time you had to fire someone," because the latter assumes an experience not every candidate has had.

Behavioral interview questions by competency

Here are tested examples organized by the competencies you're most likely to be evaluating.

Problem solving and decision making

Tell me about a time you had to make a decision with incomplete information. What was the situation, and how did you decide?
Describe a time when you had to solve a problem that didn't have an obvious answer. Walk me through your approach.
Tell me about a decision you made that turned out to be wrong. What did you learn?

Communication and collaboration

Tell me about a time you had to give difficult feedback to a colleague. How did you approach it?
Describe a time you worked with someone whose style was very different from yours. How did you navigate it?
Walk me through a time you had to explain something technical to a non-technical audience.

Ownership and accountability

Tell me about a time you made a mistake that had real consequences. What did you do?
Describe a project where you took ownership of something outside your formal remit. Why and what happened?
Tell me about a time a project you were leading went off track. How did you respond?

Prioritization and execution

Describe a time you had 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 deliver under a tight deadline. What trade-offs did you make?

Handling conflict or pressure

Tell me about a time you disagreed with your manager. How did you handle it?
Describe a high-pressure situation at work. How did you manage it?
Tell me about a time you had to deliver bad news. How did you approach the conversation?

Learning and growth

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 do that?
Walk me through a time you were out of your depth. How did you handle it?

Common mistakes to avoid

Asking too many in one interview. Behavioral questions take time. Each one should get eight to twelve minutes including follow-ups. For a 45-minute interview, four or five questions is plenty.

Not following up. The first answer a candidate gives is rarely the most useful one. Follow up with "What specifically did you do?" or "What was the result?" or "What would you do differently now?" These probes are where the real insight comes from.

Accepting vague answers. If a candidate responds with "we decided" or "the team did," ask what they specifically did. If they can't answer, that tells you something.

Using the same questions for every role. Behavioral questions should map to the competencies of the specific role. A question that works for a sales hire might be irrelevant for an engineering hire. Tailor your question set.

Scoring based on how well the story was told rather than what the story actually demonstrates. Strong storytellers can make weak examples sound impressive. Focus your scoring on evidence of the competency, not on delivery.

Behavioral vs situational questions

A common point of confusion: what's the difference between behavioral and situational questions?

Behavioral questions ask about something that actually happened. "Tell me about a time you..."

Situational questions ask about a hypothetical. "How would you handle..."

Behavioral questions are more predictive and more reliable. Use them as the backbone of your interview. Situational questions are useful as a supplement when a candidate may not have direct prior experience with something, for example when interviewing early career candidates or someone switching industries. In those cases, a situational question lets you assess their reasoning even when the behavioral example isn't there.

For a fuller overview of how both fit into a structured interview, see What Is a Structured Interview? (And Why It Makes Hiring Better