Competency-Based Interview Questions: 60 Examples by Competency

Competency-based interview questions ask a candidate to describe a real situation from their past that called for a specific skill: what they faced, what they personally did, and what happened. Below are 60 of them, five for each of 12 competencies, each with a follow-up to ask when the answer stays general and a line on what a strong answer includes.

You won't use all 60. A good interview picks the three to five competencies the role really needs and asks one or two questions on each. The sections before the list cover how to choose the competencies and how to run the questions; the sections after it cover scoring and the mistakes that waste a good question.

What is a competency-based interview?

A competency-based interview assesses a candidate against the specific skills and behaviors a job needs, the competencies, using questions about what they have actually done. "Tell me about a time a customer was angry about something you couldn't fix" tests customer focus with evidence. "How do you deal with angry customers?" only invites a description of good intentions.

The reasoning is simple: the best available evidence of how someone will handle a situation is how they handled a similar one before. That is why competency-based questions sit at the core of the structured interview, the format research ranks first among selection methods. The same questions, asked in the same order and scored against the same written scale, let you compare candidates on evidence instead of impressions.

Two kinds of question do this work:

• Behavioral questions ask about the past: "Tell me about a time you…". They need the candidate to have met the situation before.
• Situational questions ask about a scenario: "What would you do if…". They suit people early in their careers who haven't met the situation yet, though they test reasoning more than track record.

Most of the questions below are behavioral, because past behavior is the stronger evidence. Where a role hires people with little work history, such as graduates or career changers, swap in a situational version of the same question.

How do you choose competencies for a role?

Start from the job, not from the list. Read the job description and ask what someone has to do well in the first six months for the hire to be a success. Each answer is a candidate competency. Then cut:

1. Keep what separates good from great in this role. If every applicant will clear it, it doesn't need interview time.
2. Keep what you can hear in an answer. Typing speed or a license are checked another way. Problem solving or customer focus come through in a story.
3. Stop at three to five. More than that, and each one gets a single shallow question.

A customer support role might take customer focus, communication, problem solving and adaptability. A team lead role might take leadership, decision making, conflict resolution and ownership. If you're starting from a job description, the guide to turning a job description into interview questions walks through it step by step.

How should you use these questions?

Ask, then listen for STAR. A complete answer covers the Situation, the Task, the Action the candidate took and the Result. Candidates don't have to use the labels, but a strong answer contains all four. When one is missing, the follow-up usually supplies it.

Use the follow-up when the answer stays general. The most common weak answer describes what the team did, or what the candidate usually does, rather than one real event. "What did you personally do?" and "What happened in the end?" turn a general answer into evidence. The follow-ups below are written for the gaps each question tends to leave.

Keep the order and the wording. Asking every candidate the same questions, worded the same way, is what makes the answers comparable. Change a question between interviews and you are comparing different tests.

Write it down as you go. Note the candidate's own words for the part of the answer that matters. Those notes are the evidence for your rating later, and the fairest way to compare two people a week apart. An interview scorecard gives you a place for both the rating and the words.

60 competency-based interview questions

Communication

Getting information across clearly to the people who need it, in a form they can use, and checking that it landed.

1. Tell me about a time you had to explain something complicated to someone outside your field.
   Follow-up: What did you change when they didn't follow at first?
   A strong answer includes: Names the audience, adapts the explanation, checks understanding, gives the outcome.

2. Describe a time you had to deliver news that someone didn't want to hear.
   Follow-up: How did you prepare, and how did they react?
   A strong answer includes: Prepares the message, delivers it early and plainly, stays with the reaction, agrees on next steps.

3. Tell me about a written message, such as an email, report or proposal, that got you the result you needed.
   Follow-up: Who was the reader, and what did you leave out?
   A strong answer includes: Writes for a specific reader, leads with the point or the request, cuts what the reader didn't need, names the result.

4. Give me an example of a misunderstanding at work that caused a problem. What happened?
   Follow-up: What do you do differently now to prevent it?
   A strong answer includes: Owns their part of it, fixes the immediate problem, changes a habit such as confirming decisions in writing.

5. Tell me about a presentation you gave to a group. How did you prepare?
   Follow-up: Which question from the audience surprised you, and how did you answer it?
   A strong answer includes: Knows the audience and the goal, structures the message, handles questions honestly, says what they would change.

Teamwork

Working with others toward a shared result: sharing information, pulling their weight and helping when a teammate is stuck.

6. Tell me about a project where the result depended on several people. What was your part?
   Follow-up: What would have happened if you hadn't done your part?
   A strong answer includes: Describes their own contribution clearly rather than only what 'we' did, shows how it fit with others' work, gives the outcome.

7. Describe a time a teammate was struggling to keep up. What did you do?
   Follow-up: How did you help without taking over their work?
   A strong answer includes: Notices early, offers specific help, respects the teammate's ownership, involves the lead if needed, gives the outcome.

8. Tell me about a time you disagreed with how your team decided to do something.
   Follow-up: Once the decision was made, what did you do?
   A strong answer includes: Raises the concern with reasons in the right forum, then commits to the decision and helps it succeed.

9. Tell me about a time you worked closely with someone whose style was very different from yours.
   Follow-up: What did you change about how you worked with them?
   A strong answer includes: Describes the difference without blame, adapts their own approach, finds what the other person does well, gives the result.

10. Tell me about a time you helped another team or shift, even though it wasn't your job.
    Follow-up: What did it cost you, and was it worth it?
    A strong answer includes: Sees the bigger goal, helps without dropping their own work, keeps their manager informed, names the effect.

Problem solving

Working out what is actually wrong, weighing the options, and fixing the cause rather than the symptom.

11. Tell me about a difficult problem you solved at work. How did you work out the cause?
    Follow-up: What did you rule out along the way, and how?
    A strong answer includes: Defines the problem, gathers facts, tests possible causes, fixes the root cause, checks that the fix worked.

12. Describe a time you fixed a problem that kept coming back.
    Follow-up: Why hadn't the earlier fixes held?
    A strong answer includes: Spots the pattern, looks past the symptom, changes a process or system, shows the problem stopped.

13. Tell me about a time a solution you tried didn't work. What did you do next?
    Follow-up: What did the failed attempt tell you?
    A strong answer includes: Says so plainly, learns from the failed attempt, adjusts the approach, reaches a fix that works.

14. Tell me about a time you used data or numbers to solve a problem.
    Follow-up: What didn't the numbers tell you?
    A strong answer includes: Picks relevant data, analyzes it sensibly, draws a conclusion, acts on it, knows the limits of the data.

15. Describe a time you had to choose between a quick fix and a proper fix.
    Follow-up: What did you tell people about that choice?
    A strong answer includes: Weighs urgency against long-term cost, makes the trade-off visible, schedules the proper fix if the quick one comes first.

Adaptability

Staying effective when priorities, tools or circumstances change, and adjusting how you work rather than resisting it.

16. Tell me about a time your priorities changed suddenly. How did you handle it?
    Follow-up: What did you drop, and who did you tell?
    A strong answer includes: Re-plans quickly, tells people what will slip, keeps the most important work moving, doesn't dwell on the change.

17. Describe a time you had to learn a new system or process because the old one was replaced.
    Follow-up: What was hardest about letting go of the old way?
    A strong answer includes: Engages early, learns actively, helps others adopt it, raises real gaps constructively instead of resisting.

18. Tell me about a plan of yours that fell apart. What did you do?
    Follow-up: Looking back, what early sign did you miss?
    A strong answer includes: Stays calm, reassesses quickly, forms a new plan, keeps people informed, reflects on the warning signs.

19. Give me an example of working for a new manager or team whose way of working was very different from what you were used to.
    Follow-up: What did you change about how you work?
    A strong answer includes: Learns the expectations deliberately, asks questions, adjusts habits, keeps what works, gives the outcome.

20. Describe a time you were asked to do something well outside your usual role.
    Follow-up: How did you get up to speed?
    A strong answer includes: Accepts the stretch, finds help and resources, delivers something useful, is honest about the limits.

Leadership

Getting a group to a result: setting direction, developing people and taking responsibility for the outcome, with or without a title.

21. Tell me about a time you led a group to a result without having authority over them.
    Follow-up: Why did people follow your lead?
    A strong answer includes: Sets a clear goal, earns buy-in by involving people, coordinates the work, takes responsibility for the result.

22. Describe a time you had to address poor performance on your team.
    Follow-up: What did you actually say in that conversation?
    A strong answer includes: Acts early, is specific about the gap, agrees on a plan with support and a date, follows through either way.

23. Tell me about someone you helped develop. What did you do?
    Follow-up: How do you know it made a difference?
    A strong answer includes: Gives stretch work and regular feedback, coaches rather than rescues, can point to the person's growth.

24. Give me an example of getting a team behind a decision they didn't like.
    Follow-up: What did you do about the people who still disagreed?
    A strong answer includes: Explains the why, listens to objections, changes what can change, holds firm on the rest, checks in later.

25. Tell me about a time a project you led failed or missed its goal.
    Follow-up: What did you tell your team and your manager?
    A strong answer includes: Takes responsibility without blaming the team, explains the causes honestly, applies the lessons to the next project.

Customer focus

Understanding what customers need, solving their problems, and balancing their interests with the organization's.

26. Tell me about a time you dealt with a customer who was very upset.
    Follow-up: What was the first thing you said?
    A strong answer includes: Listens and acknowledges, stays calm, finds the real issue, fixes it or sets clear expectations, follows up.

27. Describe a time a customer asked for something you couldn't give them.
    Follow-up: What did you offer instead?
    A strong answer includes: Says no clearly and kindly, explains why, offers a real alternative, keeps the relationship.

28. Give me an example of going beyond the usual process to solve a customer's problem.
    Follow-up: Did it change how your team handles that problem now?
    A strong answer includes: Understands the customer's real need, uses judgment within policy, gets it done, feeds the lesson back to the team.

29. Tell me about a time you worked out what a customer needed before they told you.
    Follow-up: What were you watching or listening for?
    A strong answer includes: Pays attention to signals such as usage, questions and complaints, acts on them, shows how the customer benefited.

30. Describe a time you had to balance what a customer wanted with what was right for the business.
    Follow-up: Who did you involve in the decision?
    A strong answer includes: States both interests honestly, finds a workable middle, involves the right people, explains the outcome to the customer.

Ownership

Treating a result as yours: following through without being chased, flagging problems early and fixing what you broke.

31. Tell me about a mistake you made at work. What happened next?
    Follow-up: Who did you tell, and when?
    A strong answer includes: Admits it quickly, tells the right people, fixes the impact, puts something in place to prevent a repeat.

32. Describe something you improved at work that wasn't strictly your job.
    Follow-up: Why did you take it on?
    A strong answer includes: Spots a problem nobody owned, takes it on without being asked, sees it through, can show the result.

33. Tell me about a commitment you couldn't keep. How did you handle it?
    Follow-up: When did you first know it was at risk?
    A strong answer includes: Flags the risk early, proposes options, renegotiates rather than going quiet, delivers on the new commitment.

34. Give me an example of a task you saw through when nobody was checking.
    Follow-up: What would have happened if you had let it slide?
    A strong answer includes: Finishes the unglamorous part, closes the loop, holds their own standard without supervision.

35. Tell me about a time something went wrong on a project you were part of and someone had to step up.
    Follow-up: What did you personally do?
    A strong answer includes: Steps forward rather than waiting, focuses on fixing rather than blame, coordinates others, reports honestly.

Attention to detail

Getting the small things right and catching errors before they reach a customer, a patient or production.

36. Tell me about an error you caught before it caused a problem.
    Follow-up: How did you spot it?
    A strong answer includes: Describes the specific check or habit that caught it, corrects it, traces where it came from.

37. Walk me through how you check your own work before you hand it over.
    Follow-up: Tell me about a time that check caught something.
    A strong answer includes: Has a concrete method such as a checklist or a second pass, matches it to the risk, gives a real example.

38. Tell me about a time you had to work accurately through a lot of data or paperwork under time pressure.
    Follow-up: How did you keep your accuracy up as you got tired or rushed?
    A strong answer includes: Uses structure such as batches and reconciliations, checks totals, slows down where errors are costly.

39. Give me an example of a mistake of yours that got through. What did you change afterward?
    Follow-up: Has that change caught anything since?
    A strong answer includes: Owns it, understands why their checks missed it, changes the process rather than just promising to be careful.

40. Tell me about a time you noticed something small that turned out to matter.
    Follow-up: Why did you decide it was worth following up?
    A strong answer includes: Notices an inconsistency, follows it up instead of assuming, explains why it mattered, gives the outcome.

Time management

Planning and prioritizing work so the important things get done on time, and renegotiating early when they can't be.

41. Tell me about a week when you had more work than time. How did you decide what to do first?
    Follow-up: What did you let slip, and who did you tell?
    A strong answer includes: Prioritizes by impact and deadline, makes trade-offs explicit, tells people what will slip, delivers the critical items.

42. Describe how you planned a piece of work with a hard deadline several weeks away.
    Follow-up: What did you do when the plan started to slip?
    A strong answer includes: Breaks the work into milestones, builds in a buffer, tracks progress, acts early when it slips.

43. Tell me about a time you missed a deadline.
    Follow-up: What would you do differently now?
    A strong answer includes: Is honest about the cause, warned people early or admits they didn't, limited the damage, changed how they plan.

44. Give me an example of saying no to a request, or pushing it back, to protect a priority.
    Follow-up: How did the person react?
    A strong answer includes: Knows their priorities, says no or offers a later date with a reason, keeps the relationship.

45. Describe a time you were interrupted constantly but still had to finish work that needed focus.
    Follow-up: What did you change about your day?
    A strong answer includes: Protects time for focused work, batches interruptions, sets expectations with colleagues, delivers.

Conflict resolution

Handling disagreements directly and respectfully, so the work moves forward and the working relationship survives.

46. Tell me about a disagreement with a coworker that you resolved.
    Follow-up: What did you say when you first raised it?
    A strong answer includes: Raises it directly and privately, listens to the other side, focuses on the work rather than the person, reaches an agreement that holds.

47. Describe a time you disagreed with your manager.
    Follow-up: How did you raise it, and what happened?
    A strong answer includes: Disagrees with reasons and respect, accepts the final call or escalates properly, keeps the relationship intact.

48. Tell me about a time you had to settle a dispute between two people or teams.
    Follow-up: How did you stay neutral?
    A strong answer includes: Hears both sides separately, finds the shared goal, proposes a fair way forward, follows up.

49. Give me an example of a conflict you handled badly. What did you learn?
    Follow-up: What would you do differently today?
    A strong answer includes: Owns their part without excuses, names a specific lesson, shows they have applied it since.

50. Describe a time someone at work was upset with you. How did you respond?
    Follow-up: Was the working relationship different afterward?
    A strong answer includes: Stays calm, seeks to understand before defending, acknowledges valid points, repairs the relationship.

Learning agility

Picking up new skills and knowledge quickly, and applying the lessons from mistakes and feedback.

51. Tell me about a skill you had to learn quickly for a job. How did you go about it?
    Follow-up: How did you know you'd learned it well enough?
    A strong answer includes: Has a deliberate method such as practice, asking experts or reading the documentation, applies it quickly, checks progress.

52. Describe the most useful feedback you've had at work. What did you do with it?
    Follow-up: What changed in your work as a result?
    A strong answer includes: Takes the feedback without defensiveness, acts on it, can point to a concrete change.

53. Tell me about a time you were wrong about something important at work. How did you find out?
    Follow-up: What do you do now to catch that kind of mistake sooner?
    A strong answer includes: Admits being wrong, updates their view on the evidence, changes a habit.

54. Give me an example of something you learned in one job that you applied in a very different one.
    Follow-up: What did you have to adapt?
    A strong answer includes: Sees the underlying principle, transfers it thoughtfully, shows a result in the new setting.

55. What's something you've taught yourself for work in the last year?
    Follow-up: What was the hardest part, and how did you get past it?
    A strong answer includes: Has a real, recent example, explains how they learned it, shows persistence through the hard part.

Decision making

Making sound calls on time, often with incomplete information, and owning the result.

56. Tell me about a decision you had to make without all the information you wanted.
    Follow-up: What would have changed your mind?
    A strong answer includes: Identifies what matters most, gathers what they can in the time, makes the call, manages the risk, reviews the outcome.

57. Describe a decision you made that turned out to be wrong.
    Follow-up: What did you do once you realized?
    A strong answer includes: Explains the reasoning at the time, spots the error quickly, corrects course, separates bad luck from bad judgment.

58. Tell me about a time you had to choose between two good options.
    Follow-up: How did you explain the choice to people who preferred the other one?
    A strong answer includes: Sets criteria, weighs the trade-offs openly, decides, explains the reasoning.

59. Give me an example of a decision you made that was unpopular.
    Follow-up: Would you make the same decision again?
    A strong answer includes: Explains why it was right despite the opposition, listens to objections, communicates clearly, reflects honestly.

60. Describe a time you had to decide whether to escalate a problem or handle it yourself.
    Follow-up: Where do you draw that line now?
    A strong answer includes: Knows the limits of their authority, weighs risk and urgency, escalates with a recommendation rather than just a problem.

How do you score competency-based answers?

Decide what each rating means before the first interview, in a sentence or two for each competency. A three-point anchor is enough to start:

Then rate each answer against the anchor, not against the last candidate. Write the evidence next to the rating in the candidate's own words. If two interviewers saw the same candidate, rate separately before you compare notes, so the first opinion in the room doesn't become everyone's.

Weight the competencies by how much the job depends on them, and keep the overall recommendation separate from the individual scores. A candidate who is strong on four competencies and weak on the one the job can't do without is not a 4.

What mistakes should you avoid?

• Hypothetical answers to behavioral questions. "I would…" is a plan, not evidence. Ask for a real time it happened.
• Accepting "we". Teams do the work, but you are hiring one person. Ask what they personally did.
• Leading questions. "Tell me about a time you showed great leadership" signals the answer you want. Ask about the situation and let the candidate show the competency.
• Too many competencies. Twelve competencies in a 30-minute interview means twelve rushed questions and twelve shallow ratings.
• Rating the storyteller. A fluent speaker can make a thin example sound strong. Score what they did, not how well they told it.
• Skipping the notes. A rating with no written evidence can't be checked, compared or defended.

How do you turn these into an interview?

Pick three to five competencies from the job, choose one or two questions for each, and keep the follow-ups. The free interview question generator does this from the same 60 questions: tick the competencies, choose how many questions each, and copy the result into your interview guide.

If you would rather not run every first round yourself, DIO, Dio's AI interviewer, asks candidates past-behavior questions about the competencies in the job, follows up when an answer is thin, and rates each competency from 1 to 5 against anchors written for the role. Every competency score quotes the candidate's own words, and a person on your team makes the decision. See how it works.