Choose from a wide range of NEWCV resume templates and customize your NEWCV design with a single click.
Use ATS-optimised Resume and resume templates that pass applicant tracking systems. Our Resume builder helps recruiters read, scan, and shortlist your Resume faster.
Use professional field-tested resume templates that follow the exact Resume rules employers look for.
Create Resume
Use professional field-tested resume templates that follow the exact Resume rules employers look for.
Create ResumeCompetency based interview questions are used by UK employers to test how you have behaved in real work situations, not how well you can describe yourself. They usually ask for examples of teamwork, leadership, problem solving, communication, resilience, conflict, initiative, decision making, and working under pressure. The best answers are specific, structured, and evidence led. A hiring manager is not looking for a perfect story. They are looking for proof that you can handle the situations the role will realistically throw at you. In recruitment, I see strong candidates fail these interviews not because they lack experience, but because they give vague answers, choose weak examples, or explain the situation without showing their own judgement.
Competency based interview questions are designed to uncover patterns in your past behaviour. The logic is simple: how you handled something before gives the employer clues about how you may handle similar situations again.
That sounds tidy in theory. In reality, these interviews are often a mix of useful assessment, employer anxiety, and hiring managers trying to reduce risk.
When an employer asks, “Tell me about a time you dealt with a difficult stakeholder,” they are rarely just checking whether you have met a difficult person before. They are trying to understand:
Whether you stay professional when things are awkward
Whether you can influence without becoming defensive
Whether you understand commercial priorities
Whether you escalate too quickly or too late
Whether you can explain your judgement clearly
Whether your version of “difficult” is actually just normal workplace friction
UK employers use competency based interviews because they want a fairer and more consistent way to compare candidates. This is especially common in graduate schemes, public sector recruitment, corporate hiring, financial services, consultancy, healthcare, education, engineering, project management, operations, HR, and leadership roles.
The employer is usually trying to assess whether you have the behaviours needed for the job, such as:
Communication
Teamwork
Leadership
Problem solving
Adaptability
Commercial awareness
Customer focus
That last point matters. Candidates often hear the question literally. Recruiters and hiring managers hear the answer diagnostically.
A competency answer is not just a story. It is evidence of how you think, prioritise, communicate, recover, and make decisions when work gets messy.
Resilience
Decision making
Accountability
Conflict management
Planning and organisation
Stakeholder management
Here is the honest recruiter view: competency based interviews are not always brilliantly designed. Some companies use them well. Others copy a question bank, attach a scoring sheet, and hope the process magically becomes objective.
That means your job as a candidate is not only to answer the question. Your job is to make your evidence easy to score.
A strong competency answer helps the interviewer see the behaviour clearly. A weak answer forces them to dig, interpret, or guess. Most interviewers will not work that hard for you, especially if they have six more candidates to interview before lunch.
These are the competency based interview questions I see most often in UK hiring processes.
Tell me about a time you worked as part of a team
Give me an example of when you solved a difficult problem
Tell me about a time you had to deal with conflict at work
Describe a situation where you had to work under pressure
Tell me about a time you had to influence someone
Give me an example of when you showed leadership
Tell me about a time you made a mistake
Describe a time when you had to adapt to change
Tell me about a time you managed competing deadlines
Give me an example of when you improved a process
Tell me about a time you handled a difficult customer or stakeholder
Describe a time you had to make a difficult decision
Tell me about a time you received feedback
Give me an example of when you went above and beyond
Tell me about a time you had to learn something quickly
The wording may change, but the assessment is usually the same. Employers are looking for evidence that you can perform the behaviours required in the role.
A good way to prepare is to stop memorising questions and start mapping examples to competencies. One strong example can often work for several questions, as long as you adjust the angle.
For example, a project that went off track could show:
Problem solving
Stakeholder management
Resilience
Communication
Prioritisation
Accountability
Leadership
The mistake candidates make is preparing twenty separate robotic answers. That is not preparation. That is panic with bullet points.
The best way to answer competency based interview questions is to use a clear structure. The STAR method is popular because it helps candidates avoid rambling.
STAR stands for:
Situation
Task
Action
Result
But most candidates use STAR badly. They spend too long on the situation, rush through the action, and give a weak result. From the interviewer’s side, the most important part is usually the action, because that shows what you actually did.
A better way to think about it is:
Brief context
Clear challenge
Your specific action
Why you chose that approach
Measurable or meaningful outcome
What you learnt or improved
The missing part in most answers is judgement. Candidates say what they did, but not why they did it. Hiring managers care about the why because it shows whether your decisions were thoughtful or accidental.
“I worked on a group project where we had a tight deadline. Everyone was stressed, so I helped the team stay organised. We finished the work on time and the client was happy.”
This sounds positive, but it is too thin. I cannot tell what the candidate actually did. “Helped the team stay organised” could mean anything. It could mean leading the work, sending one reminder, or making tea while everyone else did the heavy lifting.
“In my previous role, I was part of a team preparing a client report that had to be delivered by Friday. By Wednesday, it was clear we were behind because two sections were still waiting on data from another department. I spoke with the team lead, mapped out what was blocking each section, and suggested we split the remaining work by dependency rather than by original ownership. I contacted the data team directly, clarified exactly what we needed, and agreed a same day cut off so we could finalise the report on Thursday. We delivered the report on time, and the client approved it with only minor changes. What I learnt was that under pressure, structure matters more than simply working faster.”
This answer works because it shows action, communication, prioritisation, and judgement. It also shows maturity. The candidate did not pretend everything was heroic. They explained the problem, their contribution, and the outcome.
When I listen to competency answers, I am not just waiting for the official competency word to appear. I am listening for whether the answer feels real, relevant, and transferable.
Hiring managers usually listen for:
Ownership
Specificity
Decision making
Communication style
Awareness of other people
Results
Learning
Relevance to the role
A common candidate mistake is using language that sounds impressive but gives no evidence.
For example:
“I am a proactive team player with excellent communication skills.”
That sentence is almost useless in a competency interview. It is a claim, not evidence.
A stronger answer shows the behaviour:
“I noticed the team was duplicating work because updates were happening in separate calls. I created a shared tracker, agreed owners for each workstream, and used the morning stand up to flag blockers before they became delays.”
That tells me much more. It shows initiative, organisation, communication, and practical awareness.
Recruiters are trained, formally or informally, to separate claims from proof. Hiring managers may not describe it that way, but they do it too. They are asking themselves, “Would I trust this person with this situation in our team?”
Most poor competency answers fail for predictable reasons. The candidate may be perfectly capable, but the answer does not prove it.
Vague answers are the biggest problem. Candidates often speak in general terms because they are trying to sound professional.
They say:
“We worked collaboratively to resolve the issue.”
But the interviewer needs to know:
Who did what
What the issue actually was
What you personally contributed
What made it difficult
What changed because of your actions
If your answer could have been given by anyone else in the team, it is not specific enough.
Not every answer needs to be dramatic, but the example must be strong enough to prove the competency.
If you are interviewing for a senior operations role and your leadership example is about helping a new starter find the printer, that is not leadership. That is basic decency. Lovely, but not enough.
Choose examples that match the level of the role. A manager should show decision making, accountability, stakeholder judgement, and impact. A graduate candidate can use university, volunteering, part time work, internships, or societies, but the example still needs substance.
Team examples are useful, but be careful. If every sentence starts with “we”, the interviewer may not know what you did.
There is nothing wrong with acknowledging the team. In fact, it is a good sign. But your answer must clearly show your contribution.
Use “we” for shared context and “I” for your actions.
For example:
“We were responsible for delivering the project, and I took ownership of coordinating the client updates.”
That is much clearer than hiding behind the group.
Over rehearsed answers can sound polished but lifeless. Interviewers can usually tell when someone has memorised a script.
The risk is that you become so attached to your prepared answer that you stop answering the actual question. The interviewer asks about conflict, and you deliver your teamwork answer because it has a nice ending. That is not strategic. That is just refusing to leave the safety blanket.
Prepare examples, not scripts. Know the key points, but stay flexible.
A competency answer without a result feels unfinished. The result does not always need to be a huge metric, but it must show the effect of your actions.
Good results can include:
Revenue protected
Time saved
Customer complaint resolved
Process improved
Stakeholder relationship repaired
Deadline achieved
Risk reduced
Error prevented
Team performance improved
When possible, quantify the result. But do not invent numbers. Recruiters can smell fake metrics from a distance, and not in a charming way.
The strongest candidates prepare a small bank of flexible examples. They do not try to predict every question. They prepare evidence that can be adapted.
Before your interview, choose examples from different types of situations:
A time you solved a problem
A time you worked with others
A time you handled pressure
A time you influenced someone
A time you made a mistake or learnt something
A time you improved something
A time you dealt with conflict or difficulty
A time you led or took ownership
For each example, write down:
The situation in one or two sentences
The main challenge
Your specific actions
Why you made those choices
The outcome
What the example proves about you
The last point is important. Every example should have a purpose. Do not choose an example just because you remember it. Choose it because it proves something the employer needs to believe before hiring you.
If the job description mentions stakeholder management, do not rely on an example that only shows you can complete solo tasks. If the role requires pace and ambiguity, choose an example where priorities changed and you had to make sensible decisions without perfect information.
That is what good interview preparation really is: matching your evidence to the employer’s risk.
This happens often, especially for graduates, career changers, returners, and candidates moving into more senior roles.
The worst thing you can do is panic and say, “I have never done that.” Sometimes that may be true in the exact wording, but you may have relevant transferable evidence.
If you are asked about leadership and you have never managed people, you can use an example where you:
Took ownership of a task
Coordinated people informally
Trained someone
Improved a process
Led a project workstream
Made a decision others followed
Took responsibility when something went wrong
If you are asked about conflict and you have never had a major workplace dispute, use an example involving disagreement, competing priorities, stakeholder tension, or miscommunication.
You can say:
“I have not had a serious formal conflict at work, but I have dealt with disagreement around priorities. One example was…”
That is much better than forcing a dramatic story. Interviewers do not need workplace theatre. They need evidence of maturity.
For career changers, the key is translation. Do not expect the employer to do the mental work for you. Explain why the example is relevant to the new role.
For example:
“Although this was in a retail environment, the core challenge was stakeholder management under pressure, which is relevant here because the role involves balancing customer expectations with operational limits.”
That kind of framing helps the hiring manager connect the dots.
Many UK employers use scoring criteria during competency based interviews. This is common in structured recruitment processes, especially in larger organisations.
A typical scoring approach may assess whether your answer includes:
A relevant example
Clear personal contribution
Evidence of the required competency
Appropriate complexity
Positive outcome or learning
Communication quality
Some scoring systems are formal. Others are informal but still operate in the hiring manager’s head.
A weak answer may lose marks because it is too general, even if the candidate is strong. That is one of the frustrating realities of interviews. You are not assessed on everything you have ever done. You are assessed on what you communicate in that room or on that video call.
This is why clarity matters.
Candidates sometimes think interviewers will “get the idea”. Maybe. But you do not want your hiring outcome depending on someone else’s interpretation skills.
Make the evidence obvious. Make the relevance obvious. Make your decision making obvious.
That does not mean dumbing yourself down. It means respecting the fact that interviews are compressed judgement environments. The interviewer is collecting evidence quickly and comparing candidates who may all look broadly suitable on paper.
Strong competency answers usually have certain patterns. They are specific, grounded, and commercially aware.
Employers like candidates who can take ownership without sounding arrogant.
A strong answer might include:
“I realised waiting for the issue to resolve itself would put the deadline at risk, so I took ownership of clarifying the next steps.”
That sentence shows initiative and judgement.
Real work is full of trade offs. Time, quality, cost, stakeholder expectations, and risk rarely line up neatly.
A candidate who can explain trade offs sounds more credible than someone who pretends every decision was obvious.
For example:
“I knew we could not complete all three requests by Friday, so I prioritised the two that affected the client launch and agreed a later deadline for the internal reporting piece.”
That shows prioritisation, not just busyness.
Most competency questions involve other people, even when they look technical.
A good answer shows that you considered communication, expectations, and relationships.
For example:
“I spoke to the stakeholder before changing the timeline because I did not want them to find out through a missed deadline.”
That is a small detail, but it signals professional maturity.
Candidates sometimes think every answer needs to make them look flawless. It does not.
In fact, answers about mistakes, feedback, or conflict are stronger when they show self awareness.
A good answer might say:
“At first, I assumed the delay was caused by lack of resource. After speaking to the team, I realised the bigger issue was unclear ownership, so I changed my approach.”
That is much more believable than pretending you instantly knew everything.
Here are practical answer patterns you can adapt. Do not memorise them word for word. Use them to understand the level of detail and logic employers are listening for.
Question: “Tell me about a time you worked successfully as part of a team.”
Weak Example
“I worked in a team on a project and we all supported each other. I helped where needed and we completed the project successfully.”
The issue here is not that teamwork is missing. The issue is that the evidence is missing.
Good Example
“In my previous role, I worked on a cross functional project to improve the onboarding process for new clients. The challenge was that sales, operations, and customer support all had slightly different priorities. I noticed meetings were becoming repetitive because actions were not clearly owned, so I suggested a simple action tracker and agreed owners for each stage. I took responsibility for coordinating updates between operations and support, especially where client information was being handed over. As a result, we reduced missed handover details and the team agreed to keep the tracker for future onboarding projects. The main thing I learnt was that teamwork is not just being helpful. It is creating enough clarity that people can actually work together properly.”
Question: “Give me an example of a time you solved a difficult problem.”
Weak Example
“There was a problem with a process, so I looked into it and found a solution. My manager was pleased with the outcome.”
This is too vague. It gives no scale, no thinking, and no evidence.
Good Example
“In one role, we were receiving repeated customer queries about order updates, even though the information existed internally. I reviewed the process and found that customers were only being updated at two fixed points, which meant any delay created confusion. I spoke with customer service to understand the most common complaints, then worked with operations to introduce a simple interim update when orders passed a certain delay threshold. It was not a complicated fix, but it addressed the actual source of frustration. Query volume reduced, and the customer service team had fewer escalations to manage. What worked was looking at the problem from the customer’s experience, not just the internal process.”
Question: “Tell me about a time you dealt with conflict at work.”
Weak Example
“I had a disagreement with a colleague, but we talked about it and sorted it out professionally.”
This may be true, but it is too neat. The interviewer cannot assess much from it.
Good Example
“I worked with a colleague who wanted to delay a client update until we had all the details, while I felt we needed to communicate earlier because the client was already asking for progress. Rather than arguing over who was right, I suggested we separate what we knew from what still needed confirmation. I drafted a short update that gave the client a realistic position without over promising. My colleague agreed once they saw we were not presenting assumptions as facts. The client appreciated the transparency, and we avoided a more difficult conversation later. For me, the lesson was that conflict is often about risk tolerance, not personality.”
That final sentence is the kind of insight that makes an answer feel more mature.
Do not rush straight into your answer. It is perfectly acceptable to take a few seconds.
You can say:
“That is a good question. I am just thinking of the most relevant example.”
This is better than launching into the first story that appears in your brain and hoping it behaves.
When answering, listen carefully to the wording. “Tell me about a time you influenced someone” is not the same as “Tell me about a time you communicated clearly.” Influence requires resistance, persuasion, or stakeholder movement. Communication may simply require clarity.
After you answer, watch the interviewer. If they look unsure or ask follow up questions, do not panic. Follow ups are normal. They often mean the interviewer needs more evidence to score the competency.
Common follow up questions include:
What was your specific role?
What was the outcome?
What would you do differently?
How did the other person respond?
How did you decide that was the right approach?
What did you learn?
These questions are not always a bad sign. Sometimes they are giving you a chance to strengthen your answer.
Preparation should make you clearer, not robotic.
A practical way to prepare is to create a simple competency bank. Choose six to eight examples and practise explaining each one in two minutes.
For each example, know:
What competency it proves
What role requirement it connects to
What the challenge was
What you personally did
What result came from it
What you learnt
Then practise adapting the same example to different questions.
For example, a project delay could answer:
“Tell me about a time you worked under pressure”
“Tell me about a time you managed stakeholders”
“Tell me about a time you solved a problem”
“Tell me about a time you had to prioritise”
The difference is where you place the emphasis.
For pressure, focus on calm prioritisation.
For stakeholders, focus on communication and expectation management.
For problem solving, focus on diagnosis and solution.
For prioritisation, focus on trade offs and decision making.
This is how strong candidates sound natural. They are not winging it. They understand their own evidence well enough to use it intelligently.
To stand out, do not just answer what happened. Explain what the situation proves about how you work.
Average candidates describe events. Strong candidates reveal judgement.
For example, instead of only saying:
“I managed the deadline and delivered the report.”
Add the thinking:
“I prioritised the client facing sections first because those carried the highest risk if delayed.”
That small addition changes the quality of the answer. It shows decision making.
Another way to stand out is to connect your answer back to the role without sounding forced.
For example:
“That experience is relevant to this role because the job description mentions working with multiple internal teams, and I know that success in that environment depends on clear ownership and early communication.”
That is useful because hiring managers are constantly asking, “Can this person do this job here, with our pressures, our people, and our constraints?”
Your answer should help them say yes.
Competency based interviews often use polite, neutral language. But behind the question, there is usually a sharper concern.
When an employer asks about working under pressure, they may mean:
“Will you stay useful when priorities change, or will you become chaotic?”
When they ask about teamwork, they may mean:
“Can you work with people who do not think like you, or do you only perform when everyone is easy?”
When they ask about conflict, they may mean:
“Can you handle disagreement without creating drama?”
When they ask about mistakes, they may mean:
“Are you self aware enough to learn, or will you blame everyone else?”
When they ask about stakeholder management, they may mean:
“Can we trust you with people who have strong opinions and limited patience?”
This is why generic answers fall flat. The real question is often underneath the official question.
The more senior the role, the more this matters. Senior candidates are not just assessed on whether they completed tasks. They are assessed on judgement, risk awareness, influence, and whether they make life easier or harder for the people around them.
A strong competency based interview answer is not about sounding perfect. It is about giving clear, relevant evidence that helps the employer trust your behaviour in the role.
Before your interview, prepare examples that show real situations, real actions, and real outcomes. Choose examples with enough substance for the level of the job. Practise explaining them clearly, but do not memorise a script.
During the interview, slow down, answer the question asked, and make your personal contribution obvious. Explain your judgement, not just your activity. A hiring manager does not only want to know that you did something. They want to know whether you understood what mattered, acted sensibly, and achieved an outcome that would be valuable in their team.
That is the difference between a candidate who sounds prepared and a candidate who sounds hireable.
Written by Simar Malhi, a recruiter and headhunter with international recruitment experience. I write about CVs, job applications, hiring decisions, and the reality behind recruitment processes. My goal is to help candidates understand more honestly how employers, recruiters, and hiring managers actually select candidates.
Learning applied later
Upload Resume
Import from Linkedin