How a knowledge gap was found, tested, corrected, and transferred.
HOW TO ASK · HOW TO ANSWER · HOW TO CHOOSE
Questioning framework
The library is a set of prompts, not model answers. This page explains the reasoning behind those prompts and gives both sides a practical way to prepare a useful conversation.
THE CORE VIEWPOINT
Compare, challenge, execute, and verify
The same reasoning applies to technical, product, operations, hiring, and promotion questions. The evidence changes with the role; the inquiry stays contextual.
- 01
Set the comparison
Compare with internal history, a similar case, an industry or competitor reference, an alternative approach, and doing nothing. State what is and is not comparable.
- 02
Choose a challenging goal
Describe the baseline, intended change, constraints, and why the target is difficult. Keep stop and direction-change conditions visible.
- 03
Generate more than one route
Compare plausible solutions—including technical implementations—by correctness, quality, cost, risk, reversibility, and fit to context. Do not force a fixed number of options.
- 04
Reconstruct real contribution
Separate role and authority from team context. Ask what the person decided, implemented, tested, negotiated, delegated, or changed in practice.
- 05
Test causality and outcome
Use a suitable metric and time window, check counter-signals and other causes, then explain what can reasonably be attributed.
- 06
Find and express the highlight
Show why the contribution exceeded the relevant role expectation, what evidence supports it, what limits the claim, and what learning transferred.
Four lenses for sustained growth
How useful work was initiated and advanced while adapting or stopping when evidence changed.
How the problem was decomposed, modeled, compared, and the judgment updated.
How the person recovered from setbacks, sought support, and changed the next attempt.
HOW A QUESTION CARD IS BUILT
From a real question to bounded evidence
Each card is designed to help someone ask, clarify, and reason. Its inference is a hypothesis to check, not a conclusion about a person.
- 01Objective problem
What real uncertainty does the question help resolve?
- 02Assessment intent
Which job-related capability is in focus?
- 03Possible inference
What hypothesis might the answer suggest, and what else could explain it?
- 04Signals and context
What evidence or follow-up would clarify the story?
- 05Decision and trade-offs
Given the context, what choices and consequences matter?
- 06Evidence anchors
How does this response compare with the question-specific 1–4 references?
INTERVIEWER
Use questions to gather comparable evidence
A strong interview is planned around role requirements. Follow-ups clarify the same evidence dimensions without forcing identical stories.
- 01
Anchor to the role
Choose a capability that matters for this work and ask everyone a comparable, job-related lead question.
- 02
Reconstruct one real event
Clarify the situation, the candidate’s responsibility, constraints, options, and the decision they personally made.
- 03
Probe cause and alternatives
Ask what evidence supported the explanation, what else could have caused the result, and what changed after the action.
- 04
Compare positive and difficult cases
Use both a strong outcome and a setback to understand repeatable judgment, learning, and recovery. A contradiction is a cue to clarify context, not proof of dishonesty.
- 05
Record evidence before inference
Separate observed actions and outcomes from interpretations. Apply the same role-specific anchors to each candidate and note uncertainty.
Interview answers are evidence with limits. Gaps may reflect memory, access, role boundaries, or a poorly framed question. Clarify before drawing conclusions; do not infer intent or character from one response.
CANDIDATE · ANSWERING
Turn an experience into a traceable causal story
STAR is a useful memory aid, but a strong answer also makes choices, evidence, attribution, and learning visible.
- 01Context
What was happening, who was affected, and what constraints mattered?
- 02Responsibility
What outcome were you accountable for? What was yours versus the team’s?
- 03Choices and action
What options did you consider, what did you decide, and why?
- 04Result and evidence
What changed? How do you know, and what other factors contributed?
- 05Learning and transfer
What would you repeat or change? Where have you used that learning since?
Do not force every story into a perfect success narrative. Name constraints, missed assumptions, team contributions, and what changed in your later work.
CANDIDATE · TWO-WAY CHOICE
Use reverse questions for mutual due diligence
Choose a few questions whose answers could change your decision. Ask for examples and compare the answer with what you heard from other interviewers.
Clarify the work
What outcomes, users, or problems will occupy this role in the first months? What work is common, and what is unusually difficult?
Clarify conditions
Which decisions can this role make? What dependencies, resources, on-call duties, or trade-offs shape delivery?
Clarify the environment
How are disagreements resolved? What would cause the team to change direction? Can you share a recent example?
Clarify support and success
How are expectations calibrated, feedback given, and progress reviewed? What support accompanies the responsibility?
For a promotion conversation
- What responsibility changes at the target stage, and which parts must already be sustained?
- Which outcomes and behaviors count as evidence, over what period, and how is personal contribution distinguished from team context?
- If evidence is not yet sufficient, what specific work would close the gap, who will support it, and when will it be reviewed?
These prompts clarify expectations, evidence, and organizational commitments. They are not scored against the candidate rubric.
Further reading
These sources support structured, job-related assessment practices; they do not validate this site’s question bank or scoring anchors.