How to prepare for a competency-based interview

Understand what the question is testing

Questions such as “Tell me about a time you influenced a difficult stakeholder” are asking for observable evidence. The interviewer is listening for the context, the choices you made, how you acted and what happened. The surface topic is the story; the competency is the reason the story is being requested.

Read the job description and group repeated language into likely competencies: judgement, collaboration, delivery, leadership, customer focus, analysis or resilience. Do not prepare equally for every competency in the world. Prepare for the ones this role is likely to score.

Build an evidence bank before writing answers

List projects, difficult decisions, failures, improvements, conflicts and moments of responsibility from your real experience. Then map each example to the competencies it could demonstrate. One strong example may support several questions, but it should not be forced into every answer.

Include examples from work, study, volunteering or substantial personal projects when they provide the clearest evidence available. The standard should match your career stage. An early-career candidate is not expected to have executive scope; they are expected to explain their own contribution honestly.

• What was at stake?
• What was specifically yours to decide or deliver?
• What action did you take, and why?
• What changed, and what did you learn?

The STAR answer framework

STAR stands for Situation, Task, Action, Result. It is useful because it stops an answer becoming a long scene-setting exercise. Keep the situation and task brief, usually one or two sentences each. Spend most of the answer on your action and the result.

In practice: Situation sets the context in one line. Task states what you specifically needed to achieve. Action is the longest part: what you actually did, and why you chose that approach. Result closes the answer with what changed, ideally something concrete and honestly stated.

Reflection can strengthen the answer when it is real: what you would repeat, what you would change or what the experience taught you. Preparation should make the route through the story familiar while leaving the language natural.

• Situation: one or two sentences of context, no more.
• Task: the specific outcome you were responsible for.
• Action: what you did and the reasoning behind it, in your own words.
• Result: what changed, and what you took from it.

Structure is there to make your evidence easier to follow, not to make every answer sound identical.

Three example competency questions and answers

These are shortened example answers, not scripts to copy. Use them to see how STAR compresses a real situation into a clear, checkable answer.

1. Question: “Tell me about a time you had to influence someone who disagreed with you.” Answer: “A department head wanted to cut a project timeline I felt was unsafe. I gathered the delivery risks in writing, proposed two alternative timelines with trade-offs, and walked through them in a short meeting. We agreed on the middle option. The project shipped on the revised date with no quality issues, and that head asked me to review two later projects before sign-off.”
2. Question: “Describe a time you had to manage conflicting priorities.” Answer: “I was running two client deliverables due the same week with one analyst supporting both. I ranked the work by contractual risk, moved one non-critical task to the following week with the client's agreement, and reassigned two tasks based on who had capacity. Both deliverables landed on time and the client was not aware there had been a conflict.”
3. Question: “Tell me about a time something went wrong that was your responsibility.” Answer: “I approved a report that went to a client with an outdated figure in it. I flagged the error to my manager within the hour, sent a correction directly to the client with an apology, and added a second reviewer step to our sign-off process. The client accepted the correction without issue, and the same error has not happened since.”

A weak answer versus a stronger answer

Most weak answers are not dishonest. They are vague, and they hide the candidate's own contribution inside the team. The pair below shows the difference. Both are illustrative examples written for this guide. Do not copy them as your own experience. Use them to see what evidence-led detail sounds like, then build the same shape from your real situations.

Question: “Tell me about a time you worked under pressure to meet a deadline.”

• Weaker answer: “We had a tight deadline and the whole team was under a lot of pressure. Everyone worked really hard and I helped where I could. In the end we got it done on time.”
• Stronger answer: “A client report was due in two days when we found a reconciliation error in the figures. I was responsible for the numbers, so I re-ran the reconciliation, traced the error to two source files that had been merged incorrectly, and corrected them. I briefed my manager on the change before the report went out. It was delivered on time and the client did not need a revised version.”
• Why the stronger answer works: it names what was at stake, makes clear what was personally yours to deliver, shows the specific actions taken in order, and ends with a result that can be checked. The weaker answer could describe almost anyone.

A competency question bank to practise with

Use these as practice prompts, not predictions. For each one, choose a real example from your evidence bank, outline it in STAR, and say it aloud once. One or two good examples will often cover several of these categories.

• Leadership: “Tell me about a time you led others through a difficult change.” “Describe a time you had to take responsibility for a decision that others disagreed with.”
• Teamwork: “Give an example of a time you helped a team achieve something it could not have achieved alone.” “Tell me about a time you had to work with someone whose style was very different from yours.”
• Problem-solving: “Describe a complex problem you solved and how you approached it.” “Tell me about a time you found a better way of doing something.”
• Conflict: “Tell me about a disagreement with a colleague or manager and how you handled it.” “Describe a time you had to deliver a message someone did not want to hear.”
• Customer service: “Tell me about a time you turned around an unhappy customer or client.” “Describe a time you went beyond what was expected to help someone.”
• Adaptability: “Tell me about a time your priorities changed suddenly.” “Describe a time you had to learn something new quickly to do your job.”
• Delivery and accountability: “Tell me about a time you missed a target and what you did next.” “Describe a project you were accountable for from start to finish.”

See how competency interviews fit into the Be Chosen stage of the Seen Method →

A preparation checklist you can use before the interview

Work through this the day before, not the morning of. It is designed to take under an hour once your evidence bank exists.

• List the competencies the job description repeats or implies.
• Choose two or three real examples per competency, from work, study or a substantial project.
• Write each example as a short STAR outline, not a full script.
• Say each answer out loud once, at a natural pace, and time it.
• Identify the one number or outcome in each answer you can defend if questioned.
• Prepare two or three questions to ask the interviewer about the role.
• Get a good night's sleep instead of rehearsing until the last hour.

Turn this into ready-to-use interview answers with the Interview Room Kit →

Prepare for probing questions

Interviewers may ask what you personally did, why you chose that approach, what alternatives you considered or how you know the result was successful. A memorised answer often collapses here. A real example becomes clearer.

Practise explaining the example at two lengths: a concise version and a fuller version. Record yourself once. Listen for missing actions, excessive background, unexplained jargon and places where “we” hides your own contribution.

Prepare the whole room, not only the questions

Review the organisation, the role and the likely concerns behind the hire. Prepare questions that help you understand the work, success measures and constraints. Also prepare a short introduction that connects your experience to this role without retelling your full CV.

On the day, listen to the exact question. Use the nearest truthful example, not the story you were most determined to tell. If an example is imperfect, say what you learned. Trust is built by clarity and judgement, not by pretending every situation ended perfectly.