A behavioral interview asks candidates to describe specific things they actually did in past work situations, rather than what they would do in hypotheticals. The premise is simple: past behavior predicts future behavior. If someone resolved a conflict well last year, they are more likely to resolve one well on your team. This guide covers what a behavioral interview is, how the STAR method works, sample questions by competency, and how to tell a real answer from a rehearsed one.
Key takeaways
- Behavioral interviews ask about specific past situations because how someone acted before is the strongest signal for how they will act again.
- STAR (Situation, Task, Action, Result) gives you a frame to probe: candidates use it to structure answers, you use it to check the answer is complete.
- Score answers on concrete detail (named people, real numbers, actual decisions) over polished generalities that could describe anyone.
- Behavioral prompts work well as one-way async video questions, letting you screen more candidates on the same competencies before booking live time.
What a behavioral interview is
A behavioral interview replaces hypothetical questions (What would you do if...) with evidence questions (Tell me about a time you...). Instead of testing how well someone imagines a situation, you are asking for a real event with a real outcome. The working theory is that past behavior predicts future behavior, so you gather concrete stories and judge the pattern behind them.
Your job as the interviewer is to pick the competencies that matter for the role, ask for a specific example of each, and then dig until you understand what the candidate personally did. Hypotheticals reward smooth talkers. Behavioral questions reward people who have actually done the work.
- Hypothetical: How would you handle a missed deadline? (easy to answer well, tells you little)
- Behavioral: Tell me about a deadline you missed and what you did next. (harder to fake, tells you a lot)
- Follow-up matters more than the opening question: What did you do, not the team? What would you change?
The STAR method
STAR is a four-part structure for a complete answer. Candidates use it to keep their story clear. You use it as a checklist: if a part is missing, ask a follow-up to fill it in.
- 1
Situation
The context. What was going on, when, and who was involved. Keep this short: enough to understand the stakes, not a full backstory.
- 2
Task
The specific responsibility or goal the candidate owned in that situation. This separates what they were accountable for from what the team did.
- 3
Action
What the candidate personally did, step by step. This is the core of the answer. Listen for I, not we, and push for the reasoning behind each decision.
- 4
Result
How it turned out, ideally with a concrete outcome (a number, a shipped feature, a resolved conflict) and what the candidate learned.
When an answer stalls, name the missing STAR part out loud. Ask what was your specific role there? for a vague Task, or how did that turn out? for a story with no Result. This keeps candidates on track without leading them to the answer you want.
Sample questions by competency
Pick three to five competencies that actually matter for the role and ask one behavioral question for each. Asking every candidate the same core set makes answers comparable.
| Competency | Example question |
|---|---|
| Teamwork | Tell me about a time you worked with someone whose working style clashed with yours. How did you get the work done? |
| Leadership | Describe a time you had to get people to follow a plan without having authority over them. |
| Conflict | Tell me about a disagreement with a coworker or manager. What did you do and how did it end? |
| Problem-solving | Walk me through a hard problem you solved where the answer was not obvious at first. |
| Adaptability | Tell me about a time priorities changed suddenly. How did you adjust? |
| Ownership | Describe a mistake you made at work. How did you handle it and what changed afterward? |
How to evaluate answers
The difference between a strong answer and a weak one is specificity. A strong answer has details only someone who lived it would know: the actual constraint, the real tradeoff, the name of the tool, the number that moved. A weak answer stays at the level of principles that would fit any story.
| Real specifics (score higher) | Vague generalities (score lower) |
|---|---|
| We were three weeks from launch with a broken payment flow | There was a challenging situation with a tight timeline |
| I rewrote the retry logic and cut failures from 8 percent to under 1 | I worked hard and improved things a lot |
| I disagreed with my manager, so I pulled the data and showed her the drop-off | I always try to communicate openly and align with stakeholders |
- Score after each answer against the same rubric so you are comparing candidates, not memories.
- Weight the Action most: it is what the candidate controlled and the best predictor of future behavior.
- Down-weight answers where the candidate only describes what the team did and never their own role.
- A learning or what they would change next time signals reflection, not just a rehearsed win.
Spotting rehearsed or fake answers
The fastest test for a rehearsed or invented story is an unscripted follow-up. Ask who else was in the room, what the other option was, or what you would do differently now. Real memories have texture and get more specific under questioning. Fabricated ones get vaguer, contradict earlier details, or slide back to generic principles.
A polished STAR answer is not a red flag on its own. Good candidates prepare, and structure is a skill. The concern is a story that sounds complete but has no verifiable detail. Probe one layer deeper and see whether the candidate can still answer concretely.
Behavioral questions as async screening
Behavioral prompts are a good fit for one-way (asynchronous) video interviews. You send a fixed set of Tell me about a time questions, candidates record answers on their own schedule, and you review them later. Because every candidate answers the same prompts, the responses are directly comparable, and you spend live interview time only on people who already showed real examples.
- Keep async sets to three or four questions so candidates stay focused and recordings stay reviewable.
- Tell candidates to use STAR in the instructions: it gets you fuller answers without a live prompt.
- Use async to screen breadth, then reserve live interviews for the deep follow-up questions that expose rehearsed stories.
Related guides
Situational Interview Questions: A Guide for Employers
How to use situational (hypothetical) interview questions to assess candidates: what they are, how they differ from behavioral questions, how to write and score them, and when to use them.
Read guidePanel Interview Guide for Employers
How to run an effective panel interview: pick the right panelists, split question areas, brief the group, and score independently before you discuss.
Read guideHow to Conduct a Phone Screen Interview
A practical guide to running an effective phone screen: what to prepare, a 15-to-30 minute structure, questions to ask, red flags to watch, and when to advance a candidate.
Read guide