Behavioural Interview Mastery - The 20 Questions You Must Prepare

Behavioural interviews exist because past behaviour is the best predictor of future performance. When an interviewer asks "Tell me about a time you disagreed with your manager," they are not making conversation - they are scoring you against a competency rubric.

The Competency Model

Most companies assess five core competencies. Every behavioural question maps to one of these:

| Competency | What They Assess | Signal They Want | |-----------|-----------------|-----------------| | Leadership | Driving results without authority | Ownership and initiative | | Teamwork | Collaboration across functions | Empathy and communication | | Conflict Resolution | Handling disagreements professionally | Maturity and pragmatism | | Failure & Resilience | Learning from mistakes | Self-awareness and growth | | Growth & Ambition | Continuous improvement | Curiosity and drive |

The 20 Questions You Must Prepare

Leadership (1-4)

1. Tell me about a time you led a project with no formal authority.
2. Describe a situation where you had to make a decision with incomplete information.
3. Give an example of when you raised the bar for your team.
4. Tell me about a time you had to influence a senior stakeholder.

Teamwork (5-8)

5. Describe a time you worked with a difficult colleague.
6. Tell me about a cross-functional project you contributed to.
7. Give an example of when you helped someone else succeed.
8. Describe a situation where you had to compromise.

Conflict Resolution (9-12)

9. Tell me about a disagreement with your manager. How did you handle it?
10. Describe a time two teams had conflicting priorities. What did you do?
11. Give an example of receiving harsh feedback. How did you respond?
12. Tell me about a time you had to push back on a requirement.

Failure & Resilience (13-16)

13. Tell me about your biggest professional failure.
14. Describe a project that did not go as planned. What happened?
15. Give an example of a mistake that affected your team.
16. Tell me about a time you missed a deadline.

Growth & Ambition (17-20)

17. What is the most important thing you have learnt in the last year?
18. Describe a time you stepped outside your comfort zone.
19. Tell me about a skill you taught yourself.
20. Where do you see yourself in three years, and what are you doing to get there?

Crafting Stories Using STAR

For each of the 20 questions, prepare a STAR story (Situation, Task, Action, Result):

• Situation (2-3 sentences): Set the scene. Company, team, timeline, stakes.
• Task (1-2 sentences): What was your specific responsibility?
• Action (3-5 sentences): What did you do? Use "I", not "we". Be specific about decisions and trade-offs.
• Result (2-3 sentences): Quantify the outcome. What changed? What did you learn?

Aim for 90 seconds per story. Time yourself. Most candidates ramble past two minutes and lose the interviewer.

The 90-Second Pitch: "Tell Me About Yourself"

This is not your life story. Structure it as Present → Past → Future:

1. Present (20 sec): "I am a senior backend engineer at Acme Corp, building real-time data pipelines that process 2M events per second."
2. Past (40 sec): "Before this, I spent three years at StartupX where I led the migration from a monolith to microservices, reducing deployment time by 70%."
3. Future (30 sec): "I am excited about this role because your team is tackling distributed ML inference at scale, which combines my backend expertise with my growing interest in AI systems."

"Why This Company?" - The Research Framework

Never give a generic answer. Use this framework:

1. Product/Mission: What do they build and why does it matter to you personally?
2. Technical Challenge: What interesting engineering problems are they solving?
3. Culture Signal: Reference a blog post, talk, or open-source project that shows their values.

"I have been following your engineering blog - the post on migrating to event sourcing resonated because I faced a similar challenge. Your commitment to open-sourcing internal tools shows a culture I want to be part of."

Red Flags to Avoid

• Badmouthing previous employers - even if they were terrible, frame it diplomatically
• Being vague - "I am a team player" means nothing without a specific example
• Taking credit for team work - say "I" for your actions, acknowledge others for theirs
• Memorising scripts - prepare bullet points, not word-for-word answers

Handling "I Don't Know" Gracefully

If you genuinely lack an experience, do not fabricate one. Instead:

1. Acknowledge the gap: "I have not faced that exact situation."
2. Bridge to something related: "The closest experience I have is..."
3. Hypothesise if needed: "If I were in that situation, my approach would be..."

This shows honesty and problem-solving - two things interviewers respect deeply.

Handling Follow-Up Questions

Interviewers will probe deeper: "What would you do differently?" or "How did your manager react?" Prepare for these by:

• Reflecting on what you would change in hindsight for every story
• Knowing the outcome metrics (numbers, timelines, feedback received)
• Being ready to discuss alternative approaches you considered

Practice Strategies

• Record yourself answering questions and review the playback
• Mock interviews with a friend or service like Pramp (free) or interviewing.io
• Write out all 20 stories in bullet-point form, then practise speaking them
• Rotate stories - you need 8-10 strong stories that cover multiple competencies

📚 Further Reading

• Amazon Leadership Principles - The gold standard for behavioural interview competencies
• Pramp - Free peer-to-peer mock interview platform
• interviewing.io Blog - Data-driven insights on what actually works in interviews