Show credible ownership at available scope, collaboration, technical fundamentals, learning, and honest authority limits.
Loading Engineering Foundry…
Loading Engineering Foundry…
Use descriptive anchors to locate the next question - not to collapse a person or an interview into a score.
Each row stands alone. “Exceptional” is not required; the useful result is a supported observation and a next probe.
| Dimension | Needs evidence | Acceptable | Strong | Exceptional |
|---|---|---|---|---|
| RelevanceThe event answers the evidence target rather than a nearby question. | Does not answer the target | Related event | Direct evidence | Direct evidence with a nuanced boundary |
| OwnershipPersonal decisions are visible without erasing the team. | Team-only ‘we’ | Personal contribution is visible | Decisions and accountability are clear | Creates leverage while crediting others |
| JudgmentThe choice is understandable from evidence available at the time. | Decision is unexplained | Basic reason is present | Alternatives, constraints, and trade-offs are clear | Updates intelligently and anticipates second-order effects |
| Outcome and evidenceThe result is supported and its causal limits are explicit. | Vague success | Honest outcome | Supported impact with a caveat | Multiple evidence types with causal limits |
| SpecificityOne event has enough timeline and action detail to inspect. | Generic claims | One concrete event | Clear timeline and actions | Precise evidence without unnecessary detail |
| Technical understandingTechnical detail explains the decision and failure mode. | Jargon-heavy or absent | Understandable basics | Mechanism and failure are clear | Depth adapts and connects technical and product consequences |
| LearningReflection changed a later behavior, system, or decision. | Generic lesson | Specific reflection | Behavior or system changed | Durable mechanism transferred elsewhere |
| Follow-up depthCanonical facts remain stable under deeper questions. | Facts collapse under a probe | Answers a basic probe | Handles ownership, rationale, and result | Handles counterfactual, risk, scale, and disagreement |
| Level and scopeEvidence is calibrated to available authority, consequence, and leverage. | Below the target evidence | Plausible target scope | Strong target evidence | Broader durable leverage appropriate to context |
| IntegrityClaims stay truthful, attributable, and safe to disclose. | Embellished or confidential | Safe and truthful | Limits and team credit are explicit | Sensitive ambiguity is resolved responsibly |
| CommunicationThe answer is coherent, bounded, and ready for dialogue. | Hard to follow | Coherent | Concise, natural, and probe-ready | Adapts in dialogue without losing facts |
Scope is relative. Bigger organizations and management titles are not proxies for stronger evidence.
Show credible ownership at available scope, collaboration, technical fundamentals, learning, and honest authority limits.
Show end-to-end delivery, independent judgment, trade-offs, incidents, and durable service or team improvements.
Show consequential ambiguity, architecture or risk judgment, cross-team influence, prioritization, mentoring, and durable leverage.
Show organizational framing, multi-team mechanisms, long-term trade-offs, sponsorship, and durable technical direction without requiring a management title.
Translate local titles, scale, and organizational shorthand; language style is not a proxy for competence.
Calibrate scope by ambiguity, consequences, and leverage - not company headcount or brand size.
Show influence, standards, and technical direction without implying that people management is required.