The DRW trading interview is built to feel like the firm itself: a Chicago principal trading house that puts its own capital at risk across nearly every asset class, from listed options and futures to fixed income, energy, and crypto. Because DRW trades its own money rather than running a client flow business, the interview filters hard for people who reason cleanly about probability and expected value, compute fast under pressure, and stay composed when a position moves against them. This page covers the full process end-to-end, what each round tests, the question types you will see, the firm-specific nuances, and a multi-week prep plan tuned to the loop.
The full process, end to end
A typical DRW trading pipeline runs like this:
- Application and online assessment. Most candidates start with an online screen. For trading roles this is usually a timed quantitative and aptitude test — arithmetic, probability, sequences, and logical reasoning under a clock — sometimes paired with a personality component. For quant-dev and software-leaning roles the screen is a coding assessment instead. This stage filters on raw speed and accuracy before anyone speaks to you.
- Recruiter conversation (20-30 min). A recruiter walks through the loop, confirms which track you are on (trader vs. quant/dev), and covers your background and why trading and why DRW. Fit-and-logistics, with a light probe on how you think about risk.
- First-round interview (30-45 min). A trader-led or quant-led round mixing mental math, expected-value problems, and a few probability brainteasers. Conversational — they want to hear your reasoning out loud, not just the final number. Some candidates get a short live arithmetic drill here on top of the online test.
- Market-making game(s) (45-60 min). The signature round. You quote a two-sided market on a hidden quantity, the interviewer trades against your prices, new information arrives, and you requote while tracking your position and running P&L. Strong loops often run more than one variation.
- Coding / technical round (some roles). For quant-developer and software-engineering seats, and for trader roles with a development lean, expect a Python, C++, or Java screen — frequently a data, simulation, or systems task rather than abstract puzzle code. Pure-trader loops may be lighter here; confirm with your recruiter.
- Final / superday and offer. A cluster of rounds at DRW's Chicago office (or a regional hub) combining a deeper market-making or probability conversation with behavioral and team-fit, often a chat with senior traders, then a level and offer discussion.
The whole pipeline runs three to eight weeks for most candidates, faster for interns with a single onsite day, slower for full-time seats that need to schedule multiple rounds.
What the rounds actually test
DRW is filtering for a specific profile, and every round maps to it:
- Probability and EV reasoning. Because DRW trades its own capital, the question behind almost every problem is "what is this worth, and how confident am I?" Can you frame a messy situation as an expected value, attach a probability to each branch, and act on it cleanly?
- Mental-math speed. Trading on listed markets means pricing and updating in seconds. If three-digit arithmetic slows you down, you cannot keep up in a market-making game, so the loop checks raw arithmetic both directly and implicitly inside EV problems.
- Market intuition. DRW wants traders who feel where a fair price sits, how wide to quote given their uncertainty, and how to adjust when information arrives — judgment under incomplete information, not a memorized formula.
- Risk and P&L awareness. The firm wants traders who always know whether they are long or short and up or down. Losing track of your position in a market-making game is a major negative signal.
- Composure. Traders watch for tilt — visibly rattled by a losing trade, a missed multiplication, or an aggressive counterparty. Resetting cleanly after a bad outcome is itself a scored behavior.
- Engineering ability (technical tracks). For quant-dev and software seats, clean, correct, efficient code and reasoning about trade-offs carry as much weight as the quantitative content.
There is no published pass rate, but DRW — like its principal-trading peers — takes a small fraction of the candidates who reach the trading rounds.
Question types by round
Probability and expected value
The backbone of the trading loop. Expect a steady diet of:
- Expected value of a game — "You pay to roll a die and receive the face value in dollars. What is the most you should pay?" (3.5.) Follow-ups add structure: re-rolls, caps, or the option to stop.
- Conditional probability and Bayes — disease-test false-positive setups, urn draws, "given that you saw X, how does your estimate of Y change?"
- Sequential decisions and optimal stopping — "you see numbers one at a time and must pick one; what is your rule?" and bet-sizing problems where the answer is a strategy, not a single number.
- Fair-value and edge problems — "this bet costs 4 and pays 10 if a fair coin comes up heads twice; do you take it, and how much?"
DRW grades the structure of your reasoning as much as the answer. State your assumptions, narrate the branches, and arrive at a number you can defend.
Mental math
Whether through the online assessment or a live drill, DRW checks arithmetic speed directly:
- Two-digit (and harder) multiplication — 37 x 48, 84 x 76, often quickly in sequence.
- Percentages and fractions — 17% of 1,240; 7/13 as a decimal; conversions both ways.
- Division with decimals — 1,237 / 47 to a couple of places, fast.
- Mixed-sign arithmetic — negatives sprinkled in so you cannot autopilot.
The bar is fast-and-right. Fast-and-wrong loses to medium-and-right, and slow loses to both. This is pure trainable mechanics and the single highest-leverage thing to drill.
Market-making games and market intuition
The signature DRW round. The interviewer names a quantity with a hidden value — "the sum of two dice," "the number of countries in Africa," "the windows on the building across the street" — and you quote a two-sided market (a bid and an ask) you will trade at, wide enough to avoid being picked off and tight enough to show confidence: "Sum of two dice — 6 at 9." The interviewer trades ("I lift your offer" — they buy at 9, leaving you short), then feeds new information ("one die is a 4," so the expected sum is now 4 + 3.5 = 7.5). You reassess P&L and requote, adjusting your spread to your confidence, and the loop repeats until they end the game.
The interviewer grades initial-quote quality, how fast you integrate new information, whether you always know your running position and P&L, and whether you stay composed after a losing trade. It is a repeated game about edge and information flow, not a pricing exam with a single right answer. Because DRW trades across many products, some interviewers layer in light market intuition — "where would you quote this option," "what happens if volatility spikes" — to see whether you reason like a trader, not just a puzzle-solver.
Coding and technical (some roles)
For quant-developer and software-engineering seats, and for trader roles with a development lean, DRW runs a coding screen in Python, C++, or Java. The flavor leans practical — data structures and algorithms, a simulation or data task, sometimes a systems or low-latency-adjacent problem — rather than obscure trick puzzles. The bar is clean, correct, efficient code and reasoning about edge cases and trade-offs out loud. DRW's technology organization is large and central to the firm, so for these tracks the engineering bar is real. Pure-trader loops may be lighter on coding — confirm your role's format with your recruiter.
Firm-specific nuances
A few things set the DRW loop apart from its peers:
- Principal trading shapes the questions. DRW risks its own capital across a broad set of markets, so the interview cares about EV discipline and risk awareness over client-facing or sales instincts. The question behind the question is always "what is the edge, and what is the risk."
- Trader and quant/dev tracks diverge. A pure-trader loop front-loads mental math, probability, and market-making; a quant-developer or software loop front-loads coding and systems thinking. Some quantitative-trading seats blend both. Knowing which track you are on tells you where to spend your highest-leverage weeks.
- Breadth of asset classes. DRW trades options, futures, fixed income, energy, crypto, and more. You are not expected to know every product, but curiosity about markets and a willingness to reason about unfamiliar instruments is a positive signal.
- Chicago trading culture. DRW is a Chicago-rooted firm with a direct, performance-oriented culture. The behavioral and fit portions probe whether you are calm under stress, collaborative on a desk, and genuinely interested in markets — credentials matter less than reasoning and temperament.
A multi-week preparation plan
Weeks 1-2 — Own the arithmetic. Daily timed mental-math drills on Arithmetic Zetamac (two-digit multiplication, division, percentages, fractions) with negatives mixed in. Target a top-tier Zetamac score and a fast, clean rhythm before moving on. This foundation underpins every later round and is pure trainable mechanics.
Weeks 3-4 — EV and market-making. Drill 5-10 EV and probability problems a day from Heard on the Street and a quant question bank until framing any new problem as an expected value is automatic. In parallel, drill market-making games out loud with a partner or a tool that takes the other side — quote, get hit or lifted, integrate new information, requote, and track P&L.
Weeks 5-6 — Probability depth and brainteasers. Push into harder conditional-probability, Bayes, and sequential-decision problems, plus a steady diet of structured brainteasers. Keep a daily timed-arithmetic warm-up so the speed does not decay, and narrate your reasoning out loud so the structure is clear to a listener.
Week 7 (and technical-track candidates) — Coding and full mocks. If your role includes a coding screen, drill data-structure and simulation problems in Python, C++, or Java under a timer, plus at least one systems- or strategy-flavored task. For everyone, run 3-5 full mock loops a day chaining a timed math block, a probability round, and a live market-making game. DRW's loop is fatigue-inducing; build the stamina to stay sharp in the final rounds.
The single biggest differentiator is the combination of fast, accurate mental math and disciplined EV reasoning, and candidates underinvest in the math drills because they are boring. Boring is the point.
How to practice for the DRW loop
InterviewDen's quant-trading track simulates the DRW loop end-to-end. The mental-math module runs against a ratcheting timer so you can push your speed and accuracy on the exact shapes DRW uses, including division and negative-number arithmetic. The market-making module runs the full live flow — you name a two-sided market out loud, the AI trades against your quotes, new information arrives, and you requote while it tracks your running position and P&L. The EV and probability rounds ask live follow-ups the way a trader would, and the scored debrief flags exactly what DRW grades: hesitation, quoting too tight, losing track of P&L, and panic-widening after a bad trade. It is voice-driven and free to start, so you rehearse the actual skill — quoting and computing out loud under pressure.
For the full breakdown of mental-math bars, market-making mechanics, and EV taxonomy across firms, read the quant trading interview guide, and warm up on the exact problem shapes with the quant trading brainteasers. When you are ready, run a trading mock and get a scored debrief on speed, EV discipline, and composure.
Common mistakes
- Underdrilling mental math. Arithmetic speed underpins every later round, and it is pure trainable mechanics. Candidates who treat it as an afterthought stall the moment a market-making game speeds up.
- Quoting markets too tight. Nervous candidates quote a one-wide market to look confident and get picked off. Wider-but-defensible is a better signal than falsely tight.
- Losing track of P&L. By the fifth trade in a market-making game you must know your running position and whether you are up or down. Candidates who lose the thread cannot make rational updates.
- Ignoring the EV structure. DRW wants to see you frame a problem as an expected value with explicit probabilities, not jump to a guessed number. Narrate the branches.
- Freezing on a wrong answer. If you miscompute and realize it, say "recomputing" and redo it cleanly. Sitting silent reads as tilt.
- Treating market-making like a pricing exam. It is a repeated game about edge and information flow, not a hunt for the one true number.
- Walking in without knowing your track. Trader and quant/dev loops weight things very differently. Confirm your track with your recruiter so you prepare for the right loop.
FAQ
How hard is the DRW trading interview?
It is highly competitive, in line with other top Chicago principal trading firms. The loop tests fast, accurate mental math, disciplined expected-value reasoning, and live market-making, and the bar on each is high. DRW does not publish a pass rate, but like its peers it takes a small fraction of candidates who reach the trading rounds. The most decisive skill — arithmetic speed — is pure trainable mechanics, and weeks of daily timed drilling move it reliably.
What does the DRW online assessment look like?
For trading roles it is typically a timed quantitative and aptitude test — arithmetic, probability, sequences, and logical reasoning under a clock — sometimes paired with a personality component. For quant-developer and software roles the screen is a coding assessment instead. The common thread is filtering on speed and accuracy before any live conversation. Confirm the exact format for your role with your recruiter, since it varies by track.
Does DRW require a coding interview?
It depends on the role. Quant-developer and software-engineering seats include a real coding screen (Python, C++, or Java), usually a data, simulation, or systems task rather than abstract trick puzzles. Some quantitative-trading roles with a development lean include lighter coding, and pure-trader loops may skip it. DRW's technology organization is central to the firm, so for technical tracks the engineering bar is weighted heavily.
How does DRW market making work in the interview?
The interviewer names a quantity with a hidden value, you quote a two-sided market (bid and ask) you will trade at, and they buy or sell against you. New information then arrives and you requote, adjusting your spread to your confidence while tracking position and P&L. They grade quote quality, update speed, risk awareness, and composure. It is a repeated game about edge and information flow, not a single-answer pricing problem.
What is the difference between the DRW trader and quant/dev tracks?
The trader track front-loads mental math, probability and EV, and market-making games, with a lighter coding component. The quant-developer and software track front-loads coding, data structures, and systems thinking, with less emphasis on live market-making. Some quantitative-trading seats blend both. Ask your recruiter which track you are on so you can spend your highest-leverage prep weeks on the right skills.
Do I need a finance background to interview at DRW?
No. DRW recruits strong candidates from math, physics, computer science, statistics, and engineering, and does not require finance coursework or a graduate degree for trading seats. The filter is raw reasoning, arithmetic speed, EV discipline, and composure under pressure. Genuine curiosity about markets helps more than a finance major.
How long is the DRW interview process?
Three to eight weeks is typical: an online assessment, a recruiter conversation, a first-round interview, one or more market-making games, possibly a coding screen, and a final or superday with an offer discussion. Intern loops can compress into a single onsite day, while full-time seats that need multiple rounds scheduled take longer.
How should I prepare for DRW mental math?
Drill daily on Arithmetic Zetamac and similar timed tools — two-digit multiplication, division with decimals, percentages, and fractions, with negatives mixed in. Target a top-tier score and a fast, reliable rhythm, then keep a short timed warm-up going so the speed does not decay. Pair the arithmetic with EV drills so you can compute quickly inside a probability problem, which is where DRW most often tests it.