# Competency Based Interview Questions: What They Test and How to Answer Them

Canonical URL: https://headwayskills.com/knowledge/employability/competency-based-questions-interview/
Markdown URL: https://headwayskills.com/knowledge/employability/competency-based-questions-interview.md
Entity type: Article
Last updated: 2026-07-07
Language: en
Primary audience: professionals improving building self-awareness at work
Owner: Headway Skills
Contact: https://headwayskills.com/contact/

## Short answer

Competency based interview questions ask for real examples of skills like teamwork. See the 7 common types, what each tests, and how to answer with STAR.

## Key facts

- Title: Competency Based Interview Questions: What They Test and How to Answer Them
- Category: Employability
- Primary skill: Building Self-Awareness
- Related skills: Communication, Building Confidence
- Primary keyword: competency based questions interview
- Source page: https://headwayskills.com/knowledge/employability/competency-based-questions-interview/

## What this page covers

- Competency based interview questions ask for real examples of skills like teamwork. See the 7 common types, what each tests, and how to answer with STAR.
- Practical guidance for competency based questions interview
- How this topic connects to Building Self-Awareness

## Detailed explanation

Competency based questions in an interview ask you to describe a specific time you showed a skill the job needs, such as teamwork, communication or problem-solving. They usually start with "Tell me about a time when…", and the interviewer judges what you actually did, step by step, and what happened as a result.

If most of your experience is a part-time job and a few group projects, that can sound like a test built for people with longer resumes. It isn't. These questions reward preparation more than years of experience, and once you can see what each question type is really checking, a small set of well-chosen stories from your own life covers most of them. The place to start is what the interviewer is listening for.

## What competency based interview questions are really testing

Every competency question rests on one premise: the way you handled a real situation is the best evidence of how you will handle a similar one in the job. That is why the wording matters. "Tell me about a time when…" and "Give an example of when you…" are requests for one real occasion, with a beginning, a middle and an end. An answer that starts "I would…" or "I usually…" sounds reasonable but misses the question, because it offers an opinion about yourself instead of evidence.

Each question is aimed at a named competency. The ones that come up most often are teamwork, communication, problem-solving, leadership, adaptability, time management and prioritization, and initiative, with conflict resolution close behind. In a formal competency-based interview, the employer has decided in advance which of these the role needs, and they are rarely a secret: the job description and the person specification usually spell them out. Read them with a pen in hand. Every competency named there is a question you can expect, which turns a vague dread about "what they might ask" into a short list you can actually prepare for.

## How to answer competency based questions without rambling

The structure almost every interviewer expects is STAR: the Situation (the context), the Task (what you were responsible for), the Action (what you did) and the Result (what happened). It works because it follows the way your answer is being judged.

The Action carries the weight. The situation and task are only there so the interviewer can follow along; the action is where the competency itself shows up. Two habits quietly weaken good examples here. One is spending most of the answer on background, so the part that matters gets squeezed into the last few seconds. The other is saying "we" throughout. The interviewer is not hiring your project group, so describe what you decided, said and did, even when the work was shared.

For a practical length check, the University of New Mexico's career services STAR packet suggests roughly two to three sentences for the situation, one to two for the task, two to three for the action and two to three for the result. That comes to about seven to eleven sentences in total. If you need a long run of background before anything happens, the setup is crowding out the part being assessed.

Finish on a result you can actually name. Concrete beats vague: the deadline your group hit after all, the society event that filled its room, the customer who came back. Where you have a number, use it. If the outcome was mixed, say so and add what you would do differently next time; an honest result is still a result.

## Seven common competency questions and what each one tests

The wording changes from one employer to the next, but most questions belong to a small set of types. For each one, here is what it usually asks and what the interviewer is listening for.

### 1. Teamwork

A teamwork question typically asks for a time you worked with others toward a common goal. The interviewer is assessing how you collaborate and how you communicate inside a group, not simply whether the group succeeded. So the evidence has to be your own share of it: the task you took on, the information you passed along, the moment you noticed a teammate was stuck and stepped in. "I'm a good team player" is a claim. "When our timeline slipped, I took over the data analysis and reorganized who did what" is evidence. Group assignments, sports teams and a busy shift at a part-time job all qualify.

### 2. Communication

Communication questions often ask you to describe a time you explained something complex to someone outside your field. The interviewer listens for whether you can simplify without talking down, and whether you adjusted the message to the person in front of you. Tutoring a classmate, explaining your thesis to a friend from another program, or walking a customer through a confusing policy are all good material. Say what you changed for that listener, such as the example you chose or the jargon you dropped, because the adjustment is the competency.

### 3. Problem-solving

Here the question usually asks for a complex challenge you resolved, often with limited resources or incomplete information. The interviewer wants to see how you think and how you make decisions under pressure. The strongest answers make the reasoning visible: which options you weighed, which one you chose, and why. A clever fix with no visible reasoning tells the interviewer less than a modest one whose logic they can follow.

### 4. Adaptability

Adaptability questions ask how you responded to a significant change: new responsibilities, a reshuffled team, a goal that moved halfway through. The interviewer is checking whether you adjusted constructively or dug in. Again, the reasoning is the substance. Describe what changed, how you read the new situation, and what you did differently as a result. A course that was restructured mid-semester or a part-time job where your role suddenly shifted are fair examples.

### 5. Conflict resolution

Conflict questions ask for a disagreement that was resolved successfully, and many candidates dread them because they seem to invite blame. The example does not have to come from a job. UCD Professional Academy's STAR guide builds its conflict-resolution answer around a final-year capstone project in which a four-person team reached an impasse over how the workload was divided. Choose a [disagreement about the work](/knowledge/teamwork/resolving-conflict/) rather than about a person, keep your account fair to the other side, and spend most of the answer on what you did to move things forward.

### 6. A mistake or failure

This is the question people fear most, and it is scored differently from how it feels. The interviewer is mainly assessing what you took from the mistake and what you did differently afterward, not how big the error was. So treat the mistake as the setup and the learning as the answer: a short, honest account of what went wrong and your part in it, then most of your time on what you changed and how that played out the next time. Ending on the mistake makes you sound defeated. Ending on the changed behavior makes you sound like someone who improves.

### 7. Initiative and leadership

Questions about a time you went above and beyond what was asked test initiative and leadership, two of the competencies employers assess most often. You do not need a formal title. Organizing a study group, fixing a process at a part-time job that everyone grumbled about, or volunteering for the task nobody had claimed all count. Make it clear that nobody asked you to do it, then show what changed because you did.

## Building a story bank you can rely on under pressure

You do not need a separate story for every possible question. The University of New Mexico's packet recommends drafting five STAR stories in advance: an accomplishment you are proud of, a time you went above and beyond, a conflict that was resolved successfully, a challenge you overcame, and a [mistake you learned from](/knowledge/confidence/learn-from-mistakes/). Five is enough because stories can be reused. The group project that nearly fell apart can answer a teamwork question, a conflict question or a problem-solving question, depending on which part of it you lead with.

Draw the stories from anywhere. University projects, [part-time jobs](/knowledge/employability/employability-examples/), volunteering, sport and student societies are all valid, because the interviewer is assessing the behavior, not the setting. Then map them: write the competencies from the job description down one side of a page and your five stories across the top, and mark where each story fits. Empty rows show you where to dig for one more example. If you are unsure which of your strengths you can back up best, it helps to [find your strongest work skills](https://assessment.headwayskills.com/) first and choose your lead stories to match.

How you rehearse matters as much as what you rehearse. Keep each story as a bulleted STAR outline rather than a written-out script. Outlines build confidence without making you sound memorized, and they leave room to adapt when a question is worded differently than you expected or the interviewer follows up. Then say the stories out loud, more than once. The first time you speak a story is rarely its best version, and that first time should not be in the interview.

[Nerves will still turn up](/knowledge/confidence/performance-anxiety/) on the day, and they are not a sign that you are underprepared. One of the young people we interviewed about starting work put it this way:

> It's OK to walk in to meet someone important thinking, 'Phew, I really hope I don't mess this up.' I think that's a healthy feeling — rather than just thinking it's all a game. I'm glad I understood that it's OK to be nervous when you have to talk to someone important.

He was talking about meeting senior people at work, and an interview panel fits the description just as well. Preparation does not remove that feeling. It means that when the nerves arrive, you have five stories to reach for instead of a blank.

## What makes these answers easier to give

Look back across the seven question types and the same three demands keep returning: knowing what your own experience actually proves, putting it into words an interviewer can follow, and doing both while you are nervous.

**Building Self-Awareness** is what turns a vague sense of "I've done some things" into evidence. It starts with noticing your natural strengths by looking honestly at how you worked and what results you got, which tells you which experiences genuinely demonstrate a competency and which only sound as if they might. It also changes how you handle the mistake question: if you have taken in a piece of criticism, added your own view and reflected on it, the learning part of your answer already exists. The point is not to claim every strength the job ad lists. It is knowing which ones you can back up.

**Communication** decides whether a good experience scores as one. The habits that matter here are few: put the main point first, be clear and direct, keep it brief, and adapt to your listener, who in this case is someone listening for one specific competency. Listening is half of it. Hearing exactly what a question asks, rather than answering the one you rehearsed, is what separates a targeted answer from a rambling one. None of this means memorizing model answers; it means a clear structure that holds up when an unexpected follow-up arrives.

**Building Confidence**. Before an interview, confidence comes from doing, and preparation is a form of doing. Rehearsing one story out loud, then the next, then all five in a mock run builds readiness in small steps. Deciding in advance exactly when and where you will practice keeps the preparation from sliding to the night before. And when one answer goes badly in the room, the skill is to accept the jolt of anxiety and focus on the next question instead of replaying the last one. The aim is to perform with the nerves, not to wait for them to leave.

Each of these improves with practice, and you can find out [which one needs practice most](https://assessment.headwayskills.com/) with the free Job Skills Test, which scores all three alongside **nine more skills that shape working life**, so the days before your interview go where they will make the most difference.

## The stories you already have

Some of these question types may have brought a specific memory to mind already. If you can name the group project that stalled until someone got it moving, or the shift when a customer's complaint landed on you and you dealt with it, you are holding the raw material for at least two of the seven answers. What is left is learning to see that material clearly and tell it well, and both are skills you build, without becoming a different person in the interview room. Describing your own work with evidence does not stop mattering once you are hired, either: a first performance review or a conversation about taking on more asks for the same thing, and it gets easier every time you practice it. The useful next step is knowing which of your skills to build on first.

## Know where to focus before the interview

One small step turns all of this into a plan. The Job Skills Test is a **free** self-assessment of your workplace skills. In 7 minutes it shows how you score across all twelve, and which ones will make the biggest difference to your interviews and your first months in a job.

**[Get my skills profile](https://assessment.headwayskills.com/)**

*Free, 7 minutes, with your results shown the moment you finish.*

## Who this is for

- Professionals building practical workplace skills
- Readers looking for specific, usable work advice
- Managers, educators, and coaches supporting career readiness

## Common questions

### What is this guide about?

Competency based interview questions ask for real examples of skills like teamwork. See the 7 common types, what each tests, and how to answer with STAR.

### Which Headway skill does this connect to?

This guide connects primarily to Building Self-Awareness. It also relates to Communication, Building Confidence.

### What is the recommended next step?

Use the free Work Skills Test to reflect on which work skill to improve next.

## Related pages

- https://headwayskills.com/knowledge.md
- https://headwayskills.com/knowledge/employability.md
- https://headwayskills.com/knowledge/self-awareness.md
- https://headwayskills.com/knowledge/communication.md
- https://headwayskills.com/knowledge/confidence.md
- https://headwayskills.com/work-skills-test.md

## Citation guidance

Use the canonical page when citing this content:
https://headwayskills.com/knowledge/employability/competency-based-questions-interview/

Preferred summary:
"Competency based interview questions ask for real examples of skills like teamwork. See the 7 common types, what each tests, and how to answer with STAR."

## Change log

- 2026-07-07: Content collection version published.
