“Tell me about a time when you…” is the sentence that defines a competency-based interview. The interviewer is not being nostalgic. They are asking for a real episode because an episode is something concrete to examine, where “I’m a good team player” is only a claim. This article explains what is going on on the other side of the table, how a good answer is built, and where a self-rating such as the Competency Test can, and cannot, help you prepare.
What the interviewer is doing when they ask for a story
A competency-based interview, sometimes called a behavioral interview, is built around the competencies a role needs. In a well-run process the employer has decided in advance which ones matter for the job, for example planning, teamwork or problem solving, and prepared a question for each. Each question asks for a real example: “Tell me about a time you had to change your plan at short notice.”
The interviewer then listens for specifics. What was the situation? What did you personally do? What happened? Often they take notes against a short guide describing what a weaker and a stronger answer sound like. Follow-up questions such as “What did you say to them?” or “What would you do differently?” exist to separate a lived episode from a rehearsed one.
Compare that with a hypothetical question like “What would you do if a deadline slipped?” which invites a tidy, ideal answer. A past episode is harder to polish, because real episodes have loose ends.
Situation, action, result: the shape of a good answer
Most advice reduces the structure to three beats, sometimes four when the task is split out (often called STAR). The labels matter less than the proportions.
- Situation: one or two sentences of context. Who, what, and why it mattered. No more.
- Action: the longest part. What you did, step by step, and why. “We” is fine for context, but the interviewer is assessing you.
- Result: what happened, honestly, including anything that did not go to plan, and what you took from it.
Here is a compact example for a planning question. Situation: a client report was due Friday, but the data arrived on Wednesday afternoon. Action: I told the client that day, offered a shorter version for Friday and the full version on Monday, and moved two other tasks to make room. Result: they accepted the shorter version, the full report went out on Monday, and I now ask for inputs earlier on any project that depends on someone else’s data.
Notice what is absent: no claim to “always” plan well, and no adjectives. The listener can judge planning, communication and adaptability from the actions alone.
How it differs from a personality test or an ability test
The three tools ask different things of you.
- An ability test asks what you can do right now on a set task. The answer is scored as right or wrong.
- A personality questionnaire asks about broad tendencies through ratings, and the result describes you in general rather than in one moment.
- A competency-based interview asks for your own account of a specific past episode and judges it, through a person, against stated criteria.
That last point is also the weak spot. A person is doing the judging, so the outcome depends partly on how well you tell the story, how the interviewer reads you and how well you remember the details. Research on selection methods in personnel psychology (Schmidt & Hunter, 1998) supports a useful qualitative idea: structured methods, where each candidate gets the same job-related questions and answers are assessed against a set guide, tend to be more informative than loose, unstructured conversation. Structure reduces the role of impression and chance; it does not remove it. A fluent storyteller can still outshine someone who did excellent work quietly.
Where a competency self-rating helps you prepare
The Competency Test on JobCannon gives you something practical: six headings (communication, problem solving, leadership, planning, adaptability, teamwork), each with a level word and your own sense of where you are strong and where you are still building. Used well, that is a filing system for your examples, not a forecast.
- For a competency that came back Strong, find two real episodes you can tell in the shape above. If you cannot, look again at how you rated yourself.
- For one that came back Developing or Early stage, find at least one honest, small example, or prepare to say what you have been doing to build the habit.
- Read the job description. The employer chooses the competencies, and the test cannot know which ones they will ask about.
It is worth saying clearly that the test does not predict how an interview will go. It is a self-rating, not a validated instrument, and it does not measure real skill. A high level on teamwork is not a promise that your teamwork answer will be good; the answer still has to be a specific, true story. For how to describe your result out loud, see how to talk about your self-assessment in an interview, and for the strengths-and-weaknesses question in particular, strengths and weaknesses answers from your competency profile.
Building an example bank before the interview
- List six to eight episodes from the last few years. Work is best, but study, volunteering and projects at home count when they are real.
- For each, note the competencies it shows. One episode often covers two or three (the six core work competencies shows how they overlap).
- Write the situation, action and result in three or four sentences each, then cut anything the listener does not need.
- Say them aloud. Answers that read well on paper often speak badly.
- Add one line to each: what you would do differently. It is a common follow-up, and having an answer ready helps.
Watch for the usual mistakes. Answering with a general habit instead of an episode (“I always plan ahead”). Describing the team’s work without saying what you did. Choosing an example where the good result was luck. Reciting a script so smoothly that the first follow-up question throws you. A self-rating can point you to the right headings, but the examples have to come from your own working life.