Interview guide · Interview types
Behavioral interview questions
In short
Behavioral interview questions ask candidates to describe how they actually handled past situations, usually starting with tell me about a time. They work because past behavior in similar situations predicts future behavior better than hypotheticals. This page gives 32 questions by competency, how to probe with STAR, red flags and a scoring rubric.
A behavioral interview replaces what would you do with what did you do. Instead of asking a candidate how they would handle a missed deadline, you ask them to describe the last deadline they missed, what they did, and how it turned out. Candidates can rehearse a good opinion. It is much harder to invent a detailed, consistent story under three follow-up questions, which is why behavioral questions sit at the core of almost every structured interview.
Use this page in three steps. Pick the four to six competencies that matter most for the role from your job analysis or job description. Choose one or two questions per competency from the groups below, and write the same follow-up probes for each. Then score every answer against an anchored rubric, like the scorecard at the bottom, before you compare candidates. For a definition of the method and its history, see our glossary entry on the behavioral interview.
What these questions assess
- A real, specific situationStrong answers name a place, a time and the people involved. Answers built on usually or I always tend to describe intentions, not behavior.
- Personal ownership of the actionListen for I rather than we when the candidate describes what was done. Team results are fine, but you are hiring the individual and need to know their part.
- A measurable or observable resultGood stories end with what changed: a number, a decision, a customer outcome. Missing results often mean the story is not finished or did not go well.
- Reflection and learningCandidates who can say what they would do differently show self-awareness, a reliable predictor of how they will respond to coaching.
- Consistency under probingDetails should hold together when you ask follow-up questions. Stories that shift or get vaguer under questions are a signal to dig further.
- Relevance to the jobA polished story about the wrong competency scores low. The best answers match the level and context of the role you are filling.
Teamwork and collaboration
Tell me about a time you had to work closely with someone whose style was very different from yours.
- Why ask it
- Shows how the candidate adjusts to others rather than expecting others to adjust to them.
- A strong answer
- Describes the specific difference (pace, detail, communication), what they changed in their own approach, and how the working relationship or result improved.
- Red flags
- The other person is the problem in every part of the story.
Describe a time a teammate was not pulling their weight. What did you do?
- Why ask it
- Reveals whether the candidate addresses problems directly, quietly absorbs extra work, or goes straight to the manager.
- A strong answer
- Talked to the teammate first, tried to understand the cause, agreed on a plan, and escalated only if that failed. Shows respect throughout.
- Red flags
- Complained to others or did the work themselves and let resentment build without saying anything.
Tell me about a time you helped a coworker succeed even though it did not benefit you directly.
- Why ask it
- Tests generosity and team orientation, which matter in shared queues, shift work and project teams.
- A strong answer
- Concrete help such as training, covering, or sharing a method, with a clear outcome for the coworker.
- Red flags
- Cannot think of an example or frames help as a favor to be repaid.
Give an example of a time you had to rely on another team or department to get something done.
- Why ask it
- Cross-team dependencies are where most delays happen. This shows influence without authority.
- A strong answer
- Explains how they built the relationship, made the request clear and easy, followed up, and handled delays.
- Red flags
- Just waited, or escalated over the other team's head at the first delay.
Tell me about a time you joined a team that already had established ways of working.
- Why ask it
- Useful for every new hire. Shows how they learn norms before trying to change them.
- A strong answer
- Spent time observing and asking questions, adapted first, and suggested changes once they understood the reasons behind existing practices.
- Red flags
- Tried to change everything in the first week.
Communication and conflict
Tell me about a time you disagreed with your manager's decision. What did you do?
- Why ask it
- Shows whether the candidate can raise concerns professionally and still commit once a decision is made.
- A strong answer
- Raised the concern privately with reasons or data, listened to the other view, and either changed the decision or committed to it fully.
- Red flags
- Went along silently and complained later, or ignored the decision.
Describe a time you had to deliver bad news to a customer, client or colleague.
- Why ask it
- Every role involves saying no. This shows directness and empathy together.
- A strong answer
- Delivered the news early and plainly, explained the reason, offered what they could, and handled the reaction calmly.
- Red flags
- Delayed the news, softened it until it was unclear, or blamed someone else.
Tell me about a misunderstanding that caused a problem at work. How did you resolve it?
- Why ask it
- Shows ownership of communication and the habits they built afterward.
- A strong answer
- Identifies where the communication broke, takes their share of responsibility, fixes the immediate problem and describes a change they made, such as confirming in writing.
- Red flags
- Entirely the other person's fault, with no lesson.
Give me an example of a time you explained something complicated to someone without your background.
- Why ask it
- Tests clarity and audience awareness, important for customer-facing, training and technical roles.
- A strong answer
- Describes how they simplified, used an example or visual, checked understanding, and what the person was able to do afterward.
- Red flags
- Blames the listener for not understanding.
Tell me about a conflict between two people on your team and what role you played.
- Why ask it
- Reveals maturity and judgment in situations that do not involve the candidate directly.
- A strong answer
- Stayed neutral, encouraged a direct conversation, helped find common ground, or involved a lead when appropriate.
- Red flags
- Took sides publicly or spread the story.
Problem solving and judgment
Tell me about a time you solved a problem that others had given up on.
- Why ask it
- Shows persistence and analytical method, not just effort.
- A strong answer
- Explains how they diagnosed the root cause, what they tried that did not work, what finally did, and the measurable result.
- Red flags
- The solution came from someone else or was luck with no method.
Describe a decision you made without all the information you wanted.
- Why ask it
- Most real decisions happen with incomplete data. This shows how candidates balance speed and risk.
- A strong answer
- Names what they knew and did not know, how they limited the risk, the decision, and how they checked the outcome afterward.
- Red flags
- Avoided deciding until someone else did, or decided recklessly with no thought to risk.
Tell me about a time you noticed a problem before anyone asked you to look at it.
- Why ask it
- Tests initiative and attention to detail together.
- A strong answer
- Spotted something specific (an error pattern, a process gap, a customer trend), raised it, and helped fix it.
- Red flags
- Noticed it but did nothing because it was not their job.
Give me an example of a time you had to choose between two good options. How did you decide?
- Why ask it
- Shows the criteria the candidate uses, which tells you a lot about their priorities.
- A strong answer
- Lays out the options, the criteria (customer impact, cost, time, risk), who they consulted, and why they chose as they did.
- Red flags
- Picked based on gut feeling alone with no reasoning they can explain.
Tell me about a time a plan you made did not work. What happened next?
- Why ask it
- Shows adaptability and honesty about failure.
- A strong answer
- Admits the plan failed, explains why, describes the adjusted plan and what they learned for next time.
- Red flags
- Insists the plan was right and circumstances were wrong.
Adaptability, pressure and resilience
Tell me about a time your priorities changed suddenly. How did you handle it?
- Why ask it
- Shifting priorities are normal in operations, recruiting and customer roles. This shows flexibility and organization.
- A strong answer
- Re-planned quickly, communicated what would slip and to whom, and delivered the new priority.
- Red flags
- Got frustrated and kept working on the old priority.
Describe the most stressful stretch you have had at work or school. What did you do to get through it?
- Why ask it
- Shows coping strategies and self-awareness under sustained pressure, not just a single bad day.
- A strong answer
- Specific situation, practical tactics (prioritizing, asking for help, routines), and how they protected quality.
- Red flags
- Says they never feel stress, or describes coping that hurt their work or teammates.
Tell me about a time you had to learn a new tool or process quickly to do your job.
- Why ask it
- Learning agility predicts speed to proficiency in almost every role.
- A strong answer
- Describes their learning approach, how long it took, and how they used it successfully.
- Red flags
- Waited to be fully trained before trying anything.
Give an example of a time you received tough feedback. What did you change?
- Why ask it
- Coachability is one of the clearest separators between average and strong hires.
- A strong answer
- Names the feedback specifically, admits it stung if it did, and describes a concrete change and the result.
- Red flags
- Cannot recall any critical feedback or still argues it was wrong.
Tell me about a time you failed at something important to you.
- Why ask it
- A real failure story tests honesty and resilience. Rehearsed fake failures are easy to spot.
- A strong answer
- A genuine failure with consequences, clear ownership, and a lesson that has visibly shaped later behavior.
- Red flags
- A disguised strength such as I worked too hard.
Reliability, integrity and ownership
Tell me about a time you made a mistake that nobody else had noticed yet.
- Why ask it
- Strong integrity signal. Shows whether the candidate surfaces problems or hopes they go away.
- A strong answer
- Raised it promptly, explained the impact, fixed it, and changed a habit to prevent repeats.
- Red flags
- Fixed it quietly and hoped nobody found out, or did nothing.
Describe a time you were asked to do something you felt was not right.
- Why ask it
- Tests ethical judgment and courage, especially in regulated, cash-handling or data-sensitive roles.
- A strong answer
- Questioned the request, sought clarification or guidance, and refused or escalated appropriately.
- Red flags
- Did it because they were told to, with no discomfort.
Tell me about a commitment you found hard to keep. What did you do?
- Why ask it
- Shows reliability and how the candidate communicates when they are at risk of missing something.
- A strong answer
- Flagged the risk early, renegotiated or found help, and kept the person informed.
- Red flags
- Missed the commitment without telling anyone in advance.
Give me an example of a time you followed a process you thought was inefficient.
- Why ask it
- Balances compliance with improvement mindset, which matters in audited and safety-sensitive work.
- A strong answer
- Followed it while raising a suggestion through the right channel, with reasons.
- Red flags
- Ignored the process or followed it while complaining with no attempt to improve it.
Tell me about a time you took responsibility for a result that was not fully in your control.
- Why ask it
- Reveals ownership mindset, the difference between explaining a miss and fixing it.
- A strong answer
- Accepted accountability, focused on what they could influence, and drove a better outcome next time.
- Red flags
- Lists every factor that was outside their control.
Leadership and initiative
Tell me about a time you led a group without formal authority.
- Why ask it
- Useful for individual contributors and future leads. Shows influence and organization.
- A strong answer
- Explains how they got buy-in, organized the work, handled resistance and delivered a result.
- Red flags
- Describes leadership as telling people what to do.
Describe a time you coached or trained someone. How did you know it worked?
- Why ask it
- Shows teaching ability and whether the candidate measures impact.
- A strong answer
- Specific person and skill, their method (show, practice, feedback), and evidence of improvement.
- Red flags
- Training meant handing over a document.
Tell me about an improvement you made to how your team worked.
- Why ask it
- Shows initiative and change management on a small scale.
- A strong answer
- Names the problem, the change, how they got others to adopt it, and the result in time saved, errors reduced or similar.
- Red flags
- Change was imposed without consulting anyone, or the result is unclear.
Give an example of a time you had to hold someone accountable for performance or behavior.
- Why ask it
- Essential for supervisors and managers. Shows directness and fairness.
- A strong answer
- Prepared with facts, had a private and direct conversation, agreed on expectations, and followed up.
- Red flags
- Avoided the conversation or handled it publicly.
Tell me about a time you volunteered for work outside your normal role.
- Why ask it
- Initiative indicator that also shows what kind of work energizes the candidate.
- A strong answer
- Clear reason for volunteering, how they balanced it with their regular work, and what came of it.
- Red flags
- Their regular work suffered and they did not notice or care.
Describe a time you had to make an unpopular decision. How did you handle the reaction?
- Why ask it
- Tests leadership resolve and communication for lead and manager roles.
- A strong answer
- Explained the decision and the reasoning openly, listened to concerns, stayed with it or adjusted for good reasons, and kept relationships intact.
- Red flags
- Reversed at the first pushback or ignored people's concerns entirely.
Tell me about a goal you set for yourself at work and how you tracked it.
- Why ask it
- Shows self-direction and whether the candidate thinks in measurable terms.
- A strong answer
- A specific goal, a clear measure, the actions taken, and whether they hit it.
- Red flags
- Goals are vague such as be better, with no tracking.
Sample answers
I was a payroll clerk at a regional healthcare company, and two days after a run I realized I had keyed overtime for one department at straight time. Fourteen people were underpaid by about $40 to $180 each. Nobody had complained yet. I told my supervisor that morning, with a list of the affected employees and the exact amounts. We ran an off-cycle correction the same week, and I drafted a short note for the department manager to send so people heard it from us first. Then I added a check to my process: I now compare overtime hours to the prior period by department before I submit. If a number moves more than 20 percent, I look at it again. It has caught two other problems since.
At my last job in recruiting, my manager wanted to drop the phone screen for warehouse roles and go straight to on-site interviews to save time. I thought we would get more no-shows. I pulled our numbers for the previous quarter: candidates who had a phone screen showed up to on-site interviews about 70 percent of the time, and walk-in applicants only about 45 percent. I showed her that in our one-on-one. She agreed the gap was real but still needed the time back, so we compromised on a five-minute text-and-call check instead of a full screen. Show rates held at about the same level as before, and we saved several hours a week.
I planned a weekend hiring event for our call center that was supposed to produce 40 offers. We got 22. I had advertised mainly on one job board, and the event fell on a local festival weekend, which I had not checked. On Monday I looked at where applicants came from and saw nearly all our attendees had come from referrals and a community college posting. For the next event I moved the date, put most of the budget into referral bonuses and the college partnership, and added text reminders the day before. That event produced 47 offers. I still check the local calendar before I book anything.
Interview scorecard
| Competency | Weight | Strong (4–5) | Weak (1–2) |
|---|---|---|---|
| Specificity of examples | 25% | Every answer describes one real situation with concrete details: when, where, who, and what exactly happened. | Speaks in generalities like I always or I usually, or switches to hypotheticals when asked for an example. |
| Personal action and ownership | 25% | Clearly separates their own actions from the team's, explains their reasoning, and owns mistakes. | Relies on we throughout, cannot explain their own role, or blames others. |
| Results and impact | 20% | States outcomes with numbers or observable changes and connects them to their actions. | No result, or a result unrelated to anything the candidate did. |
| Reflection and learning | 15% | Explains what they learned and shows how it changed later behavior. | No lesson, or a lesson that is generic and unconnected to the story. |
| Relevance to the role | 15% | Examples match the scale, context and level of the job being filled. | Examples are from unrelated situations or far below the level the role requires. |
Score each competency from 1 to 5 straight after the interview, before discussing the candidate with anyone else, then multiply by the weight.
How to run a behavioral interview well
Behavioral questions only predict performance when the interview around them is structured. A good process looks like this:
- Start from the job, not a list. Pick four to six competencies from the job analysis. For a contact center agent that might be composure, listening, reliability and coachability. For a staffing account manager it might be client communication, negotiation and ownership. Do not ask every question on this page.
- Write the probes in advance. For each main question, prepare the same three or four follow-ups: What exactly did you say? What did you do next? What was the result? What would you change? Probing is where behavioral interviews earn their value, and it is also where unstructured interviewers drift.
- Use STAR as a listening frame, not a script. Situation, Task, Action, Result tells you which piece is missing. Most candidates spend too long on the situation and skip the result. Redirect politely: That gives me the context, so what did you personally do?
- Take notes on behavior, not impressions. Write what the candidate said they did, not that they seemed confident. Notes are your evidence if a decision is challenged later.
- Score each answer before the next question or immediately after the interview. Use anchored levels from 1 to 5 where each level describes what an answer at that level sounds like. Compare scores across interviewers before discussing candidates, so the loudest opinion does not set the outcome.
Plan about 8 to 12 minutes per behavioral question with probes. A 45-minute interview fits four questions comfortably. Trying to fit eight produces shallow answers you cannot score.
Behavioral questions pair well with the forward-looking situational interview questions, which help when candidates are early in their careers and have fewer examples. If your organization uses a formal competency framework, the competency-based interview questions page maps questions to common frameworks.
Mistakes interviewers make with behavioral questions
The most common failure is accepting a hypothetical. The candidate is asked for a time they handled conflict and answers with I would sit down with the person. That is a situational answer, and it scores lower. Ask again: Can you think of a specific time that happened?
Other mistakes we see often:
- Leading the witness. Questions such as Tell me about a time you showed great teamwork by helping a struggling colleague signal the answer you want. Keep the stem neutral.
- Letting we stand. Team stories are natural, but if you do not ask what was your part, you may hire the bystander on a successful project.
- Scoring polish, not substance. Candidates who have practiced STAR answers sound fluent. Fluency is not evidence. Score the content: was there a real action and a real result relevant to the job?
- Ignoring candidates with thin work history. Entry-level and career-change candidates can draw on school, volunteering, caregiving or sports. Tell them up front that any example is fine. Otherwise you screen out good people for having fewer jobs.
- Asking every candidate different questions. It feels conversational, but it destroys comparability and makes the process harder to defend. Our interview questions to ask candidates guide covers when open conversation helps and when it hurts.
Legal do's and don'ts
Behavioral interviews are generally lower risk than unstructured conversations because every candidate gets the same job-related questions. A few cautions still apply in the US:
- Watch where stories lead. A candidate asked about a stressful period may mention a medical condition, pregnancy, or a family situation. Do not follow up on it. Redirect to the behavior: What did you do at work during that time? Under the Americans with Disabilities Act, employers generally cannot ask disability-related questions before a conditional job offer.
- Keep competencies job-related. Under Title VII and EEOC guidance, selection procedures that disproportionately screen out protected groups need to be job-related and consistent with business necessity. A documented link from each competency to the job is your best defense.
- Do not ask about age, religion, national origin, marital status or plans for children, even to build rapport. See the full list in our illegal interview questions guide.
- Keep notes and scores. Federal contractors have record-keeping obligations, and many employers retain interview records for at least a year. State and local rules vary, so check with counsel for your locations.
Using behavioral questions in high-volume hiring
Behavioral interviewing is easy to do well for one hire and hard to keep consistent across 500. Picture a retailer hiring 300 seasonal associates across 40 stores. Forty store managers asking their own favorite questions produce 40 different hiring standards and no usable data.
What works at volume:
- A fixed question set per job family. Three or four behavioral questions, the same probes, the same 1 to 5 anchors. Train managers in 30 minutes, not a full day.
- Async first rounds. Candidates record answers to the same questions on their phones at a time that suits them, and reviewers score against the rubric. An AI interviewer that asks follow-up probes can push for the missing action or result the way a trained interviewer would, which fixes the biggest weakness of one-way video. Keep a human accountable for decisions, give candidates notice, and check selection rates by group. New York City Local Law 144 requires a bias audit and notice for automated employment decision tools, and other jurisdictions have their own rules.
- Check the questions against outcomes. After 90 days, compare interview scores to retention and early performance ratings. Keep questions whose scores track with good hires and replace those that do not.
The same principle applies in every setting: same questions, same probes, same rubric, scored independently. That is what makes behavioral questions predictive rather than just conversational.
Frequently asked questions
What are the most common behavioral interview questions?
The ones you will hear most are: tell me about a time you handled a conflict with a coworker, a time you made a mistake, a time you failed, a time you dealt with a difficult customer, a time you worked under pressure, a time you disagreed with your manager, and a time you showed leadership. Most map to teamwork, problem solving, adaptability and ownership.
What is the STAR method for behavioral interview questions?
STAR stands for Situation, Task, Action and Result. It is a structure for answering, and for listening to, behavioral questions: set the scene briefly, explain what you were responsible for, describe what you personally did, and say what happened as a result. Interviewers use it to notice which part of an answer is missing and probe for it.
What is the difference between behavioral and situational interview questions?
Behavioral questions ask about past behavior (tell me about a time you did X). Situational questions ask about a hypothetical future (what would you do if X happened). Behavioral questions tend to work better for experienced candidates; situational questions help with entry-level candidates who have fewer examples. Many structured interviews use both.
How many behavioral questions should you ask in an interview?
Plan on four to six for a 45 to 60 minute interview, with about 8 to 12 minutes per question including follow-up probes. Asking more usually means you get surface answers without enough detail to score them reliably.
How do you score behavioral interview answers?
Use an anchored rating scale, typically 1 to 5, where each level describes what an answer looks like for that competency. Score specificity of the example, the candidate's own actions, the result and the reflection. Each interviewer should score independently before any group discussion.
Are behavioural interview questions different in the UK?
No. Behavioural is the UK and Commonwealth spelling, and the method is the same. UK employers often call it competency-based interviewing, and public sector employers frequently publish the competencies in the job pack so candidates can prepare examples.