— GUIDE —
QUANT TRADER VS. QUANT RESEARCHER VS. QUANT DEVELOPER
Three titles that sit on the same floor and solve different problems. Here is how the daily work, the skills, and the interview process differ across them.
UPDATED 2026-09-08 · 6 MIN READ · BY THE VARIANCE TEAM
Plenty of people pick a lane because one title sounded better in a forum thread. A more useful filter is which of these three days you would want to repeat for a few years.
Three jobs people blur together
They all sound "quant," and they often sit on the same floor. But the day-to-day can feel very different. A good first question is not which title pays more; it is what kind of problem you want to wake up and solve.
Side by side
| Role | Daily work | Core skills | Interview focus |
|---|---|---|---|
| Trader | Pricing, quoting, managing risk and inventory, reacting to what the market does | Fast probability, expected value, decisions under uncertainty | Mental math, market-making questions, live judgment calls |
| Researcher | Testing whether a signal is real, building and validating models | Statistics, data handling, experiment design, skepticism | Probability and statistics depth, past projects, methodology |
| Developer | Building the data pipelines, systems, and tools the desk runs on | Programming, systems design, performance, correctness | Coding problems, system design, debugging under pressure |
Trader
Traders live closer to the decision. They price, manage risk, watch what the market is doing, and decide what to do when the picture is incomplete. If you like fast feedback and can make a call without knowing everything, it may fit.
The screen usually reflects that. Expect timed arithmetic, quick probability, and questions where you are asked to quote a price and defend it. The market-making questions guide walks through that format with worked examples.
Researcher
Researchers spend more time asking whether a pattern is real. A large part of the job is trying to break your own result: checking whether it survives a different time period, a different universe of instruments, or a more honest accounting of costs. People who enjoy digging into a question tend to do well here.
Interviews go deeper on probability and statistics and usually spend real time on something you have already built. Being able to say what you tried, what failed, and why is worth more than a polished summary.
Developer
Developers build the data, systems, and tools that let everyone else use an idea safely and quickly. That covers a wide range: a research platform, a market data feed, an execution path where a few microseconds matter. It suits people who enjoy making difficult systems work and who care when something is subtly wrong.
How much they overlap
More than the titles suggest. Traders write code. Researchers care about how their model behaves in production. Developers need enough market context to know which failure modes matter. At smaller firms one person may do all three; at larger ones the split is sharper.
You do not need to get it perfect
Teams overlap and titles vary by firm. Start with the path that sounds most fun, then read a few real job descriptions and talk to people doing the work. Your first choice is a direction, not a life sentence.