How to Prepare for a Competency-Based Interview

A competency-based interview is not a test of whether you can think on your feet. It is a test of whether you have done something specific in the past that demonstrates a required behaviour. If you have done it, and you can describe it clearly, you will do well. Preparation is almost entirely what separates strong answers from weak ones.

Unlike conversational interviews where the structure shifts depending on the interviewer's instincts, competency-based interviews follow a predictable format. The questions start with "tell me about a time when..." or "give me an example of...". The interviewer is working from a scoring rubric. They are looking for specific evidence of specific behaviours. Once you understand that, the preparation process becomes straightforward.

What Competency-Based Interviews Are

Competency-based interviewing, also called structured behavioural interviewing, is built on a simple premise: the best predictor of future behaviour is past behaviour. Rather than asking candidates what they would do in a hypothetical situation, this format asks what they actually did in a real one.

Companies use this format because it is more reliable than unstructured interviews. When every candidate is asked the same questions and scored against the same criteria, the process is fairer and the outcomes tend to be better. It reduces the influence of first impressions and makes it harder for a confident communicator to paper over thin experience.

For candidates, it is genuinely more learnable than a free-form interview. The questions are predictable. The structure of a good answer is consistent. The preparation is specific. If you put the work in before the interview, you will be in a strong position.

The STAR Method Explained

STAR is a framework for structuring your answers. It stands for Situation, Task, Action, Result.

Situation: Briefly describe the context. Where were you, what was happening, what was the challenge or opportunity? Keep this short — one or two sentences. The interviewer needs enough context to follow your answer, not the full backstory.

Task: Explain what your specific role or responsibility was. What were you trying to achieve? This is where you start distinguishing your contribution from the team's contribution.

Action: This is the most important part. Describe in specific detail what you personally did. Use "I" not "we." Explain your reasoning. Show how you approached the problem, what decisions you made, and why. This is what the interviewer is primarily scoring.

Result: What happened? Be specific about the outcome. Numbers and measurable results are ideal, but a clear qualitative outcome is also valuable. What did you learn? Would you do anything differently?

Most candidates spend too long on Situation and not long enough on Action and Result. Flip the proportion: roughly 60 to 70 percent of your answer should be in Action and Result.

An interviewer does not need the full context of the project. They need to understand what you specifically did, and what it produced.

Building Your Example Bank

Before the interview, build a bank of eight to ten strong examples from your career. These should be drawn primarily from the last three to five years, from roles relevant to the level you are applying for. Each example should be specific, clear, and something you can narrate confidently.

The goal is to have enough variety that you can adapt the same example to different competency questions by emphasising different elements. A situation involving a difficult internal stakeholder might be your best example for questions on communication, conflict resolution, influencing without authority, and resilience, depending on which aspect you lead with.

For each example, write down: the situation in one sentence, your specific role, the three or four actions you took, the result, and one sentence on what you learned or would do differently. Practice saying it out loud until it is fluent and under three minutes.

The Most Common Competencies

Most competency frameworks assess some combination of the following. Prepare at least one strong example for each:

• Leadership: Taking ownership, driving a team towards an outcome, making decisions under pressure
• Teamwork and collaboration: Working with others to achieve a shared goal, including across functions
• Problem-solving: Identifying a root cause, developing options, executing a solution
• Resilience: Handling setbacks, recovering from failure, maintaining performance under pressure
• Commercial awareness: Understanding business implications, thinking about cost, risk, or customer impact
• Communication: Explaining something complex, managing a difficult message, adapting to different audiences
• Conflict resolution: Navigating disagreement or tension, reaching a workable outcome

Look at the job description carefully before your interview. Most companies list their competency framework or values explicitly, and the interview questions will map directly to them.

What Interviewers Are Actually Scoring

An interviewer in a structured competency interview is usually working from a scoring guide with four or five levels. Strong answers tend to be scored on four things: specificity, ownership, results, and reflection.

Specificity: Is this a real, specific example with real details? Or is it vague and generic? "I once had to deal with a difficult colleague" scores lower than "In Q3 of last year, I had a situation where a peer in the finance team was blocking sign-off on a project because of a misalignment around budget ownership..."

Ownership: Did this person personally do something, or did they describe what the team did? "I" scores better than "we." Interviewers are trying to understand your individual contribution, not the group effort.

Results: What actually happened? Was it a good outcome? How do you know? Vague answers — "it went well," "the team was happy" — score lower than specific ones. Quantify where you can.

Reflection: Does the candidate understand what happened and why? Can they identify what they would do differently? This shows maturity and self-awareness, which interviewers at a senior level care about significantly.

The Most Common Mistakes

These are the answers that consistently score lower:

• Too vague: Describing a type of situation rather than a specific one. "I often have to manage competing priorities" is not an example.
• Overusing "we": The interviewer cannot score the team. They are scoring you. Make your personal contribution explicit.
• Choosing examples where nothing went wrong: Interviewers tend to trust answers that include a genuine challenge, a mistake, or a difficult moment. Perfect stories that resolved neatly are less convincing.
• Answering the question you wish you had been asked: If the question is about a time you handled conflict, answer that question. Do not redirect to a different example because your conflict story is weaker.
• Going too long on context: If you are three minutes in and still explaining the background, you have lost the interviewer.

How to Handle a Question When You Have No Strong Example

This happens, even with good preparation. If you are asked a question and no strong example comes to mind, do not panic and do not make something up.

It is completely fine to say: "Let me take a moment to think about the best example for that." A brief pause to think is not a weakness. It is a sign that you are taking the question seriously.

If you genuinely do not have a direct example, be honest and offer the closest relevant one: "I haven't faced that exact situation in a direct management role, but a similar challenge I encountered was..." This is far better than a vague or invented answer, which experienced interviewers will identify immediately.

You can also draw on examples from outside your core work history — a significant project, a role in a professional association, or a situation from earlier in your career — as long as you are transparent about the context and the example is genuinely relevant to the competency being tested.

Frequently Asked Questions

What is the STAR method?

STAR stands for Situation, Task, Action, Result. It is a framework for structuring answers to competency-based interview questions. You describe the context (Situation), explain what you specifically needed to do (Task), detail the steps you took (Action), and share what happened as a result (Result). The most important parts are Action and Result — these are where interviewers are scoring you. Many candidates spend too long on Situation and not long enough on what they actually did and what it achieved.

How many examples should you prepare for a competency interview?

Aim for eight to ten strong examples drawn from across your career, ideally from the last three to five years. Each example should be specific enough to work for multiple competency questions by emphasising different aspects. For instance, one example involving a difficult client situation might serve questions on communication, resilience, problem-solving, and stakeholder management depending on which elements you emphasise.

What happens if you cannot think of a good example during the interview?

Ask for a moment to think — this is completely acceptable and interviewers expect it. If no strong example comes to mind, be honest: "I haven't faced this exact situation in the same form, but a similar challenge was..." You can also draw on examples from outside direct work experience, such as a significant project, a volunteer role, or a situation from earlier in your career, as long as you are transparent about the context.

---