Citadel Securities Quant Interview Math Prep

There isn't one published "Citadel math test" to reverse-engineer. The process changes by role, and internet accounts tend to blur together Citadel, Citadel Securities, research, trading, and software interviews.

This guide keeps three buckets separate: what the firm says, what candidates report, and what we recommend for practice.

What Citadel officially says

Citadel's quantitative research interview process page, dated November 9, 2024, describes four steps. It says the process typically takes four to five weeks. The first round is a 45–60 minute remote interview covering technical and behavioral skills, including programming, research ability, data structures and algorithms, and problem solving. The second round is usually three to five 60-minute onsite interviews (Citadel process guide, verified August 12, 2026).

The same guide tells candidates to pause before solving, ask clarifying questions, explain their thinking, discuss trade-offs, and ask for a hint when stuck. That is a strong case for practising how you communicate. It is not proof of a universal arithmetic screen.

Citadel's quantitative-research FAQ says math and statistics are foundational, and that candidates should have statistical intuition. It lists probability and statistics, data analysis, programming, and problem solving among strong-candidate signals (Citadel QR FAQ, verified August 12, 2026).

Role-aware preparation

What is reported, and what is not

Prep sites and candidate discussions mention mental arithmetic, probability, expected value, and online assessments for some trading roles. Those accounts may be useful, but they aren't universal Citadel policy. Formats can change with the role, region, team, and recruiting cycle. We found no official current question count, timer, penalty rule, or pass score.

That makes for a less satisfying headline, but a more useful guide. An anecdote from one internship cycle should not dictate how a software engineer or a quantitative researcher spends the week before an interview.

Representative math practice

Start with these three checks. They are representative training questions, not official Citadel questions.

▸Expected value

A payoff has a 40% chance of +30 and a 60% chance of −10.

0.40 × 30 + 0.60 × (−10) = 12 − 6 = +6

Answer: +6 expected value, before costs, risk limits, or model uncertainty.

▸Probability complement

If failure probability is 0.18, success is 1 − 0.18 = 0.82, or 82%.

▸Basis-point conversion

Investor.gov defines one basis point as 0.01 percentage point. Therefore 25 × 0.01% = 0.25%, so 25 bps = 0.25% (Investor.gov glossary, verified August 12, 2026).

A practical routine

Wall St Math can train the arithmetic layer. It can't substitute for probability, coding, research, or a good conversation about your own work.

1. ▸Run a short arithmetic set and note errors, not just the total.
2. ▸Redo five examples from the slowest pattern.
3. ▸Solve one expected-value problem and state your assumptions aloud.
4. ▸Practice one role-specific coding or data question from the official job process.
5. ▸End with a two-minute explanation of a project and its business impact.

Use Sprint for a fixed arithmetic contract or Drill Setup for general practice. Neither is a Citadel assessment simulator.

What official sources do not establish

The official sources we reviewed don't establish a universal Citadel "online assessment," a required Zetamac score, a cutoff in the 60s, or any number that guarantees an offer. Wall St Math isn't affiliated with Citadel.

How preparation changes by role

Citadel publishes useful detail about quantitative research. The lazy move would be to copy those requirements into every Citadel and Citadel Securities role. We won't do that.

Open the current page for your role and note the location, date, and stated process. A quant-research intern and a software engineer may apply to the same brand and still face very different interviews.

The communication layer

The official guidance keeps coming back to thought process, clarifying questions, trade-offs, and asking for hints. You can rehearse that without pretending to know the questions:

1. ▸Restate: "I am calculating expected payoff before costs."
2. ▸Choose a route: "I will use 40% of 30 minus 60% of 10."
3. ▸Compute: 12 − 6 = 6.
4. ▸Qualify: "That is positive expected value under the stated probabilities."
5. ▸Invite the next condition: "I would update if the probability or payoff changed."

Don't memorize the wording. The point is to stop arithmetic, assumptions, and interpretation from collapsing into one unexplained number.

Ten questions to work aloud

These questions are Wall St Math training recommendations, not leaked or official Citadel questions. Answers were recomputed independently.

1. ▸A 30% chance of +20 and 70% chance of −5: 0.3×20 − 0.7×5 = 6 − 3.5 = 2.5. Answer: +2.5.
2. ▸A 55% chance of +12 and 45% chance of −9: 6.6 − 4.05 = 2.55. Answer: +2.55.
3. ▸Odds 3:2 in favor: 3 ÷ (3+2) = 3/5. Answer: 60%.
4. ▸Failure probability 0.27: 1 − 0.27. Answer: 73% success.
5. ▸A rate rises from 4.0% to 4.4%: difference 0.4 percentage point = 40 bps.
6. ▸18% of 250: 0.10×250 + 0.08×250 = 25 + 20. Answer: 45.
7. ▸A quote is 98 bid / 106 ask: midpoint (98+106)/2 = 102, spread 106−98 = 8. Answer: midpoint 102, spread 8.
8. ▸Fair value 102 moves up 25% of an 8-point spread: 0.25×8 = 2; new value 104.
9. ▸A 15% estimate on 320: 0.10×320 + 0.05×320 = 32 + 16. Answer: 48.
10. ▸A sample rises 75 to 84: change 9; 9 ÷ 75 = 0.12. Answer: 12% increase.

After each answer, say what the number means and name one assumption that could change it. A correct number with no unit is only half an answer.

Fourteen-day plan

Use Drill Setup for general practice or Sprint for a fixed arithmetic contract. The timer creates pressure. It doesn't turn the set into a replica of an undisclosed employer assessment.

What we checked

2026-08-12: We checked the official Citadel pages and found no universal Zetamac-style test, cutoff, or score. If those pages change, this article should change with them. A fresh date on old evidence would be worse than leaving the original date alone.

How to read the official process without overclaiming

The official process article is useful for an unglamorous reason: it tells you how to behave when solving a problem. "Assess the problem," "ask clarifying questions," and "share your thought process" are all things you can rehearse. None tells us that an arithmetic sprint appears in every first round.

The four-to-five-week timeline is described as typical, not guaranteed. If you have another deadline, tell the recruiting contact, as the page suggests. Don't assume every application moves on the same clock.

Role-specific practice blocks

▸Quantitative research

Spend one block on arithmetic and probability, another on a data or modeling question, then explain a research project. For the project, cover the hypothesis, data, validation, failure mode, and what changed after feedback. That matches the FAQ's emphasis on applied research without pretending Citadel handed us a script.

▸Quantitative trading or investing

Use short expected-value, odds, percentage, and estimation prompts. Then change one assumption and update the conclusion. That is closer to the reasoning in the public materials than memorizing the score ranges of a named arithmetic game.

▸Quantitative development and software engineering

Keep arithmetic in the warm-up. Use the current role page for algorithms, coding, debugging, or systems expectations. A quant-research FAQ cannot establish a software-engineering requirement. If you're applying for software, spending less time on mental math may be the right call.

Six more questions when the first set feels easy

Again, these are representative training, not official questions:

1. ▸A 20% chance of +40, 50% chance of +4, and 30% chance of −20: 8 + 2 − 6 = 4. EV = +4.
2. ▸Odds 5:3 against: favorable probability 3 ÷ (5+3) = 3/8. Answer: 37.5%.
3. ▸A 12% rate on 750: 0.10×750 + 0.02×750 = 75 + 15. Answer: 90.
4. ▸A 2.4% rate is 240 bps because 2.4 × 100 = 240. Answer: 240 bps.
5. ▸A fair value of 80 increases 15%: 80 × 0.15 = 12; new value 92.
6. ▸A payoff of 18 with probability 0.65 and loss 11 with probability 0.35: 11.7 − 3.85 = 7.85. EV = +7.85.

For each, say whether the result is exact or approximate and identify a missing cost, risk, or data assumption.

How to use candidate reports

Attach a date, role, and geography to every third-party account. A 2024 report about a summer trading internship is not a 2026 global policy. When reports conflict, your official invitation wins.

Interview-day checklist

• ▸Confirm the role and interview stage.
• ▸Ask what units, rounding, and tools are permitted.
• ▸State assumptions before calculating.
• ▸Keep intermediate values visible in speech.
• ▸If stuck, ask a clarifying question or request a hint, consistent with the official guidance.
• ▸Review the answer for sign, units, and reasonableness.

A mock interview structure

This 45-minute mock gives you enough time to practice the transitions between math, technical work, and conversation. It is not a prediction of Citadel's process:

• ▸5 minutes: summarize the role and ask what assumptions are permitted.
• ▸15 minutes: solve three arithmetic/probability prompts aloud.
• ▸15 minutes: discuss one project, including a failed approach and a revised approach.
• ▸5 minutes: answer a data or coding question appropriate to the role.
• ▸5 minutes: review signs, units, and communication gaps.

Adjust the mix to the job description. A research candidate may need more time on data; a developer may need more coding. The only universal part is that this mock isn't the firm's interview.

How to handle uncertainty in a live prompt

The first calculation is rarely the interesting part. The prompt gets harder when one input changes and you have to update without starting over:

1. ▸State the original result.
2. ▸Identify which input changed.
3. ▸Recompute only the affected term.
4. ▸Say whether the direction of the conclusion changed.

If the +30 payoff in the first example falls to +20, EV changes from 0.4×30 − 0.6×10 = +6 to 0.4×20 − 0.6×10 = +2. The simplified answer is still positive, just less so. You changed one term instead of rebuilding the problem. That is the habit to practice.

What "finance can be taught" means

The QR FAQ says Citadel can teach finance while expecting strong mathematical and statistical foundations. That doesn't mean market vocabulary is useless. A sensible split is:

• ▸learn enough market language to state what a quantity represents;
• ▸drill the arithmetic needed to manipulate it;
• ▸practice explaining what would make the estimate unreliable;
• ▸use the role description to decide how deeply to study finance.

For a physics, mathematics, or computer-science candidate, that is a manageable starting point: enough market language to explain the quantity, then more depth where the role demands it.

Before you stop

Before you stop, ask: Did I answer the question that was actually asked? Is the sign right? Did I give the unit? Is this exact or estimated? What would change the conclusion? That check travels well across research, trading, and investing interviews. A fabricated score target does not.

Dates matter here

The sources below are dated because interview pages change. When an official page changes, the related paragraph and citation should change together. A new candidate anecdote belongs in the reported bucket; it shouldn't quietly rewrite the employer's documented process.

Sources and verification

• ▸Citadel quantitative research interview process - official, dated 2024-11-09; checked 2026-08-12.
• ▸Citadel quantitative research candidate FAQ - official, dated 2024-11-09; checked 2026-08-12.
• ▸Citadel investing candidate FAQ - official; checked 2026-08-12.
• ▸Wall St Math feature details - verified against the August 12, 2026 product build.