Why Strong Candidates Still Struggle With Competency Questions

You know your job inside out. You have the qualifications, the track record and genuine enthusiasm for the role. Then the interviewer asks, "Tell me about a time you had to influence someone more senior than you," and your mind goes completely blank. It happens to capable people every week.

Competency-based interviews are different from the conversational chats you may have had elsewhere. Instead of asking what you would do in a hypothetical situation, they ask what you did do. Past behaviour is treated as the best predictor of future performance, so every answer needs to be grounded in something that actually happened. That is why preparation matters more here than raw confidence.

What the Interviewer Is Really Listening For

Most public sector employers, large graduate schemes and many private companies score your answers against a defined framework. Typically they are looking for evidence of:

• Communication and influence – how you adapted your message to different audiences
• Planning and organisation – how you prioritised competing demands and managed deadlines
• Teamwork and collaboration – your specific contribution, not just the team's success
• Problem solving – how you analysed a situation and chose between options
• Resilience and adaptability – how you responded when plans changed or pressure mounted

Notice the pattern: they are assessing your behaviour and your reasoning, not just the outcome. A tidy result achieved by luck will score lower than a messy situation you navigated thoughtfully.

Build a Bank of Examples Before the Interview

The single most effective preparation technique is to build an example bank. Take a blank sheet of paper or a spreadsheet and list eight to ten situations from the last three to four years that you are proud of, or that taught you something. Include a mix:

• A project you delivered against a tough deadline
• A time you disagreed with a manager or colleague
• A mistake you made and what changed afterwards
• A moment you led a team, even informally
• A situation where you improved a process or saved money
• A time you handled an unhappy customer, client or service user

For each one, jot down four or five keywords rather than a full script. A handful of strong examples will flex across many questions, so you will rarely be caught short. Keep the detail honest — embellishment unravels quickly under follow-up questioning.

Structure With STAR – and Finish Strongly

The STAR format remains the clearest way to organise an answer: Situation, Task, Action, Result. It is familiar to interviewers, and it keeps you from rambling.

Where candidates come unstuck is the balance. Many spend two minutes on the background and twenty seconds on what they actually did. Flip it. Give the situation one or two sentences, state your specific responsibility, then spend the bulk of your answer on your actions — what you said, what you decided, who you spoke to and why. Close with the result and, crucially, what you learned or would do differently.

If you can, quantify. "We improved customer satisfaction" is vague. "Complaints dropped from around fifteen a month to four within a quarter, and the team stopped working weekends" tells the interviewer something concrete about your impact.

Handling the Awkward Ones: Failure, Conflict and Pressure

Questions about failure or conflict are not traps. Interviewers ask them because they want to see self-awareness and maturity, and because people who claim never to have failed are either inexperienced or not being straight with them.

Choose a genuine example where the stakes were real but the consequences were recoverable. Own your part without blaming others, then focus on the correction and the lasting change. "I underestimated how long the testing phase would take" is far stronger than "the supplier let us down."

For conflict questions, avoid framing yourself as the hero who single-handedly sorted out a difficult colleague. Show that you listened, sought to understand the other person's pressures, and found a workable way forward. For pressure questions, be specific about the techniques you used — renegotiating a deadline, splitting a task, escalating at the right moment — rather than simply saying you stayed calm.

Practise Out Loud Until It Feels Natural

Reading your notes is not practice. Speaking your answers aloud is. Record yourself on your phone, or ask a friend to fire questions at you in a random order. You are aiming for answers of roughly ninety seconds to two minutes that sound like a considered conversation, not a rehearsed speech.

Expect follow-up questions, and welcome them. "What would you do differently?" and "How did your manager react?" are invitations to show depth. After each practice run, note where you waffled and tighten it.

On the day, take a breath before answering. It is perfectly acceptable to say, "Let me think of the best example for that." A pause of five seconds reads as thoughtful; a rushed, unfocused answer does not. Prepare thoroughly, be yourself, and let the evidence speak for you.