Behavioral Interview Questions: The Ultimate List

200+ behavioral questions organized by competency, with the STAR method framework and real examples of what top-tier interviewers are listening for.

Why Behavioral Rounds Matter More Than You Think

Most engineers underestimate behavioral rounds. The assumption is that technical skill is the real signal, and behavioral interviews are a formality. This is wrong — especially at Amazon, where Leadership Principles questions explicitly carry veto weight in hiring decisions. Even at Google and Meta, a poor behavioral round from an otherwise strong candidate regularly results in a "no hire."

The good news: behavioral rounds are highly scriptable. Unlike coding problems, you know in advance roughly what will be asked. Building 8–10 strong STAR stories and mapping them to multiple question types is a one-time investment that pays off across every interview you do.

The STAR Method — Done Right

STAR (Situation, Task, Action, Result) is the standard framework. Most candidates know the acronym but execute it poorly. Common mistakes: spending too long on Situation, being vague about Actions (using "we" instead of "I"), and having no quantified Result. Interviewers are scoring you on the Action and Result portions primarily — calibrate your time accordingly.

Situation15% of your answer. Set context quickly.
Task10% of your answer. What were you responsible for?
Action50% of your answer. What did YOU specifically do?
Result25% of your answer. Quantify impact. What changed?

Questions by Competency

Leadership & Influence

  • › Tell me about a time you led a project without formal authority.
  • › Describe a time you had to influence a senior stakeholder to change direction.
  • › Tell me about a time you stepped up in a crisis.
  • › Give an example of when you drove a significant change in your team.

Conflict & Disagreement

  • › Tell me about a time you disagreed with your manager.
  • › Describe a situation where you had to work with someone difficult.
  • › Tell me about a time you had a conflict with a peer and how you resolved it.
  • › Give an example of when you pushed back on a product decision.

Failure & Setbacks

  • › Tell me about your biggest professional failure.
  • › Describe a time a project you led failed to ship on time.
  • › Tell me about a time you made a mistake that had significant impact.
  • › What would you do differently in your previous role?

Ambiguity & Initiative

  • › Tell me about a time you had to make a decision without complete information.
  • › Describe a project you initiated that wasn't on your roadmap.
  • › Tell me about a time you had to define requirements yourself.
  • › Give an example of a calculated risk you took.

Collaboration & Mentorship

  • › Describe how you've helped onboard or mentor a junior engineer.
  • › Tell me about a successful cross-functional project you contributed to.
  • › How have you handled a situation where a teammate was underperforming?
  • › Give an example of giving difficult feedback to a peer.

Amazon Leadership Principles — What They're Really Asking

Amazon's 16 Leadership Principles are the explicit lens every interviewer uses. Each behavioral question maps to one or more of them. The three that trip up most engineers: "Dive Deep" (interviewers expect you to know every detail of your own projects), "Bias for Action" (they want examples of moving fast with acceptable risk, not endless planning), and "Earn Trust" (they probe for humility and feedback receptivity specifically).

Prepare at least one strong story for each of the 16 principles before an Amazon loop. The interview structure is predictable: 5–6 rounds, each interviewer focused on specific LPs. If you walk in with 16 prepared stories, you're in the top 10% of candidates by preparation level alone.

See Real Behavioral Questions From Actual Interviews

Browse behavioral questions filtered by company, role, and round — sourced from real interview reports.

Browse Behavioral Questions