EXECUTION & JUDGMENT
Technical Competency
Practical product-technology judgment, not coding ability: architecture, scalability, technical debt, and build-versus-buy tradeoffs, tied to customer and business outcomes.
← All 16 dimensions in the competency frameworkWhat strong evidence looks like
- A specific technical tradeoff (build vs. buy, debt vs. velocity) made with engineering
- The business or customer consequence of that tradeoff
- Evidence of genuine engineering partnership, not just deference
What weak evidence looks like
- General technical vocabulary with no real tradeoff decision attached
- No example of a build-versus-buy or debt-versus-velocity call actually made
A real follow-up question
“What technical debt did you knowingly accept, and what did that cost you later?”
Questions like this follow directly from what you just said, not from a fixed script -- they exist to find out whether an answer holds up, not to check a box.
Related dimensions in Execution & Judgment
See where you actually stand on this
A self-assessment only goes so far. The adaptive interview tests exactly this kind of evidence, in your own words, with follow-up questions built to find out whether it holds up.