Curated roadmap for quant finance interviews (Quant Trader, Quant Researcher, Quant Analyst): probability, mental math, brainteasers, coding & high-signal resources.
๐ Awesome Quant Interview Prep
Welcome! ๐ This repository is a curated guide to preparing for quantitative finance interviews across Quant Trader, Quant Researcher, and Quant Analyst roles.
Itโs designed for:
- ๐ students and new graduates
- ๐ career switchers
- ๐ผ early and experienced professionals moving into quant
This repo focuses on signal over noise:
- what to study
- how interviews differ by role
- which resources are actually worth your time
- how to prepare in a structured way
๐ Table of Contents
- ๐ Start Here
- ๐ง Quant Roles Explained
- ๐ฆ Types of Firms
- ๐ What to Study
- ๐ Best Resources
- ๐บ๏ธ Suggested Preparation Roadmap
- ๐ Study Plans
- ๐ Resume, Projects & Strategy
- ๐ฏ What Interviews Actually Look Like
- โ ๏ธ Common Mistakes
- โ FAQ
- ๐งช Practice Platforms
- ๐ค Contributing
- โญ Final Advice
๐ Start Here
If you are a beginner
- Learn basic probability & expected value
- Start solving simple brainteasers
- Practice mental math daily (10โ15 min)
- Use structured resources (see below)
If you target Quant Trading roles
- Focus on:
- Practice under time pressure
If you target Quant Research roles
- Focus on:
- Build small projects
๐ If you target Quant Analyst / Strat roles
- Focus on:
If you are short on time (2โ4 weeks)
- Do:
๐ง Quant Roles Explained
| Role | What You Do | What Is Tested | |------|------------|----------------| | Quant Trader | Make trading decisions in real-time | Mental math, probability, decision-making | | Quant Researcher | Build models & strategies | Stats, ML, coding, probability | | Quant Analyst / Strat | Data + finance modeling | Python, SQL, probability, finance basics |
A lot of candidates prepare too generically. A future quant trader should not prepare exactly like a future quant researcher.
๐ฆ Types of Firms
| Firm Type | Interview Style | |----------|----------------| | Prop Trading (Jane Street, Optiver, IMC) | Fast-paced, mental math heavy, games | | Hedge Funds (Citadel, Two Sigma) | More modeling, coding, deeper probability | | Banks | Slower pace, more finance + general quant |
Interview prep should be aligned with the type of firm you are targeting.
For example:
- prop trading usually rewards speed + clarity
- hedge funds often reward depth + technical strength
- banks are often broader and slightly less specialized in style
๐ What to study
Not all topics are equally important โ and more importantly, they are tested very differently in quant interviews.
The goal is not just to โknowโ these topics, but to understand how they are used in practice.
- ๐ฒ Probability (expected value, conditional probability)
- ๐ Statistics (distributions, variance, estimation)
- โก Mental Math (speed & accuracy)
- ๐ป Programming (Python / C++ / LeetCode-style)
- ๐ง Brainteasers & logic problems
- ๐ Markets basics (for trading roles)
๐ฒ Probability (most important)
This is the core of most quant interviews, especially for trading roles.
What matters:
- Expected value (EV)
- Conditional probability
- Basic distributions
- Symmetry and simplification
- Logical modeling of situations
How it shows up in interviews:
- Games (dice, cards, coins)
- Decision-making under uncertainty
- โWhat would you do?โ scenarios
- Estimation of outcomes
What is actually tested:
๐ Your ability to model a problem clearly and reason step-by-step, not memorization of formulas.How to train effectively:
- Focus on understanding structure, not formulas
- Re-solve problems until the reasoning becomes intuitive
- Practice explaining your thought process out loud
โก Mental Math (critical for trading roles)
Mental math is often a filtering stage in trading interviews. If you struggle here, you may not reach later rounds.
What matters:
- Speed + accuracy
- Comfort with fractions, decimals, percentages
- Quick expected value calculations
How it shows up:
- Timed arithmetic tests (e.g. โ80 questions in 8 minutesโ)
- Fast calculations during probability problems
- Real-time decision-making tasks
What is actually tested:
๐ Your ability to stay accurate under time pressureHow to train effectively:
- Practice daily (10โ15 minutes)
- Track speed and accuracy over time
- Focus on consistency, not just peak performance
๐ Statistics (more important for research roles)
Statistics becomes more important for Quant Research / Analyst roles.
What matters:
- Distributions and moments
- Estimation and inference
- Regression basics
- Variance and bias
How it shows up:
- Interpreting data
- Explaining models
- Reasoning about uncertainty in datasets
What is actually tested:
๐ Your ability to reason about data and uncertainty, not just recall definitions.How to train effectively:
- Focus on intuition behind concepts
- Work through applied examples
- Be able to explain ideas simply
๐ป Programming (role-dependent importance)
Programming is critical for some roles, less relevant for others.
What matters:
- Data structures and algorithms (for coding rounds)
- Writing clean, correct code
- Problem-solving under constraints
How it shows up:
- LeetCode-style questions
- Data manipulation tasks
- Simple modeling or simulation problems
What is actually tested:
๐ Your ability to solve problems clearly and efficiently in codeHow to train effectively:
- Focus on core patterns (arrays, hash maps, graphs, etc.)
- Practice writing code without over-relying on libraries
- Prioritize understanding over volume
๐ง Brainteasers & Logic
These are used to test thinking process, not just answers.
What matters:
- Breaking down complex problems
- Making reasonable assumptions
- Structuring your reasoning
How it shows up:
- Open-ended puzzles
- Estimation problems
- โThink out loudโ questions
What is actually tested:
๐ Your ability to reason clearly under uncertaintyHow to train effectively:
- Practice explaining your reasoning step-by-step
- Focus on structure, not clever tricks
- Learn to simplify problems
๐ Markets & Finance Basics (for trading roles)
Not always heavily tested, but useful context.
What matters:
- Basic market mechanics (bid/ask, market making)
- Risk vs reward thinking
- Expected value in trading contexts
How it shows up:
- Simple market scenarios
- Decision-making questions
- Discussions about strategies
What is actually tested:
๐ Your intuition and reasoning, not deep finance knowledgeHow to train effectively:
- Focus on intuition rather than theory
- Understand simple trading scenarios
- Connect probability to real-world decisions
๐ง Key takeaway
These topics are not tested independently.
Strong candidates are able to:
- combine them
- apply them under time pressure
- explain their reasoning clearly
๐ Best Resources
Most candidates donโt lack resources: they lack a strategy for using them.
The goal is not to use as many resources as possible, but to use a small number of high-quality ones in the right way.
๐ Books
Xinfeng Zhou โ A Practical Guide to Quantitative Finance Interviews (โGreen Bookโ)
โญ One of the highest ROI resources
Best for: probability + brainteasers
How to use it effectively:
- Do selected problems, not necessarily cover-to-cover
- Focus on understanding the reasoning deeply
- Re-do problems multiple times until they become intuitive
- โ Treating it as a textbook to read passively
- โ Rushing through problems without mastering them
Mark Joshi โ Quant Job Interview Questions (โRed Bookโ)
Broader coverage across quant topics Good complementary practice after the Green Book
How to use it:
- Use as a second layer for additional exposure
- Donโt rely on it as your main resource
๐ฒ Probability & Core Prep
Jane Street โ Probability & Markets Guide
๐ https://www.janestreet.com/probability-markets/One of the most relevant resources for interview-style thinking
Why itโs valuable:
- Reflects how top firms think about problems
- Focuses on reasoning rather than formulas
- Go through it early in your prep
- Make sure you understand why each solution works
Jerry Qin
๐ https://jerryqin.com/High-quality probability-style questions
How to use it:
- Great for deepening intuition
- Use after basic foundations are in place
Brainstellar
๐ https://brainstellar.comStructured problem bank
How to use it:
- Good for building volume and consistency
- Useful once you want more repetition
QuantBrainteasers
๐ https://quantbrainteasers.comStructured practice across probability, brainteasers, and role-specific prep
How to use it:
- Use for organized, role-specific practice
- Especially useful if you want a more guided workflow
โก Mental Math
Zetamac
๐ https://arithmetic.zetamac.comOne of the simplest and most effective tools
How to use it:
- Practice daily (10โ15 minutes)
- Track your score over time
- Focus on consistency, not just peak performance
TradingInterview / TraderMaths
๐ https://www.tradinginterview.com ๐ https://www.tradermaths.com/math-testsGood additional sources for realistic drills
๐ป Programming
LeetCode
๐ https://leetcode.comBest general-purpose coding platform
When it matters:
- Critical for Quant Research / Dev roles
- Less relevant for pure trading roles
- Focus on core patterns, not volume
- Prioritize:
Common mistake:
- โ Doing random problems without pattern recognition
- โ Over-indexing on LeetCode for roles where itโs not central
๐ง Brainteasers & Puzzles
Project Euler
๐ https://projecteuler.net/A collection of challenging but structured problems combining math, logic, and programming
Why itโs useful:
- Develops problem-solving intuition and structured thinking
- Many problems rely on clever insights rather than brute force
- Great training for breaking down unfamiliar problems
- Not interview-style questions, but excellent for building core thinking skills
- Can become technical/programming-heavy if overused
- Use selectively to sharpen reasoning and creativity
- Donโt treat it as your main interview prep source
Other sources
- Jerry Qin
- Brainstellar
- QuantBrainteasers
๐ง Key principle
The goal is not to use everything.
A strong setup is often:
- 1โ2 core probability resources
- 1 mental math tool (daily)
- 1 structured problem source
- coding practice if needed
๐บ๏ธ Suggested Preparation Roadmap
The order in which you prepare matters a lot.
Many candidates follow a scattered approach (random problems, mixed topics, no structure), which leads to slow progress and gaps that show up during interviews.
A more effective approach is to build skills progressively, in a way that matches how interviews actually work.
- Learn probability fundamentals
- Start solving problems daily
- Add mental math practice
- Add coding (if needed)
- Practice under time pressure
- Review mistakes deeply
- Repeat
Step-by-step structure
Build probability fundamentals
Start with expected value, conditional probability, and basic distributions.
Goal:
- understand how to model simple situations
- reason step-by-step
- focus on clarity, not speed
Solve structured problem sets
Move to curated question sets (not random problems).
Goal:
- build intuition
- recognize patterns
- understand common problem types
- quality > quantity
Introduce daily mental math
Start early and stay consistent.
Goal:
- improve speed and accuracy
- get comfortable with calculations under pressure
- 10โ15 minutes daily is enough if done consistently
Add coding preparation (if relevant)
Mainly for Quant Research / Dev roles.
Goal:
- master core patterns
- write clean, correct code
- focus on understanding patterns, not solving hundreds of random problems
Introduce time pressure
This is where preparation becomes realistic.
Goal:
- simulate interview conditions
- identify weak points
- problems that feel easy untimed often become difficult when timed
Review mistakes deeply
This is one of the highest ROI steps.
Goal:
- turn weaknesses into strengths
- make reasoning automatic
- re-solve problems until you can do them quickly and confidently
Simulate interview conditions
Final stage of preparation.
Goal:
- think clearly under pressure
- communicate your reasoning effectively
- explain your thinking out loud
- simulate real interview scenarios
โ ๏ธ Common wrong approach
Many candidates do something like:
- jump between topics
- solve random problems
- delay mental math
- avoid timed practice
- focus too much on reading instead of solving
- slow progress
- inconsistent performance
- difficulty under interview conditions
๐ง Key takeaway
Preparation should be:
- structured
- role-specific
- practice-heavy
- progressively timed
๐ Study Plans
A good study plan is not about doing everything: itโs about focusing on the highest ROI activities in the right order.
Below are realistic plans depending on your timeline.
๐ฅ 4-Week Crash Plan (High Intensity)
This is for:
- upcoming interviews
- tight deadlines
- candidates who already have basic foundations
Week 1 โ Foundations + Structure
Focus:
- probability fundamentals (expected value, conditional probability)
- core problem types
- start daily mental math
- work through key sections of the Green Book
- solve 10โ20 structured problems per day
- start mental math (10โ15 min daily)
- understanding > speed
Week 2 โ Pattern Recognition
Focus:
- common interview problem types
- building intuition
- continue Green Book / structured resources
- start mixing sources (e.g. QuantBrainteasers, Brainstellar, Jerry Qin)
- begin light timed practice
- aim for noticeable speed improvement
Week 3 โ Pressure + Integration
Focus:
- solving under time constraints
- combining skills
- timed sets (important)
- mixed problem sessions (probability + brainteasers + math)
- introduce mock-style practice
- start coding practice on LeetCode
Week 4 โ Interview Simulation
Focus:
- performance under pressure
- communication
- full mock interviews
- simulate real conditions (timing, stress, explanation)
- review mistakes deeply
- keep daily practice (non-negotiable)
๐ 8-Week Plan (Most Effective for Most People)
This is the optimal balance for most candidates.
Goal: ๐ build strong fundamentals + reach interview-level performance
Weeks 1โ2 โ Foundations
Focus:
- probability basics
- expected value
- simple brainteasers
- structured learning (Green Book, guides)
- untimed problem solving
- start mental math daily
Weeks 3โ5 โ Structured Practice
Focus:
- problem solving
- pattern recognition
- increasing difficulty
- solve curated problems daily
- mix multiple sources (e.g. QuantBrainteasers, Brainstellar)
- start light timed sessions
- coding practice on LeetCode
Weeks 6โ7 โ Pressure Phase
Focus:
- speed
- consistency
- handling uncertainty
- timed problem sets
- mock interviews
- identify weak areas
- this is where most candidates struggle
Week 8 โ Refinement
Focus:
- polishing performance
- fixing weaknesses
- revisit weak topics
- redo difficult problems
- simulate full interview sessions
โก Quant Trader Focus (Specialization Layer)
If targeting trading roles, prioritize:
- daily mental math (non-negotiable)
- expected value & probability intuition
- fast decision-making
- timed drills
๐ Quant Research Focus (Specialization Layer)
If targeting research roles, prioritize:
- probability + statistics depth
- Python + data analysis
- modeling and experimentation
- coding
โ ๏ธ Common mistakes in study plans
- trying to cover too many topics at once
- delaying mental math practice
- avoiding timed practice until too late
- focusing on reading instead of solving
- not reviewing mistakes
๐ง Key takeaway
A strong study plan should:
- evolve from understanding โ practice โ speed โ simulation
- be consistent rather than intense and irregular
- match your target role
๐ Resume, Projects & Strategy
Your resume is not a formality. ๐ It is the filter that decides whether you even get an interview.
Most candidates fail here without realizing it.
๐ง What firms are actually looking for
Recruiters and hiring managers scan your resume in ~10โ20 seconds.
They are looking for signals of:
- analytical ability
- problem-solving
- technical skills
- evidence of excellence
- long descriptions
- generic responsibilities
- buzzwords
๐ The 3 strongest signals (in order)
1. ๐ Proof of excellence
This is the most powerful signal.
Examples:
- math / programming competitions
- strong academic performance
- selective programs
- scholarships
2. ๐งช Projects with real substance
Not:
- โimplemented X modelโ
- โanalyzed datasetโ
- clear problem
- clear method
- measurable outcome
Example (strong โ ): Developed a mean-reversion strategy on equities using Python, achieving a Sharpe ratio of 1.4 over a 5-year backtest
3. ๐ป Technical skills that are actually usable
Relevant signals:
- Python (NumPy, pandas, data analysis)
- C++ (for low-latency / dev roles)
- SQL
- machine learning (if applied, not theoretical)
โ ๏ธ What most candidates do wrong
- โ list responsibilities instead of outcomes
- โ include projects they donโt fully understand
- โ add too many weak or irrelevant items
- โ write vague bullet points with no numbers
- โ treat resume as a formality
๐งฑ How to structure your resume
Keep it 1 page maximum.
Recommended structure:
- Education
- Experience / Projects
- Skills
- (Optional) Awards / Competitions
โ๏ธ How to write strong bullet points
Use this structure:
๐ Action verb + method + result
Example:
- Built a Monte Carlo simulation in Python to price options under stochastic volatility models
- Analyzed 1M+ data points to identify inefficiencies in FX markets, improving signal accuracy by 20%
๐ง Golden rule
๐ If you cannot explain a line in depth, remove it.
In interviews:
- they will pick random lines
- they will go deep
- they will test your understanding
๐ Projects that actually help
Good project types:
- backtesting trading strategies
- probability simulations
- data-driven research projects
- Kaggle competitions
- building tools (even small ones)
- 1 strong project you deeply understand
- 5 shallow projects
๐งช Interview strategy (very important)
Getting the interview is step 1.
Passing it requires:
1. ๐ฃ๏ธ Clear thinking
- explain your reasoning step by step
- donโt jump to conclusions
- structure your thoughts
2. โ๏ธ Balance speed vs accuracy
- trading roles โ speed matters
- research roles โ depth matters
3. โ Asking good questions
Shows:
- curiosity
- understanding
- maturity
๐ค Networking (realistic view)
Networking helps, but:
๐ it will not compensate for weak preparation
Useful actions:
- reach out to people in target roles
- ask specific, thoughtful questions
- understand interview processes
โ ๏ธ Final advice
- your resume gets you the interview
- your skills get you the offer
๐ฏ What Interviews Look Like
Most candidates prepare without a clear understanding of what interviews actually look like.
This leads to:
- practicing the wrong things
- being surprised during interviews
- underperforming despite good preparation
๐งฉ The typical interview pipeline
Most firms follow a structure like this:
- Online Assessment (OA)
- Phone / First-round interviews
- Onsite / Final rounds
๐งช Stage 1 โ Online Assessment (OA)
This is often the first filter.
What it looks like
Depending on the role:
- mental math tests
- probability / brainteasers
- coding challenges (often via LeetCode-style problems)
- logic or game-based assessments
What is being tested
- speed
- accuracy
- basic problem-solving
- ability to stay calm under time pressure
Key insight
๐ This is mostly a filter stage, not a deep evaluation
You donโt need to be exceptional โ you need to be fast, clean, and consistent
Common mistake
- underestimating mental math
- not practicing under time pressure
๐ Stage 2 โ First-Round Interviews
Usually 1โ3 interviews.
What it looks like
- probability questions
- brainteasers
- mental math
- sometimes coding (for research/dev roles)
- interactive
- conversational
- often time-constrained
What is being tested
- reasoning process
- clarity of thought
- ability to structure problems
- communication
Example flow
You might get:
- a probability problem
- followed by variations
- then deeper follow-ups
Key insight
๐ Most candidates fail here not because they donโt know the answer, but because they cannot structure their thinking clearly
๐ข Stage 3 โ Final / Onsite Interviews
This is the most important stage.
Typically:
- 3โ6 interviews
- multiple interviewers
- mix of topics
What it looks like
- harder probability problems
- deeper discussions
- trading games (for trader roles)
- coding + system thinking (for dev roles)
- project deep-dives (for research roles)
What is being tested
- consistency
- depth of understanding
- ability to handle pressure
- intellectual honesty
Trading roles โ specific component
You may encounter:
- market-making games
- expected value decisions
- fast-paced scenarios
- decision-making
- risk/reward intuition
- composure
Research roles โ specific component
You may be asked:
- to explain projects in depth
- to reason about data / models
- to write or discuss code
- rigor
- technical depth
- ability to think like a researcher
๐ง The most important meta-skill
Across all stages:
๐ Thinking out loud clearly
Strong candidates:
- explain assumptions
- structure their reasoning
- adapt when corrected
- jump to answers
- stay silent while thinking
- get stuck without communicating
โ ๏ธ What interviews are NOT
- not trivia tests
- not pure knowledge checks
- not about memorizing solutions
๐ What actually makes the difference
Top candidates:
- stay calm under pressure
- communicate clearly
- simplify problems
- show structured reasoning
๐งช How to prepare effectively
To match real interviews, you should:
- practice under time constraints
- simulate interviews (very important)
- explain solutions out loud
- review mistakes deeply
๐ฏ Final takeaway
If you understand:
- how interviews are structured
- what each stage is testing
โ ๏ธ Common Mistakes
- โ only reading, no practice
- โ ignoring mental math
- โ practicing without time pressure
- โ doing only LeetCode and assuming that is enough
- โ not reviewing mistakes
- โ preparing too broadly
- โ overfitting to one companyโs exact style
โ FAQ
Do I need a PhD to break into quant?
No. Many trading roles hire from bachelorโs and masterโs backgrounds. PhDs are more common in some research-heavy roles, but they are not the only route.Is LeetCode enough?
No. It helps for coding, but quant interviews often also require probability, expected value, mental math, and interview-style reasoning.How long should I prepare?
For many candidates, a serious prep cycle is around 4โ12 weeks, depending on your starting level and target role.What matters most in interviews?
Usually some combination of:- speed
- accuracy
- clarity of reasoning
- composure under pressure
๐งช Practice Platforms
- QuantBrainteasers โ structured quant interview practice
- Brainstellar โ puzzle bank
- Jerry Qin โ probability prep
- LeetCode โ coding
- Zetamac โ mental math
๐ค Contributing
We welcome contributions!
To contribute:
- add high-quality resources
- include short descriptions
- avoid duplicates
- keep it practical and curated
โญ Final Advice
Consistency beats intensity.
A simple routine done regularly is usually more effective than chaotic bursts of preparation.
- Practice every day
- Think deeply about problems
- Simulate real interviews
- Review mistakes honestly
โค๏ธ Support
If you found this helpful:
- โญ star the repo
- share it with others
- contribute useful resources
Maintained by QuantBrainteasers ๐ https://quantbrainteasers.com