The STAR method: how to answer behavioral interview questions (with examples)

The four parts, and how long each should be

• Situation (10%): one or two sentences of context. Where you were, what was going on. No company history.
• Task (10%): what you specifically were responsible for. 'I' not 'we'.
• Action (60%): what you did, step by step, and why. This is what they are assessing. Include the decision points and the trade-offs.
• Result (20%): what happened, with a number if you have one, and what you learned or would do differently.

Example: 'Tell me about a time a project's scope changed'

Situation: 'I was leading an EMR upgrade for a provincial health authority, planned for three hospital sites.'

Task: 'Halfway through, leadership asked us to add two more sites without moving the go-live date, and I owned the plan and the budget.'

Action: 'I did three things. First, I re-planned with the steering committee rather than quietly absorbing it: I showed them what five sites meant for testing time and training capacity. Second, I negotiated with the vendor to run training for the new sites in parallel, which cost nothing extra because their trainers were already on site. Third, I cut two low-value customisations from the original scope to protect the testing window, and got that agreed in writing.'

Result: 'All five sites went live on the original date, the budget stayed within 5% of the $3.2M plan, and the committee adopted the re-planning format for later projects.'

Example: 'Tell me about a time you disagreed with your manager'

Situation: 'My manager wanted to launch a new client onboarding flow to all customers at once.'

Task: 'I was the implementation lead and believed a staged rollout was safer.'

Action: 'I did not argue in the meeting. I put together a one-page comparison: the risk of a full launch, what a two-week pilot with three clients would cost in delay, and what we would learn. I asked for 15 minutes with her and walked through it, and I offered to own the pilot personally so it did not add to her workload.'

Result: 'She agreed to the pilot. It caught a billing bug that would have hit every client, and the full launch went out two weeks later with no incidents. I learned that bringing a concrete alternative works far better than objecting.'

The mistakes that make good stories fall flat

• 'We' throughout. Interviewers cannot tell what you did. Use 'I' for your actions and 'we' only for team outcomes.
• No result. 'And it went well' is not a result. A number, a date met, a decision changed, a lesson.
• A story with no decision in it. If you just did what you were told, it is not a strong example of anything.
• Choosing the biggest project instead of the clearest story. A small story with a clear decision and result beats a large vague one.
• Rehearsing word for word. Know the beats, not the script, or you will stall when they interrupt.

Build your story bank before the interview

Write six to eight STAR stories from your last few years, each tagged with the themes it covers: conflict, scope change, failure, leadership, tight deadline, persuading someone, learning something fast. Most behavioral questions map to one of those. In the interview, pick the story that fits and tell it in the structure.

If you want help under pressure, Break-In Bad's interview assistant listens to the question and shows you, on your screen only, which of your stories fits and the points to hit, built from your resume and the job. The interviewer never sees it, even on a shared screen.