Behavioral questions
Use real episodes with clear ownership. STAR can organize a story, but the reasoning between the action and result matters most. Apply the separate factual support checks in evaluation. All anchors are editorial.
B01 — Tell me about an accomplishment that matters to you
Variants: What are you proud of? Describe a project where you made a difference.
Intent: Understand contribution, relevant impact, and the candidate's values.
Strong answer target: Explain the starting problem and why it mattered, identify your responsibility, and describe the key decisions and actions. Connect the result to an observable change for customers, colleagues, or the business. Name collaborators and limitations. A durable improvement can be more instructive than one dramatic launch.
Profile inputs/adaptation: Episode, scope, contribution, outcome evidence, and target capability. IC: implementation or technical influence. EM: conditions that enabled team delivery and growth. Executive: organizational mechanism and business effect, with shared ownership. Small scope can still supply strong evidence.
Acceptable alternatives: Preventing a problem, improving maintainability, developing someone, or stopping wasteful work can be accomplishments. Exact metrics are optional when unavailable; identify the observation instead.
Probes: What would have happened without your contribution? What remained imperfect? How did the improvement continue after you stepped back?
Failure modes: Team success presented as sole authorship, unexplained numbers, or a story about activity without an effect.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Contribution | Cannot identify personal decisions or actions | Names decisive contributions and credits others |
| Relevant effect | Lists work without explaining why it mattered | Connects the work to an observable useful change |
| Judgment | Presents success as self-evident | Explains a consequential choice and the result's limits |
Provenance: Practice extrapolation; U01 informs sustainable success. The accomplishment prompt and anchors are ours.
B02 — Tell me about a failure or a decision you regret
Variants: When did you miss a commitment? What would you do differently?
Intent: Examine accountability, reasoning, and changed practice.
Strong answer target: Choose a meaningful episode, define the expectation, and state what did not work. Identify your contribution without taking blame for everything. Explain what was knowable at the time, what you missed, how you responded, and what you changed afterward. Distinguish a poor decision from a reasonable decision with a bad outcome.
Profile inputs/adaptation: User-selected episode, contemporary constraints, personal decision, consequences, repair, and later practice. Manager/executive: include effects on others and the operating change. IC: describe detection, technical reasoning, and coordination within actual authority.
Acceptable alternatives: A small but consequential failure is valid. The candidate can defend part of the original reasoning while recognizing a real limitation. Not every failure has a neat redemption.
Probes: Which signal did you overlook? What would you repeat? What evidence shows that your later approach changed?
Failure modes: Fake failure ending in triumph, blaming others exclusively, or hindsight certainty that ignores information available at the time.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Responsibility | Avoids any identifiable personal contribution | Owns a bounded contribution and its consequences |
| Decision analysis | Gives only an outcome or hindsight slogan | Distinguishes available information, choice, and uncertainty |
| Changed practice | “I learned a lot” without a change | Describes a specific repair or later behavior and its limits |
Provenance: Practice extrapolation from L10; no requirement that every unsuccessful outcome imply incompetence.
B03 — Describe a disagreement with a colleague
Variants: How did you handle conflicting technical views? Tell me about friction.
Intent: Understand collaboration under real differences.
Strong answer target: Explain the substantive disagreement and the other person's goals fairly. Describe how you checked assumptions, surfaced tradeoffs, and reached or supported a decision. State your authority and how the working relationship and outcome developed. “I convinced them” is not sufficient.
Profile inputs/adaptation: Episode, competing goals, decision process, communication, and result. IC: technical options and adoption. EM: process and power dynamics. Executive: peer priorities and enterprise consequences. A manager should explain how they avoided silencing people with formal authority.
Acceptable alternatives: You can change your mind, compromise, escalate a decision appropriately, or support a decision you still disagree with. Agreement is not mandatory; unresolved disagreement can be described honestly.
Probes: What was reasonable in their position? Who had decision authority? What would they say about your handling of it?
Failure modes: Caricaturing the colleague, winning through rank, avoiding the issue indefinitely, or confusing respect with unconditional agreement.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Understanding | Cannot represent the other position fairly | Explains differing goals or evidence without caricature |
| Decision process | Relies solely on force, avoidance, or persuasion | Uses relevant evidence, tradeoffs, and clear decision authority |
| Collaboration | Ignores effects on people or follow-through | Describes respectful handling and what happened afterward |
Provenance: Practice extrapolation from H03 and R03.
B04 — Tell me about difficult feedback you received
Variants: How have you responded to criticism? What surprised you in a review?
Intent: Understand how the candidate examines feedback and acts on it.
Strong answer target: State the feedback as a behavior and effect, describe how you clarified it, and explain what you accepted, questioned, or tested. Show a concrete response and how you observed its effect. You need not pretend that criticism felt easy or that every criticism was accurate.
Profile inputs/adaptation: User-selected feedback, context, reflection, action, and follow-up. IC: work habits or collaboration. EM: impact of management behavior. Executive: how peers or team members could safely challenge you. Do not imply psychological traits from the response.
Acceptable alternatives: Respectfully rejecting unsupported feedback after investigation can be sound. If formal reviews were absent, use a colleague's comment or a retrospective. Personal or discriminatory criticism need not be treated as a valid development instruction.
Probes: What did you ask to understand it? What would the giver observe now?
Failure modes: Defensiveness without examination, automatic agreement with no action, or a changed behavior unrelated to the feedback.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Understanding | Cannot explain the actual concern | Identifies the behavior, effect, and relevant context |
| Examination | Dismisses or accepts without considering evidence | Clarifies and evaluates the feedback fairly |
| Response | Supplies no action or reasoned conclusion | Describes a relevant change/test or justified disagreement |
Provenance: Practice extrapolation from H01; receiving-feedback criteria are our adaptation of the author's feedback practice.
B05 — Tell me about working through ambiguity
Variants: How did you start when the problem was unclear? Describe an uncertain decision.
Intent: Examine diagnosis and progress with incomplete information.
Strong answer target: Distinguish what was known, assumed, and missing. Explain how you found the highest-value information, involved relevant people, and chose a bounded next step. Identify the risk of acting and of waiting, plus how the approach would change as evidence arrived.
Profile inputs/adaptation: Unclear problem, constraints, information sought, decision, and results. IC: technical or product uncertainty. EM: team and delivery uncertainty. Executive: business and organizational diagnosis. Scale the story to actual authority instead of making every ambiguity “strategy.”
Acceptable alternatives: A reversible experiment, immediate action on a known urgent risk, or pausing for critical information can all be appropriate. Hypothetical answers are permitted when labeled as such.
Probes: Which assumption could invalidate the approach? What did you choose not to investigate? What would trigger a change?
Failure modes: Imported solution before diagnosis, indefinite research, or confusing decisiveness with unsupported certainty.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Diagnosis | Assumptions and observed facts are indistinguishable | Names the uncertainty and the evidence needed |
| Bounded progress | No next step or unjustified irreversible commitment | Chooses a proportionate action given urgency and risk |
| Adaptation | No way to notice the approach is wrong | States a useful check or revision trigger |
Provenance: Practice extrapolation from L07, extended from strategy diagnosis to other role scopes.
B06 — Tell me about competing priorities or saying no
Variants: How do you handle too much work? When did you push back on a deadline?
Intent: Understand prioritization, explicit tradeoffs, and communication.
Strong answer target: Explain the competing obligations and constraints. Show the decision rule, what you delayed, reduced, delegated, or declined, and how affected people learned about it. Describe the consequence and any reconsideration. Do not present habitual overtime as the prioritization method.
Profile inputs/adaptation: Demand, capacity, decision authority, options, stakeholders, and result. IC: negotiate scope with owners. EM: protect team capacity while making delivery tradeoffs visible. Executive: allocate resources and align peers on opportunity costs. Delegation must account for others' capacity.
Acceptable alternatives: A bounded exceptional push can be sensible if risks, recovery, and consent are considered. Deferring a high-value item may be necessary. An unpopular refusal can be justified without being confrontational.
Probes: What stopped getting done? Who disagreed? When would you revisit it?
Failure modes: “Everything was a priority,” silent missed commitments, passing overload to someone else, or constant rescue work.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Tradeoff | Cannot name what was deprioritized | Explains a clear choice and its opportunity cost |
| Capacity | Ignores resource limits or merely transfers overload | Uses realistic capacity and proportionate options |
| Communication | Leaves dependents expecting impossible delivery | Communicates consequences and a revision path |
Provenance: Practice extrapolation from H04 and R05.
B07 — How have you influenced people without authority?
Variants: Describe cross-functional alignment. How did you get another team to help?
Intent: Understand collaboration beyond formal control.
Strong answer target: Name the problem, the other groups' priorities, and why participation would matter to them. Show how you built a shared understanding, clarified a decision, and made the work feasible. Explain what you changed in response to others. Adoption and follow-through matter more than one presentation.
Profile inputs/adaptation: Episode, stakeholders, incentives, approach, and observable adoption. IC: technical proposals or cross-team delivery. EM: dependencies and support. Executive: peers with legitimate competing objectives. Keep formal mandate separate from voluntary agreement.
Acceptable alternatives: Adjusting the proposal, running a small pilot, finding a willing partner, or using appropriate decision escalation can work. Not every party needs to be enthusiastic for a clear agreement to be effective.
Probes: What did others gain or give up? What changed because of their input? How did you know agreement became action?
Failure modes: Manipulation, title-dropping, claiming influence because a document was sent, or ignoring the other team's costs.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Shared understanding | Treats others as obstacles with no valid needs | Identifies relevant priorities and constraints |
| Influence mechanism | Describes only pressure or generic persuasion | Shows a concrete path to a workable decision |
| Adoption | Equates announcement with success | Provides follow-through evidence and bounded contribution |
Provenance: Practice extrapolation from H03; the influence rubric is ours.
B08 — Tell me about changing your mind
Variants: When did evidence overturn your view? When did you stop a project?
Intent: Examine learning and revising a position responsibly.
Strong answer target: Explain the original belief and why it was reasonable, the information that challenged it, and how you tested its importance. Describe the revised choice, communication, and consequences. State remaining uncertainty. Updating a plan is not automatically an admission that the original decision was poor.
Profile inputs/adaptation: Original decision, new evidence, decision authority, revision, and effect. IC: design or implementation. EM: process or team approach. Executive: investment or strategy. Explain costs of reversal for people who depended on the original plan.
Acceptable alternatives: A partial update, a decision to stop learning expensively, or maintaining a view after serious examination can be discussed; the last option needs a different example if the interviewer specifically asks for an actual change.
Probes: What made the evidence persuasive? What would change your view again?
Failure modes: Change for fashion or authority alone, denying the earlier view, or claiming flexibility without naming a revised decision.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Initial reasoning | Original view has no understandable basis | Explains why the prior choice made sense then |
| Evidence update | Changes without examining relevant information | Shows how evidence altered a key belief or constraint |
| Responsible revision | Ignores costs and dependents | Describes implementation, communication, and remaining limits |
Provenance: Practice extrapolation from L08.
B09 — Describe handling a crisis or sustained pressure
Variants: What did you do when delivery was in trouble? How did you respond to an incident?
Intent: Examine risk management, coordination, and sustainable recovery.
Strong answer target: Name the immediate risk, your role, and the initial priorities. Explain how work, decisions, and communication were coordinated. Distinguish immediate mitigation from later diagnosis. Describe recovery and what changed so the same problem was less likely or easier to handle.
Profile inputs/adaptation: Incident or overload episode, authority, choices, stakeholders, and follow-up. IC: safe mitigation and technical communication. EM: roles, workload, and team support. Executive: business decisions, resources, and peer coordination. Do not imply expertise from a crisis the candidate only observed.
Acceptable alternatives: Seeking help, handing leadership to a better-suited person, or stopping unsafe work can be strong actions. Visible stress or a calm voice does not determine quality. Not every emergency could have been prevented.
Probes: What did you deliberately avoid doing? How did you know recovery was real? Who needed support afterward?
Failure modes: Hero story with no coordination, unsafe shortcuts, blaming tired people, or leaving recurring overload untreated.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Risk response | Cannot explain the immediate priority | Takes proportionate action based on actual risk |
| Coordination | Relies only on personal effort | Establishes useful roles, help, and communication |
| Recovery | Treats exhaustion or temporary mitigation as completion | Describes recovery checks and a relevant follow-up change |
Provenance: Editorial crisis application of R05, whose topic is leadership overload rather than incident-response procedure. The technical incident criteria are our synthesis.
B10 — When have you pushed back on a leader's decision?
Variants: What if you disagree with your manager? Describe raising an important concern.
Intent: Understand independent judgment, constructive challenge, and limits.
Strong answer target: Explain the concern and its evidence, the leader's constraints as you understood them, and how you raised options and consequences. Describe decision authority and what happened next. Distinguish an ordinary preference disagreement from a safety, integrity, or policy concern that needs different handling. “Disagree and commit” is not a universal answer.
Profile inputs/adaptation: Real episode or explicitly hypothetical scenario, facts, authority, communication, and outcome. IC: raise technical/product risk. EM: protect delivery and people. Executive: challenge peer or CEO decisions with business consequences. Do not prescribe jurisdiction-specific legal processes.
Acceptable alternatives: Privately challenging then supporting a legitimate decision, escalating a serious concern, or declining an action can be defensible. Use proportionate channels and acknowledge retaliation risks without inventing them.
Probes: What alternative did you offer? What would have made further escalation necessary? Which part was within your authority?
Failure modes: Uncritical obedience, theatrical confrontation, or invoking ethics to dismiss a reasonable disagreement without examining facts.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Grounded concern | Pushback has no relevant reason or evidence | States a material concern and examines its context |
| Constructive action | Offers only compliance or opposition | Communicates options through proportionate channels |
| Judgment of limits | Treats all disagreements identically | Distinguishes decision authority from serious constraints |
Provenance: Editorial synthesis, informed by the inspection principle in L10; this is not an author-supplied ethical interview rubric.
B11 — What makes a decision a good decision?
Variants: How do you evaluate decision quality? Can a good decision have a bad outcome? Can a successful decision still have been bad? When is waiting a good decision?
Intent: Reveal the candidate's explicit criteria for judgment before asking for a success or failure story.
Strong answer target: Define quality relative to the purpose, legitimate constraints, plausible alternatives, and information available when deciding. Explain why the chosen option was preferable, what was uncertain, what was given up, and why the amount of investigation and timing suited the stakes. Show how the decision becomes usable action with accountable ownership and a way to learn or revise. Distinguish the quality of reasoning from the eventual outcome: luck can reward weak reasoning or defeat a sound choice. Outcomes still test assumptions; do not use uncertainty to excuse repeated errors or ignore new evidence. Demonstrate the definition with a bounded example or counterexample. There is no requirement to attach a large checklist to every small decision.
Profile inputs/adaptation: One actual decision, its purpose, authority, available evidence, alternatives, assumptions, consequences, and later learning. An IC can discuss a local choice. A manager can discuss team commitments or development. An executive should account for business and system consequences within actual responsibility; greater seniority does not mean more ceremonial process. A hypothetical counterexample is valid if clearly labeled.
Acceptable alternatives: Speed, expert intuition, deliberate delay, or a small experiment can each be sound when the candidate explains their basis and limits. A deliberately accepted downside need not invalidate the choice. Useful delegation can improve judgment when authority, support, and accountability are clear; avoiding responsibility is different.
Probes: Give a good decision that ended badly and explain why. What could have made a successful decision unsound? What information would have changed your choice? What did you stop investigating, and why? How would you know that you were rationalizing after the result?
Failure modes: “It worked, so it was good”; consensus or confidence as proof; no plausible alternative; indefinite analysis; hindsight reconstruction; reasoning so general that it cannot reject a choice; or a polished process used to excuse harm, ignored constraints, or failure to learn.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Decision criterion | Defines goodness only by outcome or preference | Gives purpose- and context-specific criteria that can distinguish defensible and unsound choices |
| Reasoning under uncertainty | Hides alternatives, costs, or unknowns behind confidence | Explains a material tradeoff, available evidence, uncertainty, and proportionate timing |
| Evaluation and learning | Rewrites history or dismisses all outcome evidence | Separates prior reasoning from results and identifies meaningful action, learning, or revision conditions |
Provenance: Practice extrapolation from L10, which separates process, decisions, and outcomes, and R07, which explores rationale, context, and avoidance. Criteria and anchors are our synthesis; neither author provides this question's validated grading scheme.