Behavioural Interview Questions

What are behavioural interview questions?

Behavioural interview questions ask you to describe something you actually did, rather than what you would do in a hypothetical. “Tell me about a time you disagreed with a technical decision” is behavioural; “How would you handle a disagreement?” is not. For software engineers they usually come in a dedicated round, often run by a hiring manager or a senior engineer, and at many companies they carry as much weight in the final decision as any single coding round.

The interviewer is not grading the story. They are grading it against a rubric of competencies: ownership, dealing with ambiguity, influencing without authority, learning from failure, delivering under constraints. Every company has a version of this list, and the questions are chosen to probe specific items on it. Preparing for behavioural interview questions means knowing which competencies a given company scores and having a story ready for each.

Common behavioural interview questions for software engineers

The exact wording varies, but nearly every question is a variant of a small set of prompts, each mapped to a competency the interviewer is trying to observe:

• Conflict — a time you disagreed with a teammate, a manager, or a design decision, and what happened.
• Failure — a project that went wrong, a bug you shipped, a deadline you missed, and what you changed afterward.
• Ambiguity — a time you were handed an underspecified problem and had to decide what to build.
• Influence — a time you changed a decision you did not have the authority to make yourself.
• Ownership — a time you took on something outside your remit because it needed doing.
• Prioritisation — a time you had more work than time and had to choose what to drop.
• Growth — the hardest feedback you have received and what you did with it.

Six to eight well-prepared stories cover all of these. The same incident often serves several prompts depending on which part of it you emphasise, which is why a story bank works better than preparing an answer per question.

Why company rubrics matter more than a generic list

A behavioural interview at Amazon is scored against the Leadership Principles, and the interviewer will have been assigned two or three specific principles to probe. A behavioural round at a company with a published set of engineering values will map to those values. Answering a question about conflict with a story that demonstrates “bias for action” when the interviewer was assigned “earn trust” is a good story that scores badly.

This is the part most preparation skips. Generic advice gives you a list of questions and the STAR format. It does not tell you that the same question means different things at different companies, or that the competency being scored is often predictable from the company and the level you are interviewing for. The behavioural interview questions here are organised by company, with the competencies each company evaluates and the questions that typically probe them.

How to structure an answer without sounding rehearsed

STAR — Situation, Task, Action, Result — is the standard structure, and it is useful as a checklist. It is a poor script. Answers that march through the four sections in order sound recited, and interviewers hear a dozen of them a week. Use STAR to check that a story has all four parts, then tell it the way you would tell a colleague: a sentence of context, what was hard about it, what you specifically did, and what changed as a result.

Two details separate strong answers from adequate ones. First, “I” rather than “we” when describing the action — the interviewer needs to know what you did, not what the team did. Second, a result that is specific enough to be checked: a number, a shipped date, a decision that was reversed, a process that still exists. “It went well” is not a result.

How behavioural prep fits with the rest of the loop

Behavioural rounds are rarely standalone. The same onsite will include coding interview practice rounds and, for mid-level and above, a system design interview. The stories you prepare should be consistent with the experience on your resume, because interviewers will often pick a bullet from it and ask you to tell the story behind it. When an application in your job application tracker reaches a behavioural round, the company card links to that company's rubric and question set.

What is coming

The behavioural interview questions product is in development. At launch it will cover the same companies as the coding and system design question banks, with a story bank you write once and map to each company's competencies, and company-specific rubrics sourced from candidate reports rather than reconstructed from public values pages. Join the waitlist above to be notified when it opens.