Mock Interview Complete Guide — Structure, Timing, and Analysis Framework

Why Mock Interviews Matter

Solving problems alone is necessary but not sufficient. Interviews test communication, time management, and adaptive problem-solving under pressure — skills only practice interviews can build.

The 5-Week Mock Schedule

2-Hour Session Structure

0:00 — 0:05   Warm-up: pick 1 easy problem, solve mentally
0:05 — 0:55   Problem 1 (50 min)
  ├─ 0:05 Clarify constraints + examples (5 min)
  ├─ 0:10 State brute force approach (5 min)
  ├─ 0:20 Derive optimal approach (10 min)
  ├─ 0:40 Code solution (20 min)
  └─ 0:55 Test + trace through edge cases (15 min)
0:55 — 1:45   Problem 2 (50 min, same structure)
1:45 — 2:00   Review + self-assessment

The UMPIRE Framework

Use this for every problem:

• Understand — restate the problem, ask clarifying questions
• Match — identify the pattern (sliding window? DP? BFS?)
• Plan — write pseudocode / outline approach
• Implement — code cleanly with good variable names
• Review — trace through with test cases
• Evaluate — state time and space complexity

Simulating Real Conditions

1. No IDE autocompletion — use plain text editor or paper
2. Timer visible — keep the clock on screen
3. Talk out loud — narrate every thought
4. No pausing — if stuck, say "I'm thinking about X..." rather than going silent
5. Record yourself — review to catch filler words and silence gaps

Self-Assessment Rubric

Score yourself 1-5 on each dimension after every mock:

Target: average 4+ by week 5.

Tracking Progress

Keep a log for each session:

Date: ___
Problem 1: ___ (Easy/Med/Hard) — Solved? Y/N — Time: ___
Problem 2: ___ (Easy/Med/Hard) — Solved? Y/N — Time: ___
Scores: Understanding__ Approach__ Code__ Comm__ Edge__ Complexity__
Key weakness this session: ___
One thing to fix next time: ___