Behavioral questions all share a shape: tell me about a time when…. The premise is that what you did before predicts what you'll do next, which is imperfect but a good deal better than asking whether you're a team player.

Most candidates know about STAR. Far fewer use it well, because the framework is usually taught as four boxes to fill rather than as an argument to make.

STAR, done properly

Situation — the context, in two sentences. Where, when, what was at stake.

Task — your specific responsibility. This is the box people skip, and skipping it is why interviewers can't tell whether you did the work or watched it happen.

Action — what you did, step by step. First person singular. "We" is the enemy of this section.

Result — how it ended, with a number where one exists, plus what you'd do differently.

Two rules that matter more than the acronym:

Spend 60% of your time on Action. That's the part being assessed. A common failure is a beautifully detailed situation, an elaborate task, and then "…so we fixed it and it went well."

Bring a result even when it's ugly. "We shipped three weeks late, but we caught the data corruption bug before it reached customers, and I now run a pre-launch review that has caught two similar issues since" is a stronger answer than a vague success. Interviewers are listening for self-assessment.

Build a story bank, not fifteen answers

Fifteen questions do not need fifteen stories. Most interview loops draw from six or seven traits, and one good story usually serves three or four questions with a change of emphasis.

Pick six projects from the last three years. For each, write down: the situation, your specific role, the three or four things you personally did, the outcome with numbers, and what you learned. That is your story bank. In the interview you are selecting from it and re-framing, not recalling.

The 15 questions, by trait

Conflict and difficult people

Tell me about a time you disagreed with your manager.
Describe a conflict with a coworker and how you resolved it.
Tell me about a time you had to work with someone difficult.

What's being tested: whether you can disagree without damage, and whether you can describe a conflict without making the other person a villain.

Worked answer — disagreeing with a manager:

Situation: "Last year my director wanted to ship our billing migration in a single cutover over a weekend. I thought the blast radius was too big — about 30,000 active subscriptions."

Task: "I owned the migration, so if it went badly at 2am on a Saturday it was going to be me and one other engineer."

Action: "I didn't push back in the meeting — I asked for a day to put together the alternative. I wrote up a three-phase plan: 5% of accounts, then 40%, then the rest, over two weeks, with a documented rollback at each phase. I costed both options in engineer-hours, because his concern was the timeline, and the phased version was only four days longer. Then I asked for fifteen minutes to walk him through it, and I led with the timeline comparison rather than the risk, because that was what he cared about."

Result: "He took the phased plan. We caught a proration bug in the 5% phase that would have hit about 1,200 accounts in a full cutover. It shipped six days later than his original date. The bigger thing I took from it is that I'd initially framed my objection as a risk argument, and it went nowhere until I reframed it in his terms."

Note the last line. Interviewers remember candidates who can name their own mistake inside a story where they were right.

Failure and recovery

Tell me about a time you failed.
Describe a mistake you made and what you did about it.
Tell me about a project that didn't go as planned.

What's being tested: whether you take real responsibility, and whether the lesson produced a behaviour change.

Choose a genuine failure with real consequences. The disguised humblebrag — "I cared too much about quality and we shipped late" — reads as evasion and costs you more than the failure would have.

The structure that works: what went wrong, your specific contribution to it, what you did immediately, what you changed permanently. That last part is the answer. Everything before it is setup.

Leadership and influence

Tell me about a time you led without authority.
Describe how you got buy-in for an unpopular decision.
Tell me about a time you mentored someone.

What's being tested: whether you can move people who don't report to you — the actual definition of seniority in most organisations.

The strongest version of these answers is specific about how you persuaded: who you talked to first, what objection you anticipated, what you conceded. "I brought everyone together and we aligned" describes an outcome, not an action.

Pressure and prioritisation

Tell me about a time you had competing deadlines.
Describe a situation where you had to work under significant pressure.
Tell me about a time you had to say no.

What's being tested: whether you have a prioritisation method or just work longer hours.

Worked answer — competing deadlines:

Situation: "In Q3 I had a compliance deadline and a customer launch land in the same two weeks, both with external commitments."

Task: "I was the only engineer with context on both."

Action: "I wrote out what actually broke if each one slipped. The compliance date was a hard legal deadline with a fine attached; the launch date was a marketing commitment, painful but movable. So I took that to the launch's stakeholder with two weeks' notice rather than two days, offered a reduced-scope launch that kept the date — the demo path working, the admin tooling deferred — and let them choose. They took the reduced scope. Then I blocked mornings for compliance and afternoons for launch so I wasn't context-switching hourly."

Result: "Both landed. The compliance audit passed with no findings, and the launch went out on the original date with about 70% of scope; the rest followed three weeks later. What I'd do differently is raise the collision earlier — I saw it coming a month out and spent two weeks hoping it would resolve itself."

Ambiguity and initiative

Tell me about a time you had to make a decision without enough information.
Describe something you started that nobody asked you to.
Tell me about a time you had to learn something quickly.

What's being tested: whether you can move without instruction, and whether your judgement is sound when the answer isn't available.

For question 13, name what you did to reduce the uncertainty before deciding — who you asked, what you tested, what you deliberately chose not to find out because it wasn't worth the delay.

Delivery notes

Ninety seconds to two minutes. Longer and the interviewer loses the thread; shorter usually means the Action section is thin. Time yourself once and you'll calibrate.

Say "I". Recount the team's contribution honestly, but be explicit about your part. Consistent "we" is the most common reason a strong story fails to land.

Have the numbers ready. Before the interview, write down the numbers attached to each of your six stories. Recall under pressure is unreliable.

Then stop talking. Candidates who reach a clean result and keep going tend to talk their way into caveats. Land it and wait.

Practising

The gap between a story you've written and a story you can tell is only closed out loud. Say each of your six stories to a wall, timed. The ones that run long are the ones with a bloated Situation.

If you want it scored rather than self-assessed, Terview's mock interview runs behavioral rounds and rates each answer on STAR completeness, specificity, and whether the Action section is actually about you. For questions specific to a role and company, the question generator builds a set from the job description.

15 Behavioral Interview Questions and How to Answer Them (STAR Method)