Engineering Notes
Home/Interview Preparation/Behavioral Interviews/The Behavioral Question Bank
Interview Preparation · Behavioral Interviews

The Behavioral Question Bank

Almost every behavioral question is a variant of a few dozen common ones. Here they are, each with what the interviewer assesses and an outline of a strong answer, plus interactive flashcards for timed, out-loud practice and notes on how big companies run their behavioral rounds.

🎤 Interview Preparation● Intermediate⏱ 5 min read▶ 1 interactive🛠️ 2 exercises

🎯 What you'll learn

  • The 42 most common behavioral questions
  • What each question assesses
  • Outlines of strong answers
  • How Amazon, Google and Meta run behavioral rounds

Almost every behavioral question is a variant of one of the questions below. For each, know which story from your bank you'd use and what the interviewer is assessing. The flashcards let you practise: read the question, answer out loud against the clock (aim for 2–3 minutes), then reveal the outline and compare.

1How to Use This Bank

  1. Go through the list and write the story name you'd use next to each question.
  2. If a question has no good story, that's a gap in your story bank: fill it.
  3. Practise with the flashcards daily for a week: 5–10 questions a session, out loud, timed.
  4. Mark a card as known only when you can answer it fluently without notes.

2Practise with Flashcards

Answer each card out loud before revealing the outline. The timer starts when the card appears.

3The Full List

#QuestionAssesses
1Tell me about yourself.Communication; whether your path fits the role
2Why do you want to work here?Genuine interest; research
3Why are you leaving your current job?Judgment; no negativity
4What are you looking for in your next role?Fit and self-awareness
5Walk me through the project you're proudest of.Depth, impact, ownership
6Tell me about a time you went above and beyond your role.Initiative
7Tell me about a time you took ownership of a problem that wasn't yours.Ownership without overreach
8Describe a decision you made without having all the information.Judgment under uncertainty
9Tell me about a time you had to balance short-term and long-term needs.Trade-off thinking
10What's something you've improved that nobody asked you to?Sustained ownership
11Tell me about your biggest technical challenge.Technical depth plus delivery
12Tell me about a time you delivered under a tight deadline.Prioritization; quality bar
13Tell me about a project that had a big impact on the business.Impact orientation
14Describe a time you improved performance or reliability significantly.Technical judgment, measurement
15Tell me about a disagreement with a teammate.Collaboration, maturity
16Tell me about a time you disagreed with your manager.Courage plus respect
17Tell me about a time you disagreed but committed anyway.Disagree and commit
18Tell me about working with a difficult stakeholder.Empathy, communication
19Have you ever had to push back on a product or business requirement?Customer focus, judgment
20Tell me about a time you failed.Self-awareness, accountability
21Tell me about a mistake that affected production.Incident behaviour
22Tell me about a project that didn't go as planned.Adaptability
23What's the most critical feedback you've received?Coachability
24What's your biggest weakness?Self-awareness
25How did you convince a team to adopt a technical change?Influence without authority
26Tell me about a project you led end to end.Leadership, delivery
27How do you get buy-in for paying down tech debt?Business framing
28Tell me about a time you had to lead without formal authority.Leadership
29Tell me about a time you changed your mind.Intellectual honesty
30Tell me about someone you mentored.Multiplying others
31How do you onboard new engineers?Team building
32How have you raised the engineering bar on your team?Standards
33Tell me about a time you gave someone difficult feedback.Courage, care
34Tell me about a project with unclear requirements.Handling ambiguity
35How do you prioritize when everything is urgent?Prioritization
36Tell me about a time you had to say no.Judgment, communication
37Tell me about a time the plan changed mid-project.Adaptability
38Tell me about an incident you led.Incident leadership
39How do you make architectural decisions on your team?Technical leadership process
40How do you approach code reviews?Standards, collaboration
41Tell me about a time you improved a team process.Continuous improvement
42How do you estimate a large project?Planning

4Company-Specific Notes

  • Amazon: every question maps to a Leadership Principle (Customer Obsession, Ownership, Dive Deep, Have Backbone; Disagree and Commit, Deliver Results…). Expect 2 LP questions per interviewer and deep "dive deep" follow-ups; a bar raiser joins the loop.
  • Google: "Googleyness and leadership" round: collaboration, comfort with ambiguity, humility, doing the right thing for users. Also hypotheticals ("what would you do if…").
  • Meta: behavioral round focuses on conflict, ownership, growth and driving results; it heavily influences the level of the offer.
  • Product companies and start-ups: often fewer structured questions and more conversation about past projects, ownership and pace. Expect "why us?" to matter more.

⚠️ Common Pitfalls

  1. Answering the question you prepared, not the one asked: listen for the competency.
  2. Reusing the same story for every question in one loop.
  3. Reading answers you've memorized: the outline is a checklist, not a script.
  4. Skipping the "why this company" research.

📋 Quick Reference

text
Map every question → a story from your bank; no story = a gap to fill
Practise 5–10 cards a day, out loud, 2–3 minutes each
Listen for the competency behind the question
Amazon: Leadership Principles · Google: Googleyness + hypotheticals · Meta: conflict/ownership/growth

🧠 Key takeaways

  • Most questions are variants of ~42 common ones; map each to a story.
  • Listen for the competency behind the question.
  • Practise out loud and timed, 5–10 questions a day.
  • Research the company's values and how its loop is structured.

🛠️ Practice exercises

Each exercise is a file in this topic folder. Code exercises are self-checking: run them and make the checks pass.

✅ Check yourself

Answer the questions — feedback is instant.

1. A question has no good story from your bank. What should you do?
Gaps tell you what to prepare.
2. What does Amazon map its behavioral questions to?
Each question targets an LP.
3. When should you mark a flashcard as 'known'?
Recall, not recognition.
4. "Tell me about yourself" should take roughly…
Short, structured, relevant.