Why behavioural interviews matter for engineers
Most engineers focus exclusively on technical interview preparation — LeetCode, system design, algorithms. But for mid-to-senior roles, 40–60% of the interview process is behavioural.
At companies like Amazon, Google, and Meta, behavioural interviews are structured against specific frameworks (Amazon's Leadership Principles, Google's Googleyness, etc.) and carry equal or greater weight than the technical rounds for hiring decisions.
For senior and staff engineers, the bar is different: the question isn't "can you code?" but "can you operate at a level that multiplies the team around you?"
Collaboration and teamwork
1. Tell me about a time you had to work with a difficult colleague.
What they're looking for: Maturity, empathy, conflict resolution, not throwing colleagues under the bus.
Guidance: Focus on what you did to understand their perspective, how you tried to find common ground, and the outcome. Don't just describe the person as difficult — describe the dynamic.
2. Describe a time you had to give difficult feedback to a peer.
3. Tell me about a situation where you disagreed with your tech lead's technical decision.
4. Describe a time you had to onboard a new team member when you were already under pressure.
5. Tell me about a time you worked across teams to deliver something neither team could have done alone.
6. Describe a situation where a team member was underperforming. What did you do?
7. Tell me about a time you had to work with ambiguous requirements from a non-technical stakeholder.
8. Describe a time you had to say no to a feature request from a PM or designer.
Ownership and initiative
9. Tell me about a time you identified and fixed a problem that wasn't strictly your responsibility.
Amazon Leadership Principle: Ownership. Strong answers involve you proactively addressing a problem, taking it through to resolution, and not waiting to be asked.
10. Describe a time you drove a technical initiative from idea to production without being asked.
11. Tell me about a time you inherited a codebase that was in poor shape. What did you do?
12. Describe a situation where you had to make a technical decision under time pressure without complete information.
13. Tell me about a time you made a mistake that had production impact. What happened and what did you do?
Guidance: Don't minimise the incident. Own it clearly, describe what you did to mitigate it, and spend significant time on what you changed to prevent recurrence. Blameless post-mortems and systemic fixes score highly.
14. Describe a time you advocated for technical investment (e.g. refactoring, test coverage) when the business wanted features instead.
15. Tell me about a time you reduced technical debt that was slowing your team down.
Technical leadership
16. Describe a time you led a technical design discussion with a senior audience.
17. Tell me about a time you mentored a junior engineer. What was your approach?
18. Describe a situation where you had to make a build-vs-buy decision.
19. Tell me about a time you proposed a new tool, framework, or process and had to convince the team to adopt it.
20. Describe a time you reviewed a major PR or architecture proposal and found a significant issue. How did you handle it?
21. Tell me about the most complex technical problem you've solved.
Guidance: Walk through your diagnostic process, the constraints you were working under, the options you considered, and why you chose the approach you did. Depth of reasoning matters more than the outcome.
22. Describe a time you had to balance technical quality with a hard delivery deadline.
23. Tell me about a time you improved your team's engineering practices (testing, deployment, code review, etc.).
Communication and impact
24. Describe a time you had to explain a complex technical concept to a non-technical audience.
25. Tell me about a time you wrote technical documentation that made a meaningful difference.
26. Describe a situation where a miscommunication caused a significant problem. What did you learn?
27. Tell me about a time you presented a technical risk or concern that leadership initially dismissed.
28. Describe a time you had to change course mid-project because of new information. How did you communicate it?
Resilience and growth
29. Tell me about a time you failed to deliver on a commitment. What happened and what did you do?
30. Describe the most critical feedback you've received from a manager. How did you respond to it?
31. Tell me about a time you had to learn a new technology quickly under pressure.
32. Describe a time you worked in a team where morale was low. What did you do?
33. Tell me about a time you faced a significant obstacle on a project. How did you push through?
Prioritisation and delivery
34. Describe a time you were working on multiple projects simultaneously and had to reprioritise.
35. Tell me about a time you had to manage scope to hit a hard deadline.
36. Describe a situation where you had to push back on a timeline or deliverable estimate from above.
37. Tell me about a time you delivered a project that was significantly different from the original spec. How did you manage that?
Situational and values questions
38. What would you do if you discovered a security vulnerability in production code that would require significant time to fix?
39. How do you decide when code is "good enough" to ship?
40. What does "senior engineer" mean to you, and how do you know when someone is ready for that step?
Scoring criteria for SWE behavioural interviews
At most companies, your answers are scored against these dimensions:
| Dimension | What they're looking for | |-----------|--------------------------| | Ownership | Did you take responsibility? Did you see it through? | | Impact | What was the measurable outcome? | | Collaboration | How did you work with others involved? | | Growth | What did you learn? What changed? | | Clarity | Was the answer structured and easy to follow? |
Practise these questions with AI feedback
AI Career Mentor generates behavioural interview questions tailored to your level (junior, mid, senior, staff) and scores your answers on structure, ownership, impact, and delivery. You'll hear your question spoken aloud — exactly as in a real interview.