The STAR method: how to answer
competency questions

Picture a brilliant professional: twelve years in HR, team leader, candidate for a Head of People role. An impeccable career. She reaches the final interview again and again… and again and again she's passed over. Not for lack of talent, but because of the way she answers.

It's a real Próximo Rol case — we'll call her Valentina— and it will probably feel more familiar than you'd like. Because what happened to her happens to most highly capable professionals: they have the answers, but they don't tell them in a way the interviewer can actually "see". Below you'll see exactly what she was doing wrong and how we fixed it. But first, let's understand why it happens.

Almost every serious professional interview revolves around situational or competency-based questions: "tell me about a time you resolved a conflict", "give me an example of a project you led". From that sentence on, your CV stops answering: you do, live. And behind the anecdote the interviewer is after something deeper — they want to see how you structure your thinking, whether you can be concise, whether you actually answer what you were asked, and whether you understand what they need to hear before you launch into talking.

The good news: there's a structure that organises all of this and takes an afternoon to learn. It's called the STAR method, and it's the standard for behavioural interviews in any company, from a small business to a consultancy. It's exactly what Valentina was missing.

What a competency question is really assessing

When you interview for a role with responsibility, your technical competence is usually taken for granted: your CV already cleared the filter. What the interviewer still doesn't know — and needs to settle before hiring you — is who you are at work.

• Do you think in an orderly or chaotic way? Will you bring structure to the team, or more noise?
• Can you prioritise what matters? Or do you tell everything without distinguishing what weighs?
• Do you have judgement? Can I trust how you decide when I'm not watching?
• Will you make my life easier? That, in the end, is the question your future boss is asking.

The STAR method, in four steps

STAR is an acronym (Situation, Task, Action, Result) that gives you a mental script for telling any example in an orderly, high-impact way:

The most common mistake is getting stuck on the S and the A (the story) and forgetting the R (the result). If you don't have the exact number, estimate it and say so: "by my calculations, around 30%". That's valid and it sounds confident. Without a result, your story is just an anecdote; with one, it's evidence of your impact.

Back to Valentina: three mistakes you may be making too

Valentina was a candidate for a Head of HR role at a fast-growing company (we share her case with permission and with every detail changed). An extremely strong profile. And still, she kept falling at the final hurdle.

And here's the interesting part: Valentina comes from HR. She interviews other people for a living. You'd assume she'd arrive better prepared than anyone for her own interview. But she understood something many forget: coming from HR is precisely why her bar is higher. Her interviewers expect more of her, competition for those roles is fierce, and any slip counts double. Knowing the rules of the game doesn't excuse you from following them: it obliges you to execute them better than anyone. She knew that, which is why she chose to prepare properly instead of coasting.

When we ran the practice interview, the problem jumped out: it wasn't content, it was way. Read these three moments and ask yourself honestly: wouldn't I do the same?

We asked her something simple: "Have you led team restructuring processes?". A yes-or-no question, with nuance. Valentina answered with a five-minute story, detailed and well told… but one that made the interviewer wait until the end to learn the only thing he'd asked: whether she can or can't.

The difference is enormous. The second version answers the essentials first, shows she has an orderly mental framework, and hands control back to the interviewer so they can ask for the example if they want it. Concision + structure + reading what the other person needs.

We asked her: "What would your strategy be for the first 90 days?". Valentina started listing specific tasks she'd do. But that question is almost never after your to-do list: it's after seeing whether you have a method for approaching the unknown.

Same person, same knowledge. But the second version shows how she thinks — which is exactly what's assessed for a leadership role — and ends with a question that turns an interrogation into a conversation.

To the judgement question "What would you do if the leadership asked you for something that goes against the employees?", Valentina told a real and sensitive case from her current job, with details that were probably under confidentiality. The story demonstrated her judgement… but the way she told it revealed a problem of judgement about what can be shared.

It answers the essentials first (the judgement), backs it with the fact that the case is real, and protects what's confidential. In a role with responsibility, that adds judgement points instead of subtracting them.

The mistakes the STAR method helps you avoid

These four mistakes show up in almost every interview. The good news is that each has a concrete fix that's easy to practise.

1. Answering before understanding

It's the most common one, especially among quick, intelligent people: you hear the question, you already have an answer, and you start talking immediately. The problem is that, without processing it, you spiral into over-explaining and end up answering something other than what you were asked.

The fix isn't to answer faster, it's to take a second. Process the question before you open your mouth; that brief silence doesn't cost you, it earns you. And there are two lines that buy you time and project judgement at the same time:

2. Listing duties instead of achievements

The interviewer already knows what your job does; describing your responsibilities tells them nothing new. What they don't know is what you achieved tú. The fix: close every example with a concrete result and, wherever you can, a figure (even an estimated one). Move from "I handled recruitment" to "I cut time-to-hire from 45 to 28 days".

3. Confusing quantity with quality

Talking more isn't convincing more. A well-structured thirty-second answer beats five minutes of storytelling. The fix: answer the essentials first in one or two sentences and offer the example only if they ask. If you notice you've gone over a minute without reaching the point, that's the signal you've lost your way; go back to the question.

4. Forgetting what the other person needs to hear

It's not about saying what "sounds good", but about understanding which doubt the interviewer is trying to settle with that question. The fix: before answering, ask yourself what they're really assessing (judgement? structure? handling conflict?) and answer that doubt head-on, not the literal version of the question.

Your quick template for preparing the interview

Before any competency interview, prepare 5 or 6 stories in STAR format covering the most common questions. Don't memorise them word for word: learn the idea and say them in your own words, out loud, until they come out naturally.

1. A time when you spotted and fixed an inefficiency (with a saving or improvement figure).
2. A time when you built or launched something from scratch.
3. A time when you resolved a conflict with a colleague or another department.
4. A time when you led a team to a result.
5. A time when you made a hard decision under pressure or with little information.

For each one, write the S, T, A and R in a single line. When the question comes, you'll already have the skeleton; you just tell it. That preparation is, almost always, the difference between the candidate who makes the shortlist and the one who gets the job.

A full example, step by step

Let's see it with one of the most uncomfortable questions: "Tell me about a time you got something wrong at work." Here the interviewer isn't after the mistake itself but three things: that you take responsibility, that you know how to correct course and that you learn. Here's how the answer looks organised with STAR:

In short: the form is the message

Valentina didn't change her experience or her achievements: she had them from the start. What changed was how she told them. She stopped opening with five-minute stories, started answering the essentials first, and structured every example with STAR so her impact came through clearly. A month later she walked into her next final interview and turned it into an offer.

The STAR method isn't a trick for sounding good: it's the structure that lets the interviewer ver how you think. Situation and Task for context, Action to show what you did, and Result — always with a figure, even an estimate — to prove it had impact. Add the golden rule (pause, confirm, answer the essentials first) and you have what separates the candidate who tells stories from the one who looks like a leader.

Prepare your 5 or 6 stories, write the S-T-A-R of each in a single line, and practise them out loud until they sound like you. That preparation is, almost always, the difference between making the shortlist and getting the job.