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 answers work best when they prove behaviour, judgement and impact. In a UK interview, employers are not asking competency questions because they enjoy hearing rehearsed STAR stories. They are trying to understand how you behave when work becomes messy, urgent, political, unclear or commercially important. A strong competency answer gives a specific situation, explains what you personally did, shows the thinking behind your actions, and proves the result.
The mistake I see candidates make is treating competency answers like memory tests. They prepare neat stories but forget the real purpose: helping the interviewer trust their judgement. Good answers are not just well structured. They are credible, relevant and easy for the hiring manager to score.
Competency answers are structured responses to interview questions that ask you to prove a skill through a real example. These questions usually start with phrases such as:
Tell me about a time when you handled conflict
Give me an example of when you worked under pressure
Describe a time you influenced a stakeholder
Tell me about a time you solved a difficult problem
Give me an example of when you showed leadership
In the UK job market, competency based interviews are common across graduate schemes, public sector roles, professional services, finance, healthcare, operations, customer service, project management, HR, technology and management positions. They are also used heavily when employers want a fairer, more evidence based way to compare candidates.
In theory, competency interviews are objective. In practice, they are only as useful as the interviewer’s ability to probe properly and the candidate’s ability to explain their evidence clearly. That is where strong competency answers make a serious difference.
A hiring manager is not just listening for whether you have “teamwork” or “communication skills”. Everyone claims those. They are listening for patterns:
Employers ask competency questions because past behaviour is one of the clearest available indicators of future behaviour. It is not perfect, but it is better than asking candidates to describe themselves in flattering adjectives.
When an employer asks, “Tell me about a time you dealt with a difficult stakeholder,” what they often mean is:
“We have difficult stakeholders here. We need to know whether you can handle them without escalating every minor disagreement, damaging relationships or disappearing into passive aggression.”
When they ask, “Tell me about a time you worked under pressure,” they often mean:
“This role gets busy, priorities change, and we need someone who can stay useful when things are not perfectly organised.”
When they ask, “Tell me about a time you made a mistake,” they often mean:
“We want to know whether you take responsibility or start constructing a courtroom defence.”
This is why generic answers fall flat. Candidates often answer the surface question, but strong candidates answer the concern behind the question.
A recruiter or hiring manager is usually trying to reduce risk. They want to know whether hiring you will solve a problem or create a new one. That sounds blunt, but hiring is risk management dressed up as opportunity. Your competency answers should make the decision feel safer.
Do you take ownership or wait for someone else to fix things?
Can you explain your thinking clearly?
Do you understand the commercial or operational impact of your work?
Can you handle pressure without becoming chaotic?
Do you learn from difficult situations?
Are your examples relevant to the level of the role?
That last point matters more than candidates realise. A good answer for an entry level role can sound too light for a manager role. A good answer for a manager role can sound too vague for a technical specialist role. Competency answers are not one size fits all. They need to match the job, the seniority and the employer’s real concern.
The most common structure for competency answers is STAR:
Situation: What was happening?
Task: What needed to be done?
Action: What did you personally do?
Result: What happened because of your actions?
STAR is useful, but candidates often use it too mechanically. They spend too long setting the scene and rush through the part that matters most: the action.
A better recruiter approved version is:
Context: Give enough background for the example to make sense
Problem: Explain the challenge, risk, conflict or goal
Action: Show what you personally did and why
Result: Explain the measurable or meaningful outcome
Reflection: Add what you learnt, improved or would repeat
Reflection is often the missing piece. It is especially valuable in UK interviews because it shows maturity. Hiring managers like candidates who can think beyond “I did the thing and it went well”. They want to see judgement.
A strong competency answer should usually follow this balance:
Context should be brief
Problem should be clear
Action should be detailed
Result should be specific
Reflection should be short but thoughtful
The action section should usually be the longest part. That is where the interviewer sees your behaviour, decision making and practical value.
Strong competency answers usually have four qualities: relevance, ownership, specificity and impact.
Relevance means the example fits the competency and the role. If you are applying for a project manager role, your example should show planning, stakeholders, risk, delivery or coordination. If you are applying for a customer service role, your example should show communication, empathy, problem solving and follow through.
Ownership means the answer makes clear what you personally did. This is where many candidates accidentally weaken themselves. They say “we” throughout the answer because they do not want to sound arrogant. I understand the instinct, but interviews are not group therapy. The employer is assessing you. You can acknowledge the team while still making your contribution clear.
Specificity means the answer includes real details. Not unnecessary waffle, but enough evidence to make it believable. Vague answers sound rehearsed. Specific answers sound lived.
Impact means the result matters. It does not always need to be a huge commercial win. Impact can be a resolved complaint, a saved client relationship, a faster process, fewer errors, better communication, improved team performance, a successful deadline, or a lesson that changed how you worked afterwards.
The strongest answers also show judgement. They explain why you chose a certain approach. That is important because employers are not only hiring your activity. They are hiring your decision making.
Here is a common competency question:
“Tell me about a time you had to deal with a difficult stakeholder.”
Weak Example
“In my last role, I had a difficult stakeholder who kept changing their mind. I stayed professional, communicated clearly and eventually we got the project finished successfully.”
This answer is not terrible, but it gives the interviewer almost nothing to score. It says the right words but proves very little. “Communicated clearly” is one of those phrases candidates use when they have not explained what they actually did.
Good Example
“In my previous role, I supported a project where the operations team needed weekly reporting changes, but the finance stakeholder kept challenging the format because it did not match their internal process. The risk was that both teams were making separate requests, and the reporting deadline was becoming unrealistic.
I arranged a short call with both stakeholders instead of continuing the back and forth by email. Before the call, I mapped out which parts of the report were essential for operations, which parts finance needed for reconciliation, and where there was overlap. During the discussion, I kept the focus on the business outcome rather than personal preferences. I suggested one core report with two additional fields for finance, which meant operations still got a simple weekly view and finance had the data they needed.
The result was that we agreed the format in the same meeting, reduced the weekly reporting changes, and avoided delaying the next reporting cycle. What I learnt was that stakeholder conflict is often not really about difficult people. It is usually about competing priorities that have not been made visible enough.”
This works because it shows the situation, the risk, the candidate’s personal action, the outcome and the learning. It also gives the interviewer something useful to believe: this candidate can move a messy conversation towards a practical solution.
The best competency answers usually come from real situations where something was at stake. Not necessarily dramatic, but meaningful.
Good examples often involve:
A deadline that could have been missed
A stakeholder who needed influencing
A customer or client issue that needed careful handling
A process that was inefficient
A mistake that needed ownership
A team challenge that required communication
A change that needed adaptation
A decision made with incomplete information
A measurable improvement
A situation where you had to balance competing priorities
Weak examples usually have one of three problems. They are too old, too minor or too disconnected from the role.
For example, if you are applying for a mid level operations role and your teamwork example is from university group work six years ago, the interviewer may wonder why you do not have a stronger professional example. That does not mean academic examples are always wrong. For graduates or career changers, they can be perfectly valid. But your examples need to match where you are now.
This is where candidates need to be honest with themselves. The question is not, “Can I make this story sound good?” The question is, “Does this example prove I can handle the reality of the role?”
In UK interviews, especially in competitive markets, strong candidates do not just prepare random examples. They map examples against the job description. If the role mentions stakeholder management, deadlines, analysis, customer service, leadership and problem solving, you should have evidence for each of those areas before the interview.
There is a fine line between prepared and robotic. Preparation is good. Sounding like you are reading from an invisible script is not.
Interviewers can usually tell when an answer has been memorised too tightly. The rhythm is too polished, the wording sounds unnatural, and the candidate struggles when asked a follow up question. That is a problem because real interviews are not theatre performances. They are conversations with assessment attached.
A good competency answer should have structure, but it should still sound human. You should know the key points of your example, not memorise every sentence.
I usually recommend preparing examples in notes like this:
Competency being tested
Situation in one sentence
Main challenge
Three actions you personally took
Result
Lesson or reflection
Link to the role
This gives you control without making you sound like you have swallowed a careers website.
The best candidates are not always the ones with the most polished wording. They are the ones who can explain their work clearly, answer follow up questions honestly and show that they understand why their actions mattered.
Most weak competency answers fail for predictable reasons. The frustrating part is that many candidates are capable, but their answers do not let the interviewer see it.
Mistake one: spending too long on background
Some candidates spend two minutes explaining the company structure, team history and every character in the story before getting to what they did. By then, the interviewer is already mentally searching for the point.
Keep the context short. The interviewer does not need the full Netflix documentary.
Mistake two: using “we” for everything
Teamwork matters, but the interviewer needs to know your contribution. Say “we” when describing the team context and “I” when describing your actions.
Mistake three: choosing examples with no real challenge
If everything went smoothly, it is usually not a strong competency answer. Competency questions are designed to reveal behaviour under pressure, ambiguity, conflict or responsibility.
Mistake four: giving personality traits instead of evidence
Saying “I am resilient” is not evidence. Explaining how you handled a difficult situation and kept delivering is evidence.
Mistake five: hiding the result
Candidates often explain what happened but forget to say what changed. The result is where your answer becomes persuasive.
Mistake six: pretending every story was perfect
Real work is rarely that tidy. A little honesty makes answers more credible. You can say what was difficult, what you adjusted, or what you would do differently now. That often shows more maturity than a suspiciously flawless success story.
Competency answers are often scored against a framework, especially in structured interviews. The interviewer may be assessing whether you gave a relevant example, what actions you took, whether the result was positive, and whether your behaviour matches the required competency.
But there is also the human layer. Hiring managers are listening for confidence, clarity, judgement and fit. They are asking themselves:
Can I trust this person in the situations this role actually involves?
Do they understand the level of responsibility required?
Are they giving evidence or just saying what they think I want to hear?
Would their approach work in our environment?
Do they take accountability?
Do they communicate in a way that would work with our team, clients or stakeholders?
This is why a technically correct STAR answer can still feel weak. Structure alone does not win interviews. The content has to reassure the employer.
A useful way to think about it is this: every competency answer should reduce one hiring concern. If the employer is worried about pressure, your answer should prove calm prioritisation. If they are worried about stakeholder management, your answer should prove influence and judgement. If they are worried about leadership, your answer should prove direction, accountability and people awareness.
Do not just answer the question. Answer the risk behind the question.
A strong competency answer changes depending on seniority.
For early career candidates, employers usually look for potential, learning agility, reliability and communication. Your examples may come from internships, part time jobs, university projects, volunteering or early professional experience. What matters is that you explain your thinking clearly and show you can learn quickly.
For mid level professionals, employers expect stronger ownership. Your answers should show that you can manage priorities, solve problems without constant supervision, communicate with stakeholders and understand business impact.
For managers, competency answers need to show leadership through others. If every answer is about what you personally delivered, the hiring manager may question whether you can delegate, coach, influence and make decisions through a team.
For senior leaders, answers should show judgement, strategic trade offs, commercial awareness, risk management and the ability to operate with ambiguity. Senior competency answers should not drown in task level detail. They need to show decision quality.
This is a common reason candidates underperform in interviews after a promotion or career step up. They keep using examples from the level below. The answer may be true, but it does not position them at the level they want.
Start with the job description, not a random list of common questions. Job descriptions often reveal the competencies that will be tested, even when they do not say so directly.
Look for repeated words and themes such as:
Stakeholder management
Communication
Problem solving
Leadership
Commercial awareness
Customer focus
Prioritisation
Analytical thinking
Resilience
Collaboration
Change management
Attention to detail
Then prepare examples that match those themes. You do not need a completely different story for every possible question. One strong example can often answer several related questions, as long as you adapt the emphasis.
For example, a project delivery example might work for:
Working under pressure
Managing stakeholders
Solving problems
Prioritising workload
Communicating across teams
Handling change
The skill is not memorising dozens of answers. The skill is knowing your strongest examples well enough to adapt them.
Before the interview, ask yourself:
What competency does this example prove?
What was genuinely difficult about the situation?
What did I personally do?
Why did I choose that approach?
What changed because of my action?
What would a hiring manager find reassuring about this example?
Is this example strong enough for the level of role I am applying for?
That final question is the one candidates skip. It is also the one that often decides whether an answer feels convincing.
If you cannot think of a strong example, do not panic and do not invent one. Interviewers can usually smell a fake example because it lacks detail. The follow up questions expose it quickly.
Instead, look at your experience more carefully. Candidates often dismiss good examples because they think they are too ordinary. In reality, hiring managers are not always looking for dramatic hero stories. They are looking for evidence of how you behave at work.
Useful examples can come from:
Fixing a recurring problem
Improving a process
Handling a difficult conversation
Supporting a colleague
Dealing with a customer complaint
Managing workload during a busy period
Learning a new system quickly
Taking responsibility for an error
Influencing someone who initially disagreed
Helping a team work more effectively
The key is to find the decision point. What did you notice, decide, change, prevent, improve or take ownership of?
That is usually where the answer becomes interesting.
If your example still feels small, strengthen the explanation of impact. A small action can be valuable if it prevented confusion, saved time, improved accuracy or protected a relationship.
The best competency answers sound like a clear professional explaining a real situation. They do not sound like an HR textbook.
Use direct language. Avoid empty interview phrases such as:
I am a people person
I thrive under pressure
I always go above and beyond
I have excellent communication skills
I am very passionate
These phrases are not banned, but they are usually weak because they are claims without proof.
Replace them with evidence.
Weak Example
“I have excellent communication skills and always make sure everyone is aligned.”
Good Example
“I realised the issue was not a lack of effort, but that three teams were working from different assumptions. I created one shared update with the decision needed, the deadline and the owner for each action, so people were no longer interpreting separate email threads differently.”
That is stronger because it shows communication in action. It also shows the candidate understands why communication fails in real workplaces. Spoiler: it is rarely because someone forgot to “communicate clearly”. It is usually because ownership, priorities or decisions are unclear.
A good competency answer should make the interviewer think, “Yes, that sounds like someone who understands how work actually gets done.”
Use this framework when preparing your answers:
What was the situation? Keep it brief and relevant
What made it difficult? Show the challenge, risk or pressure
What did I personally do? Focus on actions, decisions and communication
Why did I do it that way? Show judgement, not just activity
What was the outcome? Include measurable or meaningful impact
What did I learn? Add reflection where useful
Why does this matter for the role? Connect the example to the employer’s need
That last point is powerful. You do not need to end every answer with a forced sales pitch, but you should make the relevance obvious.
For example:
“That is why I would be comfortable in this role where stakeholder communication and changing priorities seem to be a regular part of the environment.”
That kind of sentence helps the interviewer connect your evidence to their vacancy. Do not overdo it, but do not assume they will do all the linking for you.
Competency answers are not about sounding perfect. They are about proving you can handle the situations the role will realistically involve. In UK interviews, especially when competition is strong, employers are looking for evidence they can trust.
The strongest candidates prepare properly, but they do not over polish themselves into a corporate robot. They choose relevant examples, explain their personal contribution, show the thinking behind their actions and make the result clear.
The real secret is this: employers do not just assess what happened in your example. They assess how you understood it.
Two candidates can describe similar situations. One sounds like they completed a task. The other sounds like they understood the business problem, managed the people involved, made sensible decisions and learnt something useful. That second candidate is usually the one who feels safer to hire.
Good competency answers give employers confidence. Not because they are dramatic, but because they are clear, credible and relevant to the job in front of you.
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.
Upload Resume
Import from Linkedin