Interview Question Bank: 100 Structured Questions Ready to Use
Interview Question Bank: 100 Structured Questions Ready to Use
Search "interview question bank" and the results compete on volume: 200 questions, 500 questions, the biggest list wins. That instinct is backwards. A question bank carries what I'll call a bloat tax: every question you add without retiring one quietly widens the gap between what you intended to ask and what forty interviewers actually ask. The bank below gives you 100 structured questions, organized by competency so you can pull a tight set per role. But the questions are the cheap part. A bank is only useful when it's paired with a scoring key and a single owner, and the bloat tax is what eats it alive when those two things are missing.
Here's the frame the big-list articles skip: the value of a question bank comes from subtraction, not addition. You win by pulling six right questions for a role and scoring them the same way every time, not by handing interviewers a buffet of 100 and hoping they self-organize. This guide is for the person who owns hiring quality across teams, not a manager filling one seat. For the wider case on why structure beats instinct, see Behavioral Interview Questions: A Guide for Interviewers (Not Candidates).
The Bank Is a Liability Until Someone Owns It
A question bank turns from asset to liability the moment no single person owns it, because the bloat tax compounds with every unowned edit. A hiring manager pastes in a question they like. A recruiter softens one that felt awkward on a call. A new interviewer copies last quarter's deck and inherits a fork nobody approved. Within two quarters your "bank" is nine slightly different banks, and the consistency you built it for is gone.
That drift is exactly what the selection research warns against. The Canadian Psychological Association fact sheet on structured hiring, written by Drs. Thomas O'Neill and Derek Chapman at the University of Calgary with Dr. Blake Jelley and revised by Dr. Nicolas Roulin, states the standard plainly: "All interviewers administer the same set of questions in a standardized order to each interviewee." A bank with no owner cannot meet that bar, because there is no one to hold the same set as the set. The owner is the load-bearing fix, and the owner is the first thing most banks lack.
At Asked, we work from the recorded transcript side of this problem. When a question bank lives in an open doc, the questions interviewers actually speak on the calls start drifting from the written bank inside a few weeks, and the people-ops lead has no way to catch the bloat tax accruing until a debrief falls apart. The owner needs a place to govern from, and the bank needs structure before anyone can govern it.
The 100-Question Bank, Organized by Competency
A 100-question bank is safe only when it's partitioned by competency, because that partition is what lets an owner hand each role a tight subset instead of the whole list. Pull four to six competencies per role, one to two questions each, and the bloat tax never lands. For a smaller, ready-made set already grouped this way, see our 40 STAR Interview Questions for Interviewers (Organized by Competency). Here are 100 structured, behavioral prompts across ten competencies most teams hire against. Treat them as raw material to draw from, never as a single interview to run end to end.
Problem-solving (1-10): Tell me about the hardest problem you solved last year. Walk me through a decision you made with incomplete data. Describe a time your first solution failed and what you tried next. When did you change your mind after seeing new evidence? Tell me about a problem others called unsolvable. Describe a time you simplified something overcomplicated. When did you have to choose between two bad options? Walk me through how you debugged something unfamiliar. Tell me about a tradeoff you made and regretted. Describe a problem you caught before anyone else noticed.
Ownership (11-20): Tell me about something you shipped end to end. Describe a time you fixed a problem that wasn't yours. When did you take the blame for a team miss? Walk me through a commitment you kept under pressure. Tell me about a project you championed against resistance. Describe a time you said no to scope creep. When did you escalate a risk early? Tell me about a deadline you owned and missed. Describe how you handled a dropped handoff. When did you go past your formal role?
Collaboration (21-30): Tell me about a conflict with a teammate and how it resolved. Describe working with someone whose style clashed with yours. When did you change a peer's mind without authority? Walk me through giving hard feedback. Tell me about a time you were wrong in a group decision. Describe supporting a struggling colleague. When did cross-team work break down on you? Tell me about a compromise you didn't like but accepted. Describe building trust with a skeptical stakeholder. When did you defuse a tense meeting?
Communication (31-40): Tell me about explaining something technical to a non-expert. Describe a time your message landed wrong. When did you have to deliver bad news? Walk me through how you handled a misunderstanding. Tell me about persuading a senior leader. Describe writing something that drove a decision. When did you have to listen more than talk? Tell me about presenting under hostile questions. Describe simplifying a complex update. When did silence serve you better than speaking?
Leadership (41-50): Tell me about developing someone who outgrew the role. Describe a decision your team disagreed with. When did you hold the line on quality? Walk me through delegating something hard to let go. Tell me about a culture problem you fixed. Describe motivating a team after a setback. When did you remove a barrier for your team? Tell me about a hire you got wrong. Describe setting a goal that stretched the team. When did you lead without the title?
Adaptability (51-60): Tell me about a priority that shifted under you. Describe learning a new skill fast. When did a plan fall apart mid-execution? Walk me through joining a project late. Tell me about adjusting to a new manager's style. Describe a time ambiguity stalled you. When did you abandon sunk cost? Tell me about a reorg you navigated. Describe handling a tool change you disliked. When did you thrive in chaos?
Initiative (61-70): Tell me about something you started without being asked. Describe spotting an opportunity others missed. When did you automate a manual task? Walk me through a side project that paid off. Tell me about pushing past a "that's not possible." Describe improving a broken process. When did you ask for more responsibility? Tell me about a risk you took that worked. Describe a time you prototyped to prove a point. When did you act before permission?
Resilience (71-80): Tell me about your biggest professional failure. Describe recovering from public criticism. When did you keep going after repeated setbacks? Walk me through a stressful stretch and how you held up. Tell me about a goal you missed and revisited. Describe handling rejection of your idea. When did burnout creep in and what did you do? Tell me about staying calm in a crisis. Describe a comeback after a bad quarter. When did persistence backfire?
Customer focus (81-90): Tell me about a hard customer you turned around. Describe a time you said no to a customer. When did you advocate for the user internally? Walk me through handling an angry escalation. Tell me about a feature you killed for users' sake. Describe learning something surprising from a customer. When did you trade speed for quality? Tell me about a promise you couldn't keep. Describe measuring whether you actually helped. When did the data contradict customer requests?
Integrity (91-100): Tell me about a time you reported a mistake. Describe a shortcut you refused to take. When did you disagree with leadership on principle? Walk me through handling confidential information. Tell me about admitting you didn't know. Describe a conflict of interest you flagged. When did you correct credit that went to the wrong person? Tell me about holding a peer accountable. Describe a rule you followed at a cost. When did honesty hurt short term?
Raw List Versus Governed Bank
The difference between a question dump and a usable bank is governance, not question count, and the comparison below is the build target for everything that follows.
| Dimension | Raw question list | Governed question bank |
|---|---|---|
| Size | As many as possible | Tight subset pulled per role |
| Owner | Whoever edited last | One named people-ops owner |
| Scoring | None, or per interviewer | Behavioral anchors per question |
| Versioning | Edits overwrite silently | Dated versions, change log |
| Consistency | Drifts into forks | Same set, same order, every candidate |
| Bloat tax | Compounds unchecked | Capped by retire-one rule |
Every section under this one populates the right column: who owns the bank, how each question gets scored, and how you keep the bloat tax from creeping back. Consistency is a property of the system, not of any single question.
Build and Govern the Bank in Five Steps
Build the governed bank in five sequential steps, and run them in order, because each step caps the bloat tax the next one would otherwise reintroduce.
- Partition the bank by competency. Group the 100 questions above (and your own) under named competencies, exactly as the ten headers do, so an owner can pull a role-specific subset instead of the whole list.
- Pull four to six competencies per role. From a short job analysis, name the criteria that actually predict success in this specific job, then take one to two questions each. The Uniform Guidelines treat a step causing adverse impact as unlawful unless job-relatedness is established, and that job analysis is your defense.
- Attach a scoring key to each pulled question. OPM guidance holds that rating scales should be anchored by clear, verifiable, and behaviorally based descriptions of what each response option means. Write a 1-5 anchor per question before it ships.
- Name one owner and a version number. A single people-ops owner stamps the bank v1.0 and holds edit rights. Everyone else proposes; the owner approves or rejects.
- Enforce the retire-one rule. No question enters the live bank unless a stale or redundant one leaves. This is the only mechanic that caps the bloat tax over time.
Step three depends on step two, because a scoring key with no job analysis behind it anchors interviewers to the wrong behavior, which is where rating-scale design earns its keep.
Score Each Question or the Bank Is Decoration
A question bank predicts nothing without a scoring key, because an unscored question lets every interviewer rate the answer on a private, shifting scale. OPM finds that interviews with higher degrees of structure show higher validity, rater reliability, rater agreement, and less adverse impact, and the rating scale is the lever that delivers it. Schmidt and Hunter's 1998 meta-analysis put structured interviews at 0.51 validity against 0.38 for unstructured; Sackett and colleagues re-estimated the gap in 2022 at 0.42 versus 0.19, a wider spread. None of that validity transfers to a bank whose questions arrive without anchors.
Behavioral anchors are what make a score repeatable across interviewers. "Strong communicator" is not a scoring key; it's a Rorschach test. A real anchor reads like a transcript: a 1 is "had to re-ask the question twice to get a usable answer," a 5 is "concise and structured on the first pass." For a worked example of anchoring a score component by component, see How to Score STAR Method Answers: A Rubric for Interviewers. We saw this qualitatively in the scorecards Asked drafts from live transcripts: when each question carries written anchors, two interviewers scoring the same recorded answer land within a point far more often than they do against a bare 1-5. Before any question ships into the bank, run it through this gate:
- The question maps to exactly one competency in your bank.
- It carries written behavioral anchors at 1, 3, and 5, not just numbers.
- The anchors describe what the candidate said or did, not how the interviewer felt.
- A weak and a strong candidate would answer it visibly differently.
- Two interviewers piloting it scored a sample answer within one point.
- Adding it triggered the retire-one rule on a stale question.
A question that fails any line goes back to the owner, not into the live bank.
Frequently Asked Questions
How many questions should an interview question bank hold?
The bank can hold 100 or more as raw material, but any single interview should draw only six to ten, covering four to six competencies. The constraint is the scoring key: every question pulled needs behavioral anchors and pilot evidence, and you cannot maintain that quality if interviewers run twenty questions per call. Size the bank generously, size the interview tightly.
Can one question bank serve every team?
The governance model serves every team; the pulled subsets should not be identical. Competencies are role-specific, so an engineering pull and a sales pull will differ, but both follow the same rules: one owner, versioned questions, behavioral anchors, the same set in the same order for every candidate. Standardize the system, not one universal list.
How do I stop the bank from getting bloated?
Run the retire-one rule and a quarterly review. Each new question forces a stale one out, and every quarter the owner re-checks each question against the job analysis and cuts the ones that stopped separating strong candidates from weak. The cadence matters more than the calendar date; the point is that one named person owns the cut.
Do This Next
Pick one role you are actively hiring for and pull six questions from the bank above across four competencies. Build a 1-5 behavioral anchor for each before anyone runs an interview. Choose one owner in people-ops and stamp the set v1.0 so no one forks it silently. Set the retire-one rule now, while the bank is small enough to govern. Take your next three candidates and score them against the same six questions independently, then compare notes in the debrief to see whether the anchors held. Start today: try Asked free and let it draft the scorecard straight from the call transcript so the bank you built is the bank that actually gets asked.