Quant Interview Practice Schedule
How to build a weekly quant interview practice schedule that balances diagnostics, focused drills, timed sets, and review.
Candidates who need a repeatable weekly structure for quant interview prep.
Start from the weakest bucket
A schedule should start from evidence, not preference. Use a diagnostic or a recent mock to rank your buckets - sample-space setup, counting, conditioning, expected value, market making, mental math, statistics, coding, explanation - and give the weakest one the first focused block of the week, when your attention is highest. The ranking matters more than the score: you need to know which two buckets to attack, not what percentage you got.
Use four block types
Four block types do four different jobs. A focused repair block fixes one method and should stay on that one method for the whole session. A mixed block tests recognition, which is the skill the interview actually measures, and it only works if you do not know in advance which method each question needs. A timed block tests whether the methods survive pressure. A review block converts misses into the next assignment. Skipping review is the most common way to make a schedule look productive while preserving every error inside it.
Concrete weekly schedule
A five-session week: Monday, 30 minutes reviewing last week's error log and picking two repair targets; Tuesday, 60 minutes of focused repair on target one; Wednesday, 60 minutes on target two; Friday, a 45-minute timed mixed set of ten to twelve questions at roughly three minutes each; Sunday, a 60-minute mock or market making game plus 15 minutes of review. Cut to three sessions by keeping one repair block, one mixed block, and one review block - and drop the timed work first, because untimed accuracy has to exist before there is anything worth timing.
Balance timed and untimed work
Untimed work is where methods are learned; timed work is where they are tested. Candidates routinely reverse this and run timed set after timed set without repairing the cause of the misses, which trains fast execution of a broken model. Add pressure gradually: only time a method once you have got it right untimed three times running, then start at a generous limit and tighten it over a few sessions.
Track the right metrics
Track miss type, recovery quality, arithmetic error rate, and whether you needed a hint. Problems attempted is weak signal, because that number rises fastest when you practice what you already know. The more honest metric is the retest gap: schedule every repaired method for a cold retest three to seven days later and record whether it survived. A method that passes immediately after its repair block and fails a week later was never actually fixed.
Common mistakes
The main mistake is making every week identical - if your error log changes and your schedule does not, the schedule is decoration. The second is avoiding weak topics because they feel slow, when the schedule should spend the most time where improvement is cheapest, which is almost never where practice feels best. The third is scheduling by topic name rather than by method, which is how a candidate runs four "probability" sessions and repairs nothing.
Practice the pattern
Use the LeetQuidity curriculum and calibration to turn this topic into a focused practice plan.