Behavioural interview questions: how to use the STAR method

What is a behavioural interview question?

It is any question that asks what you did, not what you would do or what you think. You can recognise it by how it opens: "Tell me about a time…", "Give me an example of…", "Describe a situation where…", "Walk me through how you handled…". The interviewer wants one specific occasion, with you in it.

Two neighbours get confused with it.

• Situational questions ask what you would do: "What would you do if a client disagreed with your recommendation?" Answer with your approach, then, if you can, "I actually had something similar happen…" and turn it into a short STAR example. Real beats hypothetical every time.
• Opinion questions ask what you think: "What makes a good team?" A two-sentence view is fine, but an example is what makes it credible.

Most Canadian corporate interviews for the roles our students target include behavioural questions, often several in a row. Some interviews are almost entirely behavioural. If you have ever come out of an interview thinking "they only asked me about times I did things", that was one.

Why do employers ask behavioural questions?

Because what you did last time is better evidence than what you say you would do next time. Anyone can say they handle conflict calmly. A specific story about a specific conflict, with what you did and how it ended, is much harder to fake and much easier to believe.

You can see this logic in the guidance the Public Service Commission of Canada gives to federal public service interviewers. It tells them that when they ask behavioural questions, they should establish the particulars of the situation, task, problem or context, the actions the applicant took, and the results or impact of those actions [2]. That is guidance for the federal public service, not a rule for private employers. But it is the clearest public statement of what an interviewer asking "tell me about a time" is listening for, and it is STAR in everything but name.

It also tells you what happens next. Interviewers who are listening for those parts will ask for any part you skipped. "What was your role specifically?" "What happened in the end?" "What would you do differently?" In the mock interviews I run, those follow-ups are where weak answers fall apart, because the candidate did not decide in advance what the story actually was.

How does the STAR method work?

STAR is four parts, in order, with very uneven weight. Job Bank recommends it as a way to structure your examples in an interview [1]. The part most guides leave out is the proportion.

If you remember one thing from this guide, make it the third row. The Action is the part the interviewer is scoring. Situation and Task are only there so the Action makes sense.

Bani Singh wrote about behavioural questions in our newsletter in February 2024 using CAR instead: Context, Action, Result. It is the same idea with the Task folded into the Context. We are not attached to the acronym. Use whichever one you can remember with your heart rate up. The point is that the answer has a shape, and that the shape is heavy in the middle.

A STAR answer, before and after

Here is the same experience told twice, in answer to "Tell me about a time you had to deal with a difficult stakeholder."

Before. This is what we hear in most first mock interviews.

So at my last company we were implementing a new CRM system, and it was a big project, there were a lot of teams involved, sales, marketing, IT, and the timelines were very tight because leadership wanted it before the new financial year. There was one sales manager who was not happy with the project and he was quite difficult. We had a lot of meetings with him and eventually we managed to get him on board and the project was successful.

It is all true, and it scores almost nothing. Most of it is Situation. The Action is "we had a lot of meetings", which could mean anything. The Result is "successful", which means nothing. And the interviewer still does not know what you did.

After. The same story, restructured.

Situation. We were moving our sales team to a new CRM, and the sales manager for our largest region was openly against it. His team was a third of our revenue, so if they didn't adopt it, the project failed.

Task. I was the project coordinator, and it was my job to get his team trained and using the system before launch.

Action. First, I booked thirty minutes with him alone rather than raising it in the group meeting, and asked what his actual concern was. It turned out not to be the software. He was worried his reps would lose a week of selling time to training. So I changed the plan for his team. I split the training into four 45-minute sessions before the working day instead of two full days, and I asked him to pick one of his reps to test the system with me first, so the feedback came from inside his team. I also sent him a short weekly note with his team's progress, so he never heard about a problem from someone else first.

Result. His region was fully live on launch day, and his test rep ended up running the refresher sessions for the other regions. What I took from it: when someone blocks a project, find out what they are protecting before trying to convince them.

The second version is barely longer. The difference is where the words went: the Action now carries three specific decisions, each with a reason, and the Result is something an interviewer can write down. (That example is illustrative, not a student's story. Your version has to be your own.)

Notice the paragraph breaks too. You will not say "Situation", "Task" out loud in the interview, but you should hear the four parts yourself as you speak.

The five ways STAR answers go wrong

These are the patterns I see most in mock interviews. Most people who struggle with behavioural questions are doing one or two of them, and they are all fixable before your next interview.

1. All situation, no action. The most common one by far. If your first minute is still background, you have lost the interviewer. Fix: write your Situation and Task as two sentences, and practise stopping there.
2. "We" instead of "I". "We decided", "we built", "we delivered". In many workplaces that is simply good manners, but a Canadian interviewer scoring your Action cannot tell what you did. Say what you did in the first person, and credit the team in a sentence of its own. There is more on this in why capable people fail Canadian job interviews, mistake 3.
3. No result, or a vague one. "It went well." "The client was happy." Give a number, a date, a before-and-after, or something that stopped going wrong. If there genuinely is no number, say what changed and who noticed.
4. A hypothetical in disguise. "In that kind of situation, I would usually…" is not an example. The interviewer asked for a time. If you cannot think of one, say so briefly and offer the closest real one you have.
5. Too long, or memorised word for word. Past about two minutes, the interviewer stops listening closely. A memorised script, on the other hand, breaks the moment the question is phrased slightly differently, and it sounds memorised. Prepare the four parts of each story, not the sentences.

Build a story bank before the interview

Prepare six real stories, each told in STAR, and you can answer most behavioural questions by choosing among them. Start with three strong ones, then add three more. This is the preparation that actually moves results, and it is the part most people skip because it takes an evening.

Pick stories that each show several things, then map them.

For each story, write four lines, one for each part of STAR, and one number. Not a script. Then say each one out loud, timed. You will find that the first attempt runs to four minutes and has no result. That is normal, and it is exactly why you do this at home and not in the interview.

The same stories feed your other answers. The result from your best story often belongs in your answer to "Tell me about yourself", which Bani Singh breaks down in how to answer "Tell me about yourself" with the WWW framework.

Common behavioural questions, and what they are really testing

Every one of these is a request for a specific story. Knowing what sits underneath each one tells you which story from your bank to pick.

Can you use examples from outside Canada, from school, or from a survival job?

Yes. A behavioural question asks how you behaved, and you behaved the same way whichever country you were in. Use your strongest real example, add one line of context so the interviewer can judge its scale, and tell it in STAR like any other.

The Public Service Commission of Canada makes the same point in its guide to mitigating bias in assessment. It lists too much emphasis on past work behaviours as a potential bias, and encourages hiring managers to let people draw on all their experience, including volunteer, school or community work, within and outside Canada [3]. That guide is written for the federal public service, and a private employer is not bound by it. It is still the government's own advice to its own interviewers, and it matches what we tell students: the best example is the most relevant one, wherever it happened.

Three practical notes.

• Examples from abroad need context, not apology. "At a national logistics company in India, about 3,000 people, I ran operations for 11 warehouses." Then the story. More on presenting that experience is in our guide to getting hired in Canada without Canadian experience.
• A survival job is full of behavioural stories. Difficult customers, a manager who changed the schedule at the last minute, training a new colleague, a busy shift that went wrong. For a customer-facing or sales role, these can be your best material.
• School and volunteer work count, especially if you are early in your career. A group project where a teammate stopped contributing is a real conflict story. Tell it with the same care as a work one.

How do you answer "Tell me about a time you failed"?

With a real failure, told in STAR, where the Result includes what you changed afterwards. It is the behavioural question people most want to dodge, which is exactly why interviewers ask it. The candidate who tells a real story and shows what they learned comes across as safer to hire than the one who claims never to have failed.

What does not work:

• A disguised success. "I failed to delegate because I cared too much about the quality." The interviewer hears the move.
• A failure that was someone else's fault. If the story ends with the client, the manager or the market being the problem, you have not answered the question.
• Something catastrophic and recent. Choose a real failure with a clear lesson, not the one that still keeps you up at night.

What does: a genuine mistake that was yours, what it cost, what you did to fix it at the time, and the concrete thing you do differently now. The last part is the one that gets you hired. "Since then, I send a written summary after every client call, so nothing depends on my memory" is a Result an interviewer can picture on their team.

How should you practise behavioural answers?

Out loud, timed, and with someone watching if you can arrange it. Reading your story bank silently feels like preparation, and it is not. The words you rehearse in your head come out differently at the pace of speech, and the first time you hear yourself say them should not be in the interview.

1. Say each story out loud, with a timer. Aim for about two minutes. Cut Situation first.
2. Record yourself once. Listen for "we", for filler words, and for whether the Result is clear.
3. Have someone interrupt you. A friend asking "what did you do?" halfway through teaches you more than ten uninterrupted run-throughs.
4. Do it with someone who interviews for a living, if you can. In our coaching that means full one-on-one mock interviews with feedback straight afterwards, at least four per student and more for anyone who needs them.

It works when people actually do it. Pratima, who spent two years applying to Canadian banks, found the behavioural questions the hardest part of her interviews: she was not able to answer them properly. She went through our interview book, the videos and the recordings of past weekly calls where other students shared how they had answered, then did a mock interview with Bani Singh a few days before her real interview and used that feedback in the room. Her offer came within a week of the interview.

What to do after a behavioural interview

Write down every question you were asked, which story you used for each, and where you felt the answer go thin. Do it the same day. That list is the most useful preparation you will ever have for the next interview, because it is made of real questions from real employers in your field.

If you are in Ontario, there is now a rule about hearing back. Since 1 January 2026, an employer covered by Ontario's job-posting rules that interviews you for a publicly advertised posting must tell you whether a hiring decision has been made within forty-five days of your last interview [4]. It does not require them to explain the decision, and it applies in Ontario only. It does mean that silence past forty-five days from a covered employer is not how the process is supposed to work.

If you keep reaching the last round and losing there, the problem may not be behavioural questions at all. Bani Singh's piece on why people get rejected after the final interview covers the three things final rounds are really deciding.