How to Run a Mock Interview That Actually Surfaces Your Blind Spots

What mock interviews are actually for

Mock interviews are not for solving problems. You can solve problems alone in less time and at lower coordination cost. Mock interviews are for the parts of the interview that only manifest under another person's gaze: how you handle being interrupted, how you narrate when you get stuck, how you respond to a hint you did not ask for, what your hands do when you do not know the answer. Those behaviors are invisible in solo practice and decisive in real loops.

Once you understand that mocks are for behavior diagnostics, the protocol changes. You set up the session to maximize observable behavior, not to maximize solved problems. The interviewer (your peer) is not there to evaluate the code — they are there to record what you said, when you stopped talking, and what triggered each visible doubt.

Peer selection: who actually helps and who hurts

The right peer is one level above you and ideally interviews regularly at the kind of company you are targeting. Friends at your own level can spot pattern-matching but rarely catch seniority signals. Friends two levels above tend to grade harshly on the wrong axis (they have forgotten what L4 looks like). The Goldilocks zone is one level above, currently practicing or interviewing.

Whichever route you take, lock in continuity: the same peer for three to five sessions over two weeks. Continuity is what lets feedback compound. A new partner each time has to learn your patterns from scratch and you lose the diff between session two and session four.

The session protocol

1. 1Pick the prompt before the session. Match it to a target company's typical question style — not random LeetCode roulette.
2. 2Schedule for 60 minutes hard-stop: 5 setup, 45 interview, 10 feedback.
3. 3Interviewer takes notes throughout — what you said, where you paused, what they had to remind you to do. No interruptions for note-taking afterward.
4. 4Hold to time. If you do not finish, do not finish. The unfinished interview is itself signal.
5. 5Feedback in writing within 24 hours, structured against the rubric below.

Resist the urge to debrief in the moment. Both of you are in flow and will rationalize what happened. Wait twenty-four hours, write it down, then meet again briefly. Written feedback survives the next session; verbal feedback evaporates.

A simple, honest rubric

Real rubrics at FAANG-tier companies have five to seven dimensions and a 1-4 scale. Your mock-interview rubric should be the same shape, simplified. Borrow the dimensions verbatim from any published rubric (Google's hiring guide, Meta's posted criteria) — that calibration is the point.

Score each dimension independently on the 1-4 scale. The headline output is not the average — it is the lowest score. That is the dimension to drill before the next session.

The post-mortem template

Within a day of the session, both parties fill out the same short template. The candidate fills it out from memory. The interviewer fills it out from notes. Comparing the two versions is the most revealing artifact in the entire mock-interview practice.

# Mock interview post-mortem — 2026-04-19
Problem: <link or title>
Result: completed / partial / not completed

## Rubric scores (1-4)
- Problem comprehension:
- Approach articulation:
- Code quality:
- Communication under pressure:
- Verification:

## Three things that went well
1.
2.
3.

## One thing to change before next session
-

## What I will drill this week (3-5 reps)
-

## Differences between candidate self-eval and interviewer eval
-

Cadence and progression: how to ramp

Two mock interviews per week for four weeks is the right ramp for most candidates. More is rarely better — you outpace your own feedback loop. Progress through difficulty deliberately: weeks one and two on mediums in the patterns you are weakest at; week three at company-specific question styles; week four at full-loop simulation (two technical mocks plus a behavioral mock in one day, scheduled like a real onsite).

1. 1Week 1: weakest patterns, mediums only, no time pressure.
2. 2Week 2: weakest patterns, mediums to hards, 30-minute time-box.
3. 3Week 3: company-style prompts, 45-minute time-box, recorded.
4. 4Week 4: full-loop day with 2 coding + 1 behavioral, debrief same evening.

Warning signs you should fire your mock partner

Not all mock partners are net positive. Some actively hurt your prep by reinforcing weak habits or by miscalibrating your sense of where you stand. The relationships are awkward to end because they tend to be peer relationships, but a wrong partner for three sessions costs you more than the awkward conversation will.

• They give pat 'that looked good' feedback every session. Either you are perfect or they are not paying attention. Both are wrong.
• They give problems they have already memorized so they can give you 'tips' mid-solution. You are practicing being interviewed, not being tutored.
• They run over time and refuse to hold the artificial deadline. Real interviews do not run over. The pressure is the practice.
• They go quiet when you struggle, the way a real interviewer would not. Good mock interviewers ask follow-up questions and provide measured hints when stuck.
• They treat the session as their own prep, narrating their solution while you watch. That is two solo practice sessions sharing a Zoom call, not a mock.

Replacement is not a value judgment. Some peers are excellent collaborators in study groups but bad mock interviewers, and vice versa. Run two or three sessions, evaluate, switch if needed. Continuity matters but not so much that you should stay with a partner who is not surfacing useful signal.

Finally, treat your mocks the way you would treat real interviews. Dress for them, sit at a desk, close other tabs, do them at the time of day your real interview is scheduled. The state-dependent muscle memory is real — practicing in pajamas with snacks and then performing in a video call wearing a button-down at nine in the morning is a context shift that costs you a half-level of perceived performance. Match the conditions and you will hit the ground at the right pace on the day.