Behavioral Interview Questions: Six Competencies, Asked Thirty Ways

Behavioral interview questions look endless, but they aren't. Every "tell me about a time" probes one of a handful of competencies the interviewer rates on a written scale, and US federal hiring guidance says a structured interview typically scores four to six of them. Six cover most of what gets asked. Learn them, find a story for each, and you can answer almost any phrasing.

Here are the common questions, grouped by what they're actually scoring:

Competency being scored	Common behavioral interview questions	What your answer must show
Conflict and disagreement	"Tell me about a time you disagreed with your manager." "Describe a conflict with a coworker."	A disagreement you didn't win cleanly, and how you kept the relationship
Learning from failure	"Tell me about a time you failed." "What's your biggest mistake?"	A named cost that landed on you, and what you changed afterward
Influence and leadership	"Tell me about a time you persuaded someone." "Describe a time you helped someone improve."	Who you moved or developed, what they cared about, and what changed because of you
Ambiguity and judgment	"Describe a decision you made without all the information." "Tell me about a time priorities changed suddenly."	What you were missing, and how you limited the risk
Prioritization under pressure	"Tell me about a time you managed competing deadlines." "When did your workload get overwhelming?"	What you dropped, and who you told
Initiative and ownership	"Describe a time you saw a problem and took initiative." "Tell me about a time you went above and beyond for a customer."	What you did that nobody asked for, and who it helped

And here's what one well-built answer sounds like, using STAR (situation, task, action, result):

Question: "Tell me about a time you disagreed with your manager."

Answer (STAR): "Situation: I was an operations analyst, and my manager wanted to cut our weekly supplier report to save time. Task: I owned that report, and I thought cutting it would hide late shipments. Action: Instead of arguing in the team meeting, I pulled six months of data and showed her the three delays the report had caught early. Then I proposed a shorter version that kept only the late-shipment section. Result: She agreed to the shorter version, it took half the time to produce, and it flagged a delayed order the next month. What I'd do differently: I spent a week building that case alone. Next time I'd ask her what problem the cut was solving before I built anything."

Here's what most people get wrong. They find a list of thirty questions, draft an answer under each, and rehearse until every one runs smooth. That produces thirty shallow answers and depth nowhere. The interviewer isn't grading question fourteen. They're rating a competency, and the follow-up (like that last "what I'd do differently") is where they get the detail to rate it. Nobody rehearses that, because you can't rehearse it alone.

What are the 10 most common behavioral interview questions?

These ten come up again and again, and each maps to a row in the table above. All but #2 (the disagreement with your manager) are drawn from The Muse's list of 33 behavioral interview questions, sorted into seven categories from teamwork to motivation and values:

1. "Tell me about a time you had a conflict with a coworker." Conflict.
2. "Tell me about a time you disagreed with your manager." Conflict, plus judgment.
3. "Tell me about a time you failed." Learning from failure.
4. "Tell me about a time you were under a lot of pressure." Prioritization under pressure.
5. "Give an example of a time you managed numerous responsibilities." Prioritization.
6. "Tell me about a time you persuaded someone." Influence and leadership.
7. "Describe a time you had to adapt to a change." Ambiguity and judgment.
8. "Tell me about a time you made sure a customer was pleased." Initiative and ownership.
9. "Describe a time you saw a problem and took initiative." Initiative and ownership.
10. "What's your proudest professional accomplishment?" Initiative and ownership, or whichever row the story proves.

Ten questions, six competencies.

How do you answer behavioral interview questions?

Tell one specific, true story using STAR, spend most of your time on what you personally did, and end with what you learned. Then expect the follow-up and be ready for it.

MIT's career office gives a useful weighting: situation 20%, task 10%, action 60%, result 10%. The same guide warns that "we" statements make it hard for an employer to see what your skills are, so say "I" for the parts you did. Weak answers invert that: a minute of scene-setting, a vague "so we worked on it," a result tacked on.

STAR is a useful structure. The failure mode is reciting it: interviewers can hear a template, which is why the template makes you sound like everyone who read the same blog post. Use STAR on paper to confirm each story has a real situation, a decision you made, and a one-sentence result. Then close the notebook and tell it like a person.

What is a behavioral interview actually scoring?

A handful of named competencies, on a numbered scale, written down before you walked in.

The US Office of Personnel Management's guide to structured interviews states that the structured interview is typically used to assess between four and six competencies, unless the job is unique or at a high level. Four to six. Not thirty. Its premise: the best predictor of future behavior on the job is past behavior under similar circumstances.

It tells the interviewer to build a rating scale beforehand, and the anchors on OPM's five-level version show what gets rewarded. Level 5 "applies the competency in exceptionally difficult situations." Level 2 "applies the competency in somewhat difficult situations." The scale rewards how hard the situation was, not how articulate you were.

Google's hiring guidance works the same way, documenting what a poor, borderline, solid, and outstanding answer would cover for each attribute a question is designed to test.

This machinery exists because it works. Sackett and colleagues' 2023 review of the validity evidence puts structured interviews at a mean operational validity of .42, ahead of general cognitive ability at .31. That's why the rubric beats the interviewer's gut.

Why do the same questions show up in thirty different phrasings?

Because the hiring side keeps a list of competencies and generates questions from it.

Harvard Medical School's HR guide, Sample Behavioral Questions by Competency, files roughly 500 sample questions under 24 competency headings, and cautions that it should be used only after a competency analysis of the job. The University of Arkansas career center publishes a similar bank organized entirely by competency.

Some employers publish theirs outright. Amazon's interview loop page points candidates to behavioral-based questions, its Leadership Principles, and the STAR method, and the 16 Leadership Principles are public, including Customer Obsession and Have Backbone; Disagree and Commit. Map your stories to them and you've done most of the Amazon prep.

What are the hardest behavioral interview questions?

The hardest one is rarely the first question. It's the second: the follow-up you couldn't script.

Google's guidance says its questions carry predetermined follow-up questions that help elicit a high level of detail. OPM devotes a whole build step to writing probes. For one interpersonal-skills question, its published examples include "what was the most important factor you considered in taking action?" and the one that ends most rehearsed answers: "is there anything you would have said and/or done differently?"

Harvard's bank carries probes in parentheses on the end of the question itself: (How did you cope?) and (What happened? What did you do? What was the result?). The follow-up is the script, and it's where a memorized answer runs out of material.

The story, told well by two candidates: "We were three weeks from launch when our largest client asked for a scope change that would have slipped the date. I pushed back, proposed a phased release, got them to agree, and we shipped on time with phase two four weeks later."

Weak follow-up, "what would you have done differently?": "Honestly, not much. Maybe communicated a little earlier, but the team executed really well and the client was happy."

Strong follow-up: "I'd have gone to the client before I went to my own team. I spent two days building the phased plan internally and only then took it to them, so when they pushed back on which features landed in phase two I had nothing left to trade. It cost about a week of goodwill I didn't need to spend. Now I take the rough shape of a compromise to the other side first and let them shape it."

Same story. The weak version scores down, because someone who can't find a flaw in their own decision is either not reflective or not describing a real one. The strong version scores on judgment, self-awareness and ownership at once, and no template produces it. It requires that the thing happened and that you thought about it afterward. It's the same muscle as a real greatest-weakness answer.

How many stories do you need for a behavioral interview?

Six to eight, each strong enough to cover two or three competencies. That's a smaller job than drafting thirty answers.

Pick them on difficulty, not outcome. The top of OPM's scale is "exceptionally difficult situations," so a clean win in an easy situation can rate below a partial win in a hard one.

Then audit for coverage. Lay your stories against the six rows of the table at the top and find the gaps. Check two rows hardest, because they're the easiest to fudge: a real failure where the cost landed on you, and a time you moved someone senior who didn't have to listen.

Then triage each story:

If your story...	Then
Ends cleanly in an easy situation	Swap it for a harder one, even if the ending is messier
Covers only one competency	Keep it only if that row has nothing else
Uses "we" for every action	Rewrite the action part around what you personally did
Has no answer to "what would you do differently?"	Find the answer before the interview, or drop the story
Appears in your opening pitch too	Good. Lead with it

Your best stories should also run through your opening answer. One coherent version of you beats thirty disconnected ones.

Does the follow-up catch people who make things up? (the part nobody mentions)

Not reliably.

A review of applicant faking in selection interviews by Melchers, Roulin and Buehl in the International Journal of Selection and Assessment reports Levashina and Campion's finding that follow-up questions increased faking, suggesting probing may not be a suitable way to check truthfulness. The review's practitioner table lists "ask follow-up questions as an attempt to reduce faking" under Don'ts. More room to talk is also more room to embellish.

So the follow-up isn't a truth machine. It's a detail machine, pulling out enough specifics to place you on the scale. A thin story rarely gets exposed as false. It just lands on "borderline" while real material lands on "solid," and nobody tells you why.

Two other limits. Plenty of interviews aren't structured at all, and against a gut-feel interviewer your competency map buys you less than being likable and coherent. And the behavioral round is one scored round among several, including the questions you ask at the end. Covering the competencies is necessary. It isn't the whole interview.

What to do now

1. Build the grid, not the list. Copy the six competencies from the table at the top down the left of a page. That's your prep document. Delete the thirty-question list.
2. Find six to eight real stories and map each to two or three rows. One good story usually covers conflict, influence and ambiguity at once. Coverage, not volume.
3. Grade each story on difficulty before you keep it. A "somewhat difficult" situation caps out mid-rubric. Swap in the harder one you've been avoiding because it didn't end cleanly.
4. Write the four probes for every story. What would you do differently, what did your manager say, what if that hadn't worked, what did it cost. Answer them in writing. These carry the score.
5. Say the follow-ups out loud to someone who pushes back. A friend who asks "and then what?" twice will find the thin spots faster than a mirror.
6. Fill the gaps deliberately. A competency with no story behind it is a hole in your material. Go find the project, or create one before the next round.

Want to know which competencies your stories don't cover? Message Praxy on WhatsApp. Bring your three best stories, and I'll run a voice mock interview where the follow-ups are the point, then tell you which row of the grid you're still missing a story for.