The skills quant employers are actually asking for
KnowQuant research desk · Published 6 February 2026 · 1 min read
What skills do quant employers ask for?
Across live quant vacancies, the most frequently named requirements are Python, C++, statistics and probability, machine learning, SQL and Linux. Python leads by a clear margin overall; C++ concentrates in trading and low-latency engineering. Machine learning appears widely but is more often a supporting requirement than the core of the seat.
What this piece establishes
- Counted, not guessed. Every claim here comes from counting named requirements in the live vacancies we track.
- The consistent leaders. Python leads the overall count.
- Machine learning: real but overstated. Machine learning appears in a substantial share of adverts, but reading the requirement in context matters.
- The mix moves by seat. Research adverts skew towards statistics and Python.
Counted, not guessed
Every claim here comes from counting named requirements in the live vacancies we track. Our skills index publishes the current numbers with sample sizes and a confidence band, and it updates as the market does. Where a count is too small to support a conclusion, we say so.
The consistent leaders
Python leads the overall count. Statistics and probability appear as topics rather than tools and are close to universal in research seats. C++ dominates trading systems and execution. SQL is named far more often than candidates expect. Linux and version control tend to be assumed rather than advertised, which means their true frequency is understated by any count including ours.
Machine learning: real but overstated
Machine learning appears in a substantial share of adverts, but reading the requirement in context matters. In most seats it is one tool among several, not the job. Adverts where it is genuinely central are a much smaller group.
The mix moves by seat
Research adverts skew towards statistics and Python. Development adverts skew towards C++, systems and concurrency. Trading adverts sit between the two and add execution and market-structure language.
How to use this
Pick the seat, then read the skill counts for that seat rather than the market average. The average describes nobody's job.
Take this further
Continue in the research index, or look at the employers and pay behind the argument.
Live opportunities
Act on this: live roles it covers
Open vacancies we track at quant firms, grouped by role and city. Adverts are anonymised.
Hiring for these roles? Brief the desk on a hire or check your fit for a role.
Research desk
Speak to a quant market specialist
Ask what a firm really pays, how a desk hires, or where your profile sits. One reply from the research desk, in confidence, no obligation.
Related research
- Python or C++ in quant finance: choose by the system you want to build
What actually determines whether a system is fast, where each language earns its place, a worked design example from research to a narrow native component, and a small runnable example with a correctness suite we ran ourselves.