# The Behavioral Question Bank — Part 1: 42 Questions with Answer Outlines

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.

## 1. How 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.

## 2. Practise with Flashcards

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

## 3. The Full List

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

## 4. Company-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
```