An interview technique that asks candidates to describe past situations to predict how they will behave in similar future scenarios, based on the principle that past behavior is the best predictor of future performance.
Key Takeaways
A behavioral interview is a structured interviewing technique where candidates are asked to describe real situations from their past work experience. Instead of asking "What would you do if a project went off track?" a behavioral interviewer asks "Tell me about a time when a project you were managing went off track. What happened, and what did you do?" The approach was developed in 1982 by industrial psychologist Tom Janz, based on the premise that the best predictor of future behavior is past behavior in similar circumstances. Research has consistently supported this. A meta-analysis by Schmidt and Hunter found that structured behavioral interviews predict job performance significantly better than unstructured interviews, reference checks, or years of experience alone.
Hypothetical questions ("What would you do if...") test a candidate's ability to imagine the right answer. Behavioral questions test what they actually did when faced with a real challenge. The difference matters. People are remarkably good at describing ideal behavior in theory. They're less consistent when recalling what they actually did under pressure, with limited information, or with competing priorities. Behavioral responses also give interviewers verifiable data. If a candidate says they led a cross-functional project that increased revenue by 15%, that claim can be reference-checked.
Traditional interviews tend to rely on resume walkthroughs, hypothetical scenarios, and conversational rapport. They feel more natural but produce less useful data. Two interviewers can walk away from the same traditional interview with completely different assessments because they focused on different things. Behavioral interviews standardize the process. Every candidate gets the same questions tied to the same competencies, and every answer is evaluated against the same criteria. This makes comparisons between candidates much more reliable.
STAR is the backbone of behavioral interviewing. It provides structure for both the interviewer (who uses it to probe for complete answers) and the candidate (who uses it to organize their response). Each letter represents one component of a complete behavioral answer.
Don't expect candidates to deliver perfectly structured STAR responses unprompted. Your job is to guide them through each component. If a candidate gives a vague situation, probe: "Can you be more specific about when this happened and what was at stake?" If they skip the action: "Walk me through exactly what you did, step by step." If they omit the result: "What was the outcome? How did you measure success?" Good behavioral interviewers spend 70% of their time listening and 30% probing for missing STAR components.
STAR isn't the only behavioral framework. SPAR (Situation, Problem, Action, Result) and CAR (Challenge, Action, Result) are variations. SPAR works well for problem-solving questions because it emphasizes the problem rather than the task. CAR is simpler and works for candidates who struggle with the Situation/Task distinction. The underlying principle is the same: get specific past examples with clear actions and measurable outcomes.
| Component | What It Means | What the Interviewer Listens For | Red Flag if Missing |
|---|---|---|---|
| Situation | The context and background of the experience | Specificity: when, where, who was involved, what was at stake | Vague or generic setup that could apply to any role |
| Task | The candidate's specific responsibility or objective | The candidate's individual role, not just what the team did | Unclear ownership or shifting between "I" and "we" without distinction |
| Action | The specific steps the candidate took | Decision-making process, skills applied, obstacles overcome | Jumping straight to the result without explaining how they got there |
| Result | The outcome and impact of the candidate's actions | Quantifiable outcomes, lessons learned, business impact | No measurable result or claiming credit for team outcomes without specifics |
Good behavioral questions don't come from a generic list. They come from the competencies required for the specific role. The process starts with the job description and competency framework, not with a bank of interview questions.
Identify 4-6 core competencies for the role based on the job description and input from the hiring manager. Common competencies include leadership, problem-solving, collaboration, adaptability, communication, conflict resolution, and decision-making under pressure. For each competency, write 2-3 behavioral questions that would reveal whether the candidate has demonstrated that competency in a real setting.
A strong behavioral question follows a simple formula: "Tell me about a time when you [specific situation tied to a competency]." Then prepare 2-3 follow-up probes to dig deeper. For example: Primary question: "Tell me about a time when you had to deliver results with a team that was underperforming." Follow-up 1: "What specifically did you identify as the root cause?" Follow-up 2: "How did the team respond to your approach?" Follow-up 3: "What would you do differently if you faced the same situation again?"
Questions like "Tell me about a time you showed great leadership" are leading because they telegraph the desired answer. Better: "Tell me about a time you had to get a group of people aligned on a decision they initially disagreed with." Also avoid hybrid questions that mix behavioral and hypothetical: "Tell me about a time you handled a difficult customer, and how would you handle one here?" Split these into two separate questions.
These questions are organized by the competency they assess. Use them as starting points and customize for the specific role.
Tell me about a time you had to lead a project without formal authority over the team members. Describe a situation where you had to make an unpopular decision and get your team on board. Give me an example of when you identified a problem nobody else was addressing and took the initiative to fix it.
Tell me about the most complex problem you solved at work in the last two years. Describe a situation where you had to make a decision with incomplete information. What happened? Give me an example of when your first approach to a problem didn't work. What did you do next?
Tell me about a time you worked with someone whose work style was very different from yours. Describe a situation where you had to rely on a colleague in a different department to get your work done. Give me an example of a team project where you had to compromise on your preferred approach.
Tell me about a time your priorities shifted suddenly. How did you adjust? Describe a situation where you received critical feedback that was hard to hear. What did you do with it? Give me an example of when you had to learn something new quickly to complete a task.
Tell me about a time you had to deliver difficult news to a stakeholder or client. Describe a situation where miscommunication caused a problem. How did you resolve it? Give me an example of a workplace disagreement where you helped find a resolution both sides accepted.
Asking behavioral questions without a scoring system defeats the purpose. Structured scoring is what turns a conversation into comparable, actionable data. Without it, interviewers default to gut feeling, which introduces the same biases behavioral interviews are designed to reduce.
Create a rubric with 3-5 rating levels for each competency. Define what each level looks like with specific behavioral indicators. For example, for "Problem-Solving" on a 4-point scale: 1 (Unsatisfactory) = Could not provide a relevant example or described a passive role. 2 (Developing) = Provided an example but action steps were vague. 3 (Proficient) = Described a clear situation with specific actions and a positive result. 4 (Exceptional) = Demonstrated creative thinking, quantifiable impact, and reflection on what they learned.
Before the interview process begins, all interviewers should review the rubric and discuss what "proficient" and "exceptional" look like for each competency. Run a calibration exercise using sample answers. This prevents one interviewer's "3" from being another's "4." Calibration takes 30-60 minutes and significantly improves the consistency of evaluations.
The most common mistake is scoring the candidate's presentation skills rather than their actual competency. A candidate who tells a polished story isn't necessarily better than one who gives a less fluent but more substantive answer. Other pitfalls include: anchoring on the first answer and letting it color subsequent ratings, the halo effect (one strong answer inflates all scores), and recency bias (weighting the last answer more heavily than the first).
These two approaches are often confused, but they test different things. Understanding the distinction helps interviewers choose the right tool for the right purpose.
Use behavioral questions for competencies the candidate should already have demonstrated (leadership, conflict resolution, project management). Use situational questions for scenarios specific to the role that the candidate may not have encountered before, or for entry-level candidates who lack professional examples. Many interviewers use a mix: behavioral questions for 70% of the interview, with situational questions to fill gaps.
| Dimension | Behavioral Questions | Situational Questions |
|---|---|---|
| Focus | What the candidate actually did in the past | What the candidate says they would do in a hypothetical scenario |
| Format | "Tell me about a time when..." | "What would you do if..." |
| Best for | Experienced candidates with relevant work history | Entry-level candidates, career changers, or new situations |
| Predictive validity | Higher: based on actual demonstrated behavior | Moderate: reflects intentions, not proven actions |
| Candidate prep | Requires reflection on past experiences | Requires analytical thinking and role knowledge |
| Interviewer skill | Needs probing skills to dig for STAR details | Needs domain knowledge to evaluate proposed solutions |
| Weakness | Less useful for candidates with limited experience in the area | Candidates can give idealized answers that don't reflect real behavior |
Even experienced interviewers make errors that reduce the effectiveness of behavioral interviews. Recognizing these patterns is the first step to fixing them.
When you ask "Tell me about a time when..." and the candidate responds with "What I would typically do is...", they've switched to a hypothetical answer. This happens often. Redirect them: "I appreciate that, but can you walk me through a specific situation where you actually did this?" If they can't provide one, that's useful information too.
Many interviewers accept the first version of a story without digging into the details. A candidate says "I fixed the problem and the client was happy." That's not enough. What exactly was the problem? What options did you consider? Why did you choose the approach you chose? What was the measurable impact? The richness of a behavioral answer comes from the follow-ups, not the initial response.
A 45-minute behavioral interview should cover 4-6 questions, not 15. Each question needs time for the candidate to tell their story and for the interviewer to probe. Rushing through a long list produces shallow answers that are impossible to score meaningfully. Fewer questions, deeper exploration is the rule.
"Tell me about a time you demonstrated excellent teamwork" tells the candidate exactly what you want to hear. Instead, describe the situation and let the behavior emerge: "Tell me about a time you had to complete a deliverable that required input from multiple people who had competing priorities." This surfaces the candidate's actual approach rather than their ability to match your keyword.
Understanding how candidates prepare helps interviewers anticipate rehearsed responses and dig for genuine experiences. It also helps HR teams give candidates a fair chance by setting clear expectations.
Career coaches advise candidates to prepare 8-12 detailed stories from their work experience that cover common competency areas. Each story can be adapted to answer multiple questions. A single project management example might work for questions about leadership, conflict resolution, or meeting deadlines. Interviewers should expect polished stories and focus on probing for details that a rehearsed answer wouldn't include.
Strong candidates provide specific details (dates, numbers, names, outcomes). They distinguish between what the team did and what they personally did. They include setbacks and what they learned, not just successes. They can answer follow-up questions without losing coherence. Weak candidates give vague, generic answers, describe team achievements without clarifying their role, or shift to hypothetical mode when pressed for details.
This is debated. Some companies share the competencies or even the exact questions ahead of time, arguing it reduces anxiety and levels the playing field for introverts, neurodiverse candidates, and non-native English speakers. Others worry it invites over-rehearsed answers. Research from the University of Calgary found that sharing questions in advance improved the quality of responses without reducing the interview's predictive validity. Google, Microsoft, and many government agencies now share question themes before interviews.
Data on the effectiveness and adoption of behavioral interviewing.