Behavioural interview questions ask how you handled real situations in the past, on the idea that past behaviour is the best guide to how you will work in future. The most reliable way to answer them is the STAR method: Situation, Task, Action, Result, with most of your time spent on what you personally did. This guide explains STAR with worked IT examples, the questions you are most likely to face, and how to build a small story bank that covers almost all of them.

Where you will meet behavioural rounds

Product companies, global capability centres (GCCs) and a growing number of services firms now run a dedicated behavioural, “culture fit” or hiring manager round alongside coding and design. Amazon is the best-known example: its interviews are built around 16 published Leadership Principles such as Customer Obsession, Ownership, Dive Deep and Have Backbone; Disagree and Commit, and candidates are expected to answer with specific past examples. Even where it is not a separate round, managers in services companies ask the same questions in the final discussion.

Technical skill gets you shortlisted. These answers often decide between two candidates with similar technical scores, especially for senior and client-facing roles.

The STAR method and how to split your time

MIT’s career advising office suggests a rough split that works well in practice:

PartWhat it coversShare of your answer
SituationContext: team, project, what was happeningAbout 20%
TaskYour responsibility or the goalAbout 10%
ActionWhat you did, step by step, and whyAbout 60%
ResultThe outcome, ideally with a number, and what you learnedAbout 10%

The most common mistake is the reverse: two minutes of background and one line on what you did. Keep the full answer to around two minutes, then let the interviewer dig in.

Worked example 1: a production incident

Question: “Tell me about a time you handled a production issue under pressure.”

  • Situation: “During a festive sale, our order service began timing out and checkout failures rose sharply.”
  • Task: “I was the on-call engineer, responsible for restoring checkout.”
  • Action: “The dashboards showed the database connection pool was exhausted. I traced it to a recommendations call that held connections open, switched it off with a feature flag, and added read replica capacity. I posted updates to the support channel every 15 minutes so they could answer customers. Afterwards I wrote the post-incident review and added alerts on connection-pool usage.”
  • Result: “Checkout recovered in about 25 minutes. The next month the new alert caught a similar build-up before any customer was affected.”

Worked example 2: disagreeing with a senior

Question: “Describe a time you disagreed with your manager or a senior colleague.”

  • Situation: “Our architect wanted to add a new message queue for a reporting feature that had a two-week deadline.”
  • Task: “I was building the feature and thought the queue would add risk without much benefit at our volume.”
  • Action: “Rather than argue in the stand-up, I asked for 30 minutes with him and brought data: our peak was around 200 events a minute, which our existing database handled easily in a quick load test. I proposed a simpler design with a clear trigger for when we should add the queue. He agreed, on condition that I documented the threshold.”
  • Result: “We shipped on time. Eight months later traffic grew past the threshold and we added the queue as planned, with no rework to the reporting code.”

Notice what this shows: respect, evidence over opinion, and willingness to commit to a shared decision. That is what the interviewer is checking.

The questions to prepare for

Most behavioural questions fall into a handful of themes. Prepare at least one story for each:

ThemeTypical questionWhat they are checking
ConflictTell me about a disagreement with a teammate.Maturity, listening, focus on the outcome
FailureDescribe a mistake you made at work.Honesty, ownership, learning
PressureTell me about a tight deadline.Prioritising, communication, trade-offs
LearningWhen did you learn a new technology quickly?Curiosity and speed of learning
OwnershipWhen did you go beyond your role?Initiative without being asked
StakeholdersDescribe a difficult client or stakeholder.Patience, expectation setting
ImprovementTell me about a process you improved.Problem spotting and measurable impact
LeadershipWhen did you help a colleague grow?Mentoring, even without a title

Build a story bank in one evening

You do not need a separate story for every question. Six to eight good stories, each adaptable to two or three themes, will cover almost everything. Here is a simple way to build them:

  1. List your last two or three projects and, for each, write down anything that went wrong, anything you fixed, any argument, and anything you are proud of.
  2. Pick the eight strongest moments. Prefer recent ones, from the last two to three years.
  3. Write each in STAR form in a single table row: one line each for Situation and Task, four or five lines for Action, one or two for Result.
  4. Tag each story with the themes it can answer, for example “incident story: pressure, ownership, learning”.
  5. Check the mix. If every story is a success, add a genuine failure. If every story is solo, add one about working with others.

Freshers can draw stories from final-year projects, internships, hackathons, college fests and technical clubs. The structure is the same; interviewers adjust their expectations.

Answering questions about failure

Interviewers ask about failure to see whether you take responsibility. Choose a real mistake with moderate consequences, such as a missed edge case that reached production or an estimate that was badly off. Say plainly what went wrong and your part in it, then spend most of the answer on what you changed: a test you added, a checklist you introduced, how you now estimate. Avoid disguised boasts like “I work too hard” and avoid stories where the failure was entirely someone else’s.

Practical tips

  • Say “I”, not “we”, for your own actions. The interviewer is assessing you, not your team.
  • Use numbers you can defend: minutes of downtime, percentage of test coverage, number of users, days saved.
  • Never invent stories. Follow-up questions such as “What did your manager say?” or “What would you do differently?” expose made-up answers quickly.
  • Match the company’s values. If a company publishes its principles, read them and pick stories that show those behaviours.
  • Pause before answering. “Let me think of a good example” is perfectly acceptable.
  • End with the learning in one sentence; it shows reflection.

Your opening answer often leads straight into these questions, so it helps to prepare both together. See our guide on answering “Tell me about yourself”. If you are preparing to move from a services company to a product company, where behavioural rounds carry more weight, our six-month switching plan covers the full interview loop.

FAQ

How long should a STAR answer be?

Around two minutes. If the interviewer wants more detail, they will ask; that is a good sign, not a problem.

Can I use the same story twice in one interview?

Try not to within the same round. Use a different story, or explicitly bring out a different aspect: “In that same incident, the harder part was actually managing the client…”

Last reviewed: 8 October 2026.

Sources

Leave a Reply

Trending