Behavioral interview questions: the complete guide

In this article

1. How behavioral rounds are scored
2. Start here: the learning path
3. The answer structure: STAR and how to spend two minutes
4. Build a story bank, not a script
5. Tell me about yourself
6. Questions to ask the interviewer
7. Company frameworks: leadership principles and values
8. Conflict, failure and being wrong
9. Leadership, ownership and influence
10. The wider loop
11. Questions interviewers ask on behavioral interviews
12. All 87 guides in Behavioral interviews
13. Follow-up questions
14. Sources

How behavioral rounds are scored

Not every employer runs a structured round. Where the interviewer improvises, scoring leans more on personal judgment, so the same preparation still helps, but the questions are less predictable.

In a structured interview, behavioral answers are scored against a rubric, not against a feeling. Google's re:Work guide (updated March 2026) describes the structured format: every candidate for the same job gets the same questions, scored on the same scale against predetermined qualifications. It describes behavioral questions as ones that ask candidates to connect past achievements to the job's requirements, and says the rubrics it uses often document examples of poor, borderline, solid and outstanding answers for each attribute. The guide presents this as a recommended practice, which is why you may meet it at some employers and not at others.

Two consequences follow for you. First, interviewers listen for a specific quality in your story (ownership, handling conflict, learning from a failure), so a story that never shows that quality scores low however good it sounds. Second, employers that use the format have evidence for it: in a 2022 re-analysis of selection research, structured interviews had the highest mean operational validity of the procedures reviewed, r = .42, though results varied widely between studies, according to a Human Resources Research Organization (HumRRO) summary of Sackett et al. (2022).

That is an estimated correlation of .42 between interview scores and job performance, on a scale where 0 is no relation and 1 is perfect: a useful predictor, not a perfect one. The figure is about the interview format, not about any answer method such as STAR.

This guide groups behavioral preparation into six topics, starting with answer structure. Learn the answer structure once, then reuse it in every topic around the round.

Text description of the diagram

• Behavioral questions ask for a real past example; in a structured interview each answer is scored against the same criteria for every candidate.
• The six topics are answer structure, introductions, your questions for the interviewer, company frameworks, conflict and failure, and leadership and scope.
• This guide groups behavioral preparation into six topics, starting with answer structure.

Start here: the learning path

Take the topics in the order below. Answer structure comes first because every later page reuses it; after it come the questions that frame the round, the themes interviewers return to, and the stages around the round. The first step, Situation, Task, Action, Result (STAR) and the story bank, is covered below on this page.

Behavioral interview question

A behavioral interview question is a question that asks for a specific example from your past work or study, on the idea that how you acted before is the best evidence of how you will act in the job.

STAR

Situation, Task, Action, Result (STAR) is an answer structure with four parts that keeps a story specific and puts the weight on what you personally did.

Story bank

A story bank is a short list of three to five real experiences, each outlined in notes, that you can adapt to many different behavioral questions.

1. Questions to ask in an interview: open questions about the real work
2. Amazon Leadership Principles
3. How do you answer "Tell me about yourself" in an interview?
4. Tell me about a time you influenced without authority
5. Google behavioral interview questions: how they are scored and how to answer
6. How to answer a conflict interview question
7. Tell me about a time you failed
8. Tell me about a model that failed in production: root cause and permanent fix
9. Tell me about a time you disagreed with your manager: make the case, then commit
10. Netflix behavioral interview questions and the culture memo values behind them
11. Curveball behavioral questions and answers
12. How do you explain technical work to non-technical stakeholders?
13. How do you use AI in your daily work? How to answer it
14. Why do you want to work here? How to answer it, with examples
15. Prioritising under pressure as an IC: how to answer
16. Mentoring as an IC: an interview answer built on one person and one gap
17. How do you handle ambiguity and changing requirements?
18. What is the hardest technical decision you made?
19. Pushing back when the model is not ready: launch bar, evidence, a safer option
20. Delivery under pressure: cut scope, not quality, and warn stakeholders early
21. Disagreed with your manager's decision? How to answer
22. What qualities do you look for when hiring?
23. Do you have 1 on 1s with your subordinates?
24. Tell me about a time you were wrong: how do you answer it?
25. Anthropic culture interview: what it tests and how to prepare
26. How to answer AI-safety questions in engineering interviews
27. How do you answer an ownership and initiative question?
28. Tell me about tough feedback you received: how you checked it and what changed
29. What is LinkedIn's craftsmanship round?
30. Growing engineers: interview questions on coaching and promotion, answered
31. How do you analyze risk? A sample interview answer
32. Have you ever promoted anyone? How to answer it, with examples
33. Why should we hire you? How to answer it, with examples
34. What kinds of technical bias have you seen?
35. How do you increase adoption of the product?
36. Influencing people you've never worked with: give first, share a goal, ask small
37. What does 'mission-first' mean, and how do you answer it in an interview?
38. Would you act on your values or optimize for profitability?
39. What type of work do you least enjoy doing?
40. How to answer "What are your salary expectations?" in an interview
41. How to prepare for a phone interview

The answer structure: STAR and how to spend two minutes

Situation, Task, Action, Result (STAR) is the structure to use when a question asks for an example, because it forces three things interviewers look for: context, your own action and a result. The Massachusetts Institute of Technology (MIT) Career Advising & Professional Development (CAPD) office describes the parts as Situation, to give the context; Task, the responsibility you owned or the goal; Action, "the actions that you personally took"; and Result, the outcome, with measurable outcomes and lessons where you have them (MIT CAPD, read 2026-10-24).

The guide gives a time split of Situation 20%, Task 10%, Action 60% and Result 10%, presented as a guide and not a rule. It gives no answer length, so take a two-minute answer purely as an illustration, since a round of many questions leaves little room for more. As an illustrative 120-second answer, that split gives Action 72 seconds, Situation 24, Task 12 and Result 12.¹ The point of the split is the weight: most of your answer is what you did, and the setup stays short.

Text description of the diagram

• A guide from MIT's career office suggests Situation 20%, Task 10%, Action 60%, Result 10%.
• As an illustrative 120-second answer, that split gives Action 72 seconds, Situation 24, Task 12 and Result 12.

Build a story bank, not a script

A story bank is three to five real experiences, each outlined in notes, that you reshape to fit different questions. MIT's guide advises preparing three to five stories from a bulleted outline and warns against memorizing them, because scripting "may limit your ability to adapt as needed in an interview" and can sound unnatural.

Choose stories that each cover several themes. A project that went wrong can serve a failure question, a conflict question and a "what did you learn" question, with the emphasis changed. For each story write the four STAR parts in a line, plus one number that shows the result and one thing you would do differently. Say each story aloud once, in your own words, and time it.

Tell me about yourself

Tell me about yourself is a prompt for a short professional summary that gives the interviewer a map of the rest of the round. It is not a behavioral question in the strict sense, but it often opens the round, and a clear opening sets the tone for every later answer, because it is the first thing the interviewer hears from you.

A good opening names your current role or field, one or two pieces of evidence that matter for this job, and the reason you are applying, and then stops, leaving the interviewer free to pick a thread. Treat it as the first entry in your story bank, not as a separate script. The full treatment is on the tell me about yourself page.

Questions to ask the interviewer

The closing question, "do you have any questions for us?", is part of the same round and is read the same way. Interviewers use it to see whether you listened, what you care about and whether you have thought about the work. Ask open questions about real work that your decision depends on, such as how success is measured in the first months or how the team handles disagreement. Avoid anything the website answers, and leave pay for the stage where the employer raises it. Prepare more questions than you will use, because some get answered during the round. The questions to ask in an interview page gives ten ready-to-adapt questions and a rubric.

Company frameworks: leadership principles and values

Some employers publish the qualities they hire for, and candidates prepare stories against them. Amazon, for example, lists 16 leadership principles on its jobs site, including Customer Obsession, Ownership, Have Backbone; Disagree and Commit, and Deliver Results (Amazon Jobs, read 2026-10-24). Map each story in your bank to one or two such principles before the round, using the employer's own words only where it has published them. The useful habit is to tag stories, not to rewrite them: the same incident can show ownership in one answer and disagreement handled well in another. Read the principle's wording closely, because an interviewer may phrase the question in it.

Conflict, failure and being wrong

These questions test different qualities. For failure and being wrong, show ownership: say what you misjudged in the first person and end on a changed habit. For disagreement, show how you handled the difference: raise it early with evidence, listen to the other view, reach a decision or disagree and commit (Amazon's "Have Backbone; Disagree and Commit"), and keep the relationship. Follow-ups differ too: after a failure, what you would do differently; after a disagreement, what the other person would say and what happened after the decision.

An illustrative contrast. A weak answer: "The deadline slipped because the other team was late, so I escalated." A strong answer: "I underestimated the integration work, told my manager the same day, cut the scope with the other team and now add a check-in at the halfway point of every project." This contrast is for a failure story: the strong version owns the cause and ends on a changed habit.

Leadership, ownership and influence

These questions test scope: did you act without being asked, and did you move people who did not report to you? Interviewers listen for what you did before anyone asked, whom you had to persuade, and what you gave up to get agreement. For leadership and management roles the questions get harder, since the stories must show decisions about other people, not only your own work, and leadership interviews covers that side. For product roles, the product management guide covers the behavioral round alongside product sense and metrics.

The wider loop

Behavioral questions rarely stand alone, and the preparation habits you build here carry into the rest of the process. Interview loops explains how rounds fit together and where the behavioral round usually sits, the Anthropic interview process shows one AI-lab loop from first call to offer, and salary negotiation covers what comes after a yes. Read the loop page before you plan your story bank, so you know how many behavioral rounds to expect and who is likely to run them. Then return to the negotiation page when an offer is close, because the conversation about pay follows its own rules and a calm, prepared approach to it is a skill separate from the behavioral round itself.

Questions interviewers ask on behavioral interviews

These are ten themes that recur, in our own words, with what each one tests. We make no claim about how often each is asked.

Follow-up questions

How do you answer behavioral interview questions?

Pick a real example that shows the quality the question tests, then tell it in STAR order, spending most of the time on what you personally did and ending on a measurable result. Keep it short enough to leave room for the interviewer's follow-up; a couple of minutes is a reasonable illustration, not a rule from any source.

How do you answer behavioral interview questions with no experience?

Use the best real examples you have: coursework, a group project, volunteering, a part-time job, a hobby that involved other people. The structure does not change, and an interviewer scoring against a rubric is looking for the quality, not the job title.

What are the most common behavioral interview questions?

The ten themes in the table above recur: conflict, failure, being wrong, leading without authority, hard decisions, feedback, prioritization, collaboration, initiative and motivation. Prepare the story bank first, then check that each theme has a story.

How do you answer behavioral interview questions as a software engineer?

Choose stories from engineering work, such as a production incident, a design disagreement, a delayed project or a decision between two designs, and put a number on the result (latency, errors, time saved). Say "I" for your actions and "we" only for team outcomes.

How do you prepare for a behavioral interview as a software engineer?

Write a story bank of three to five stories in STAR notes, map each to two or three themes, say each aloud once, and prepare your questions for the interviewer. The loops page shows where the behavioral round sits among the technical ones.

Sources

1. Using the STAR method for your next behavioral interview — MIT Career Advising & Professional Development (date = read date), 24 Oct 2026
2. A guide to structured interviewing for better hiring practices — Google re:Work (updated March 2026), 1 Mar 2026
3. Revisiting meta-analytic estimates of validity in personnel selection: Addressing systematic overcorrection for restriction of range — Journal of Applied Psychology 107(11), 2040-2068 (Sackett, Zhang, Berry and Lievens), 1 Nov 2022
4. Is cognitive ability the best predictor of job performance? New research says it's time to think again — HumRRO (summary of the paper above; read 2026-10-24), 27 Sep 2022
5. Amazon leadership principles — Amazon Jobs (date = read date), 24 Oct 2026