How to read this quantitative analyst resume example
The sample above is not a template to copy word for word - copied resumes read as copied. It is here to show the shape of a page that gets past a first screen: one column, standard headings, and bullets that end in an outcome rather than a duty. Models that were traded or relied on, with the validation behind them.
- Every bullet opens with a verb and carries a number. That is the pattern, not a coincidence.
- The summary makes a claim and then supports it in the first bullet underneath.
- Skills are named tools, not adjectives, and each one appears again in the experience section.
- The earlier role is short. Recent work carries the weight of the page.
The numbers in a quantitative analyst resume
The most common thing missing from a quantitative analyst resume is a number. Not because the work had none, but because nobody wrote them down at the time. These are the measures a quantitative analyst can usually reach for, and the example uses them.
- Built the pricing model now used on a book with $400m notional exposure.
- Improved backtested Sharpe from 0.9 to 1.4 by correcting a look-ahead bias in the feature set.
- Reduced daily risk-report runtime from 5 hours to 20 minutes by vectorising the simulation.
Before and after: rewriting a weak bullet
Most quantitative analyst resumes are one edit away from being much stronger, and the edit is the same every time: replace the description of the job with the result of doing it. The pairs below are the same work, written twice.
- Weak: "Responsible for python and related tasks." Strong: "Built the pricing model now used on a book with $400m notional exposure."
- Weak: "Worked on statistics projects across the team." Strong: "Improved backtested Sharpe from 0.9 to 1.4 by correcting a look-ahead bias in the feature set."
- Weak: "Helped improve processes and supported quantitative analyst initiatives." Strong: "Reduced daily risk-report runtime from 5 hours to 20 minutes by vectorising the simulation."
Adapting the example to your own history
Work backwards from the posting. Find the two or three things it actually screens for, then make sure the top third of your page answers them. Everything below that is supporting evidence.
- Reorder your bullets so the one closest to the posting comes first in each role.
- Rewrite the summary for the specific job. It is the only part a human reliably reads.
- Cut any skill you would not want to be asked about for ten minutes.
- Keep Python, Statistics, Time series visible in context, not stranded in a list.