Behavioural Interviews
36 questions across 9 competency areas. Practice with the STAR framework.
Keep this brief — 1-2 sentences. Interviewers want the story, not the backstory.
Distinguish between what the team did and what YOU specifically owned.
This is the most important part. Use "I" not "we". Give 3–4 specific actions.
Quantify wherever possible: "reduced incidents by 40%", "shipped 2 weeks early".
Difficulty
Tell me about a time you led a project or initiative without formal authority.
Interviewer is assessing your ability to influence peers and drive outcomes without a management title.
Describe a situation where you had to influence a senior stakeholder or executive to change direction.
You disagreed with a product or architecture decision being pushed from above. How did you handle it?
Tell me about a time you mentored a junior engineer and helped them grow significantly.
A new grad joined your team 6 months ago. Describe the structure of your mentorship and the outcome.
Tell me about a time you had to prioritize between multiple urgent competing demands.
Your sprint is full, a production issue just came in, and your manager needs a report by EOD.
Describe a time you drove a meaningful change in your team's engineering processes or culture.
Think about something like introducing observability, shifting to IaC, or improving on-call hygiene.
Tell me about a significant disagreement with a colleague over a technical approach.
You both had strong opinions on the right architecture. How did you resolve it?
Tell me about a time you disagreed with your manager about a technical or process decision.
Your manager wanted to ship a feature you believed had serious reliability or security risks.
Describe a time you had to say no to a stakeholder request.
Product asked for a feature on an impossible timeline, or asked you to cut corners on security.
Tell me about a time you received very critical feedback. How did you respond?
Your manager or a senior peer told you something difficult — about your code, communication, or attitude.
Tell me about a time a teammate was consistently underperforming and it was affecting the team.
Missed deadlines, low-quality PRs, or disengaged in standups — how did you handle it?
Tell me about a production incident you caused. What happened and what did you learn?
Walk me through the incident: discovery, impact, remediation, and what changed afterward.
Tell me about a time you made the wrong architectural or technical decision.
A choice you made early in a project that cost the team time, money, or stability later.
Describe a time you missed an important deadline. What was the impact and how did you handle it?
A quarterly release or a critical integration that slipped — what went wrong and what did you own?
Tell me about a project you led that failed or was cancelled. What did you learn?
Think of a migration, re-architecture, or product initiative that did not reach its goal.
Describe a successful cross-functional project you worked on with product, design, and engineering.
How did you align on goals, handle disagreements, and ensure the technical constraints were understood?
How have you kept a distributed or remote team aligned and productive on a complex project?
Think about async communication, time zones, knowledge sharing, and culture in a remote-first team.
Tell me about a time you went significantly above and beyond for your team or a colleague.
When did you do something that was clearly outside your job description or comfort zone for someone else?
Describe how you onboarded a new team member effectively. What did you build or establish?
You were responsible for getting a new engineer productive. What did you do in their first 30/60/90 days?
Tell me about a time you chose simplicity over a technically superior or more impressive solution.
You could have built something more sophisticated, but opted for the boring, obvious approach. Why?
Describe a time you had to make a build vs. buy decision for a significant technical component.
Should you use an off-the-shelf solution or build it yourself? Walk me through your evaluation.
Tell me about a time you had to balance technical debt against shipping new features.
The business wanted features but the codebase was fragile. How did you navigate the tension?
Tell me about a time you reversed or significantly changed a technical decision you had made.
New information, a failed assumption, or changing requirements meant you had to pivot.
Tell me about a time you had to explain a complex technical issue to a non-technical audience.
An exec or a board needs to understand an outage, a migration risk, or a technology choice.
Describe a time you had to deliver bad news to a stakeholder or your team.
A feature missed the deadline, the migration broke production, or the budget was exhausted.
Describe a time a miscommunication caused a problem on your team. What happened and what changed?
A ticket was misunderstood, a requirement was lost in translation, or an assumption was never validated.
Tell me about a time you delivered a project under significant constraints — time, people, or budget.
You had to do more with less. How did you manage scope, expectations, and delivery?
Describe how you handled scope creep on a project you were responsible for.
Mid-sprint a new request came in that could derail the timeline. How did you manage it?
Tell me about the most technically complex project you have managed end to end.
Walk me through the problem, your approach, how you managed dependencies, and the outcome.
Tell me about a time you had to make explicit trade-offs between quality, speed, and cost.
The classic triangle: pick two. How did you make the call and communicate it?
Tell me about a time you had to learn a new technology or domain quickly under pressure.
You were thrown into an unfamiliar stack or domain with a deadline. How did you approach it?
Describe a time you received feedback that fundamentally changed how you work.
Something a manager, mentor, or peer said that you act on every day — not just once.
How do you stay current with the rapidly evolving cloud and DevOps landscape?
New AWS services, Kubernetes updates, security CVEs, IaC tools — how do you keep up without drowning?
Tell me about the most stressful on-call incident you have handled.
Walk me through the severity, your role, the diagnostic process, and how you kept your composure.
Describe a time you had to debug a critical issue with very limited information or context.
No logs, no metrics, no runbook — just user reports and a broken service. How did you proceed?
Tell me about a time your system went down or degraded during peak traffic.
Black Friday, product launch, or a viral moment — unexpected load broke something. What happened?
How would you handle discovering that your system had been compromised or had a data leak?
AWS keys in a public GitHub repo, or a database with PII exposed. Walk me through your response.