Competency-Based Interviews: How to Prepare Using the STAR Method

You applied for a job. You got an interview. Now the employer wants to meet you, and they've told you it'll be a "competency-based interview".

If you've never had one before, the phrase alone is enough to make you nervous. But competency-based interviews are the most common interview format in the UK, especially for graduate schemes, public sector roles, and mid-career positions. Once you understand how they work and how to prepare for them, they're actually one of the fairest types of interview you can face.

This guide covers what a competency-based interview is, why employers use them, and how to prepare using the STAR method. We'll walk through real examples, common questions UK employers ask, and the mistakes that trip people up most often.

What is a competency-based interview?

A competency-based interview (sometimes called a behavioural interview or situational interview) is an interview format where every question asks you to describe a real situation from your past experience. Instead of asking "What are your strengths?", the interviewer asks "Tell me about a time you used [specific skill]."

The logic is simple: past behaviour is the best predictor of future behaviour. If you've successfully handled a difficult customer before, you can probably do it again. If you've never met a tight deadline under pressure, saying you're "good under pressure" doesn't prove much.

The key thing to understand is that competency-based interviews test what you can do, not what you know. A traditional interview might ask you to define a term or explain a process. A competency-based interview asks you to prove you've actually done the thing.

This is why they're popular with employers. Anyone can say they're a team player. Far fewer people can describe a specific situation where they helped a team work through a problem and explain what they personally contributed. The format forces candidates to back up their claims with evidence.

Why employers use them

Employers use competency-based interviews for three main reasons:

They're structured. Every candidate gets asked roughly the same questions, which makes it easier to compare them fairly. This matters a lot in the public sector and in organisations with strict HR policies around fair hiring.

They're evidence-based. The interviewer isn't relying on gut feeling or whether you "seemed like a good fit". They're listening for specific examples that demonstrate specific skills.

They reduce bias. Because the questions are standardised and the answers are about real situations, it's harder for an interviewer to hire someone just because they liked them. The focus stays on what you've actually done.

The competencies tested depend on the role. A project manager might be tested on stakeholder management, prioritisation, and leadership. A customer service advisor might be tested on communication, problem-solving, and resilience. The job description usually tells you which competencies matter. Read it carefully before the interview.

The STAR method explained

The STAR method is a structured way to answer competency-based questions. It gives your answer a clear shape so you cover everything the interviewer needs to hear. STAR stands for:

Situation

Set the scene. Where were you, what was the context, what was happening? Keep this brief. The interviewer needs enough context to understand your example, but they don't need a three-minute backstory.

Task

What was your specific responsibility in that situation? What were you trying to achieve? This is often the shortest part of your answer. Sometimes the situation and task blend together, which is fine.

Action

What did you do? This is the most important part of your answer. The interviewer wants to hear about your specific actions, your decisions, your reasoning. Not what the team did. Not what your manager decided. What did you do, step by step?

This is where most people go wrong. They spend too long on the situation and not enough time on the action. We'll come back to this.

Result

What happened because of your actions? What was the outcome? Use numbers if you can. If you improved a process, how much time did it save? If you resolved a conflict, did the working relationship recover? Did the project deliver on time?

If there's a learning point, mention it. "We delivered the project on time, but I learned that I should raise concerns earlier rather than hoping the timeline would sort itself out." Honest reflection scores well.

A real example

Here's what a complete STAR answer looks like in practice.

Question: Tell me about a time you dealt with a difficult colleague.

Situation: "In my previous role as a marketing coordinator, I was working on a campaign launch with a colleague in the design team. He kept missing the deadlines we'd agreed for design assets, which meant the rest of the team couldn't do their work on schedule."

Task: "I needed to get the assets delivered on time without damaging the working relationship, because we had three more campaigns together that quarter."

Action: "I booked a short one-to-one with him rather than raising it in the team meeting, because I didn't want to put him on the spot. I asked him what was getting in the way of the deadlines rather than telling him he was late. It turned out he was juggling three projects and our work wasn't visible in his prioritisation system. I suggested we add our deadlines to the shared project board so he could see them alongside his other work, and I agreed to flag any urgent assets at least a week in advance. I also spoke to his manager to make sure our campaigns were being factored into his workload planning."

Result: "He hit the next two deadlines on time. The campaign launched on schedule. We kept working together through the rest of the quarter and the relationship was fine. The lesson I took from it was to have those conversations earlier instead of waiting until deadlines have already been missed."

That answer takes about 90 seconds to say out loud. Notice the proportions. The situation and task together take about 20 seconds. The action takes about 50 seconds. The result takes about 20 seconds. The action is the longest part, because that's what the interviewer actually wants to hear.

Common competency questions UK employers ask

Competency questions usually start with "Tell me about a time...", "Describe a situation where...", or "Give an example of...". Here are some of the most common ones, along with the competency each one is testing.

"Tell me about a time you dealt with a difficult colleague"

Competency: Conflict resolution, interpersonal skills, communication

This is one of the most frequently asked competency questions in the UK. The interviewer wants to see that you can handle conflict professionally, without becoming defensive or aggressive. They want to know you can have a difficult conversation, find the root cause of a problem, and reach a resolution.

Avoid answers where the conflict was resolved by someone else stepping in, or where you avoided the person entirely. The interviewer wants to see what you did.

"Describe a situation where you had to meet a tight deadline"

Competency: Time management, prioritisation, working under pressure

The interviewer wants evidence that you can plan your work, focus on what matters, and deliver when the pressure is on. Good answers mention how you prioritised, what you deprioritised, and how you managed the constraints. Saying "I just worked really hard and got it done" isn't enough. Explain your approach.

"Give an example of when you showed leadership"

Competency: Leadership, initiative, taking responsibility

You don't need a management title to answer this. Leadership in a competency interview can mean stepping up when no one else did, taking responsibility for a problem that wasn't strictly yours, or guiding a team through uncertainty. The interviewer wants to see that you took initiative and others followed.

Other common questions

• "Tell me about a time you made a mistake and how you handled it" (accountability, learning from failure)
• "Describe a time you had to persuade someone to see things your way" (influencing, negotiation)
• "Give an example of when you worked in a team to achieve a goal" (teamwork, collaboration)
• "Tell me about a time you adapted to a significant change at work" (adaptability, resilience)
• "Describe a situation where you solved a complex problem" (problem-solving, analytical thinking)

For each of these, prepare a STAR answer from your own experience. Don't try to wing it in the interview.

How to prepare

The biggest favour you can do yourself before a competency-based interview is to prepare properly. Here's how.

Dig through your experience for 5-6 stories

You don't need a different story for every possible question. You need a small set of flexible stories that can adapt to different questions. Five or six well-chosen examples will cover the vast majority of competency questions.

Think about your experiences across these areas:

• A time you dealt with a difficult person or conflict
• A time you worked under pressure or met a tight deadline
• A time you led something or took initiative
• A time you worked in a team to achieve a goal
• A time you solved a problem or improved something
• A time you made a mistake and learned from it

These six examples cover most of the common competency areas. A single story can often answer more than one question. The story about dealing with a difficult colleague could also answer a question about communication or problem-solving. The story about meeting a tight deadline could also answer a question about prioritisation or working under pressure.

Don't restrict yourself to work examples. If you're early in your career, examples from volunteering, university projects, sports teams, or community involvement all count. The competency is what matters, not the setting.

Write them down in STAR format

For each story, write out the situation, task, action, and result. Be specific. Include names (first names are fine), numbers, and outcomes. Writing them down forces you to think through the detail and makes the stories easier to remember.

Keep what you write to bullet points rather than full scripts. You don't want to sound like you're reading from a document in the interview. Bullet points keep you structured without making you robotic.

Practice saying them out loud

This is the step most people skip. Your written answers will be different from your spoken answers. You need to hear yourself say them to know if they're the right length, if they flow, and if the action section is detailed enough.

Say each answer out loud. Time it. If you're spending more than two minutes on a single answer, it's too long. If the situation takes longer than 20 seconds, trim it. If the action takes less than 30 seconds, you need more detail.

Ask a friend or family member to listen and ask follow-up questions. If they can't follow your story or if they're not clear what you actually did, the interviewer probably won't be either.

The biggest mistake people make

If there's one mistake that ruins more competency interview answers than any other, it's this: spending three minutes on the situation and 30 seconds on the action.

Here's how it goes. The interviewer asks about a time you dealt with a difficult colleague. You start explaining the background. The colleague was this person, the team was structured like this, the project was about this, the history of the conflict went back to this, the client was involved, the deadline was coming up, the manager was away. You're two and a half minutes in and you haven't said what you did yet.

Then you rush the actual action. "So I had a chat with him and it got sorted." That's 10 seconds. The interviewer has heard nothing about your skills, your approach, or your reasoning. All they know is that something happened and it resolved itself.

The situation is just context. The interviewer needs enough of it to understand your example, but the action is what they're actually assessing. Your action section should be the longest part of your answer. It should include what you did, why you chose that approach, and how you navigated any obstacles.

A rough guide for timing your answers:

• Situation: 15 to 20 seconds
• Task: 10 to 15 seconds
• Action: 45 to 60 seconds
• Result: 15 to 20 seconds

Total: roughly 90 seconds to two minutes per answer. If you're going over two minutes, you're almost certainly spending too long on context.

What if you don't have a relevant example?

This happens, especially early in your career or when you're moving into a new field. The interviewer asks about a time you led a team and you've never managed anyone. What do you do?

Don't make something up. Interviewers can usually tell, and if they ask follow-up questions, the story falls apart. Being caught inventing an example will end your chances immediately.

Use examples from outside work. A time you organised a community event, captained a sports team, coordinated a university group project, or took charge of a volunteering activity. The competency is what matters, not the setting. An interviewer asking about leadership is testing whether you can take responsibility, guide others, and make decisions. You can demonstrate that in any context.

Be honest about the gap. If you genuinely don't have an example, say so, then talk about what you would do in that situation or describe a related experience. "I haven't had the opportunity to lead a team formally, but in my last role I took responsibility for training two new starters, which involved [specific actions]." This shows self-awareness and gives the interviewer something to assess.

Use a related but different example. If they ask about managing a difficult colleague and you've never had that exact situation, talk about a time you dealt with a difficult customer, or a time you navigated a disagreement in a team project. The skills are transferable.

The worst approach is to panic and invent. The second worst is to say "I can't think of one" and stop. The best is to acknowledge the gap and offer the closest real example you have.

How Forte helps you prepare

One of the hardest parts of preparing for a competency-based interview is figuring out what your examples actually are. Most people undervalue their own experience. You do things every day at work that demonstrate competencies, but because they feel routine, you don't think of them as examples.

Forte's AI competency extraction helps with this. When you upload your CV, Forte analyses your experience and surfaces the competencies you've actually demonstrated. Not keywords. Not job titles. The underlying skills: things like stakeholder management, analytical problem-solving, client communication, process improvement.

This does two things for your interview prep. First, it gives you a clear picture of what you can genuinely claim as a competency, so you're not guessing what to talk about. Second, it helps you spot the experiences that map to STAR examples. If Forte identifies that you've demonstrated "cross-functional collaboration" three times in your career, you've just found three potential STAR stories.

From there, the prep is the same: write them in STAR format, practice saying them out loud, make sure the action section is the longest part. Forte just makes the first step, finding your examples, faster and more accurate.

You can try it at myforte.online. Upload your CV, see what competencies come back, and you'll have the raw material for your interview prep in minutes rather than hours.

Final thoughts

Competency-based interviews reward preparation. The candidates who do well aren't necessarily the most confident or the most experienced. They're the ones who turned up with five or six clear examples, structured them properly, and made sure the action section was longer than the situation.

The STAR method isn't complicated. It's just a way of making sure you tell the full story, with the emphasis in the right place. Prepare your examples, practice them out loud, and keep the action section detailed and specific. Do that and you'll be in a better position than most of the people the interviewer sees that day.

Ready to figure out what your competencies actually are? Try Forte and start building your interview prep on what you can genuinely do.