STAR Method: What Interviewers Actually Score

For years part of my job was designing interview processes and training hiring managers to run them: which questions to ask, what to listen for, how to rate the answers. So I know what happens on the other side of a behavioral interview, and why candidates who “used STAR” still get low scores.

What the interviewer is writing down

Most companies in the US and Canada use structured behavioral interviews. Each question is tied to a competency the role needs — for example, handling conflict, prioritizing, influencing without authority. The interviewer has a scorecard that describes what a strong, average and weak answer looks like for that competency.

While you talk, they take notes on what you actually did. After the interview, they rate each competency, often on a scale of 1 to 4 or 1 to 5. Then the interviewers compare ratings in a debrief, and the hiring decision is made from those notes.

This means two things. First, every answer is scored separately, against a specific competency. Second, only what you say clearly gets written down: if the interviewer can’t quote a concrete action, it doesn’t count.

STAR in one minute

• Situation: the context, in one or two sentences.
• Task: what you were responsible for.
• Action: what you did, step by step. This is where most of the score comes from.
• Result: what changed, ideally in numbers, and what you learned.

A good balance is about 20% on situation and task, 60% on action and 20% on result. Most candidates do the opposite: two minutes of background and one sentence of action.

Five mistakes that cost points

One more that matters for senior candidates: a story that’s too small for the level. If you’re interviewing for a director role, an example about fixing a spreadsheet won’t show the scope they need, however well you tell it. The same logic decides internal promotions too — it’s one of the reasons strong performers get passed over for career advancement.

Build a story bank, not a script

You can’t predict every question, but you can prepare 8–10 stories that cover the competencies most roles test. One good story can answer several questions.

For each story, write down bullet points, not full sentences: the situation in one line, three or four actions, the result with numbers. Memorized scripts sound rehearsed; bullet points let you adapt the story to the question. Then say the stories out loud — here’s how to run a mock interview on your own or with a partner.

Here is a short example for “Tell me about a time you disagreed with your manager”: “My manager wanted to launch a new onboarding process for the whole company at once. I was responsible for the rollout and thought it was too risky. I pulled data from our last two rollouts, showed that issues had peaked in the first month, and proposed a pilot with two teams first. He agreed. The pilot found three problems we fixed before the full launch, and onboarding complaints dropped by about half compared to the previous rollout.”

If you’re changing careers or returning after a break

Your stories don’t have to come from the industry you’re applying to. A conflict you resolved as a teacher, or a budget you managed as a volunteer, demonstrates the same competency as one from a corporate job. Give the context in one sentence that an outsider will understand, then focus on what you did. Interviewers score behavior, not job titles. More on both situations: how to make a mid-career change and how to explain a gap in employment.