Preparing for a competency-based interview

Walk into a corporate interview expecting a friendly chat about your CV and you will be caught off guard. Most employers now use structured, competency-based interviewing, which means they are testing how you work, not just what you have done. The good news is that this style of interview rewards preparation more than polish, and this guide shows you exactly how to get ready.

What a competency-based interview actually is

A competency-based interview is built around the skills and behaviours the role genuinely needs: things like stakeholder management, commercial judgement, resilience, teamwork and delivery under pressure. For each competency, the interviewer wants a real example from your past, because past behaviour is the best available predictor of how you will perform in the job.

Companies lean on this approach for a practical reason. Unstructured interviews favour confident talkers and produce inconsistent hires. Scoring every candidate against the same competencies, with evidence, is fairer and far more reliable. So interviewers are listening for specifics: what the situation was, what you actually did, and what happened as a result.

Do the research the panel expects

Start with the company's website, but do not stop there. Read their latest annual report or investor pages if they are listed, skim recent news coverage, and look at what their leadership posts publicly. Check employee reviews to understand the culture questions worth asking. If they publish a strategy or values page, read it, because interview questions are usually written against it.

Then study the job description and pull out the competencies. They are usually explicit: "strong stakeholder management", "commercial acumen", "delivers at pace". Write them down and, for each one, ask yourself: when have I actually done this? That single exercise is the core of your preparation.

Build a bank of stories

For each competency, prepare one real example from your working life. Structure each story in four short parts: the situation, the task in front of you, the action you personally took, and the result. This is the STAR method, and it stops you rambling or drifting into vague generalities.

Some pointers that make stories land well:

• Say "I" rather than "we" when describing the action, because the panel is hiring you, not your old team
• Pick examples from the last few years where you can, since recent stories carry more weight
• Include at least one story where something went wrong and you put it right, because questions about failure and learning appear in almost every structured interview
• Quantify the result wherever possible: revenue, cost, time saved, error rates
• Keep each story under two minutes when spoken aloud, and practise them out loud at least once

Six to eight solid stories will cover almost any question a panel can ask, because the same example can often serve more than one competency.

Questions you can expect

Every company phrases things differently, but these patterns come up again and again:

• Tell us about a time you had to influence a stakeholder who disagreed with you
• Describe a situation where you had to deliver against a tight deadline with limited resources
• Give an example of when you made a mistake. How did you handle it?
• Tell us about a time you used data to change a decision
• When have you challenged the way something was done?
• Why this company, and why now?

That last question deserves special preparation. You do not need a rehearsed speech about the brand. An honest answer that connects something true about you to something specific about them always beats flattery.

Handle the practical parts well

Structured interviews still include ordinary interview elements, so prepare for those too. Reread the job description the night before and be ready to talk through anything on your CV, including gaps and short stints. Plan your route or test your video call setup ahead of time. Dress one notch smarter than the company's everyday standard.

Bring questions of your own. Good ones include how the team measures success, what the biggest challenge in the role will be in the first six months, and what separates the people who do this job well from the people who do it brilliantly. Asking about development and progression signals ambition, not impatience.

On the day: specifics beat performance

Panels can spot a rehearsed persona quickly, and they see dozens of them. What stands out is a candidate who listens to the question, pauses to think, and answers with something true and specific. If you do not have an example for a question, say so and offer the closest thing you do have. If you need a moment, take it. Interviewers consistently rate candidates higher for thoughtful honesty than for fast, glossy answers.

Remember that the interview runs both ways. The panel's behaviour tells you about the culture you would be joining. A panel that makes space for your questions and treats you with respect is showing you how the company works, which is exactly what you are doing for them.

After the interview

Send a short thank-you email the same day if you have a contact address. Reaffirm your interest in one or two lines and leave it there. If you are not successful, ask for feedback, because structured processes usually produce useful notes, and they will sharpen your next application. Every competency interview you sit makes the next one easier, since your story bank only grows.