Behavioural interview questions: mastering the STAR method

What are behavioural interview questions?

The premise is simple: past behaviour predicts future performance. When a hiring manager at WSO2, IFS, or John Keells Holdings asks "Tell me about a time you dealt with a difficult stakeholder," they're not making small talk. They want evidence that you can actually do what your CV claims.

Behavioural questions show up in virtually every serious interview in Sri Lanka — from Hatton National Bank and Commercial Bank of Ceylon to tech companies like Virtusa and 99X. If you've only rehearsed technical answers, you're walking into these interviews half-prepared.

The STAR method: a simple framework

STAR stands for four things:

• Situation — Set the scene in one or two sentences. The context, the team, the company.
• Task — What was your specific responsibility in that situation?
• Action — What did you do? (This is the most important part — use "I", not "we".)
• Result — What happened because of your actions? Quantify where you can.

The method works because it keeps your answer focused. Most candidates talk for too long about the situation and barely get to the action. A disciplined STAR answer spends roughly 10% on situation, 10% on task, 60% on action, and 20% on result.

Common questions and how to break them down

Here are the behavioural questions that come up most in Sri Lankan interviews — and what interviewers are actually listening for:

"Tell me about a time you worked under pressure." Common in finance and product companies. Think of a real deadline — an audit at a bank, a product launch at a startup, a client escalation at an outsourcing firm. Your action should show how you prioritised, not just that you stayed late.

"Describe a time you disagreed with your manager." This trips up many Sri Lankan professionals who default to "I always follow instructions." Interviewers want to see professional maturity. A strong answer shows you raised the concern respectfully, explained your reasoning clearly, and adapted when the decision was final.

"Give me an example of a time you led a team." Leadership here doesn't mean a job title. A junior developer who organised a cross-functional retrospective at a Colombo tech startup has a leadership story. Focus on what you did to align people, not just what the outcome was.

"Tell me about a failure." The trap is either over-apologising or picking something so minor it sounds fake. Pick a real setback — a missed target, a project that didn't land — and spend most of your answer on what you learned and changed afterward.

Build your story bank before the interview

The most common mistake is waiting until the day of the interview to think of examples. Instead, before any serious interview, write out five to seven career stories, each with a clear situation, a defined task, specific actions, and a measurable result. These become your STAR story bank.

Organise them around themes:

• Handling conflict or a difficult stakeholder
• Delivering under a tight deadline
• Adapting to rapid change (navigating the 2022 economic crisis is a real story for many)
• Taking initiative without being explicitly asked
• Helping a teammate grow or onboard

One story can flex to answer several different questions. An example about reorganising your team's tracking process at a Colombo-based fintech might work for "Tell me about a time you improved a process" — and equally for "Describe a time you showed initiative."

Why numbers matter more than you think

Sri Lankan professionals often undersell themselves by leaving out specifics. Compare:

"I helped reduce onboarding time for new joiners."

versus:

"I redesigned the onboarding checklist at MAS Holdings, cutting average time-to-productive from three weeks to nine days and reducing first-month attrition by around 15%."

The second version is memorable and signals the kind of thinking that gets you promoted. If you don't have exact figures, use honest estimates: "roughly," "approximately," "by around X%." That's still far more compelling than a vague claim, and no interviewer will penalise you for it.

One thing most candidates skip

After you finish a STAR answer, pause for a moment and check in: "Does that give you what you were looking for?" This lets the interviewer redirect if your story missed the mark. Most won't redirect — but the ones who do will appreciate that you asked.

It also signals that you're listening, not just reciting a rehearsed speech. In Sri Lankan corporate culture, where senior leaders often value humility and responsiveness, that small pause can leave a stronger impression than any polished monologue.

Your next interview could be days away. Spend 30 minutes this week writing three to four moments from your career mapped to STAR. When the interviewer leans forward and says "Tell me about a time..." — you won't need to scramble.