Behavioural interview questions: how to use the STAR method

You've rehearsed your "tell me about yourself," looked up the company on LinkedIn, and ironed the shirt. Then the interviewer at WSO2 or John Keells Holdings leans forward and asks: "Tell me about a time you had to deal with a difficult colleague." Cue the mental blank.

Behavioural questions — those "tell me about a time when..." prompts — trip up even strong candidates because they demand a specific story, not a general opinion. The STAR method gives you a four-part template that keeps your answers tight, credible, and memorable under pressure.

What STAR actually stands for

• Situation – Set the scene in two or three sentences. What was the context and why did it matter?
• Task – What was your specific responsibility? Not the team's — yours.
• Action – The most important section. What steps did you personally take, and why?
• Result – What happened because of those actions? Numbers beat adjectives: "reduced onboarding time by 30%" lands harder than "things improved."

The structure stops you rambling, forces you to own your contribution instead of hiding behind "we," and makes it easy for the interviewer to score you against their competency framework.

Why Sri Lankan employers use behavioural interviews

Virtusa, IFS, Hemas Holdings, Dialog Axiata, and most multinationals with offices in Colombo adopted structured behavioural interviewing because it predicts on-the-job performance better than hypothetical questions. Mid-market companies like 99X Technology, Calcey Technologies, and Cambio are doing the same. If your target role mentions "leadership," "stakeholder management," or "cross-functional collaboration" in its JD, you will face at least three STAR questions — usually in round two or three.

Four questions you'll almost certainly face

"Tell me about a time you missed a deadline."

Every interviewer knows timelines slip. Dodging this question signals poor self-awareness. Pick a genuine miss — maybe a client delivery at Virtusa was delayed when a third-party SLIPS payment integration failed the week before go-live. Show how you communicated early, reprioritised what you could ship, and what safeguard you put in place for the next project.

"Describe a situation where you had to convince someone who disagreed with you."

This tests influence without authority — critical for senior IC and team lead roles. Your Action section should show you listened first, gathered data, then made a targeted case. "I pulled three months of support-ticket data to show the feature was causing more confusion than it solved" is specific enough to be believable.

"Give an example of managing multiple competing priorities."

A staple at lean teams everywhere, from PickMe to Takas to smaller BPOs along Galle Road. The interviewer wants your triage logic, not just proof that you survived. Explain how you assessed urgency versus importance, what you communicated to stakeholders, and what you deferred explicitly rather than by accident.

"Tell me about a significant failure."

The trap here is over-polishing the lesson. Keep the failure real, the cost honest, and the reflection forward-looking. "I lost that client renewal, but the six-point risk checklist I built from it has been used on every proposal since" works. A vague "I learned a lot about communication" does not.

How long should a STAR answer be?

Aim for 90–120 seconds when spoken. That is roughly three to four sentences per section. Situation and Task together should take no more than 25 seconds — the interviewer already knows their industry context. Pour most of your time into the Action step, where your judgment and skills are actually visible.

Mistakes that cost candidates the offer

• Using "we" all the way through the Action step. The panel is assessing your contribution. Swap "we implemented" for "I proposed" or "I owned."
• Reaching back to university. Once you have two or more years of work experience, leave the SLIIT or University of Moratuwa group project behind. Hiring managers find it tells them nothing about how you'll behave in their team.
• Skipping the Result. Even a qualitative outcome counts — "the team adopted the new process and it's been standard ever since" closes the loop. Trailing off mid-story raises doubts about whether the action actually worked.
• Choosing a story with no real tension. STAR is built for adversity. A smooth project with no obstacles, no conflict, and no hard calls gives the interviewer nothing to score.

Prepare five stories, not fifty

You don't need a bespoke anecdote for every possible prompt. Build five robust stories from your career — each anchored to a different competency: conflict resolution, taking initiative, handling failure, collaboration under pressure, and a technical or analytical challenge. Almost any behavioural question at Brandix, HNB, or Softlogic can be answered by adapting one of those five.

Write them down. Say them aloud until they stop sounding like you're reading a script. Then tighten every Action step until it's specific enough that only someone who was actually there could have said it.

The next time a panel at Dialog Axiata or the Central Bank leans forward with "tell me about a time when...", you'll reach for a story — not a blank.