The Ultimate Quant Finance (Trading/Research/Dev) Resume Guide

I work as a quant at a hedge fund and I've spent the last few years on the other side of the hiring funnel — reading resumes for intern and junior pipelines, and reviewing a few hundred more for people I've mentored. The gap between "this person is clearly technically capable" and "this resume makes that legible in 30 seconds" is enormous, and it's the single cheapest thing to fix in your application. I edited this with AI to clean it up.

This is the long version. Skim the headers, read the parts that apply to you.

TL;DR

• One page. PDF. No photo, no columns, no color, no skill bars.
• Numbers on every bullet. Scale (rows, dollars, users, latency) and outcome (bps, %, ms, hours saved).
• Two great projects beat six mediocre ones. Delete the moving-average crossover backtest.
• Only list a language you'd be comfortable being grilled on for 20 minutes.
• Competition results (IMO/Putnam/AMC/ICPC/Kaggle) and games (chess, poker) genuinely matter for trading roles. Put them on.
• Every line on your resume is an invitation to a question. Write lines you want to be asked about.

Part 1: What actually happens to your resume

Understanding the funnel tells you what to optimize for.

Stage 1 — Recruiter / initial screen (well under a minute). Someone non-technical, or a screening model, is checking: target-ish school? GPA above the bar? Relevant coursework? Recognizable internship or a project that isn't a tutorial? Right work authorization? This stage is about not getting filtered, and it's mostly pattern-matching on the top third of page one.

Stage 2 — Desk read (2–5 minutes). An actual trader or quant reads it, usually right before or during your first call. They are looking for one thing: something to talk to you about. They will find the most technically specific line on your resume and push on it until you break or impress them. This stage is about giving them good material.

Stage 3 — The interview itself. Your resume becomes the script for 15–20 minutes of the conversation. Anything you can't defend in detail becomes a liability.

The practical implication: the top third of your resume is written for Stage 1, and the specificity of your bullets is written for Stages 2 and 3. Most people write the whole thing for Stage 1 and end up with a document that clears the filter and then gives the interviewer nothing.

Also worth knowing: most quant funds and prop shops do not run aggressive ATS keyword filtering the way F500 corporates do. The pipelines are smaller and more human. This doesn't mean you should get creative with formatting — it means the "beat the ATS" advice you read on r/resumes is mostly noise here. Optimize for the human.

Part 2: Format non-negotiables

These are boring and they are also where 40% of resumes lose.

One page. Undergrad, master's, career changer with 6 years of experience — one page. The only common exception is a PhD applying to research roles where a publication list is genuinely relevant, and even then the resume is one page with publications on page two, not a rambling two-page resume.

PDF, always. Named Firstname_Lastname_Resume.pdf. Not resume_final_v4_USE_THIS.pdf. Someone is going to have this file open in a folder with 400 others.

Single column, reverse chronological. No sidebars. Sidebars destroy copy-paste, break in some viewers, and waste 30% of your page on a "skills" column that says "Teamwork: ●●●●○".

No photo, no address, no date of birth, no marital status. US/UK convention. City and state/country is fine and slightly useful.

Typography: one serif or one clean sans (Latin Modern, Charter, Source Sans, Calibri). 10–11pt body. 0.5–0.75" margins. Consistent date alignment on the right. If you know LaTeX, use it — a clean moderncv-style or Deedy-derived template is fine, but strip the sidebar. If you don't know LaTeX, a well-set Word doc is completely fine and nobody has ever been rejected for it.

Delete these sections outright: Objective. Summary/Profile (if you're a student — it's just the resume again, in worse prose). "References available upon request." Photo. Skill rating bars. Personal logo.

Consistency is a proxy for care. Same tense (past for past roles, present for current), same date format, same bullet punctuation, same em-dash style, aligned everything. Traders and quants notice sloppy formatting the same way they notice a chart with unlabeled axes. It reads as "this person doesn't check their work."

Part 3: Section by section

Order

• Student / new grad: Header → Education → Experience → Projects → Skills → Other
• 1–3 years experience: Header → Education → Experience → Projects (if strong) → Skills
• 3+ years / PhD: Header → Experience → Education → Skills → (Publications)

Education stays on top longer in quant than in most industries, because the education line carries real signal here (school, major, GPA, coursework, competition results).

Header

Name, phone, professional email, LinkedIn, GitHub (only if it has something on it), personal site (only if it has something on it). One or two lines total.

An empty or embarrassing GitHub link is worse than no link. If your pinned repos are three abandoned tutorials from a Udemy course, either fix that this weekend or delete the link.

Education

Georgia Institute of Technology Atlanta, GA B.S. Mathematics, Minor in Computer Science Expected May 2027 GPA: 3.87/4.00 (Major: 3.94) | SAT: 1580 (M: 800) Relevant Coursework: Stochastic Processes, Real Analysis, Numerical Methods, Machine Learning, Data Structures & Algorithms, Time Series Econometrics Honors: Putnam Fellow-adjacent — Top 200, 2025 | AMC 12 Distinguished Honor Roll 

Specifics:

• GPA: include it if it's 3.5+. Below that, consider showing major GPA if it's meaningfully higher, or omitting entirely (omission signals "it's low," but a 3.1 stated outright signals "it's 3.1," which is worse at the screen stage). Many firms have hard cutoffs around 3.5.
• Standardized test scores: this is the quant-specific quirk that surprises people. SAT/ACT/GRE quant scores are commonly listed and commonly read, especially by prop shops and market makers. If your SAT math was 780+, put it on. If it was 640, don't.
• Competition math is the strongest single signal on a junior trading resume. IMO/IPhO medals, Putnam scores, AMC/AIME, national olympiads, ICPC placements, Kaggle medals. If you have any of it, it goes above the fold. Firms recruit directly out of these communities.
• Coursework: list 5–8 courses that are actually load-bearing. Stochastic calculus, measure-theoretic probability, real analysis, optimization, ML, distributed systems. Do not list "Intro to Microeconomics."
• Drop high school entirely once you're a junior — unless the high school credential is an international olympiad medal, in which case keep the medal and drop the school.

Experience

This is the section that gets you hired. See Part 4 for the bullet formula.

Three to five bullets for the most relevant role, two to three for older or less relevant ones. Include the desk/team, not just the firm: "Fixed Income Strategies, Systematic Rates" tells me more than "Summer Analyst."

Non-finance experience counts. A backend internship where you cut p99 latency from 300ms to 40ms is more interesting to a trading firm than a wealth-management internship where you built pitch decks. Quant firms hire engineers and scientists, not finance majors. Don't apologize for a software or research background — lead with it.

Research assistantships count. TA-ing a hard course counts, especially if you can quantify it (built the autograder, wrote the problem sets, 200 students).

Projects

Two to three, with the same bullet discipline as experience. This section is where most students either save or sink their application. Part 6 covers what makes a good project in detail.

Format each as a mini-role with a name, the stack, and 1–3 bullets. Include a GitHub link only if the code is clean and has a README.

Skills

Honesty-calibrated and tiered. This:

Languages: Python (expert — pandas, NumPy, PyTorch, asyncio), C++17 (proficient — STL, templates, RAII), SQL (proficient), q/kdb+ (familiar), Rust (familiar) Tools: Linux, Git, Docker, Bloomberg/BQuant, Airflow, LaTeX Math: Stochastic calculus, time-series econometrics, convex optimization, Bayesian inference 

Not this:

Skills: Python, R, C++, Java, JavaScript, MATLAB, SQL, VBA, Julia, Go, Scala, Excel, PowerPoint, Word, Leadership, Communication, Teamwork, Problem Solving 

The rule: assume you will be interviewed on every item. If someone lists Rust, I will ask about ownership and borrowing. If someone lists kdb+, I will ask them to write a select statement. Listing eleven languages tells me you have surface familiarity with eleven languages, which is a negative signal for a job that requires depth.

Don't list Microsoft Office. Don't list soft skills.

Interests / Other

Underrated for trading roles specifically. Trading desks are explicitly hiring for competitiveness, probabilistic reasoning under time pressure, and comfort with variance. Signals they read positively:

• Chess (with rating), Go, bridge, backgammon
• Poker (especially if you can talk about it in EV terms, and especially if it's real and documented — but do not put "$40k profit" unless it's true and you're prepared to discuss variance)
• Competitive esports at a ranked/national level
• Sports at a serious level, marathon/ultra times, olympic lifting numbers
• Prediction markets, fantasy sports at a high level, sports betting models you actually built

Signals that are just filler: "reading," "traveling," "music," "hiking."

One line, at the bottom, with numbers where numbers exist. Interests: Chess (2050 USCF), NL Hold'em, half-marathon (1:24), mechanical keyboards.

Part 4: The bullet formula

Every bullet should answer: what did you build, how, at what scale, and what happened as a result?

[Strong verb] + [specific thing built] + [tools/method] + [scale] + [quantified outcome] 

Two lines maximum. One is better. If a bullet wraps to a third line, it's two bullets or it's over-explained.

Verbs that work: built, designed, implemented, automated, reduced, optimized, backtested, derived, deployed, parallelized, productionized, calibrated. Verbs that don't: assisted, helped, participated, was responsible for, worked on, gained exposure to, familiarized.

Before / after examples

1. The vague internship

2. The unquantified automation

3. The backtest with no rigor

(The second version is a weaker result and a dramatically stronger bullet. It says: I know that the naive number is fake, I know why, and I measured it. A Sharpe 4.2 claim on a resume reads as "hasn't discovered look-ahead bias yet" and it is a genuine auto-reject for a lot of people.)

4. The engineering role you're underselling

5. The research assistantship

6. The class project you're embarrassed by

(This is a genuinely great bullet. Nobody believes 87%. Everybody believes 52.4% and respects the person who found their own leak.)

7. The teaching role

8. The trading-adjacent role

The "so what" test

Read each bullet and ask "so what?" If the bullet doesn't answer it, it isn't done.

Now it's a bullet.

Part 5: Tailoring by role

These are different jobs and the same resume should not go to all of them.

	Quant Trader (QT)	Quant Researcher (QR)	Quant Developer (QD)
Core signal	Fast probabilistic reasoning, competitiveness, decisions under uncertainty	Statistical rigor, research taste, ability to find and kill your own edge	Systems depth, latency, correctness at scale
Lead with	Competitions, games, mental-math-adjacent achievements, any live risk-taking	Publications, research projects, methodology depth	Low-level projects, performance numbers, infra
Language emphasis	Python is fine; breadth over depth OK	Python + stats stack, R, some C++	C++/Rust depth, systems, concurrency
Project type	Market-making sims, betting/prediction models, game-theoretic work	Alpha research with honest validation, econometrics, ML with proper CV	Exchange simulators, order books, HFT-adjacent infra, distributed systems
Underrated add	Poker/chess ratings, sports betting P&L	Negative results, replication studies	Benchmarks, profiling flamegraphs, contributions to real OSS

If you're applying to all three (reasonable when you're starting out), maintain three versions that differ in project ordering, skills emphasis, and 2–3 bullets. Not three totally different documents — 20 minutes of edits each.

Part 6: Projects that work vs. projects that don't

Projects that actively hurt you

• Moving average crossover backtest on SPY. Everyone has done it. It signals "my exposure to this field is one YouTube video."
• LSTM stock price prediction. Almost always leaks. Almost always has a plot of predicted-vs-actual that's just the actual series shifted by one day. Interviewers will spot this instantly and it is a very bad look.
• Anything with a claimed Sharpe > 3 and no cost model.
• A cloned tutorial with the variable names changed.
• "Portfolio optimizer" that is 40 lines of cvxpy on 10 tickers of Yahoo data.

What makes a project good

A good project demonstrates at least two of:

1. Real data engineering — messy, large, or point-in-time-correct data
2. Statistical honesty — proper out-of-sample design, cost modeling, multiple-testing awareness
3. Systems competence — performance, concurrency, correctness under load
4. A result you can defend, including a negative one

Five archetypes that consistently work

a) A limit order book simulator. Build a matching engine (price-time priority, partial fills, cancels), feed it real or synthetic order flow, and then build a naive market-making strategy on top of it. Measure inventory risk, adverse selection, and how your quotes perform against informed flow. Hits systems + trading intuition simultaneously. Write it in C++ if you're targeting QD.

b) A point-in-time economic data store. Ingest a set of macro releases with vintages (ALFRED gives you revision history), and demonstrate concretely how much a backtest's Sharpe changes when you use revised vs. first-print data. This is a real problem that costs real funds real money, and almost no student project addresses it.

c) A replication study. Pick a well-known published anomaly, replicate it, and then test whether it survived post-publication with realistic costs. Report the decay. This is exactly the job for a lot of QR roles and it demonstrates you can read a paper and turn it into code.

d) A sports betting or prediction-market model. Small, tractable, has real closing prices as ground truth, and has an unambiguous scoreboard. Compare your model to the closing line — closing line value is a genuinely rigorous metric and it's a great thing to talk about in an interview.

e) A vol surface fitter / options pricing library. Implement SVI or SABR calibration on real option chains, handle the arbitrage constraints (butterfly and calendar), and show your fit quality across strikes and tenors. Hits numerical methods + derivatives knowledge.

The common thread: each of these has a falsifiable claim you can defend for 20 minutes.

Part 7: Auto-reject red flags

In rough order of how much damage they do:

1. Unrealistic performance claims. Sharpe 6, "consistently 30% annual returns," "95% win rate." Either you don't understand backtest overfitting or you're being dishonest. Both are disqualifying.
2. Typos and inconsistent formatting. This job is quantitative and detail-critical. Two typos on a one-page document is a real data point.
3. Skills you can't defend. Listed C++, can't explain a virtual function. Listed "machine learning," can't explain the bias-variance tradeoff.
4. Buzzword salad with no substance. "Leveraged cutting-edge AI to synergize alpha generation across multi-asset frameworks." Say what you did.
5. "Passionate about the markets." Everyone writes this and it conveys zero information. Show it with what you built instead.
6. Personal trading account with vague results. "Manage a personal portfolio with strong returns" is meaningless. If your PA trading is genuinely sophisticated, describe the method and the sample size, or leave it off. Also be aware many firms restrict personal trading and some read a heavy PA-trading resume as a compliance headache.
7. Two-plus pages as a student.
8. Photo, graphics, skill bars, non-standard fonts, colors.
9. Listing coursework you took but got a C in. You will be asked about it.
10. Overlapping or gappy dates with no explanation.

Part 8: Two full examples

Example A — Undergrad targeting Quant Trading

EDUCATION Georgia Institute of Technology Atlanta, GA B.S. Mathematics, Minor in Computer Science Expected May 2027 GPA: 3.89/4.00 (Major 3.95) | SAT 1580 (Math 800) Coursework: Stochastic Processes, Real Analysis, Measure Theory, Numerical Methods, Machine Learning, Data Structures & Algorithms, Time Series Honors: Putnam Top 500 (2025) | AIME Qualifier ×3 | ICPC Regional 4th (2025) EXPERIENCE Optiver — Quantitative Trading Intern Chicago, IL Jun 2026 – Aug 2026 • Built a Python monitor for ETF-vs-basket dislocations across 40 sector ETFs, flagging ~35 actionable prints/day; adopted by 3 traders on the index desk. • Backtested a same-day mean-reversion overlay on the desk's existing signal with realistic queue-position assumptions; showed net Sharpe improvement of 0.3 was fully explained by 2 outlier days and recommended against deployment. • Placed 2nd of 41 interns in the firm's market-making simulation competition. Georgia Tech Quantitative Finance Lab — Research Assistant Atlanta, GA Jan 2026 – May 2026 • Implemented 4 realized-volatility estimators on 5 years of TAQ tick data (2.1B rows, Spark); pre-averaging reduced microstructure bias ~60% at 1-min. • Rebuilt the lab's data ingestion in Airflow, cutting a 6-hour nightly job to 25 minutes and eliminating 3 recurring silent-failure modes. PROJECTS Limit Order Book Simulator (C++17, Python bindings) github.com/… • Wrote a price-time-priority matching engine handling 1.2M messages/sec on a single core; validated against 3 days of ITCH data with exact fill replay. • Layered an Avellaneda-Stoikov market maker on top; measured that inventory penalty tuning mattered ~4× more than spread width for terminal PnL variance. NFL Closing Line Value Model (Python, PyMC) • Built a hierarchical Bayesian team-strength model over 12 seasons; beat the closing line on 52.9% of 1,400 out-of-sample spreads (p = 0.01). SKILLS Languages: Python (expert — pandas, NumPy, PyMC), C++17 (proficient — STL, templates), SQL (proficient), Java (familiar) Tools: Linux, Git, Docker, Airflow, Spark, LaTeX Math: Stochastic calculus, Bayesian inference, time-series econometrics INTERESTS Chess (2075 USCF) | NL Hold'em | Half-marathon 1:22 

Example B — PhD / career changer targeting Quant Research

EXPERIENCE Broad Institute — Postdoctoral Researcher, Statistical Genetics Cambridge, MA Sep 2024 – Present • Developed a hierarchical shrinkage estimator for effect sizes across 900k correlated hypotheses; cut false-discovery rate 38% vs. the standard method at matched power. Released as an ++ package (1,100+ installs). • Built the group's variant-calling pipeline (Nextflow, 400 CPU-hrs/run), reducing per-cohort turnaround from 9 days to 30 hours. • First-authored 3 papers; reviewer for 2 journals. Massachusetts Institute of Technology — Ph.D. Researcher Cambridge, MA Sep 2019 – Aug 2024 • Derived and proved consistency for a semiparametric estimator under dependent sampling; simulation study across 240 parameter regimes. • Wrote and maintained 30k LOC of C++/Python research infrastructure used by a 12-person lab. PROJECTS (Quantitative Finance) Post-Publication Decay of Equity Anomalies (Python) • Replicated 18 published cross-sectional anomalies on CRSP/Compustat with point-in-time fundamentals; mean gross Sharpe fell 0.81 → 0.29 out of sample, and 6 of 18 were not distinguishable from zero after 10bp round-trip costs. • Wrote up multiple-testing adjustment (Harvey-Liu-Zhu) showing 4 additional anomalies fail at an appropriately raised t-stat hurdle. Macro Nowcasting with Mixed-Frequency Data (Python, statsmodels) • Built a MIDAS/dynamic-factor nowcast of quarterly US GDP from 92 monthly and weekly series with proper release-vintage alignment (ALFRED); RMSE 18% below the Atlanta Fed GDPNow benchmark over 2015–2024 backtest. EDUCATION Ph.D. Statistics, Massachusetts Institute of Technology 2024 B.Sc. Mathematics, Indian Institute of Technology Bombay (Rank 3/120) 2019 JEE Advanced: AIR 214 (2015) SKILLS Python (expert — NumPy, pandas, JAX, scikit-learn), C++ (proficient), R (expert), SQL, Nextflow, Slurm, Git, LaTeX Methods: Bayesian hierarchical modeling, high-dimensional inference, time-series & mixed-frequency models, causal inference, convex optimization PUBLICATIONS — 3 first-author (full list on request / linked) 

Note what Example B does: the academic work is described in terms of methods and scale, not biology. Nobody hiring for a rates desk cares about variant calling; everybody cares that she handled 900k correlated hypotheses and cut FDR by 38%. Translate your domain into the language of scale, method, and measured outcome.

Part 9: Special situations

Low GPA (< 3.3). Compensate with an unambiguous external signal: a competition result, a serious open-source contribution, a Kaggle medal, a project with real users. Get a referral — a referral bypasses the GPA screen more often than anything else. Consider a master's if you're early enough. Do not put the low GPA on the resume; do answer honestly if asked.

Non-target school. Same answer: external verifiable signal + referral. Also apply much wider and much earlier, and go to the firms that recruit on results rather than campus (many prop shops explicitly do). Online competitions, IMC/Optiver/Jane Street puzzle contests, and open trading competitions are real doors.

Career changer from software engineering. You are in a much better position than you think, especially for QD and QR-adjacent roles. Lead with systems depth and quantified performance work. Add one serious finance project to prove domain interest. Do not rewrite yourself as a finance person — your value is that you're an engineer.

Career changer from a non-quant finance role (IB, PWM, corp fin). Harder. You need to demonstrate the technical bar independently: coursework or a master's, plus projects with real code. Your finance context is a modest bonus, not the main pitch.

PhD, non-finance field. Very common and very hireable. See Example B. Translate everything. Keep it to one page plus a publications page.

International / visa. Most US prop shops and large funds sponsor; some smaller ones don't. Stating "Authorized to work in the US (F-1 OPT/STEM eligible)" is neutral-to-helpful. Don't hide it — a late-stage discovery wastes everyone's time and burns goodwill.

Part 10: The process around the resume

Timing dominates. Quant recruiting is early and rolling. Summer internship applications for many top firms open 9–12 months ahead and classes fill on a rolling basis. A great resume submitted in January for a summer that opened in August is a worse outcome than a good resume submitted on day one. Set calendar reminders in the spring for the following summer.

Referrals are worth more than resume polish. A referral typically means your resume gets read by a human on the desk rather than filtered. The realistic path: alumni on LinkedIn, a short specific message (not "can I pick your brain" — "I built X, you work on Y, does that map to what your team does?"), and a resume attached.

Cover letters: mostly ignored at prop shops and hedge funds. Occasionally required at banks and larger asset managers. When required, three short paragraphs, specific to the firm, no adjectives.

Track your applications in a spreadsheet with dates, so you can measure your own funnel. If you're getting 0 responses from 60 applications, the problem is the resume or the targeting, not variance. If you're getting first rounds and dying there, the resume is fine and the problem is interview prep.

Iterate on real feedback. Post your resume (redacted) somewhere people will actually critique it. The most common failure mode is a person sending version 1 to 80 firms instead of version 4 to 80 firms.

Final checklist

Print this and go line by line.

• [ ] One page, PDF, named Firstname_Lastname_Resume.pdf
• [ ] No photo, no columns, no color, no skill bars, no objective
• [ ] Dates aligned, tenses consistent, zero typos (read it backwards, out loud)
• [ ] Every bullet has a number in it, or a very good reason it doesn't
• [ ] Every bullet passes the "so what?" test
• [ ] No performance claim you couldn't defend against a skeptical interviewer
• [ ] Every listed skill is one you'd survive 20 minutes of questioning on
• [ ] Projects are 2–3 strong ones, not 6 tutorials
• [ ] At least one project has a falsifiable, defensible result
• [ ] Competition/test scores included if they're good
• [ ] GitHub link only if the GitHub is presentable
• [ ] Interests line has numbers where numbers exist
• [ ] Version tailored to QT vs QR vs QD
• [ ] Someone technical has read it and pushed back on it

The uncomfortable truth is that a resume can't create signal that isn't there — it can only fail to communicate signal that is. If you go through this and find there's genuinely not much to write down, that's useful information: the fix is six weeks on one serious project, not another weekend reformatting.

Happy to critique resumes in the comments — post a redacted version and I'll be specific. Also happy to take questions on any of the above.