A competency-based interview is prepared from the job ad, not from a list of questions
A competency-based interview is one where, instead of asking what you are like, they ask for concrete cases from your past: «tell me about a time when». Behind it sits a short list of competencies that job treats as critical, and every answer is scored against one of them. Which is why it is prepared backwards from how most people do it: first work out which competencies that ad probes, then decide which of your experiences answers each one.
What it is, and how it differs from a traditional interview
The name is scarier than the format. A traditional interview asks what you are like and this one asks what you did, because of one premise: what you did in a similar situation predicts your behaviour better than anything you say about yourself.
The question points at the past
«Tell me about a time», «give me an example of», «describe a situation where». Never in the conditional. If they ask what you would do, that is another family and it does not score here.
Everyone answers the same questions
They are written beforehand and asked identically to every candidate, so the answers can be compared. Which is why improvising pays so badly here.
There is a grid behind it
The person opposite is not scoring «I liked her»: they have four to six defined competencies and note the evidence for each. A beautiful answer about a competency that is not on that list scores nothing.
They will follow up
The moment you give a case they go for the detail: which part was yours, what happened next, how you know. Without detail there is no evidence to write down.
You can tell by the second question. And it changes the preparation: a traditional interview is prepared by deciding what to say, this one by deciding what to bring: four or five cases you lived and picked on purpose.
What a competency-based interview actually measures
Two words that are not synonyms. A skill is something you know how to do; a competency is something you have been seen doing, more than once and with other people around. Excel is a skill. Delivering something through people who did not report to you is a competency, and no certificate proves it, only a case does.
The HR manuals list forty, but job ads keep probing the same six, and each wants a different kind of evidence:
Execution and delivery
That what you start gets finished, on time, without anyone chasing you. It wants a case with a deadline and an ending: what shipped, when, and what you moved.
Problem solving
Not that you fixed something, but how you decided: what you checked before acting and what you ruled out. Without that, it is an anecdote.
Working with others
The most asked and the worst prepared. It arrives as conflict («a colleague you clashed with») or as borrowed authority («something you got done through someone else's team»).
Leadership
Careful, because it does not require having had anyone reporting to you. They want a decision that affected other people and how you carried it. Typical: «tell me about a difficult decision with your team», «how did you develop someone».
Adaptability and learning
What you did when the plan changed or you did not know enough. The good evidence here is uncomfortable: a mistake, a change of direction, something you learned late.
Results focus
The one people forget. It wants a case where you chose something measurable over something comfortable, and the number is not optional.
One well-chosen case covers three of those six depending on the angle: which is why you prepare by competency and not by question.
The demo has three fictional profiles with their interview questions pulled from the job ad. No signup, no email.
Open the demoHow to pull the competencies out of a job ad
This is the step almost nobody takes, and the one that separates preparing an interview from reading a list of questions. The competencies they will assess are written in the ad, just not with that word.
Read the responsibilities, not the requirements
The requirements list is skills and filters. Competencies live in the «what you will do»: a responsibility describes a behaviour, a requirement describes a credential.
Underline what repeats
What the ad says three times in different words is what hurts, and where half the interview goes.
Find the confessed problem
Most ads let slip a line about what is going wrong: «nobody owns the number». That line is worth more than the rest of the ad put together.
Turn each line into a behaviour
«Documenting the process» is not a task, it is «builds systems that work without you». Written as a verb, you already have the competency.
An example. An Operations Manager role in quick-commerce asks for someone to «open twelve kitchens in eighteen months, documenting and standardising the opening process so local teams can run it without depending on any single person», and to «push the operational metrics: waste is our biggest margin leak today and nobody owns the number».
Two sentences, three competencies with no doubt: running an opening end to end, building a system that does not depend on you and owning a number nobody owns. The fourth, leading teams, is on another line. And look: the waste sentence tells you which story it wants to hear.
How to match each competency to one of your experiences
With the competencies on paper, preparation stops being memory and becomes inventory: one column with what the ad assesses, another with what you have lived, and a line joining each pair.
Same ad, and a candidate with eleven years in operations:
Running an opening end to end
She opened six sites, from the lease signature to opening day, all on time. The case to tell is the fourth: the permits ran late and she moved the training forward.
A system that does not depend on you
After the third opening she wrote a forty-day checklist. The evidence is not the document: it is that the sixth opening was run by somebody else without her.
Owning a number
She designed a ten-minute daily count and gave every store manager her own figure. Waste went from 6.1% to 5.0% of sales in a year, 18% down.
Leading people
She closed a site: talked to all eleven people one by one before they could hear it in an email, and moved seven. It is the uncomfortable one of the four.
Three tie-breakers when several cases fit one box: the most recent wins, the one with a checkable ending, and the one from a different job. If all four come from the same role, the interview will only be about that role.
That crossing is where BeSuix starts: it reads the role, pulls out the three or four competencies it genuinely probes and points at the moment in your profile that answers each one. Then it asks you, because you tell the story, and it orders your account without adding anything you did not say.
That pairing is what BeSuix does, and you can see it end to end on a fictional profile. No account, no email.
See the demoHow to answer: the first person, and the follow-up
Almost everyone knows the shape: situation, task, action and result, the STAR method, which has its own guide. What decides this interview is two other things: who the subject of your sentences is, and what happens when they follow up.
The subject first. Answers are scored in the first person singular, and not out of style: nobody can record evidence about a plural. «We decided» does not score. «I decided, and here is why» does.
A full answer, for the system that does not depend on you:
«After my third opening I realised I was explaining the same thing for the third time. I sat down and wrote a forty-day checklist, with who calls which supplier, which week each permit goes in, and the three mistakes I had already made. The next three ran off that. And the proof is not that the document existed: it is that the sixth was opened by a colleague without me there».
It works for three reasons: the subject never moves off the first person, there is a detail only someone who was there could know (the three mistakes), and somebody else could confirm the result.
«Which part was yours exactly?»
Comes every time the story sounds like a team. Answer by narrowing without shrinking: what you decided, and what would have happened without you.
«What would you do differently?»
Not a trap: it is what separates a case you lived from one you were told. Answering «nothing» sinks it.
«How do you know it was that?»
They are going for the result. If the number is real, you just say where it comes from. If it was dressed up, this is where it falls apart.
In the demo every story arrives with the questions it answers, built from what the profile itself said.
Try the demoThe four mistakes that sink a competency-based interview
None is about how good the candidate is, and all four are fixed before you walk in.
Answering in the conditional
They ask for a case and you say what you would do. The most common and the most expensive, because it leaves the box empty: there is no behaviour to record. If you do not have it, offer the nearest one.
Bringing one case for everything
The flagship project told four times from different angles. It shows by the second time, and what gets noted is not your answer, it is that you only have one.
Getting stuck in the situation
Five minutes of context and thirty seconds of what you did. That is what an unprepared story sounds like: the action is half the answer.
Dressing up the result
Rounding a number up survives the first question and dies on the second. And then the problem is no longer the competency, it is trust.
Getting through a competency-based interview is not about having better stories than everyone else. It is about arriving with yours matched to what that ad assesses, in the first person, with an ending that survives a follow-up. That is the work of the evening before.
Frequently asked questions
How long does a competency-based interview last?
Between forty-five minutes and an hour, which fits four or five real questions: each case takes a couple of minutes and the follow-ups come after it. If you have been booked for thirty minutes, prepare three cases rather than five.
How many examples should I prepare?
Four or five you genuinely know, not fifteen. A well-told case answers three different questions depending on the angle you tell it from, and past five you will not remember which was which once you are forty minutes into talking.
What if I have no work experience?
The format is the same and the material comes from elsewhere: a final project, a module you coordinated, volunteering, a summer job. What gets scored is that the case is real and that you can say what you decided and why.
How do I know what they assess if the ad is four lines long?
Look at the role on their site and at the people already doing it, and if there is a call with a recruiter, ask outright what weighs most in the job. Nobody takes offence, and it saves you preparing the wrong half.
Can I use the same example for two questions?
Across different interviews yes, and that is normal. Inside the same one no: the second time adds no new evidence and whoever holds the grid records it once. Which is why the cases get split by competency before you go in.
How is it different from a technical interview?
A technical round looks at whether you can do the work and accepts hypotheticals: how would you approach this. The competency one looks at how you have behaved and only accepts the past. Both often sit in the same hiring process.
Keep reading
The STAR method, and how to use it without sounding like a template
The STAR method structures an answer into situation, task, action and result. What it is, worked examples by competency, and the mistakes that sink one.
How to prepare for an interview without memorising answers
Not by memorising fifty answers. Cover the four families of question with four or five cases of your own, and prepare the one aimed at your gap.