Skip to content

Mock interview rubric

60-minute format

  • 5 minutes: clarify the change and constraints.
  • 25 minutes: implement a vertical slice.
  • 10 minutes: debug a seeded failure.
  • 15 minutes: extend the design for production.
  • 5 minutes: summarize tradeoffs and next evidence.

Score each 1–4

Dimension Evidence
Runtime reasoning Predicts render, state, and effect behavior accurately
Implementation Produces typed, coherent, incremental changes
Testing Verifies user-visible behavior and failure paths
Accessibility Uses semantics, names, focus, and keyboard interaction
Architecture Places ownership and trust boundaries deliberately
Communication States assumptions, alternatives, and uncertainty clearly

A passing performance has no critical correctness, accessibility, or security gap hidden by polished terminology.