Why Mock Interviews Matter More Than Books
Reading the green book and grinding LeetCode are necessary but not sufficient. The candidates who actually do well in quant interviews are the ones who have practised the performance - thinking out loud under time pressure, managing nerves, recovering when stuck, and getting comfortable with the rhythm of being challenged on every answer.
Most candidates massively under-invest in mocks. The typical pattern is 100+ hours of solo study and 0 hours of mock practice. The asymmetry is wrong: mocks compound faster than solo study at the late stage of preparation. This guide covers how to run effective mocks, what to score yourself on, and how to find practice partners.
For the broader prep plan, see our quant finance interview prep guide 2026.
What a Good Mock Interview Looks Like
Setup
- Camera on, in interview clothes. The actual interview will be on Zoom or in person; practice in the same conditions.
- Phone away. Quiet room. No notes visible. Mocks lose value the moment you introduce affordances you won't have on the real day.
- Time-boxed. 45 minutes is the standard length. Use a hard timer.
Structure
- 5 minutes: Quick "tell me about yourself" + one behavioural question.
- 30 minutes: Three to four technical questions, mixed across types (probability, brain teaser, coding for engineers, market intuition for traders).
- 5 minutes: "Do you have questions for me?" - practise answering this seriously.
- 5 minutes: Debrief.
The interviewer's job
- Ask each question and don't help unless asked.
- Push back on every answer ("Are you sure?" "What if...?").
- Take notes on: time to start, clarity of explanation, willingness to ask clarifying questions, recovery from being stuck.
- After the mock, give specific feedback (see scoring rubric below).
Scoring Rubric
Score each technical question on five dimensions, each 1-5:
1. Time to start (1 = took 2+ min to engage; 5 = started talking through it within 15 sec)
Why it matters: Real interviewers see 8-12 candidates per day. A candidate who spends 90 seconds in silence before starting feels lost; one who immediately begins thinking out loud feels confident.
2. Clarity of explanation (1 = mumbled, no structure; 5 = clear, well-paced, easy to follow)
Why it matters: Interviewers can only score what they can follow. Brilliant work explained badly often loses to mediocre work explained well.
3. Asking clarifying questions (1 = made wrong assumptions silently; 5 = explicitly stated assumptions and verified)
Why it matters: The strongest candidates ask 1-2 specific clarifying questions before diving in. The weakest assume.
4. Recovery (1 = froze when stuck; 5 = articulated where stuck and proposed alternative paths)
Why it matters: Everyone gets stuck. The differentiator is whether you say "let me try a different angle" or just stop talking.
5. Engagement with pushback (1 = capitulated immediately or got defensive; 5 = took the pushback seriously and either updated or defended with new evidence)
Why it matters: Interviewers test pushback specifically to see how you handle it. Both extremes are bad.
Common Feedback Patterns
After running mocks for hundreds of candidates, certain patterns repeat:
"You went silent for too long"
The most common feedback. When stuck, even saying "I'm thinking about whether to use a recursion or a closed form" is better than silence.
"You should have asked about edge cases"
Particularly for coding questions. Before writing code, ask: "Should I assume the input is sorted? Can it be empty? Can the values be negative?" Even if the answer is "use your judgement," asking demonstrates you're thinking carefully.
"You jumped to an answer without showing your work"
Especially for probability questions. Even if the answer is right, the interviewer can't tell whether you reasoned through it or guessed. Always narrate the steps.
"You didn't explore your own solution"
After getting an answer, the strongest candidates extend it: "What's the complexity? What if the input was 100x larger? What's a corner case?" The weakest stop talking once they've answered.
"You disagreed without evidence"
When the interviewer pushes back, "I'm pretty sure I'm right" doesn't work. "I'm fairly confident but let me double-check by re-doing the calculation" does.
Finding Practice Partners
Where to find them
University quant societies and finance clubs. Most top universities have one. They organise mock interviews internally; some bring in alumni from target firms.
Discord and Slack communities. Several private Discord servers (look for invite-only quant prep groups via LinkedIn) have organised mock interview swaps.
LinkedIn outreach. Message current employees at target firms asking for a 30-minute mock. Hit rate is low (5-10%) but the conversation is invaluable when you connect.
University career centre. Most career services run mock interviews. The interviewer often isn't a quant but the structure is still useful.
Paid services. Sites like Pramp (free) and Interviewing.io (paid) connect you with experienced interviewers. Pramp is reciprocal (you interview them too); Interviewing.io is one-directional.
How to ask for a mock
When asking another candidate or alumni for a mock, follow the script:
"I'm preparing for [firm/role] and I'd value 30-45 minutes of your time for a mock interview. I'm comfortable being challenged hard. In exchange, I can [reciprocate / send you a thank-you note / etc.]. Could we schedule for sometime in the next two weeks?"
Most people say yes if you're specific about the ask and brief.
Using Quantt Coding Tests as Structured Practice
The Quantt coding tests are designed to mimic the format of actual firm interviews. They're particularly useful for:
- Trader-track candidates: Quick mental math drills under timer.
- Developer-track candidates: Algorithmic problems specific to trading scenarios (order books, risk computation, signal processing).
- Researcher-track candidates: Statistical and ML problems on financial data.
Use them as structured solo practice between mock sessions. Time yourself, score yourself against the rubric above, and identify recurring weaknesses.
Mock Schedule for the Final Two Weeks
In the final two weeks before your real interview, aim for:
- 3 mocks per week (so 6 in the final fortnight)
- At least 1 with someone from the target firm (or as close to it as possible)
- At least 1 in front of a recording device (watch yourself back)
- A recurring slot (e.g., Tuesday and Friday afternoons) - habit beats heroic single sessions
After each mock:
- Score yourself on the 5-dimension rubric.
- Write down 3 specific things to improve for the next mock.
- Add any genuinely difficult questions to your "weakness sheet" and practise solving them again 24 hours later.
What NOT to Do in Mocks
Don't only practise your strengths. If you're a strong probability student, you'll naturally want to spend mocks on probability questions because you do well. Resist this. Spend the most mock time on your weakest area.
Don't skip the soft parts. Many candidates skip the "tell me about yourself" and "do you have questions" portions of the mock. These are scored on the real interview - practise them.
Don't over-prepare scripted answers. Memorising responses sounds rehearsed. Have themes you want to hit but speak naturally.
Don't argue with feedback. When your mock interviewer gives you feedback you disagree with, listen carefully. Even if they're wrong, the feedback is data about how your performance landed for at least one observer.
Don't do mocks while exhausted. A bad mock when you're tired teaches you the wrong lessons (you blame fatigue for problems that are actually skill gaps).
After the Real Interview
When the real interview is done, do a debrief immediately while it's fresh. Note:
- Which questions came up
- Which you handled well and which you struggled with
- Specific things the interviewer reacted to (positive or negative)
- Anything new you learned about the firm
This becomes invaluable data both for follow-up interviews at the same firm and for interviews at peer firms. The same questions appear across firms more often than candidates expect.
For specific question banks to drill, see:
Practise the questions Quant Mock Interview Guide: How to Practice Like the Real Thing actually asks
Reading about the interview is one thing - sitting one is another. Quantt's interactive coding tests are modelled on the same problem types that show up in firms like Jane Street, Citadel, Hudson River and Optiver. Run real Python in the browser, get instant feedback, and benchmark yourself against the bar.
Free to start - no credit card required