Behavioural questions have quietly taken over the interview. Instead of asking what you would do in a hypothetical situation, an interviewer asks what you did in a real one — because how you behaved last year is a far better guide to how you will behave next year than how well you can improvise an answer.
The questions are not hard to spot. They open with 'tell me about a time when', 'give me an example of', or 'walk me through a situation where'. What catches people out is the answer: most of us tell the story in the wrong order, spend too long on the setup, and never say what changed because of us.
What the interviewer is actually listening for
Behind every behavioural question is a competency the hiring team has agreed matters for the role. Ownership. Dealing with ambiguity. Working with people who do not report to you. Recovering from something going wrong. The question is the wrapper; the competency is the thing being scored.
That is why a well-told story about the wrong competency scores badly. Before you answer, work out which of these the question is reaching for — and if you genuinely cannot tell, ask. 'Are you more interested in how I handled the technical side or how I handled the stakeholders?' is a reasonable question and reads as thoughtful rather than evasive.
STAR, and where most answers go wrong
STAR is the standard shape for these answers: Situation, Task, Action, Result. It works because it forces the story into the order an interviewer can follow, and because it ends on the part they are actually scoring.
The proportions matter more than the acronym. Roughly a fifth of your answer sets the scene, a tenth states what you were responsible for, well over half covers what you personally did, and the last tenth says what changed. Most weak answers invert that: three minutes of context, thirty seconds of action, and no result at all.
- Situation: two sentences. Where you were, when, and what was at stake. No org chart.
- Task: what you specifically were responsible for delivering, as distinct from what the team was doing.
- Action: the bulk of it. What you decided, what you did, what you chose not to do, and why.
- Result: what measurably changed, and ideally what you learned that you still use.
Say 'I' more than you think you should
The single most common flaw in behavioural answers is the collective 'we'. It is generous, it is how most people talk about work they are proud of, and it makes your contribution impossible to score. An interviewer cannot credit you for something a group did.
Use 'we' to set the scene and 'I' for everything after it. 'We had four weeks to migrate the reporting stack. I owned the cutover plan, so I mapped every dependency, negotiated a two-day freeze with support, and ran the rehearsal on the Saturday before.' Same story, but now there is a person in it.
SOAR, when the story needs tension
For questions about problem solving or resilience, swapping Task for Obstacle gives the story a spine: Situation, Obstacle, Action, Result. It puts the thing that made the work hard right at the front, which is usually the interesting part and almost always the part being assessed.
It is the same discipline, not a different framework. If the question is 'tell me about a time something went wrong', lead with what went wrong rather than working up to it for two minutes.
The five categories worth preparing
Almost every behavioural question is a variation on one of five themes. Prepare one strong story for each and you can answer most of what you are asked without improvising.
- Problem solving: a time you got somewhere with incomplete information or not enough resource.
- Collaboration: a time you worked with someone whose style or priorities were nothing like yours.
- Leadership and initiative: a time you took responsibility for something nobody had asked you to own.
- Adaptability and failure: a time you got it wrong, and what you did in the fortnight after.
- Conflict: a time you disagreed with a decision, said so, and had to live with the outcome either way.
Build a story bank, not a script
Write down six to eight things you have actually done, in a page or two: the situation, what you owned, what you did, and the number at the end of it. Keep the file somewhere you will find it again — you will reuse it for years.
The point of the bank is flexibility. One good story usually covers three or four competencies depending on which part you emphasise, so you are not memorising answers; you are memorising material. Rehearse out loud once or twice before an interview, then stop. Over-rehearsed answers sound like a recital, and interviewers notice.
Read the job description like a scoring sheet
Before each interview, take the posting apart and list the competencies it keeps returning to. Those are the ones the panel has been briefed on, and they are what your stories should be selected against. If the posting mentions 'working across teams' three times, one of your prepared stories had better be about exactly that.
This is the same reading Apply Engine does when it scores a role against your profile: it pulls out what the posting actually asks for rather than matching on the job title, and shows you which requirements you already meet. The gaps it flags before you apply are usually the questions you get asked in the room.
Remote rounds and recorded answers
More first rounds now happen on video, and some are recorded with no interviewer present at all. The content of a good answer does not change, but the delivery does: talk to the camera rather than your own face, leave a beat before answering so you do not clip the question, and keep answers to about two minutes — without a listener to nod at you, it is easy to run long.
Check the setup the day before rather than five minutes before. Light on your face, something plain behind you, and a plan for what you do if the connection drops mid-answer.
The short version
Work out which competency is being tested. Set the scene in two sentences, say what you owned, spend most of the answer on what you did, and finish on what changed. Say 'I'. Have six stories ready and pick between them rather than inventing on the spot.
None of that is charisma. It is preparation, and it is the part of interviewing you can control.
