How to answer competency questions: tips and examples

Competency questions ask you to show how you have used a skill in a real situation. To answer them well, choose a relevant example, explain your own actions and finish with the outcome or lesson. A simple structure such as STAR helps you stay focused without making your answer sound rehearsed.

What are competency questions, and what do employers want to learn?

Competency questions ask about something you have done to help an interviewer assess a skill or behaviour. They often begin with prompts such as “Tell me about a time when…” or “Give an example of how you…”. The interviewer is looking for evidence, not just a claim that you are organised, adaptable or good at teamwork.

A question about resolving a disagreement may test communication, judgement and collaboration at the same time. A question about working to a deadline may assess planning, prioritisation and reliability. Listen for the main behaviour in the question, then choose a story that gives clear evidence of it. The example can come from paid work, education, volunteering, a student project or another relevant responsibility.

Competency questions differ from hypothetical questions. “What would you do if a deadline changed?” asks how you might respond. “Tell me about a time a deadline changed” asks what you actually did. For the first, explain your approach. For the second, provide a real example and be precise about your own contribution.

Before answering, identify what evidence the question invites:

• Action: What did you do, rather than what did the whole team do?
• Judgement: How did you decide what mattered?
• Impact: What changed, improved or was completed?
• Learning: What would you repeat or do differently?

For example, if asked about initiative, do not stop at “I am proactive”. Describe a time you spotted a problem, took an appropriate step and explain what happened. For more interview preparation, use this guide to job interviews to practise other common question types.

How do you identify the competencies in a job advert?

Start with the job description and note the skills that appear in the responsibilities, essential criteria and company values. Look for both explicit terms, such as “stakeholder management”, and implied behaviours, such as explaining technical information to non-specialists. These clues help you predict the kind of evidence the interviewer may request.

Make a short list of likely competencies, then connect each one to a specific example. Avoid trying to prepare a separate story for every phrase. One strong example may demonstrate several related skills, but you should adjust the emphasis to match the question. A project that involved a tight deadline might show planning, communication and problem-solving. For a planning question, focus on how you organised the work. For a communication question, focus on how you kept people informed.

Use a simple table while preparing:

Look beyond the job advert, too. The role title, seniority and working context affect what counts as good evidence. A junior candidate can use an example from a course project; a manager should show how they set direction, supported others or managed trade-offs. The skills-based hiring assessments guide can help you recognise how employers test practical abilities.

Write down the exact competency beside each story. This keeps your preparation focused and helps you avoid giving a polished answer that does not actually respond to the question.

How should you structure a competency answer?

STAR stands for Situation, Task, Action and Result. It gives your response a clear sequence: set the context, explain your responsibility, describe what you did, then share the outcome. You do not need to announce each letter in the interview. Use the structure as a planning tool so the interviewer can follow your example.

Keep the situation and task brief. The action is usually the most important part because it shows your judgement and contribution. Explain the steps you took, the reasons behind them and how you involved other people. The result should be concrete where possible. It might be a completed project, a resolved issue, positive feedback or a lesson you applied later. Do not invent figures or claim sole credit for a team achievement.

A useful balance is to spend roughly one sentence on context, one on your responsibility, several on your actions and one or two on the result. Adjust this to the question and the complexity of the example. A short answer can still be detailed if it includes decisions and outcomes.

Use this planning template:

• Situation: What was happening?
• Task: What were you responsible for?
• Action: What did you personally do, and why?
• Result: What happened, and what did you learn?

Example outline for a missed deadline risk: “Our team was preparing a client report when a late data update put the delivery date at risk. I was responsible for checking the figures and coordinating the final review. I identified which sections depended on the new data, agreed priorities with the project lead and sent reviewers a revised schedule. We delivered the checked report on the agreed date, and I added an earlier data-confirmation step to the next project plan.”

Practise the outline rather than memorising a script. This makes it easier to sound natural if the interviewer asks a follow-up question.

How do you choose examples that show your own contribution?

Choose examples that are relevant, specific and recent enough for you to remember clearly. A high-profile project is not automatically the best choice. A modest example can be more persuasive if it shows a clear challenge, thoughtful decisions and a result you can explain. Make sure you can answer follow-up questions about the people involved, the choices you made and what happened afterwards.

Prepare a small bank of stories that covers different behaviours. For example, select one about teamwork, one about solving a problem, one about adapting to change and one about handling a mistake or setback. Your examples can come from different parts of your life. If you are changing careers or have limited formal work experience, coursework, volunteering, community activities and personal projects can provide useful evidence. Explain the context so the interviewer understands the scale and your role.

Use these checks before choosing a story:

• Is it closely connected to the competency in the question?
• Can you describe your personal actions in detail?
• Is there a clear outcome or lesson?
• Can you discuss it honestly without sharing confidential information?
• Could you explain it simply to someone outside your previous field?

For instance, a candidate with customer support experience might use a case where they noticed repeated questions about a process. They could explain how they reviewed the queries, proposed a clearer guide and checked whether customers could use it. The example shows initiative and communication without needing to disclose customer names, account details or sensitive business information.

Keep a preparation document with a few bullet points per story rather than full paragraphs. Include the competency, context, your actions and result. If you are updating your application materials as well, this guide to resumes and cover letters can help you describe achievements consistently.

What are good sample answers to competency questions?

A useful sample answer gives enough context to understand the challenge, then spends most of its time on the candidate’s choices and actions. The examples below are models of structure, not scripts to repeat. Replace their details with something that genuinely happened to you, and do not claim a result you cannot support.

Question: Tell me about a time you worked with others to solve a problem.

“During a group project, we found that different team members were using inconsistent information, which made our draft difficult to combine. I was responsible for coordinating the shared document. I suggested that we agree on one source for each key figure, created a simple checklist and asked each person to confirm their section before the review. When we found a discrepancy, I contacted the relevant contributor and updated the document only after we had checked the source. We submitted a consistent final version, and the checklist helped us avoid the same problem during the presentation.”

This answer works because it explains the issue, identifies a personal responsibility and describes specific actions. It also credits coordination rather than implying that one person did everyone’s work.

Question: Give an example of a mistake you made.

“I once sent a draft update before checking that all the figures matched the latest source file. A colleague noticed the mismatch before the information was shared more widely. I acknowledged the error, checked every figure against the source and sent a corrected version with a brief explanation. I then added a final source-check step to my review process. The immediate issue was fixed, and I became more careful about confirming version details before sending work.”

This response is direct, takes responsibility and shows a practical change. Avoid presenting a disguised strength as a mistake, blaming someone else or exaggerating the consequences. If you are asked about a failure, choose an example with a genuine lesson and explain how you applied it afterwards.

How do you answer questions about conflict, failure or pressure?

Difficult questions can feel risky, but they are an opportunity to show how you respond when work does not go smoothly. Choose a professional example that is honest and safe to discuss. You do not need to reveal private details about colleagues, clients or an employer. Describe the situation neutrally, focus on your decisions and explain what you learned.

For a conflict question, show that you listened, clarified the issue and worked towards a practical resolution. Avoid labelling another person as unreasonable. For a failure question, state your part in what went wrong, explain how you addressed it and name a specific lesson. For pressure or competing priorities, explain how you assessed urgency, communicated trade-offs and kept important work moving.

A response to a disagreement might follow this pattern: “A colleague and I had different views about the order of tasks on a shared project. I asked what deadlines each task depended on, then compared the risks with the project requirements. We agreed to complete the time-sensitive checks first and review the remaining work together. This helped us meet the key deadline, and I learned to clarify dependencies before discussing preferences.”

If the outcome was not fully successful, do not pretend it was. You can say what remained unresolved, what you did next and what you would change. That is often more credible than a story with an implausibly perfect ending.

If you do not have a directly relevant example, say so briefly and offer the closest truthful experience. Then explain how the same approach would apply to the role. Avoid making unsupported claims or disclosing confidential information to make an answer sound more impressive.

How can you practise without sounding rehearsed?

Practise aloud using short notes, not a memorised paragraph. Your notes should contain the competency, a few context words, the key actions and the result. This gives you a route through the answer while leaving room to respond naturally. Record yourself or practise with someone who can tell you where the story becomes unclear, too detailed or too vague.

A practical practice routine:

1. Select a question and identify the competency it tests.
2. Choose one example and sketch its STAR points.
3. Give an answer in your own words, without reading a script.
4. Check whether your actions and result were clear.
5. Practise a follow-up, such as “Why did you choose that approach?”

Prepare to adapt the same story to different questions. If the interviewer asks about communication rather than teamwork, bring the communication decisions to the foreground. Do not force an example that does not fit. It is better to pause briefly and choose another relevant story than to give a fluent but unrelated answer.

In an English-language interview, use straightforward vocabulary and explain local job titles or processes that an international interviewer may not recognise. If you need a moment to think, say, “I would like to choose a relevant example,” then take a short pause. You can also ask the interviewer to repeat or clarify a question. These are normal ways to make sure you answer what was asked.

Use the job search guide to organise your applications and preparation across opportunities. Before an interview, review the role and your notes, but avoid trying to predict every possible question. Your aim is to remember evidence and communicate it clearly, not to perform a memorised speech.