Interview guide · Interview types
Competency-based interview questions
In short
Competency based interview questions test one defined skill or behavior at a time, such as decision making or customer focus, by asking for real past examples and scoring them against a written standard. This page gives 31 questions across seven core competencies, with probes, red flags, sample answers and a weighted scorecard.
A competency-based interview starts before anyone asks a question. Someone has to decide which four to six competencies separate a good hire from a poor one in this job, write down what good looks like for each, and agree on how answers will be scored. The questions below are the easy part. The framework behind them is what makes the interview fair and predictive, and it is the part most teams skip. Our glossary entry on the competency-based interview covers the method itself.
To use this page, pick the competencies that match your job analysis, choose one or two questions per competency, and write two follow-up probes for each before the first interview. Every candidate for the role hears the same core questions in the same order. Score each competency on its own anchored scale right after the answer, not hours later from memory. Most questions here are behavioral (tell me about a time), which is the usual format, and a few are situational for candidates with thin work histories.
What these questions assess
- Evidence matched to the competencyA strong story about teamwork earns nothing on a planning question. Score only what the answer shows about the competency you asked about, and note anything else separately.
- Specific, recent examplesExamples from the last two or three years at a similar level of responsibility predict best. A story from a college group project carries less weight for a supervisor role.
- Clear personal contributionCandidates who describe what they did, in the first person, give you something to score. Answers about what the team decided tell you about the team.
- Results with numbers or observable changeHandle time dropped, the client renewed, the audit passed. Outcomes show the behavior worked, not just that it happened.
- Judgment about trade-offsReal competence shows in what the candidate chose not to do and why. Answers with no tension in them are often rehearsed or inflated.
- Learning carried forwardThe best candidates name what they changed afterward. It is the clearest sign they will respond to feedback in your organization.
Communication and influence
Tell me about a time you had to explain something complicated to someone with no background in it. How did you know they understood?
- Why ask it
- Tests whether the candidate adapts language to the listener and checks for understanding rather than assuming it.
- A strong answer
- Names the audience, the specific concept, how they simplified it (an example, a picture, fewer terms), and a concrete check such as asking the person to repeat it back or watching them do the task.
- Red flags
- Says they explained it clearly and the person got it, with no sign of checking.
Describe a situation where you needed someone to agree to something they initially opposed. What did you do?
- Why ask it
- Shows influence without authority, a core competency for almost any role above entry level.
- A strong answer
- Understood the other person's objection first, adjusted the proposal or the framing to meet a real concern, used data or a small pilot, and reached agreement or a fair compromise.
- Red flags
- Won by escalating to a manager or by wearing the person down.
Give me an example of written communication you produced that had a real effect, such as a procedure, a proposal or an email to a client.
- Why ask it
- Many jobs run on written instructions and updates. This finds people who write to get something done.
- A strong answer
- Describes the purpose, the reader, how they structured it, and what happened as a result, such as fewer errors or a signed approval.
- Red flags
- Cannot name a piece of writing they are proud of or describes only volume, such as answering many emails.
Tell me about a time you had to deliver news someone did not want to hear.
- Why ask it
- Reveals honesty, timing and tact under discomfort.
- A strong answer
- Delivered it promptly and directly, gave the reason, offered what could still be done, and followed up afterward.
- Red flags
- Delayed the message, softened it until it was unclear, or let someone else deliver it.
Teamwork and collaboration
Tell me about a time a project depended on people who did not report to you. How did you keep it moving?
- Why ask it
- Tests coordination across teams, where most work actually gets stuck.
- A strong answer
- Set clear asks and dates, made it easy for others to help, followed up in a predictable rhythm, and gave credit publicly.
- Red flags
- Blames other departments for the delay and describes no action of their own.
Describe a time you changed your own approach to work better with a colleague.
- Why ask it
- Shows flexibility and self-awareness rather than expecting others to adjust.
- A strong answer
- Names the specific difference, what they changed (meeting format, level of detail, timing), and how the working relationship improved.
- Red flags
- The colleague is described only as difficult and nothing about the candidate changed.
Tell me about a time you helped a teammate succeed when it was not part of your job.
- Why ask it
- Separates people who contribute to the team from those who protect their own numbers.
- A strong answer
- Gives a concrete example of time or knowledge shared, why they chose to do it, and what it cost them.
- Red flags
- Only helps when asked by the manager or keeps score of favors.
Describe a disagreement within your team about how to do something. What was your part in resolving it?
- Why ask it
- Reveals how the candidate handles conflict among peers.
- A strong answer
- Brought the disagreement into the open, focused on the goal, proposed a way to decide such as a short test, and accepted the result even if it was not their idea.
- Red flags
- Avoided the conflict entirely or describes winning the argument as the outcome.
Problem solving and decision making
Walk me through a problem you solved where the first explanation turned out to be wrong.
- Why ask it
- Tests whether the candidate checks assumptions and digs for root cause.
- A strong answer
- Describes the obvious explanation, the evidence that did not fit, how they tested other causes, and the actual fix.
- Red flags
- Fixed the first symptom they saw and moved on.
Tell me about a decision you had to make without all the information you wanted.
- Why ask it
- Most real decisions are made with gaps. This shows how the candidate weighs risk and timing.
- A strong answer
- Explains what was known, what was missing, why waiting was costly, how they limited the downside, and how they checked the result later.
- Red flags
- Either never decides without full certainty or makes big calls with no thought about risk.
Describe a time you used data to change how something was done.
- Why ask it
- Shows analytical thinking applied to a real outcome, not just reporting.
- A strong answer
- Names the data source, the pattern they found, the change they proposed, and the measured effect.
- Red flags
- Data appears only as something they were given, never something they used.
Tell me about a decision you made that turned out badly. What did you do once you knew?
- Why ask it
- Reveals ownership and how quickly the candidate corrects course.
- A strong answer
- Owns the decision, explains their reasoning at the time, describes how they noticed it was wrong, fixed it, and what they now do differently.
- Red flags
- The bad outcome is blamed on circumstances or the candidate claims never to have made a bad call.
Customer focus and quality
Tell me about a time you went past what was required to solve a customer's problem. Where did you draw the line?
- Why ask it
- Tests customer commitment and judgment about policy and cost at the same time.
- A strong answer
- Describes the need, what they did beyond the script, and a clear sense of the limits they respected and why.
- Red flags
- Gave away anything to make the customer happy or never went beyond the minimum.
Describe a time you noticed a quality problem before anyone else did.
- Why ask it
- Shows attention to detail and willingness to raise issues early.
- A strong answer
- Explains what they noticed, how they confirmed it, who they told, and how it was fixed before it reached customers.
- Red flags
- Noticed but assumed it was someone else's job to report.
Tell me about a time you had to balance speed with accuracy. What did you choose and why?
- Why ask it
- Every high-volume operation lives with this trade-off. This shows how the candidate weighs it.
- A strong answer
- Names the pressure on each side, the risk of an error in that context, and a sensible choice, such as a quick check on high-risk items only.
- Red flags
- Says accuracy always wins or speed always wins, with no thought about context.
Planning, organizing and adaptability
Tell me about a period when you had more work than time. How did you decide what to do first?
- Why ask it
- Tests prioritization against real business impact rather than arrival order.
- A strong answer
- Describes a method (deadlines, impact, who was waiting), what they deliberately delayed, and how they told people.
- Red flags
- Worked longer hours as the only strategy or let deadlines slip without warning anyone.
Describe a plan you built that had to change halfway through. What happened?
- Why ask it
- Shows whether the candidate plans with contingencies and adjusts calmly.
- A strong answer
- Explains the original plan, what changed, how fast they noticed, how they replanned, and what they kept from the original.
- Red flags
- Kept following the original plan after it stopped making sense.
Tell me about a time a major change at work was announced that you did not agree with.
- Why ask it
- Reveals adaptability and professionalism when change is imposed.
- A strong answer
- Raised concerns through the right channel, then committed to making it work and helped others adjust.
- Red flags
- Resisted quietly, complained to peers or waited for the change to fail.
Give me an example of a process you organized from scratch.
- Why ask it
- Tests structure and follow-through without an existing playbook.
- A strong answer
- Defined the steps, owners and checkpoints, documented it, and can say how it held up after they handed it off.
- Red flags
- The process lived only in their head and fell apart when they left.
Integrity, resilience and drive
Tell me about a time you were asked to do something you thought was wrong.
- Why ask it
- Tests integrity under pressure from someone with more authority.
- A strong answer
- Raised the concern calmly with the person, explained the risk, proposed an alternative and escalated through proper channels if needed.
- Red flags
- Went along with it because they were told to or cannot think of any example.
Describe the hardest feedback you have received at work. What did you do with it?
- Why ask it
- Shows coachability and emotional maturity.
- A strong answer
- Quotes the feedback specifically, admits how it felt, describes a concrete change and how they checked it worked.
- Red flags
- Explains why the feedback was unfair.
Tell me about a goal you missed even though you worked hard for it.
- Why ask it
- Reveals resilience and honest self-assessment.
- A strong answer
- Names the goal and the gap, analyzes why without excuses, and describes what they did next time.
- Red flags
- Claims to have always met their goals or blames the target.
Describe something you improved at work without being asked to.
- Why ask it
- Tests initiative and ownership beyond the job description.
- A strong answer
- Spotted a specific problem, got permission where needed, made the change, and measured the effect.
- Red flags
- Ideas stay as complaints about what management should fix.
Tell me about a mistake you made that no one would have found if you had stayed quiet.
- Why ask it
- One of the strongest integrity questions because it has no easy rehearsed answer.
- A strong answer
- Reported it promptly, quantified the impact, fixed it, and put a check in place.
- Red flags
- Fixed it quietly and tells the story as a clever save.
Leadership and developing others
Tell me about a time you took the lead on something when no one was formally in charge.
- Why ask it
- Shows leadership behavior in candidates who do not yet hold the title.
- A strong answer
- Explains the gap they saw, how they organized others, how they kept people on board, and the result.
- Red flags
- Took over and did everything themselves.
Describe a time you taught someone a skill. How did you know it stuck?
- Why ask it
- Tests coaching ability, a core competency for leads and trainers.
- A strong answer
- Broke the skill into steps, demonstrated, had the person practice, gave feedback and checked performance a few weeks later.
- Red flags
- Teaching meant sending a document or telling the person once.
Tell me about a time you had to hold someone accountable for poor performance.
- Why ask it
- Separates leaders who address problems from those who avoid them.
- A strong answer
- Addressed it early and privately, set clear expectations, documented, followed up and describes the outcome either way.
- Red flags
- Waited months or handed it to HR without talking to the person first.
Describe a decision you made as a leader that was unpopular with your team.
- Why ask it
- Shows whether the candidate can make and explain hard calls.
- A strong answer
- Explained the reason openly, listened to concerns, held the decision where it was right and adjusted details where the team had a point.
- Red flags
- Avoided making the call or announced it with no explanation.
Situational questions for less experienced candidates
If you had two tasks due at the same time from two different supervisors, what would you do?
- Why ask it
- Tests prioritization and communication in candidates who may not have a work example.
- A strong answer
- Would tell both supervisors early, ask which matters more to the business, and propose a realistic time for the other.
- Red flags
- Would quietly pick one or try to do both badly.
Imagine you notice a coworker skipping a safety or quality step to go faster. What do you do?
- Why ask it
- Tests integrity and peer accountability without needing past experience.
- A strong answer
- Would mention it to the coworker directly first, then to a supervisor if it continued, because the risk affects others.
- Red flags
- Would ignore it because it is not their business.
Suppose a customer asks for something you are not sure policy allows. Walk me through your response.
- Why ask it
- Shows judgment, honesty and willingness to check rather than guess.
- A strong answer
- Would be honest about not knowing, check with a lead or the policy, and get back to the customer with a clear answer and time.
- Red flags
- Would say yes to keep the customer happy or flatly say no without checking.
Sample answers
I was a shift supervisor in a distribution center, and at 2 p.m. on a Friday our main carrier told us a truck might not come. They would confirm by 6. If I waited and they canceled, about 900 orders would miss their delivery promise. If I booked a backup carrier, it cost roughly $1,400 extra. I called the backup and asked whether I could hold a slot until 5:30 without paying, and they agreed. Then I had the team stage the orders by zone so either truck could load in under an hour. At 5:15 the main carrier still could not confirm, so I booked the backup. The main truck never came. Afterward I wrote a one-page rule for the other supervisors on when to book the backup, so the next person did not have to work it out from scratch.
My manager told me during a quarterly review that my team meetings were a list of announcements and people had stopped listening. She was right, and it stung, because I thought I was being efficient. I started sending the announcements in writing the day before and used the meeting for one problem we had to solve together. The first few were awkward because people were not used to talking. By the third month we were fixing things in those meetings, like the break schedule that kept leaving us short at lunch. I asked my manager to sit in again after two months. She said it was the first time she had seen my team argue in a good way.
A new agent on my team at an insurance contact center was close to failing her first month because her after-call work was taking twice the target. She had not asked for help. I noticed because she was always still typing when the rest of us were back in the queue. I asked if she wanted to see the notes template I had built for myself, and we spent two lunch breaks going through her most common call types. Her after-call time dropped from about 90 seconds to under 50 within two weeks. It cost me some breaks, but I would rather do that than watch someone good leave.
Interview scorecard
| Competency | Weight | Strong (4–5) | Weak (1–2) |
|---|---|---|---|
| Problem solving and decision making | 20% | Finds root causes, weighs risk and timing, and checks the outcome afterward. | Treats symptoms, avoids decisions or decides without thinking about the downside. |
| Communication and influence | 15% | Adapts to the audience, checks understanding and wins agreement on the merits. | One style for everyone, relies on authority or escalation to get agreement. |
| Teamwork and collaboration | 15% | Adjusts their own approach, helps others without being asked and handles peer conflict directly. | Protects their own work, blames other people or teams, avoids disagreement. |
| Customer focus and quality | 15% | Solves the real problem within sensible limits and catches issues early. | Follows the script only or gives away whatever it takes to end the complaint. |
| Planning and adaptability | 15% | Prioritizes by impact, tells people about trade-offs and replans calmly when things change. | Works by arrival order, misses deadlines silently, resists change. |
| Integrity and resilience | 20% | Owns mistakes before they are found, raises concerns properly and acts on feedback. | Hides or minimizes mistakes, defends against feedback, blames targets or others. |
Score each competency from 1 to 5 straight after the interview, before discussing the candidate with anyone else, then multiply by the weight.
Build the competency framework before you write questions
A competency is a behavior you can observe and score, not a personality trait. Customer focus is a competency. Being a people person is not. Start with the job: ask two or three of your best current performers and their manager what separates a great month from a bad one, then look at why people in this role failed probation in the last year. You will usually land on four to six competencies. More than six and the interviewer cannot score each one properly in a 45-minute slot.
For each competency, write a one-sentence definition and three anchors: what a 1, a 3 and a 5 answer sounds like. For example, for planning and organizing at a 5: prioritizes by business impact, tells affected people about trade-offs in advance, and has a fallback. At a 1: works in the order things arrive and discovers conflicts at the deadline. Anchors are what turn a set of competency based interview questions into a measurement tool, and they are what you will point to if a hiring decision is ever challenged.
Weight the competencies to match the job. A collections agent role might put 25 percent on resilience. A team lead role might put 25 percent on developing others. Keep the weights in writing and use them every time, rather than letting the panel's mood decide which competency mattered most for a given candidate.
How to run and score the interview
Plan about 8 to 10 minutes per competency: one main question, two or three probes, and a minute of silence to write notes. Four competencies fit in a 45-minute interview with time for an opener and the candidate's questions. Use the same main questions for every candidate in the requisition, and agree the probes in advance: what exactly did you do, what happened next, what would you do differently. This is the same discipline behind any structured interview, applied to a defined competency list.
Score each competency immediately after the answer, before you move on. Interviewers who wait until the end score the last ten minutes and their overall impression. If you use a panel, have each person score independently, then compare. A spread of two points or more on any competency is worth a short discussion about what evidence each person heard.
For competencies that are hard to judge in conversation, such as attention to detail or data entry accuracy, pair the interview with a short work sample or test. Skills assessments give you objective evidence for those, so the interview can focus on the behaviors that only show up in stories. For a broader bank of past-behavior questions grouped by trait, see our behavioral interview questions, and for supervisors and managers, the leadership interview questions go deeper into coaching and accountability.
Mistakes that weaken competency interviews
- Generic frameworks pasted onto every role. A corporate list of eight values is not a competency model for a warehouse lead. Pick the few that predict performance in this job.
- Letting a good storyteller score high everywhere. Polished candidates give one strong story and stretch it across three competencies. Score only the evidence that fits each question.
- Accepting hypothetical answers to behavioral questions. If the candidate says I would, redirect: can you think of a time it actually happened. Use situational questions on purpose, for candidates without the experience, not by accident.
- Skipping the probes. The first answer is the rehearsed one. The second and third follow-ups are where you find out whether the candidate was actually there.
- Changing questions mid-search. If you improve a question, use the new version for everyone from that point and note the change, or the comparison stops being fair.
- Asking about protected characteristics while probing. Follow-ups like how do you manage that with young kids are off limits under federal and state anti-discrimination law. Keep probes about the work.
Adapting competency interviews for high-volume hiring
When you hire 30 agents a month, you cannot afford a 45-minute panel for each one, and you do not need it. Cut the list to three competencies for frontline roles, usually customer focus, reliability and learning ability, and move the screening question for each into the first stage. A five to ten minute structured screen, by phone, recorded video or an AI-assisted interview, can ask the same three questions of every applicant and score them against the same anchors. Live interviewer time is then spent on the shortlist.
Keep a human in the decision. Automated scoring is useful for consistency and speed, but someone should review borderline cases and audit outcomes by group every quarter for adverse impact. Track which competency scores actually predict 90-day retention and quality scores. After two or three hiring classes you will usually find one competency that predicts well and one that predicts nothing, and you can adjust the weights accordingly.
Frequently asked questions
What is the difference between competency based and behavioral interview questions?
Behavioral questions ask about past behavior. Competency based questions are usually behavioral too, but each one is tied to a defined competency with a written scoring standard. In practice, a competency interview is a behavioral interview built on a framework, so every question measures something specific and every answer is scored the same way.
How should a candidate answer competency based interview questions?
The STAR structure works well: situation, task, action and result. Interviewers mostly score the action and result, so candidates should spend most of the answer on what they personally did and what changed. A strong answer also includes what they learned or would do differently.
What are core competencies in an interview?
Core competencies are the behaviors an organization expects from everyone, regardless of role, such as communication, teamwork, problem solving, customer focus and integrity. Role-specific competencies sit on top, for example coaching for a team lead or negotiation for an account manager.
How many competency interview questions should I ask?
One main question per competency, with two or three probes, and four to six competencies per interview. That is usually five to eight main questions in 45 to 60 minutes. Asking more questions with less probing gives you more stories and less evidence.
Are competency based interviews used in the US?
Yes, though the term is more common in the UK, the public sector and large enterprises. US employers often call the same approach a structured behavioral interview. The method is the same: defined competencies, consistent questions and anchored scoring.
Can I use competency based questions for entry-level candidates?
Yes. Let candidates draw on school, volunteering, sports or family responsibilities, and mix in situational questions that ask what they would do. Score the reasoning, not the size of the example.