​Competency-Based Interview Questions: What UK Employers Are Really Testing

There is a specific kind of silence that happens when a candidate finishes answering a competency question and the interviewer just nods, writes something down, and moves on without reaction. Most candidates read that as bad news. More often it means the interviewer has moved into scoring mode, and the decision has already gone one way or the other.

These questions are not random. Every one targets a named skill, and the interviewer is working from a rubric that tells them what a strong answer looks like before you walk in. Your job is not to impress. Your job is to give them evidence that matches what they already have written down.

If you are going for roles in London, or applying through businesses along the Dartford and North Kent corridor, this matters. Hiring across logistics, finance, business support and engineering is genuinely competitive in that part of the country right now, and structured interviews are the norm across most employers.

What a Competency-Based Interview Actually Is

Every question in this format asks you to describe something real that happened to you. Not what you would do. What you did.

Past behaviour is the evidence base because, bluntly, it is a more reliable signal than anything hypothetical. Think about how different that is from a general interview, where vague answers like "I am a strong communicator" or "I work well under pressure" can go almost unchallenged. A competency format does not let you off the hook with a personality trait. You need a story — a situation, a specific action you took, and a result that actually happened.

The interviewer already has a scoring rubric. They know what a one-out-of-five answer looks like and what a five-out-of-five looks like. You are not being judged on impression alone. You are being marked against criteria that existed before you sat down.

This is why the format is trusted across such a wide range of employers. Large firms in Canary Wharf use it. Distribution companies operating around Crossways Boulevard in Dartford use it. NHS recruitment panels use it. Engineering outfits connected to the A2 and the Dartford riverside use it. The questions differ by role. The scoring logic is the same everywhere.

The Competencies That Come Up Most

Twelve skills dominate these interviews across UK employers. Knowing them in advance means you can prepare real examples before the day, rather than searching your memory under pressure.

People skills

●     Communication

●     Teamwork

●     Conflict resolution

Thinking skills

●     Problem-solving and innovation

●     Commercial awareness

●     Decision-making

Performance skills

●     Leadership

●     Delivering results under pressure

●     Adaptability

●     Organisation and planning

●     Resilience

●     Motivation and drive

Where you are applying matters here. Roles in Dartford's construction, logistics and manufacturing base — including businesses tied to the industrial estates off Stone Road and the DP World London Gateway corridor — tend to weight resilience, problem-solving and working under pressure. Shift to client-facing or office-based work in Central London and the emphasis often moves towards communication, commercial awareness and leadership.

Not always. But often enough that it is worth adjusting your preparation accordingly.

25 Questions and the Intent Behind Each One

Read past the surface wording. The question is just the packaging. What follows each group is what the interviewer is actually trying to find out.

Communication

"Tell me about a time you had to explain something complex to someone with little background knowledge of the subject."

"Describe a situation where the way you communicated directly changed the outcome."

"Give an example of a time you had to change how you were getting your point across because the person in front of you was not following."

What they want to know: do you listen as well as talk? Can you read a room? Do you adjust, or do you just repeat yourself more slowly?

Teamwork

"Describe a time the team needed something from you that was genuinely inconvenient for you."

"Tell me about a time you disagreed with what the rest of the group wanted to do. What happened?"

"Give me an example of a time when the result came directly from how well people worked together — not just from individual effort."

"Tell me about a team that was not functioning and what your role was in that."

The distinction they are drawing is between someone who contributes to a team and someone who relies on the team to carry them through.

Problem-Solving and Innovation

"Give me an example of a time something went wrong that you had not anticipated and what you did about it."

"Describe a process or system you changed and what the actual impact was on the ground."

"Tell me about a time the obvious solution was not available and you had to find a different way through."

This is about ownership. Do you step forward or step back when something breaks down?

Leadership and Decision-Making

"Tell me about a time you had to keep a group of people focused and moving in the same direction when things were uncertain."

"Walk me through the last significant decision you made and how you got there."

"Give an example of a time you realised mid-project that your current approach was not going to work and what you did next."

"Tell me about a time you had to get people with competing goals to agree on a way forward."

They want to see whether you can lead without the safety of a formal title, and whether your decisions hold up when you look back at them honestly.

Resilience and Working Under Pressure

"Tell me about a time you achieved something when most of the conditions were working against you."

"Describe a period where you were managing several competing demands at the same time."

"How have you handled a situation where your original plan fell apart completely?"

Do you absorb pressure, or do you transfer it to the people around you?

Delivering Results and Commercial Awareness

"Give an example of when you met or exceeded a target that felt genuinely difficult."

"Tell me about a time you improved something that had a direct financial or operational impact."

"Describe a situation where you had to weigh quality against speed and still deliver."

The underlying question is whether you understand the business context behind your work, not just the task sitting in front of you.

Adaptability and Versatility

"Describe a time you were asked to take on something you had genuinely never done before."

"Tell me about a significant change in your workplace and how you responded to it over time."

"Give me an example of picking something up quickly and having to use it straight away under real conditions."

Are you genuinely flexible, or do you just say you are?

The STARR Method — and Why the Last Letter Matters

Most people know STAR. Situation, Task, Action, Result. It is a solid framework and it works. The problem is that everybody uses it, which means most answers end up sounding fairly similar. The version that actually gets remembered adds one more step: Reflection.

Here is what each part should look like in practice.

Situation is your setup. Two sentences, maybe three — enough context for the interviewer to follow the story, not the full history of the project.

Task needs to be specific to you, not the team. What were you personally responsible for? This is where many candidates go vague and start talking about collective goals without clarifying their own role.

Action is where most of your answer should sit, because it is what interviewers are actually scoring. Walk through what you did, in sequence, using "I" rather than "we." The interviewer cannot hire your whole team.

Result needs to land somewhere concrete. A number is useful if you have one. "The complaint rate dropped by about 30% over the following month." "We kept the client and renewed the contract." "It came in eight days ahead of deadline." If there is no number, describe the specific outcome rather than saying things went well.

Reflection is the step almost no one includes. One or two sentences about what you actually took away from the experience and how it changed how you work since. It does not need to be a long, philosophical statement — just an honest observation. The reason it matters, particularly in professional services hiring in London and in the more structured processes common among larger Dartford and Kent-area employers, is that it signals self-awareness. That quality is genuinely difficult to screen for any other way.

What a Complete Answer Looks Like

Question: "Tell me about a time you had to manage a conflict within your team."

Situation: I was leading a small project group at a distribution company just off the A206 in Dartford. We were in the middle of a high-volume delivery week when two members of the team stopped communicating directly following a disagreement about task ownership.

Task: The tension was slowing output and unsettling the rest of the group. Sorting it was my responsibility.

Action: I pulled each person aside separately, away from the warehouse floor, so neither felt cornered or put on the spot in front of the others. In both conversations, what I found was that neither person was actually being unreasonable — a boundary had simply never been set when the project started, and both of them had been working from different assumptions about who owned what. I got them in the same room, laid out what I had heard from each side without taking a position on who was right, and we agreed a clear split going forward. Afterwards I went back to the project manager and flagged that the scope document needed updating before phase two started.

Result: The friction dropped almost immediately. We hit the week's targets and those two people went on to work closely together throughout the following phase without issue.

Reflection: That situation could have been avoided with twenty minutes of clarity at the start. Since then, establishing role boundaries is part of every project kickoff I run — even when it feels unnecessary at the time.

That is a complete answer. It stays specific throughout, it names a real place, and it does not pad itself out.

The Patterns That Cost Candidates the Job

"I would usually..." is not a competency answer. The question was about something that actually happened. Answering hypothetically tells the interviewer either that you have not done it or you have not prepared.

Saying "we" throughout. The team may genuinely have done something impressive. The interviewer is not making an offer to the team. Candidates who never separate their own contribution from the group's effort consistently undersell themselves, even when the underlying story is strong.

No result. Telling the interviewer what you did without saying what happened as a result is like building to a punchline and then going quiet. Always close the loop.

Recycling one example. One strong story cannot cover a twelve-competency interview. The moment an interviewer hears the same project appearing for the third time under a different question, their confidence in the depth of your experience drops. You need at least eight to ten genuinely different situations.

Fumbling a follow-up. Questions like "what would you have done differently?" or "how did the others react?" are not traps. They come from an interviewer who wants more. Not having a real answer is a missed opportunity.

Getting Ready Without Overcomplicating It

Start with the job description — not just to understand the role, but to pick out every word that describes a skill or behaviour. Those words tell you exactly which competencies the employer had in mind when they wrote it.

Build your example bank next. Eight to ten real situations from different jobs, projects or contexts. The most useful examples are ones that can flex across more than one competency depending on which part of the story you foreground. A logistics supervisor role near the Dartford Crossing will draw on different areas than an account management position in the City, so match your examples to the role, not just to the competency list in general.

Practise out loud and time yourself. A solid STARR answer lands between 90 seconds and two minutes. Shorter and something is missing. Longer and you have lost the room.

Prepare at least one backup per competency area. If the interviewer asks for another example and you stall, that pause says more than you want it to.

Video Interviews: The One Thing That Changes

Most hiring processes in London and across the Dartford area now include at least one stage over Teams or Meet. The questions are identical to an in-person format. The delivery is not.

On camera, eye contact means looking at the lens — not the screen where the interviewer's face appears. Silence that feels ordinary in person feels noticeably longer on video, which means structure matters more, not less. Keep your background clear. Sort your audio before you join. For the full checklist on what to wear on camera, see our what to wear guide. A broken microphone or a cluttered background in the first thirty seconds creates an impression that does not recover easily — regardless of how strong your examples are.

Questions Candidates Often Ask

How many competency questions should I expect?

Typically three to six in a standard 45 to 60-minute interview. Larger London employers running formal assessment processes sometimes use more. Prepare across six competency areas as a minimum.

What if I blank on an example mid-interview?

Buy yourself a moment honestly. "Let me make sure I give you the most relevant example" buys you five to ten seconds without sounding evasive. Then reach for your closest situation. Never fabricate — interviewers follow up, and invented examples fall apart under a second question.

Do entry-level candidates get these questions?

Yes, and quite commonly. Someone without much formal history can draw on university projects, volunteering, part-time work or situations from outside work altogether. The depth of the example will differ naturally, and a reasonable interviewer accounts for that.

What if I am switching industries?

The transferable skills are the point. Resilience is resilience whether it came from a retail floor in Lewisham or a construction site off the A225 in Dartford. Frame your example around the skill, not around proving sector-specific experience.

How do I know which competencies to focus on?

The job description is your clearest signal. The language in the responsibilities section and the person specification usually tells you directly. Cross-reference that with what you know about the employer's size and sector, and you will land close to the right areas.

One Thing Worth Saying Before Your Interview

Preparation is the one variable you have complete control over. The questions are predictable. The format is known in advance. The employer already has a picture of what a strong answer looks like before you open your mouth.

Your job is to match your real experience to that picture — specific situations, honest outcomes, enough structure that the interviewer can score you without having to work for it. Once you've nailed your answers, don't forget the moment that comes next — the questions you ask them matter just as much.

If you are weighing up options for roles in London or around the Dartford and Kent area, talking to a recruiter who works those markets daily is a practical shortcut. Not to hand the process over. Just to walk in knowing exactly what is waiting on the other side of the table.

Civic Recruitment places candidates across London and Dartford in permanent and contract roles. If you want a clearer picture of what employers in your sector are currently asking, our team is a good place to start the conversation.