— GUIDE —
HOW TO GET INTO QUANT FINANCE
You do not need a ten-year master plan. You need a first direction, a few skills that transfer, one finished project, and a sense of when to start applying.
UPDATED 2026-09-08 · 6 MIN READ · BY THE VARIANCE TEAM
There is no single entry point, which is good news if you did not plan your degree around this. What matters is picking a direction early enough to aim your preparation somewhere specific.
Start somewhere specific
You do not need a ten-year master plan. You do need a first direction. Pick trader, researcher, or developer for now, then let that choice tell you what to learn next. If the three still blur together, the role comparison guide lays out the differences.
Get the basics under your belt
Probability, statistics, programming, and a little market context help almost everywhere. The weighting changes by role.
| If you are aiming at | Put the most time into |
|---|---|
| Trading | Fast mental arithmetic, expected value, conditional probability, and explaining a decision out loud |
| Research | Statistics, regression, experiment design, and getting comfortable with messy data |
| Development | Data structures, systems design, one language you know deeply, and performance debugging |
None of this requires a finance degree. It requires being able to use the tools under time pressure, which is a different skill from having seen them in a lecture.
Finish one thing
A small project you can explain beats a folder full of half-finished notebooks. Say what question you asked, what you tried, what you found, and where it broke. The last part is often the most interesting one.
Some shapes that work:
- A signal test. Take one hypothesis, test it honestly on real data, and report the version with costs included even if it kills the result.
- A simulation. Model a game or a market mechanism, then check the simulated answer against math you derived separately.
- A system. Build something that ingests data, processes it, and does something useful with it, and be able to explain every failure mode.
The point is not to impress anyone with scope. It is to have one artifact you can be questioned about for twenty minutes without running out of things to say.
A rough sequence
- Pick the role. A week of reading job descriptions, not a semester of deliberation.
- Build the base skills. Steady work on the row above that matches your target.
- Finish the project. Small enough to complete, specific enough to defend.
- Train for the screen. Timed practice in the format your target role actually uses.
- Apply, then keep improving. Real cycles teach faster than preparation does.
When to start applying
Earlier than feels comfortable. Campus timelines often open well before the roles start, and applications close quietly once a class fills. A rejection early costs you very little and tells you which stage is actually your weak point.
Then worry about interviews
Interview prep matters, but it makes more sense once you know the role you want. Learn the format for that role, practise the right skills, and apply before you feel like a finished product. Nobody is. The OA preparation guide is the place to start if an assessment is already sitting in your inbox.