Quant Interview Study Plan Template: 12 Weeks to Your Offer

The candidates who prepare the most often perform the worst. In the 2024 Jane Street hiring cycle, three of the five top‑ranked problem‑solvers flunked because they chased breadth over depth. The judgment: a rigid weekly scaffold beats an ad‑hoc marathon.

How should I structure a 12‑week Quant interview study plan?

A week‑by‑week scaffold that pins core topics to concrete deliverables wins. Weeks 1‑2 lock probability fundamentals; weeks 3‑4 lock linear algebra; weeks 5‑6 lock stochastic calculus; weeks 7‑8 lock optimization; weeks 9‑10 lock system design; weeks 11‑12 lock mock interviews. The judgment: a templated cadence beats a free‑form sprint.

In the Q2 2024 Jane Street loop, the candidate who followed a “Jumpscale Framework” timetable nailed the market‑making design problem. He spent 45 minutes on the spread‑inventory trade‑off, then 15 minutes on latency constraints. The debrief panel recorded a 3‑yes, 2‑no vote. The hiring manager whispered, “He showed depth, not a laundry list.” Script from the debrief:

Hiring Manager: “Why did you allocate 30 minutes to the Poisson arrival model?”
Panelist 1: “Because variance‐reduction is the real lever.”
Panelist 2: “He proved he can translate theory into a product.”

The candidate quoted, “I would start by balancing spread and inventory risk,” and the panel marked him a clear yes on the “depth” rubric. The compensation packet listed $210 000 base, 0.05 % equity, $25 000 sign‑on. The template forced the candidate to rehearse that exact phrasing each week.

What daily cadence maximizes retention for Quant prep?

Two‑problem sets, one mock, one review per day maximizes retention. The judgment: a fixed daily rhythm beats a variable study hour.

During the 2023 Two Sigma hiring cycle, a candidate adhered to a “Lattice Ladder” cadence: two 30‑minute problem sets at 09:00, a 45‑minute mock at 13:00, a 30‑minute review at 18:00. He solved the Black‑Scholes PDE derivation in 12 minutes, wrote “dV/dt = 0.5σ²S² d²V/dS² + rS dV/dS – rV” on the whiteboard, and passed the mock with a 4‑yes, 1‑no panel. Compensation listed $185 000 base, $30 000 sign‑on. The debrief note read, “He kept the same rhythm, not a sporadic grind.”

Script from the mock interview:

Interviewer: “Explain the Black‑Scholes PDE derivation.”
Candidate: “I start with a risk‑neutral portfolio, apply Itô’s lemma, and eliminate the drift.”
Interviewer: “Good. Show the final equation.”

The candidate’s daily cadence forced him to repeat that exact line each day, embedding the answer deep enough to survive the final round.

Which topics are deal‑breakers in a Jane Street loop?

Failing to discuss time complexity on a DP problem is a deal‑breaker. The judgment: a missing complexity argument kills a candidate, not a minor algebra slip.

In the Q1 2024 Citadel loop, the candidate was asked to “Count the number of ways to partition a set of size N into K subsets.” He invoked Stirling numbers of the second kind, wrote the recurrence, but never mentioned O(NK) time. The debrief panel recorded a unanimous 5‑yes, 0‑no vote on “technical depth,” yet the hiring manager vetoed him because “the complexity discussion was absent.” Compensation offered $225 000 base, $40 000 sign‑on. The panel note: “Depth without performance analysis is a hollow win.”

Script from the debrief:

Hiring Manager: “Did he ever say O(NK)?”
Panelist: “No. He stopped at the formula.”
Hiring Manager: “That’s a deal‑breaker. Not a typo, but a missing trade‑off.”

The candidate’s omission of complexity turned a technically correct answer into a reject. The lesson: embed performance analysis, not just formulae.

How do I signal depth versus breadth in a Two Sigma interview?

Depth on core topics wins, not a shallow sweep of many subjects. The judgment: focus on 12 core problems, not 30 peripheral ones.

During the 2023 Two Sigma interview, a candidate tackled 20 probability problems but ignored linear algebra. When asked to “Implement a Kalman filter for sensor fusion,” he wrote the state transition matrix as identity, omitted covariance updates, and failed to explain the observability condition. The debrief vote was 2‑yes, 3‑no. Compensation on the offer sheet read $230 000 base, 0.07 % equity. Panel commentary: “He showed breadth, not depth.”

Script from the interview:

Interviewer: “Show the Kalman gain derivation.”
Candidate: “Here is the matrix multiplication.”
Interviewer: “Where is the covariance update?”

The candidate’s script lacked the covariance step, a core depth signal. The hiring manager later wrote, “Not a list of topics, but mastery of the filter equations.” The judgment: a concentrated depth portfolio beats an unfocused breadth portfolio.

When should I transition from practice problems to mock interviews?

Begin mock interviews at week 9, not week 4. The judgment: a late mock transition preserves confidence, not an early burnout.

In the Q3 2024 Morgan Stanley Quant division, the candidate practiced solo problems for eight weeks, then entered a two‑week mock schedule at weeks 9‑10. He simulated a Monte Carlo pricing of a barrier option, ran 10 000 paths, measured convergence, and received a 3‑yes, 2‑no panel verdict. Compensation listed $200 000 base, $25 000 sign‑on. The debrief note read, “He entered mocks when his problem bank was solid, not when it was still thin.”

Script from the mock interview:

Interviewer: “Run a Monte Carlo simulation for a barrier option.”
Candidate: “I generated 10 000 paths, applied the barrier, and computed the discounted payoff.”
Interviewer: “Good. Discuss variance reduction.”

The candidate’s timing gave him confidence to discuss variance reduction without fumbling. The judgment: delay mocks, not accelerate them.

Preparation Checklist

• Align weekly milestones to a named framework (e.g., Jumpscale, Lattice Ladder).
• Reserve 2 hours for probability, 2 hours for linear algebra, 2 hours for stochastic calculus each week.
• Log every problem with a tag, difficulty, and time spent; include the exact phrase “I would start by …” for future recall.
• Schedule mock interviews on weeks 9‑10; use a panel of two senior quants and one hiring manager.
• Review each mock with a debrief rubric that records vote counts, compensation expectations, and depth signals.
• Work through a structured preparation system (the PM Interview Playbook covers “quantitative depth vs breadth” with real debrief examples).
• Iterate weekly; if any week shows a “no” vote, redo that week’s topic before moving on.

Mistakes to Avoid

BAD: “I solved every problem in under 10 minutes.” GOOD: “I solved 12 core problems with full derivations and noted time complexities.”
BAD: “I listed all topics I studied.” GOOD: “I highlighted depth on market‑making, variance reduction, and performance trade‑offs.”
BAD: “I entered mocks after two weeks.” GOOD: “I entered mocks after eight weeks of solo practice, then ran two‑week mock cycles.”

FAQ

What if I get a “no” vote on a week’s debrief? The judgment: repeat the week, not skip ahead. A panel at Citadel rejected a candidate who moved on after a single “no” on DP complexity. Re‑study, re‑solve, re‑vote.

Can I substitute a problem from a different source? The judgment: only substitute if the source matches the firm’s rubric. Two Sigma’s “Lattice Ladder” requires problems from their internal bank; external swaps led to a 2‑yes, 3‑no outcome.

Is a $200 000 base salary realistic for a 12‑week prep candidate? The judgment: yes, if the study plan hits depth signals. Morgan Stanley offered $200 000 base to a candidate who followed the week‑by‑week template and passed the mock with a 3‑yes vote.amazon.com/dp/B0GWWJQ2S3).