How to become a quant: the route people actually take

There are three different jobs behind one word

"Quant" covers at least three distinct seats, and they hire differently. Quant researchers build and test the models. Quant traders own risk and execution decisions in live markets. Quant developers build the systems everything runs on. The entry requirements diverge sharply, so pick the seat before you pick the preparation.

What the adverts ask for

Across the live vacancies we track, the requirements cluster tightly. A quantitative degree appears in the large majority of research adverts. Python appears more often than any other named technology; C++ appears most often in trading and low-latency engineering. Statistics, probability and machine learning show up as topics rather than as tools.

Use our skills index to see the current counts by role, with the sample size attached, rather than trusting any single list — including this one.

The degree question

• Research seats. A PhD is common, and in some firms effectively expected. It is a signal of independent research ability more than of subject knowledge.
• Trading seats. A strong undergraduate degree plus visible quantitative aptitude is the standard profile. Many desks prefer people who make decisions quickly over people who write papers.
• Development seats. A computer science degree and serious C++ or Python are worth more than any postgraduate qualification.

The part most people skip

Employers are buying evidence that you can finish things. A backtest you ran honestly, a system someone else used, a paper someone cited, a competition you placed in — any of these outrank another line of coursework. Bring one piece of work you can defend line by line under questioning.

A twelve-month plan that works

• Months 1–3: probability and statistics to interview depth. Work problems out loud.
• Months 4–6: build one end-to-end project with real market data. Version it, test it, write up what failed.
• Months 7–9: C++ if you are aiming at trading or engineering; production Python if you are aiming at research.
• Months 10–12: apply broadly, sit as many interviews as you can, and treat each one as data.

Where to look next

Our interview lab covers the question types firms actually use, and the salary hub shows what the roles pay by seniority and city, with the number of advertised ranges behind each figure.