Competency-based interviews: what they are and how to answer every question
· by the InterviewCrusher team
A competency-based interview (you’ll also hear “behavioral interview”) rests on a simple premise: the best way to predict how you’ll work tomorrow is to look at how you worked yesterday. That’s why almost every question starts the same way: “tell me about a time when…”, “describe a situation where…”, “give me an example of…”. The interviewer doesn’t ask what you would do in a conflict; they ask for the specific conflict you already lived through, with decisions and an outcome. It’s the favorite format of large companies, consultancies, and serious hiring processes because, done well, it works: it’s far harder to invent past behavior than an opinion.
The difference from a traditional interview lies in the script and the scoring. In a traditional one, the conversation flows around your resume and answers are judged on general impression. In a competency-based one, the interviewer carries a fixed list of competencies the role demands (leadership, adaptability, customer focus…), asks similar questions of every candidate, and scores each answer against a rubric of observable behaviors. That’s why they probe so much: “what exactly did you do?”, “what did you say to them?”, “how did it end?”. It’s not distrust, it’s the method: without verifiable detail, the answer doesn’t score.
The good news is that this is the most preparable format of all. The competencies can be deduced from the posting, the questions follow known patterns, and one well-chosen story can cover several. What you can’t do is improvise: digging for a memory live, with the interviewer waiting, is a recipe for awkward silence. Prepare your stories with this guide and then tell them out loud against an AI that fires follow-ups, because a story is only ready when it survives the interrogation, not when it looks pretty on paper.
What mistakes should you avoid when answering “What is a competency-based interview?”?
- Answering in the conditional (“what I would do is…”) when they asked for a past event. The question asks for a real case; if you offer a hypothesis, the evaluator notes you had no example, and that box stays empty.
- Dissolving into “we”. The competency being evaluated is yours: if by the end of your story it isn’t clear what you decided and did, there’s no behavior to score, however well the project turned out.
- Recycling the same anecdote for three different competencies. The interviewer notices by the second time, and the read is bad: it looks like only one interesting thing has ever happened in your entire career.
- Telling a story with no ending: no measurable result, no lesson. An anecdote that finishes with “and well, in the end it got sorted out” leaves the evaluator with nothing to write in the rubric.
How to prepare for a competency-based interview
- 1
Map the competencies in the posting
Reread the job description with a highlighter: the competencies they’re going to evaluate are almost always written down. “Ability to work in a team”, “results orientation”, “change management”… Note the four to six that repeat most, especially the ones in the requirements rather than the decorative parts. That list is your syllabus: every question in the interview will come from it.
- 2
Build an inventory of 4-5 strong stories
Don’t prepare one story per competency: prepare a few good stories that cover several. Pick situations from the last two or three years with a real challenge, decisions of your own, and a result you can measure. A rocky migration can demonstrate adaptability, problem-solving, and teamwork depending on how you tell it. Make a table with your stories as rows and the posting’s competencies as columns, and check that no column is left empty.
- 3
Structure each answer: short, with a payoff
To tell them, use the STAR method: set the context in two sentences, explain what you did, and close with a measurable result and, if there is one, a lesson. You don’t need more engineering than that: ninety seconds, first person, a number at the end. You’ll find the full guide to the STAR method, with all four steps developed and examples, in this same section of the site.
- 4
Prepare for the follow-up
In a competency-based interview, the first answer only opens the door: the follow-ups decide the score. “What exactly did you say to them?”, “why didn’t you do the opposite?”, “what if it hadn’t worked?”. A lived story handles them effortlessly; an embellished one collapses by the third. That’s why rehearsal isn’t rereading your notes: it’s having someone (or an AI) interrogate you out loud until the details come by themselves.
The structure that holds up any competency-based answer is the STAR method: Situation, Task, Action, and Result. Complete guide to the STAR method.
Sample answers
“At my previous company, a distributor, my manager went on two months’ leave right before the Christmas season, and I was asked to run the warehouse: six people, two of them brand new. We were running 20 percent below the order-prep pace the season demanded. The first thing I did was spend ten minutes talking with each person to understand where the flow was jamming, instead of imposing a plan on day one. I saw the two new hires were losing half their time hunting for product references, so I reorganized the picking zones by product turnover and paired each new person with a veteran for the first week. I put a visible daily target on a whiteboard and we reviewed it for five minutes every morning. We closed the season with 98 percent of orders shipped on time, up from 91 the year before, and no overtime in the final week. When my manager came back, she kept the zone layout. I learned that leading wasn’t knowing more about the warehouse than anyone else: it was clearing the jams so everyone could perform.”
“I had spent two years managing my company’s orders on an ERP I knew by heart when leadership announced a migration to a new system with six weeks’ notice, right in the middle of high season. Half the team took it badly; so did I, that first afternoon. I decided complaining wasn’t going to bring the old system back, so I asked for access to the test environment in week one, while it was still optional. I spent two hours every afternoon replicating my twenty most frequent operations and noting down the steps that changed. With that I built a “before/after” cheat sheet I shared with the team, and the project lead asked me to run two internal sessions. On switchover day, my area was the only one that didn’t fall behind: we got that week’s 130 orders out on time, while other departments took nearly a month to recover their pace. I didn’t like the change, and I said so, but I understood my job was to make sure the customers didn’t pay for it. Ever since, I’m the first to sign up for pilots: I’d rather find out early what’s coming.”
Sample questions by competency
The questions vary from company to company, but the patterns repeat. Here are ten, grouped under the five most commonly evaluated competencies, so you can check whether your story inventory covers them all.
- Leadership: tell me about a time you had to pull a demotivated or underperforming team forward.
- Leadership: tell me about an unpopular decision you made and how you communicated it to the team.
- Teamwork: tell me about a time you helped a colleague who was falling behind even though it wasn’t your responsibility.
- Teamwork: tell me about a project where your part depended on other people’s work. How did you coordinate it?
- Adaptability: tell me about a time your priorities changed overnight. What did you do?
- Adaptability: tell me about a time you had to learn a new tool or process in very little time.
- Conflict resolution: tell me about a disagreement with a colleague over how to do the work. How was it resolved?
- Conflict resolution: tell me about a time a boss or a client called you out on something you felt was unfair. What did you do?
- Customer focus: tell me about a time you went beyond what a client was asking for. What did you gain by it?
- Customer focus: tell me about a deeply unhappy customer you had to manage. How did it end?
Quick tips
- Give each story in your inventory a three-word title (“the warehouse Christmas”, “the ERP migration”). In the interview you won’t remember paragraphs: you’ll remember titles, and the rest will come by itself if you’ve rehearsed.
- Give the number even if they don’t ask for it. “From 91 to 98 percent of orders on time” turns an anecdote into evidence; without the number, the same story stays an opinion.
- If you’re short on work experience, draw on internships, volunteering, or academic projects. The rubric scores behaviors, not payslips: a real, recent example from college scores higher than an invented one from a job.
- Rehearse against follow-ups, not against the mirror. Ask someone (or the simulator’s AI) to interrupt you with “and what exactly did you say?”: if the story survives three follow-ups in a row without stumbling, it’s ready.
Knowing the answer isn't the same as saying it out loud
Practice this question with an AI recruiter that asks follow-ups, keeps the pressure on, and gives you honest feedback. In your language and no credit card.