Timed engineering rehearsal¶
Use this optional mock after applied course work. It measures communication and decision-making under time pressure; it does not replace capstone or spaced-retrieval evidence.
60-minute format¶
| Time | Activity |
|---|---|
| 5 min | background and clarify requirements |
| 15 min | fundamentals and reactivity questions |
| 20 min | coding/debugging exercise |
| 15 min | architecture scenario and tradeoffs |
| 5 min | candidate questions and recap |
Scoring (1–5)¶
Correctness¶
1 guesses and cannot validate; 3 reaches working core behavior; 5 identifies invariants, edge cases, and validates efficiently.
Angular mental model¶
1 recites syntax; 3 explains common component/signal/DI/router behavior; 5 predicts lifecycle, scope, rendering, and async consequences precisely.
Problem solving¶
1 makes random edits; 3 forms hypotheses and uses evidence; 5 chooses high-information experiments and adds regression protection.
Design judgment¶
1 over/under-engineers without rationale; 3 chooses reasonable boundaries; 5 compares alternatives against explicit constraints and migration cost.
Communication¶
1 narrates every keystroke or goes silent; 3 explains plan and tradeoffs; 5 is concise, invites clarification, corrects assumptions, and distinguishes fact from uncertainty.
Quality and inclusion¶
1 ignores testing/accessibility/security; 3 covers major paths; 5 integrates failure states, accessible interaction, security boundaries, and production observability.
Feedback template¶
Strongest evidence:
-
Highest-leverage gap:
-
One exercise to repeat:
-
Question to revisit:
-
Next mock constraint:
-
Do not collapse the rubric into one unexplained number. Cite observed behavior. Repeat a mock after targeted practice with a changed scenario, not the memorized same answers.