Competency interview questions — “tell me about a time when…” — are scored differently from the rest of the interview. The interviewer is not forming an impression. They are marking your answer against written criteria, and most candidates lose marks in the same two places every time.
The Short Answer
STAR structures your answer into Situation, Task, Action and Result. Spend about 15% of your answer on the situation, 10% on the task, 60% on the action and 15% on the result. Most candidates invert that, spending two minutes on background and twenty seconds on what they actually did.
Why Interviewers Do This
Competency questions exist because asking “are you a good problem-solver?” produces no usable information. Everyone says yes. So instead the interviewer asks for an instance, and scores the evidence.
This has a consequence worth internalising: a well-delivered story about a small problem beats a vague account of a big one. The interviewer is not measuring the scale of your achievements. They are measuring whether you can demonstrate a specific behaviour actually happened.
The Four Parts, and How Each Goes Wrong
Situation. Where and when, in two sentences. The failure here is scene-setting — organisational history, how you got the job, who reported to whom. Nobody is scoring this part. Get out of it fast.
Task. What you were responsible for. Most candidates skip this entirely, which leaves the interviewer unable to tell whether you led the work or watched it. One sentence, but never zero.
Action. The bulk of your answer, and the part that is actually scored. What you did, in sequence, including the decisions you made and why. If you are not saying “I decided”, “I noticed”, “I changed”, you are not yet in the Action.
Result. What changed, with a number wherever one exists. Time saved, errors reduced, revenue, volume, a deadline met. And if the result was mixed, say so — then say what you learned. A candid mixed result is more credible than an implausibly clean one.
The “We” Problem
This is the single most expensive habit in competency interviews, and it costs candidates from our region more than most.
Asked what you did, many people answer in the first person plural. “We identified the bottleneck. We rebuilt the process. We cut the backlog by half.” Every sentence is true, and the interviewer cannot score a single one, because nothing in it tells them what you contributed.
The instinct behind it is a decent one. In much of Nigeria, Ghana, Kenya, India, Pakistan and the Philippines, claiming individual credit in front of strangers reads as immodest, and saying “I” about team work can feel close to dishonest. That instinct is not wrong. It is just miscalibrated for a scoring interview.
The resolution is simple and requires no arrogance at all: credit the team for the outcome, and be specific about your own part in it.
“The team cut the backlog by half over six weeks. My part was the intake process — I mapped where files were stalling, found that 40% were waiting on one signature, and proposed delegating that approval to team leads. I wrote the case, took it to the head of department, and ran the change for the first month.”
That is generous about the team and completely clear about you. Nobody could call it boastful. Every sentence is scoreable.
Before and After
“Tell me about a time you handled a difficult customer.”
Before:
In my former company we had many customers and some of them were very difficult. I have always believed that the customer is king, so we always tried our best to satisfy them. We would listen to their complaints and resolve them professionally. My manager was always happy with how we handled such situations.
No instance, no task, no action, no result. This scores zero on every criterion — not because the candidate is weak, but because there is nothing in it to mark.
After:
(S) Last March a corporate client threatened to cancel a contract worth about 15% of our monthly revenue after we missed two deliveries. (T) I was the account manager, so the recovery was mine to run. (A) I asked for a meeting the same week rather than replying by email, because I wanted to hear the full complaint. It turned out the missed deliveries mattered less than not being told in advance. So I set up a Friday status message for them, agreed a two-day warning rule with our logistics lead, and asked the client to name one person I would deal with directly. I also waived the late fee, which I had authority to do up to a limit. (R) They stayed. Twelve months later they had increased their order volume by about a third, and we rolled the Friday update out to our four other corporate accounts.
Notice what the second version contains: a timeframe, a stake, a named responsibility, a decision with a reason behind it, three specific actions, an admission of what the real problem was, and two results — one for the client and one for the business.
Build a Story Bank, Not Answers
You cannot prepare an answer for every possible question. You can prepare six to eight stories that cover most of what gets asked.
Pick incidents that show: leading without authority, handling conflict, fixing a mistake of your own, working under a hard deadline, persuading someone senior, improving a process, and dealing with ambiguity.
Write each once in full STAR form. Then practise telling each from different angles, because one incident answers several questions. The backlog story above works for problem-solving, for influencing, and for initiative, depending on which part you emphasise.
Do not memorise the words. A recited answer sounds recited, and interviewers hear it immediately. Memorise the shape and the numbers.
When STAR Is the Wrong Tool
Candidates who have just learned the framework tend to force it onto every question, which is its own kind of wrong answer.
- Hypotheticals — “what would you do if…” wants your reasoning, not a story. Walk through how you would think about it. You can add a brief real example at the end
- Motivation questions — “why this company”, “why this role” want a genuine answer about fit, not a case study
- Technical questions want the technical answer
- “Tell me about yourself” wants a two-minute professional summary, not a single incident
Questions About Failure
“Tell me about a time you failed” is a real question and STAR still applies, with the learning as the Result.
Two mistakes to avoid. The first is the disguised boast — “I work too hard”, “I care too much about quality”. Interviewers have heard it and it reads as evasion. The second is choosing a failure so severe it raises real doubts.
Pick something genuinely yours, genuinely recoverable, and old enough that you have visibly changed since. Own it in one sentence without over-apologising, spend most of the answer on what you did differently afterwards, and if you can point to a later situation where the change held, do.
Recorded and Remote Interviews
Many employers now use one-way video interviews, where you record answers with no interviewer present. STAR matters more there, not less — there is nobody to prompt you back on track.
Practical points: check the time limit before you start, and keep to about 90 seconds to two minutes per answer. Keep a single index card with your story titles and key numbers just off-camera — not a script. Look at the camera lens rather than your own image. And test your connection and lighting in advance, because in most systems you get one attempt.
STAR Interview FAQ
What does STAR stand for?
Situation, Task, Action and Result. The Action should take roughly 60% of your answer, because that is the part being scored.
Should I say “I” or “we”?
Both, deliberately. Credit the team for the outcome and be specific about your own contribution. Answering entirely in “we” leaves the interviewer unable to score anything you personally did.
How long should an answer be?
Around 90 seconds to two minutes. Under a minute usually means the Action is missing; over three means you are still describing the Situation.
What if I have no work experience?
Use university projects, NYSC or national service placements, volunteering, family business work, or running a society. The framework does not require a salaried job — it requires a specific instance where you did something.
Can I use the same story twice?
In one interview, avoid it if you can — variety shows range. Across different interviews, absolutely. Six to eight well-prepared stories will cover most questions you meet.
What if I cannot remember a relevant example?
Say you would like a moment to think — that is entirely acceptable and better than filling silence with generalities. If nothing fits, offer the closest thing and say honestly how it differs. Never invent an example; follow-up questions expose it quickly.
Do I need numbers in the Result?
Where one honestly exists, yes — it is what makes the result checkable. Where none does, describe the concrete change instead. Do not invent figures.
Your Next Step
Write one story out tonight, in full, in the four parts. Then read the Action section back and count how many sentences begin with “we”. That count is the gap between what you did and what an interviewer can credit you for.
Once the stories are ready, make sure the document that gets you into the room is doing its job: our guide to writing a CV that passes ATS screening covers what actually gets screened, and separates the real rules from the folklore. Then aim it somewhere — Australian skilled migration, visa-sponsored jobs in Canada and jobs in the UAE all run competency interviews at some stage.
KINGNAMY never charges fees and does not sell interview coaching. This guide exists so you do not need to buy any.
No comments yet — be the first to share your thoughts or ask a question about this opportunity.