Frontend Beauty
ESC

Type to search the knowledge base.

Mock Interview Self Review

A scoring rubric to review frontend mocks — communication, correctness, structure — so each practice loop actually levels you up.

beginner4 min read
  • interview
  • mock-interview

Mocks without review are reps without progressive overload. The goal is not “feel prepared” — it is measurable improvement on the signals real interviewers write down.

How to run a useful mock

  1. Timebox like the real round (45–60m)
  2. Record audio or video (with partner consent)
  3. No notes except blank scratch
  4. Interruptions allowed — real interviewers redirect
  5. Debrief immediately with this rubric

Partner sources: peers, paid platforms, or self-record against a prompt bank.

Rubric (score 1–5 each)

A. Communication

Score Meaning
1 Long silences; no structure
3 Some narration; occasional freezes
5 Clear signposts; checkpoints; invites feedback

B. Problem solving

Score Meaning
1 Jumps in; wrong problem
3 Clarifies late; partial plan
5 Clarifies early; examples; plan before code

C. Correctness

Score Meaning
1 Broken happy path
3 Happy path OK; edges fail
5 Edges + tests traced

D. Code quality

Score Meaning
1 Unreadable; side effects everywhere
3 Works; messy structure
5 Clean modules; good names

E. Web / FE specifics

Score Meaning
1 Ignores a11y, async errors, perf
3 Mentions one production concern
5 a11y + abort/error + complexity/perf as relevant

F. Collaboration

Score Meaning
1 Argues; ignores hints
3 Accepts hints late
5 Uses hints well; thinks aloud with interviewer

Total /30. Track weekly averages.

Round-type weights

Round type Emphasize
DSA / JS util B, C, complexity
Machine coding A, D, E (a11y)
System design A, B, tradeoffs, phases
Behavioral STAR clarity, ownership
Debug Hypothesis quality

Frameworks: Machine coding · System design FE · Behavioral stories.

Self-review questions (write answers)

  1. Where did I go silent >45s? Why?
  2. First clarifying question — good or missing?
  3. Did I state complexity / MVP scope?
  4. What single skill would raise this score next time?
  5. Would I hire me for this round? Why not?

Feedback collection from partners

Ask for behavior examples, not vibes:

  • “Timestamp where you got lost.”
  • “One thing to start / stop / continue.”
  • “Hire / lean hire / no hire and why.”

Improvement loop (weekly)

Mock → score rubric → pick ONE bottleneck
→ drills 3–4 days → remock same type
Bottleneck Drill
Silence Narrate while solving easy problems only
Edges Force write 4 cases before code
React state mess Rebuild todo focusing state only
Algo gaps Pattern family from JS coding patterns
Design sprawl 20-minute outline-only designs

Recording review technique

Playback at 1.25×. Note:

  • Filler words density
  • Time to first clarifying question
  • Time to first working output
  • Whether you asked “does this match?”

Anti-patterns in review

  • Only reviewing when you “felt bad”
  • Changing 10 things at once
  • Skipping hard round types
  • Partners who never push back
  • Comparing yourself to YouTube speedrunners

Scorecard template (copy)

Date:
Round type:
Prompt:
A Comm:  /5
B Solve: /5
C Correct: /5
D Code: /5
E FE: /5
F Collab: /5
Total: /30
One fix for next mock:

Further reading

Improvement is a closed loop. If the score doesn’t move in two weeks, change the drill — not just the volume.