ummute

Public speaking

Competency-Based Interview Questions: How to Structure Strong English Answers

17 November 2026 · 6 min read

Knowing how to answer competency-based interview questions in English is partly a content problem and partly a speaking problem. Most candidates prepare the story well enough; where they lose the interviewer is in the delivery — a rushed pace, unstressed key words, or a structure so tangled that the point arrives too late, or not at all. This guide addresses both: how to build your answer and how to speak it.

What competency-based questions are actually testing

A competency-based question asks for evidence, not opinion. "Tell me about a time when you had to manage a difficult stakeholder" is not an invitation to explain your general philosophy on stakeholder management. The interviewer wants a specific incident, described clearly enough that they can evaluate the skill themselves.

This matters for your spoken delivery. Because the question demands a narrative — a real thing that happened — your answer has a natural shape: a beginning, a middle, and an end. Your job is to make that shape audible.

The STAR method as a spoken framework

The STAR method (Situation, Task, Action, Result) is widely taught for written preparation, but it is equally useful as a speaking structure. Each letter is a cue to shift register slightly — to signal to your listener that you are moving from scene-setting into action, or from action into outcome.

  • Situation: One or two sentences. Where, when, what was happening.
  • Task: One sentence. What you specifically were responsible for.
  • Action: Three to five sentences. What you did — not "we", not "the team". This is the longest section.
  • Result: One or two sentences. What changed, what was achieved, what you learnt.

The most common structural mistake is spending too long on Situation and not long enough on Action. Interviewers know that context is necessary; what they are weighing is your judgement and behaviour.

A worked example, written and spoken

Consider this competency question: "Give me an example of a time when you had to communicate complex information to a non-specialist audience."

Here is a STAR answer, marked so you can see the sections:

[Situation] "In my previous role at a logistics company, I was asked to present our new inventory system to the warehouse team — around forty people, most of whom had no background in software."

[Task] "My job was to get buy-in from the team and make sure they felt confident using the system before the go-live date."

[Action] "I decided to run three short sessions rather than one long one, so the information was easier to absorb. I replaced technical terms with analogies the team already used — for instance, I described the data sync process as 'the system doing a stocktake every night.' I also created a one-page reference card and asked two team members to test it before I printed it, so I knew the language was right."

[Result] "By the go-live date, the error rate in stock entries had dropped by roughly a third compared to the previous system, and the warehouse manager told me it was the smoothest software rollout they'd had."

Read that answer aloud. It runs to about 160 words and takes just over a minute at a comfortable pace. Notice where the natural stresses fall: three short sessions, analogies the team already used, error rate had dropped. Those are the words that carry meaning, and they deserve a small but deliberate emphasis.

Pace and pausing between sections

One of the most useful things you can do when answering competency questions is pause — briefly, deliberately — between each STAR section. Not a long silence, but the half-beat you might give between sentences when reading aloud.

That pause does two things. It tells the listener that one part of the answer is complete and another is beginning. And it gives you a moment to retrieve the next section cleanly, rather than rushing forward and losing your thread.

A typical fluent speaker covers 130 to 150 words a minute in formal conversation. If you are speaking English as an additional language, aiming for the lower end of that range in an interview is wise — not because slower sounds more foreign, but because a measured pace gives every word its due weight.

Word stress and the result

The result is the most important part of your answer. It is where the interviewer learns whether your action actually worked. Yet candidates frequently rush it, or deliver it in the same flat tone as everything before it.

Stress the verb or the number that carries the outcome. Compare these two deliveries of the same sentence:

  • "The error rate had dropped by roughly a third." (spoken flatly, no stress)
  • "The error rate had dropped by roughly a third." (stress on the key verb and the quantity)

The second version lands. The interviewer registers the outcome as significant because your voice treats it as significant.

This is true even when your result is qualitative rather than numerical. "The client renewed the contract" or "The team met the deadline without any overtime" — both carry weight when the stressed word is the verb of success: renewed, met.

Handling the words you are not sure about

If there is a word in your prepared answer that you are not confident pronouncing, replace it before the interview. This is not avoidance — it is good preparation. The clearest speakers choose words they can deliver without hesitation.

If you do stumble on a word mid-answer, do not stop and apologise. Continue, and the interviewer will almost certainly understand from context. What breaks an interviewer's concentration is not a mispronounced syllable but a speaker who loses confidence and trails off.

Preparing without over-scripting

Memorising answers word for word tends to produce stilted delivery — the voice flattens, the pace becomes unnatural, and the whole answer sounds recited rather than recalled. Instead, memorise the four STAR anchors for each story: the specific situation in a phrase, the task in a phrase, the two or three key actions, and the result in a figure or a sentence.

Then rehearse aloud — not in your head. Speaking the answer, hearing your own voice, noticing where you hesitate or rush: this is the work that makes the difference. If you have access to a tool that gives you spoken feedback on pace and fluency, use it. The ummute approach is built around exactly this kind of practice: real speaking, real feedback, in the conditions that matter.

Prepare four or five strong stories that between them cover the most commonly tested competencies — leadership, communication, problem-solving, working under pressure, and collaboration. Most competency questions can be answered with one of these stories, adapted slightly in emphasis depending on what is being asked.

The interviewer is not looking for perfection. They are looking for someone who thinks clearly, communicates honestly, and can be understood. Structure your answer so the evidence is easy to follow, speak it at a pace that respects the listener, and stress the words that carry your meaning. That is enough.

An English coach on WhatsApp, that talks like a friend.

Practise this on WhatsApp