The STAR Method: How to Answer Any Behavioural Interview Question

"Tell me about a time when you had to deal with a difficult stakeholder."

"Describe a situation where you failed and what you learned."

"Give me an example of how you've led a team through a challenging period."

These are behavioural interview questions. They're used because past behaviour is the best available predictor of future behaviour. Hiring managers use them to cut through rehearsed, theoretical answers and get to what you've actually done.

Most candidates who fail these questions don't lack experience. They lack a structure to communicate it clearly.

The STAR Method

S — Situation

Set the scene briefly. What was the context? What was the problem or challenge? Keep this to 2–3 sentences — you're providing context, not telling a story from the beginning.

T — Task

What was your specific responsibility in this situation? What were you required to do or decide?

A — Action

This is the most important section. What did you specifically do? Use "I", not "we". Be specific about your choices, your reasoning, and what you did differently from what others might have done.

R — Result

What happened as a result of your actions? Quantify if you can. What did the team, company, or client experience? What did you learn?

A well-delivered STAR answer takes 2–3 minutes. Not 30 seconds (too thin). Not 8 minutes (loses the listener).

Full Example: "Tell me about a time you dealt with conflict on a team"

Situation:

"In my previous role as project lead, a senior developer and I reached a serious disagreement over whether to delay a product release or ship with a risk mitigation plan. The deadline had significant commercial implications — the client had a hard launch event booked."

Task:

"As project lead, I was responsible for the final call. But I also knew that forcing a decision would damage a relationship I needed to work effectively."

Action:

"Rather than escalating or overriding him, I requested a one-on-one conversation and spent the first half of it genuinely listening — not responding — to understand the root of his concern. I discovered it wasn't really about the deadline; it was about post-launch support capacity. His team was already stretched. Once I understood that, I worked with him to design a phased rollout plan that addressed his capacity concern while keeping the core commercial commitment. I then presented this jointly to the client."

Result:

"We shipped on time. The phased approach actually became our standard rollout methodology and is still used by the team. More importantly, that developer became one of my strongest working relationships — he told me later that he appreciated that I'd listened before deciding. That conversation shaped how I approach disagreement now."

Building Your Story Bank

Prepare 8–10 strong stories before any interview. Cover these categories:

| Topic | Story Ready? |

|---|---|

| Leadership and initiative | |

| Managing conflict or difficult people | |

| Failure and what you learned | |

| Working under pressure or with ambiguity | |

| Influencing without formal authority | |

| Going above and beyond | |

| Collaboration and teamwork | |

| Change management or adapting quickly | |

The same story can often be adapted for multiple questions. A story about a failed project might answer: failure, pressure, learning, and leadership questions depending on how you frame the focus.

Common Mistakes

• Too much Situation, not enough Action — the S and T should take about 25% of the answer. The A should be 50%.
• Using "we" throughout — the interviewer wants to know what you did, not what the team did.
• No result — every story needs a landing. What happened? What changed?
• Choosing a weak example — if your best example of handling pressure is a busy afternoon, rethink your story bank.
• Memorising a script word-for-word — know your stories deeply, not your scripts. Rigid recitation sounds unnatural and breaks if the interviewer interrupts.