50 Structured Interview Questions by Competency (With Scoring Notes)

Most "structured interview questions" lists hand you the questions and stop there. That is the easy half. Anyone can paste 50 prompts into a doc. The hard half, the half that actually decides who you hire, is knowing what a strong answer to each question looks like versus a weak one, in writing, before the candidate opens their mouth. This guide is built for the interviewer and the evaluator, not the candidate, and it leads with the scoring note for every question because that note is where the hiring decision really lives.

Here is the frame the candidate-prep articles skip: a question is cheap, the scoring note is the asset. Two interviewers can ask the same competency question and reach opposite verdicts, because one is scoring against a written "strong vs weak" definition and the other is scoring a feeling. The questions below are organized by competency, and each one comes with a one-line scoring note so every interviewer on your panel grades the same answer the same way. Score the signal, not the vibe.

Why the Scoring Note Carries the Weight

The interviewer side of the table has a measurement problem, not a question shortage. You can ask a flawless competency question and still hire badly if every interviewer rates the answer on a private scale in their head. The research is blunt about how much structure helps: Schmidt and Hunter's 1998 meta-analysis put the predictive validity of structured interviews at .51 against .38 for unstructured ones (Schmidt & Hunter meta-analysis). The structure doing that work is mostly the scoring discipline, not the wording of the prompt.

Google's hiring research team reached the same place from a different angle. As Dr. Melissa Harrell, a researcher at Google, puts it in the company's re:Work guide, structured interviews "are one of the best tools we have to identify the strongest job candidates" (Google re:Work). That same guide recommends scoring answers against a standardized rubric (poor, borderline, solid, outstanding) and documenting examples of what each level contains. The examples are the point. A rubric with no written examples is just a number line, and a number line gets scored differently by every person holding it.

Across the interviews we have processed at Asked, the pattern holds: when two interviewers ask the same competency question without a shared scoring note, their independent ratings agree far less often than either expects. The disagreement is never really about the candidate. It is about what each interviewer silently decided "good" meant. The 50 questions below make that definition explicit, one note at a time, starting with the competency most roles get wrong.

Problem-Solving and Analytical Thinking

Lead with this competency because it travels across almost every role. Each question gets a scoring note: a strong answer isolates the candidate's own reasoning, a weak one stays abstract.

"Walk me through a problem you solved where the obvious answer turned out to be wrong." Strong: names the wrong assumption and what data corrected it. Weak: describes a textbook process with no real reversal.
"Tell me about a decision you made with incomplete information." Strong: states what was missing and how they bounded the risk. Weak: claims they "just knew" or had all the facts.
"Describe a time you found the root cause of a recurring issue." Strong: traces a specific chain to a cause others missed. Weak: treats a symptom and calls it fixed.
"When have you had to simplify something complex for a decision-maker?" Strong: shows the cut they made and why. Weak: lists detail without a decision attached.
"What is a problem you chose not to solve, and why?" Strong: defends a real prioritization tradeoff. Weak: cannot name anything they deprioritized.
"Tell me about a time your first solution failed." Strong: owns the failure and the second attempt. Weak: blames inputs or other people entirely.
"How did you validate that a fix actually worked?" Strong: names a metric and a before/after. Weak: "it felt better" with no measure.

That last note, the missing measure, is the same gap you will see in the next competency, where candidates love to describe ownership they did not actually hold.

Ownership and Accountability

Ownership questions catch the "we" problem better than any other category. The scoring note here always asks: did the candidate isolate their own action, or hide inside a team?

"Describe a project that missed its goal. What was your specific role?" Strong: first-person actions and an honest share of the miss. Weak: a passive "the project slipped."
"Tell me about something you shipped that you were responsible for end to end." Strong: scope, decisions, and outcome they personally held. Weak: a group effort with no individual line.
"When did you catch your own mistake before anyone else did?" Strong: names the mistake and the correction. Weak: cannot recall ever being wrong.
"Give me an example of a commitment you couldn't keep." Strong: how they flagged it early and what they renegotiated. Weak: silence until it blew up.
"What did you do the last time a deadline was genuinely at risk?" Strong: a concrete triage move with a named tradeoff. Weak: "worked harder," no specifics.
"Tell me about feedback you received that you initially disagreed with." Strong: what changed in their work afterward. Weak: defends the original position with no movement.
"Describe a time you took on something outside your job description." Strong: why it mattered and what they delivered. Weak: a vague claim of being a team player.

A recurring weak signal across this set is the disappearing first person. The candidate who says "we decided" four times has told you nothing scorable, which is exactly what the STAR rubric in the next section is designed to expose.

Communication and Influence

Influence questions are where charisma fools panels most. The scoring note pushes past delivery to evidence of an outcome.

"Tell me about a time you changed someone's mind without authority over them." Strong: the argument they used and the result. Weak: "I'm persuasive," no example.
"Describe a moment you had to deliver bad news to a stakeholder." Strong: how they framed it and what happened next. Weak: avoids that they delivered it at all.
"When did a message you sent get misread? What did you do?" Strong: owns the ambiguity and the repair. Weak: blames the reader.
"Give me an example of explaining a technical idea to a non-technical audience." Strong: the specific analogy or cut they made. Weak: restates the technical version slower.
"Tell me about a disagreement you resolved between two people." Strong: their actual mediation move. Weak: "they worked it out," with no role for the candidate.
"When have you pushed back on a senior leader?" Strong: the stakes and how they kept the relationship. Weak: a story with no real risk in it.
"Describe a time you had to say no to a request from a teammate." Strong: the reasoning and the alternative offered. Weak: agreement framed as a no.

Notice that every strong note in this category demands a named outcome, not a smooth delivery. That demand is exactly what an anchored STAR rubric enforces, and the rubric is worth building once and reusing forever.

How to Build a Scoring Note You Can Reuse

A good scoring note is not improvised in the room. Building the anchors before the questions, the way a competency-based interview works backward from its scorecard, is what keeps the note honest. Levashina, Hartwell, Morgeson, and Campion (2014), in their Personnel Psychology review, listed basing questions on a job analysis, asking every applicant the same questions, rating each answer, and using anchored scales as the components that make interviews work (Levashina et al., 2014). Here is the three-step procedure we recommend for writing the note before you ever ask the question:

Name the competency and one observable behavior. Not "communication" but "explains a tradeoff a non-expert can repeat back." A note you cannot observe in an answer cannot be scored.
Write the strong answer and the weak answer as two sentences. The strong sentence describes specific first-person action plus a result. The weak sentence describes the most common dodge (abstraction, hypotheticals, or hidden "we"). These two sentences become your anchors.
Attach a 1 to 5 scale to those anchors. A 5 matches the strong sentence, a 1 matches the weak one, and 2 through 4 sit between. Print it. Every interviewer scores against the same descriptions.

Do those three steps once per competency and you have a scoring note that survives across candidates and across interviewers. Holding that set steady when forty people in different teams share it is its own discipline, which Standardized Interview Questions: Build a Repeatable Set walks through. The next two competencies already have their strong-versus-weak anchors written into the notes, so you can lift them directly.

Leadership and People Management

| Question

| Strong answer | Weak answer | |---|---|---|---| | 22 | "Tell me about a time you developed someone on your team." | Names the gap, the coaching, and the change | "I support my team," no specifics | | 23 | "Describe a underperformer you managed." | The conversation and the documented path | Avoids that they addressed it | | 24 | "When did you have to make an unpopular call?" | Owns the decision and the fallout | Softens it into a consensus | | 25 | "Give an example of delegating something you'd rather keep." | Why they let go and what they checked | Delegation framed as dumping | | 26 | "How did you handle a conflict between two reports?" | Their mediation and the outcome | "They sorted it out" | | 27 | "Tell me about a hire you got wrong." | Honest reflection on the signal they missed | Claims they never miss | | 28 | "When did you change a process your team relied on?" | The reason, the rollout, the adoption | A change with no people impact named |

The leadership table works because the strong and weak columns are written down, which is the whole argument of this guide. The same table format carries cleanly into adaptability, where the dodge is almost always a hypothetical dressed as a memory.

Adaptability and Resilience

"Tell me about a major change you didn't agree with but had to implement." Strong: how they got behind it anyway. Weak: still litigating the decision.
"Describe the most ambiguous situation you've worked in." Strong: how they created structure. Weak: waited for direction.
"When did priorities shift on you mid-project?" Strong: the re-plan they ran. Weak: "I'm flexible," no event.
"Give an example of learning a new skill under pressure." Strong: the timeframe and what they could do after. Weak: a generic "I learn fast."
"Tell me about a setback that changed how you work." Strong: a specific habit that changed. Weak: a setback with no lasting lesson.
"When have you worked effectively with very little support?" Strong: what they did without it. Weak: complains about the lack of it.
"Describe adapting your style for a difficult stakeholder." Strong: the specific adjustment. Weak: "I get along with everyone."

Collaboration and Domain Depth

For collaboration (36 to 43) and role-specific depth (44 to 50), keep the same scoring note discipline: strong answers carry a first-person verb and a result, weak ones carry "we" and an adjective.

1. "Tell me about working with a team you'd never met." (Strong: how they built trust fast.)
1. "Describe a time you disagreed with the group and were right." (Strong: how they raised it.)
1. "When did you cover for a struggling teammate?" (Strong: what they did, not just noticed.)
1. "Give an example of cross-functional work that almost failed." (Strong: their specific save.)
1. "Tell me about feedback you gave a peer." (Strong: the words and the result.)
1. "When did you have to rebuild a broken working relationship?" (Strong: the repair move.)
1. "Describe sharing credit on something you mostly did." (Strong: why and how.)
1. "When did you put the team's goal above your own?" (Strong: the concrete tradeoff.)
1. "Walk me through the hardest problem in your domain you've solved." (Strong: depth a generalist couldn't fake.)
1. "What's a common mistake people make in your field?" (Strong: a specific, defended opinion.)
1. "Describe a tradeoff you weigh constantly in this work." (Strong: a real conditional.)
1. "Tell me about staying current in your field." (Strong: a named source and a recent change.)
1. "When did your expertise prevent a costly mistake?" (Strong: the catch and the cost avoided.)
1. "Describe teaching your specialty to someone junior." (Strong: what stuck.)
1. "What's an old best practice in your field you've abandoned?" (Strong: why, with reasoning.)

Every one of these 50 notes does the same job: it turns a vague impression into a number two people can argue about with the evidence in front of them. That argument, run before anyone names a favorite, is what a calibration step protects, and it is the difference between a structured interview and a structured-looking one. For the full process around these questions, see Structured Interviews: The Complete Guide for Hiring Teams.

Your Pre-Interview Scoring Checklist

Run this before your next interview. It takes about ten minutes and keeps the scorecard from becoming an after-hours guess:

Pick three to five competencies tied to the actual role, not a generic list
Attach one or two questions per competency from the banks above
Write the strong-answer and weak-answer sentence for each question
Print the 1 to 5 anchored scale so everyone scores against the same descriptions
Use identical question wording for every candidate
Probe thin answers ("what did you do?") before assigning a number
Write one evidence sentence next to every score
Score in the room, not days later
Hold a short calibration before anyone declares a winner

Frequently Asked Questions

How many structured interview questions should one interview cover?

Cover three to five competencies with one or two questions each, so roughly six to ten questions with room to probe. Asking the same set of every candidate matters far more than asking many. Depth on a few scorable competencies beats shallow coverage of a dozen.

What separates a strong answer from a weak one in scoring?

A strong answer names a specific past event, isolates the candidate's own action with first-person verbs, and reports a result. A weak answer stays general, hides inside "we," or offers a hypothetical instead of something they actually did. The scoring note for each question should spell out both ends before the interview begins.

Do I need a different rubric for every role?

You need different competencies and different strong/weak sentences per role, but the 1 to 5 anchored structure stays the same everywhere. Reuse the scale, rewrite the anchors. That keeps scores comparable inside a role while staying honest about what each role actually requires.

Do This Next

Pick one open role you are hiring for this week. Choose four competencies from the banks above and lift the questions that fit. Write the strong-answer and weak-answer sentence for each, then print the 1 to 5 scale next to your notes. Take your next two candidates through those exact notes, in the room, with one evidence sentence per number. Start today: try Asked free and let the interview agent capture the transcript and draft the scorecard from each answer, so you hire on what they said, not how you felt.