Finance · 17 min read · ~32 min study · advanced

Citadel Interview Guide

OA to superday with real questions across quant research, trading, and software engineering.

17 min read ~32 min study advanced options #interviews#citadel 20 learning outcomes

Citadel Interview: Questions, Process & Preparation Guide 2026

Everything you need to know about interviewing at Citadel and Citadel Securities - from the online assessment to superday, with real questions across quant research, trading, and software engineering roles.

What to Expect from a Citadel Interview

Citadel interviews are among the most technically demanding in the finance industry. The process is designed to test mathematical reasoning, coding ability, and problem-solving under pressure - and it's deliberately harder than most bank interviews.

This guide covers the full process for both Citadel (the hedge fund) and Citadel Securities (the market maker), including real question types, preparation strategies, and what the interview panel actually looks for. If you're preparing for quant roles more broadly, our quant interview questions guide covers the wider landscape of firms.

Citadel vs Citadel Securities - What's the Difference?

They're separate companies with separate hiring pipelines. Citadel LLC is Ken Griffin's multi-strategy hedge fund, managing roughly $65 billion in assets. Citadel Securities is one of the world's largest market makers, handling approximately 25% of all US equity volume and around 40% of US retail equity flow.

Citadel (the hedge fund) hires quant researchers, portfolio managers, and fundamental analysts. The work centers on alpha generation - finding signals that predict asset price movements across equities, fixed income, commodities, and macro strategies.

Citadel Securities (the market maker) hires quant traders, quant researchers, and software engineers. The work focuses on market making, execution optimization, and trading infrastructure. The engineering challenges tend to involve ultra-low latency systems and real-time pricing.

In practice, Citadel Securities interviews tend to be heavier on coding and systems thinking, while Citadel hedge fund interviews lean more towards statistics, probability, and financial intuition. Both are extremely competitive - acceptance rates sit below 1% for most roles.

The Interview Process - Timeline and Stages

The full Citadel interview pipeline typically takes 4 to 8 weeks from application to offer. Here's what each stage looks like.

Stage 1: Online Assessment (OA)

You'll receive a timed online test after your CV is screened. For quant roles, this typically includes probability puzzles, mental maths, and pattern recognition questions. Software engineering candidates get a HackerRank-style coding assessment with 2 to 3 algorithmic problems in 60 to 90 minutes.

The OA is a filter - roughly 70% of candidates don't make it past this stage. Speed matters as much as accuracy.

Stage 2: Phone Screen (1-2 Rounds)

One or two 45-minute calls with team members. Expect a mix of technical questions and behavioral discussion. Quant candidates will face probability brainteasers and statistics questions. Engineers should expect live coding via a shared editor.

You'll typically hear back within a week. Some candidates report being advanced directly to the superday after a single strong phone screen.

Stage 3: Superday (Final Round)

The superday consists of 4 to 6 back-to-back interviews, each lasting 30 to 45 minutes. These are held either on-site (at Citadel's New York or Chicago office) or virtually. Each interviewer covers a different domain: probability, coding, market intuition, and behavioral fit.

Offers usually come within 1 to 2 weeks after the superday. Citadel is known for competitive compensation - first-year total comp for quant researchers in New York typically ranges from $180,000 to $150,000 with senior researchers earning significantly more.

How Interviews Differ by Role

Quant Researcher

The heaviest emphasis on mathematics. Expect questions on probability theory, stochastic processes, statistical inference, and time series analysis. You'll likely be asked to derive results on the whiteboard and explain your reasoning step by step. Familiarity with the concepts in our probability fundamentals guide is essential.

Typical split: 50% probability/statistics, 25% coding (Python), 15% finance/markets, 10% behavioral.

Quant Trader

Similar mathematical rigour but with added emphasis on decision-making under uncertainty, market microstructure, and mental arithmetic speed. You'll face rapid-fire estimation questions and scenarios where you need to price instruments or make trading decisions on the spot.

Typical split: 35% probability/brainteasers, 25% market knowledge, 25% mental maths/estimation, 15% behavioral.

Software Engineer

Focused on algorithms, data structures, and systems design. Citadel Securities engineering interviews resemble FAANG-style tech interviews but with finance-specific system design questions - think order book architecture, real-time pricing engines, or low-latency message processing. C++ knowledge is a strong advantage.

Typical split: 50% coding/algorithms, 25% system design, 15% language-specific knowledge (C++/Python), 10% behavioral.

Types of Questions Asked

Probability and Statistics

These form the backbone of any Citadel quant interview. Questions range from classic problems to multi-step scenarios that test whether you can reason formally under pressure.

Example 1: Coin sequence problem You flip a fair coin repeatedly. What's the expected number of flips to get two heads in a row?

Approach: Set up states - S0 (start), S1 (one head), S2 (two heads, done). Write the system of equations: E0 = 1 + 0.5 * E1 + 0.5 * E0, and E1 = 1 + 0.5 * 0 + 0.5 * E0. Solving gives E0 = 6 flips.

Example 2: Conditional probability You have two children. Given that at least one is a boy born on a Tuesday, what's the probability both are boys?

Approach: This is a twist on the classic Boy or Girl paradox. The sample space of (child, day) pairs matters. The answer is 13/27, not 1/3 or 1/2. Interviewers want to see you carefully enumerate the sample space rather than jump to an intuitive answer.

Brain Teasers and Estimation

Citadel still uses these, particularly for trading roles. They're testing how you structure problems and communicate your reasoning.

Example 3: Estimation question How many piano tuners are in New York?

Approach: Work top-down. New York population ~~9 million. Estimate households (~~3.5 million), fraction with pianos (~~5%, giving ~175,000 pianos), tuning frequency (once per year), time per tuning (~~2 hours including travel), working hours per tuner (~1,500 productive hours/year). That gives roughly 175,000 * 2 / 1,500 = ~230 piano tuners. The exact number doesn't matter - the framework does.

Example 4: Game theory / betting I roll a fair die. I'll pay you the face value in pounds. How much would you pay to play this game? What if you can re-roll once?

Approach: Base game: E[X] = 3.5, so you'd pay up to $330,000. With one re-roll, you'd re-roll if the first result is 1, 2, or 3 (below the expected value). Expected value becomes: 0.5 * E[X | X >= 4] + 0.5 * 3.5 = 0.5 * 5 + 0.5 * 3.5 = $500,000.

Coding Questions

Citadel expects clean, efficient code. For Python roles, they'll look at your use of standard libraries and algorithmic thinking. For C++ roles, expect questions about memory management, templates, and performance.

Example 5: Algorithm question Given a stream of stock prices arriving in real time, design a data structure that supports: (a) adding a new price, (b) querying the maximum price in the last N seconds. Both operations should be faster than O(N).

Approach: Use a monotonic deque (double-ended queue) that maintains prices in decreasing order, with timestamps. When a new price arrives, pop all smaller elements from the back. When querying the max, pop expired elements from the front. Both operations are amortised O(1).

Example 6: Python coding Write a function that takes a list of trades (each with a timestamp and price) and returns the maximum profit from a single buy-sell pair, where the buy must occur before the sell.

Approach: Single pass - track the minimum price seen so far and the maximum profit at each step. O(n) time, O(1) space. Interviewers will ask you to analyze complexity and handle edge cases (empty list, all decreasing prices).

System Design (Engineering Roles)

Example 7: Order book Design an order book that supports limit orders, market orders, and cancellations. How would you optimize for latency?

Approach: Discuss the price-time priority model, sorted data structures for bid/ask sides (balanced BST or sorted map), and the tradeoffs between memory layout and cache performance. Mention lock-free structures and memory pools for the latency discussion.

Market Knowledge and Finance

Example 8: Options pricing An at-the-money call option on a stock is priced at $500,000. The stock pays no dividends. Without doing any calculations, what can you say about the price of the corresponding put?

Approach: Put-call parity: C - P = S - K * e^(-rT). For ATM options (S = K), C - P = K(1 - e^(-rT)), which is positive but small. So the put is slightly cheaper than the call. Being able to reason through parity relationships quickly is essential.

Behavioral and Fit Questions

Example 9: Teamwork under pressure Tell me about a time you disagreed with a team member on a technical approach. How did you resolve it?

Approach: Citadel values intellectual honesty and direct communication. Describe a specific situation, what the technical disagreement was, how you presented evidence, and what the outcome was. Avoid vague answers - they want concrete details.

Example 10: Motivation Why Citadel over Two Sigma, Jane Street, or DE Shaw?

Approach: Be specific. Reference Citadel's multi-strategy approach, the particular team you're applying to, or a specific aspect of their technology or culture that genuinely interests you. Generic "prestige" answers won't impress.

How to Prepare

3-Month Preparation Timeline

Months 1-2: Build foundations

Work through probability and statistics from first principles. Sheldon Ross's A First Course in Probability and Frederick Mosteller's Fifty Challenging Problems in Probability are both excellent starting points. Our probability fundamentals resource covers the core concepts.
For coding, solve 100+ LeetCode problems focusing on arrays, trees, dynamic programming, and graph algorithms. Prioritize medium and hard difficulty.
Read at least the first 5 chapters of Mark Joshi's Quant Job Interview Questions and Answers.

Month 3: Citadel-specific preparation

Do timed practice sessions simulating the OA format - 3 problems in 90 minutes.
Practice mental maths daily (there are apps for this, or use the Trader Test questions online).
Run through mock interview scenarios with a friend or study partner, particularly for probability questions where talking through your reasoning matters.
Read Citadel's recent investor letters and public commentary. Understanding their strategy shows genuine interest.

Recommended Books

Book	Best for
Heard on the Street by Timothy Crack	Brain teasers and quant interview questions
A Practical Guide to Quantitative Finance Interviews (the "Green Book") by Xinfeng Zhou	Probability, statistics, and mental maths
Quant Job Interview Questions and Answers by Mark Joshi	Derivatives pricing and stochastic calculus
Cracking the Coding Interview by Gayle McDowell	Algorithms and data structures
Trading and Exchanges by Larry Harris	Market microstructure (essential for trading roles)

For a broader reading list, see our guide to becoming a quant which covers educational pathways and recommended resources in detail.

What Citadel Looks For Beyond Technical Ability

Strong technical skills get you through the door, but they're not sufficient on their own. Based on patterns from successful candidates and Citadel's own hiring materials, here's what separates offers from rejections at the final stage.

Speed of thought. Citadel interviews move fast. Candidates who take five minutes to start a probability problem - even if they eventually get the right answer - often don't pass. You need to recognize problem types quickly and begin structuring your approach within seconds.

Communication clarity. Interviewers want to follow your reasoning in real time. Mumbling through calculations or jumping to answers without explaining your logic is a red flag. Practice thinking out loud.

Intellectual curiosity. Do you ask good questions about the role, the team's research, or the market? Candidates who treat the interview as purely one-directional miss an opportunity to demonstrate genuine interest.

Resilience under pressure. Interviewers will push back on correct answers, introduce complications mid-problem, and test how you handle being wrong. Staying calm and adjusting your approach matters more than never making mistakes.

Collaboration instinct. Despite the competitive reputation, Citadel's quant teams are highly collaborative. They're looking for people who can debate ideas constructively without ego. If you're also considering the broader quant career path, our quantitative analyst career guide covers the skills and traits firms value across the industry.

Frequently Asked Questions

How hard is it to get an interview at Citadel?

Very competitive. Citadel receives tens of thousands of applications annually for a few hundred positions. The strongest route in is through campus recruiting at target universities (MIT, Stanford, Princeton, Harvard, Columbia, CMU, Berkeley, Caltech, Chicago, NYU) or through a referral from a current employee. Experienced hires typically need a strong track record at another top firm.

Does Citadel hire from non-target universities?

Yes, but it's harder. Citadel's online assessment is open to applicants from any university, and strong OA performance will advance you regardless of school name. That said, the reality is that campus recruiting events and on-campus interviews at target schools create more direct pathways. If you're at a non-target, an exceptional GitHub profile, competitive programming results (Codeforces, ICPC), or published research can help your application stand out.

What programming languages should I know for a Citadel interview?

For quant research roles, Python is the primary language tested. For software engineering and quant developer roles at Citadel Securities, C++ is heavily emphasized - expect questions on memory management, move semantics, and template metaprogramming. Some teams also use Java or Rust. Regardless of role, being fluent in at least one language and able to write clean code under time pressure is non-negotiable.

How does Citadel's compensation compare to other quant firms?

Citadel is consistently among the highest-paying firms in the industry. Graduate quant researchers in New York can expect a first-year package of $500,000 to $500,000 (base plus bonus). In the US, total first-year comp for similar roles is typically $200,000 to $400,000. Senior quant researchers and portfolio managers earn significantly more, with top performers reportedly earning seven or eight figures. Compensation is heavily performance-linked, with bonuses making up a large portion of total pay.

How many interview rounds does Citadel have?

The standard process has three stages: an online assessment, one or two phone screens, and a superday consisting of 4 to 6 interviews. Some candidates report additional rounds depending on the role and team. From first application to offer, the process typically takes 4 to 8 weeks, though it can move faster during peak recruiting season (September to November for graduates).

Can I reapply if I'm rejected?

Yes. Citadel's general policy allows reapplication after 12 months. If you were rejected at the OA stage, focus on improving your timed problem-solving speed. If you made it to later rounds, ask for feedback (Citadel recruiters sometimes provide it) and address specific weaknesses. Many successful candidates were rejected on their first attempt.

Want to go deeper on Citadel Interview: Questions, Process & Preparation Guide 2026?

This article covers the essentials, but there's a lot more to learn. Inside , you'll find hands-on coding exercises, interactive quizzes, and structured lessons that take you from fundamentals to production-ready skills — across 50+ courses in technology, finance, and mathematics.

Free to get started · No credit card required

Keep Reading

[Finance

50 Quant Interview Questions (With Answers) for 2026

The most common quant interview questions across probability, mental maths, coding, market making, and behavioral categories — with detailed answers and tips from real interview processes.](/quant-knowledge/finance/50-quant-interview-questions)[Finance

How to Become a Quant: The Complete Guide for 2026

A practical roadmap for becoming a quantitative analyst, developer, trader, or researcher — covering required skills, qualifications, career paths, and how to break in without a PhD.](/quant-knowledge/finance/how-to-become-a-quant)[Finance

Quantitative Analyst: Career Guide, Skills & Salaries for 2026

Everything you need to know about becoming a quantitative analyst — from the skills and qualifications required to salary expectations and career progression at banks, hedge funds, and prop trading firms.](/quant-knowledge/finance/quantitative-analyst-career-guide)[Mathematics

Probability for Quant Finance: The Essential Guide (2026)

Master the probability concepts every quant needs — expected values, distributions, Bayes' theorem, the Central Limit Theorem, and risk-neutral pricing. With financial examples throughout.](/quant-knowledge/mathematics/probability-for-quant-finance)

What You Will Learn

Explain what to expect from a pn0 interview.
Build pn0 vs pn1 __pn2__urities - what's the difference.
Calibrate the interview process - timeline and stages.
Compute how interviews differ by role.
Design types of questions asked.
Implement how to prepare.

Prerequisites

Derivatives intuition — see Derivatives intuition.
Options Greeks — see Options Greeks.
Comfort reading code and basic statistical notation.
Curiosity about how the topic shows up in a US trading firm.

Mental Model

Markets are auctions for risk. Every product, model, and strategy in this section is a way of pricing or transferring some piece of risk between counterparties — and US markets give you the deepest, most regulated, most algorithmic version of that auction in the world. For Citadel Interview Guide, frame the topic as the piece that oA to superday with real questions across quant research, trading, and software engineering — and ask what would break if you removed it from the workflow.

Why This Matters in US Markets

US markets are the deepest, most algorithmic, most regulated capital markets in the world. The SEC, CFTC, FINRA, and Federal Reserve govern equities, options, futures, treasuries, and OTC derivatives. The big buy-side (Bridgewater, AQR, Citadel, Two Sigma, Renaissance) and the major sell-side (GS, MS, JPM, Citi, BofA) hire heavily against the material in this section.

In US markets, Citadel Interview Guide tends to surface during onboarding, code review, and the first incident a junior quant gets pulled into. Questions on this material recur in interviews at Citadel, Two Sigma, Jane Street, HRT, Jump, DRW, IMC, Optiver, and the major bulge-bracket banks.

Common Mistakes

Quoting risk-free rates without saying which curve (T-bill, OIS, fed funds futures).
Treating implied volatility as a forecast instead of a market-clearing quantity.
Using realized correlation as a hedge ratio without accounting for regime change.
Treating Citadel Interview Guide as a one-off topic rather than the foundation it becomes once you ship code.
Skipping the US-market context — copying European or Asian conventions and getting bitten by US tick sizes, settlement, or regulator expectations.
Optimizing for elegance instead of auditability; trading regulators care about reproducibility, not cleverness.
Confusing model output with reality — the tape is the source of truth, the model is a hypothesis.

Practice Questions

Compute the delta of an at-the-money call on SPY with one month to expiry under Black-Scholes (σ=18%, r=5%).
Why does the implied volatility surface for SPX exhibit a skew rather than a flat smile?
Define the Sharpe ratio and explain why it is annualized.
Why does delta-hedging a sold straddle on SPY produce P&L proportional to realized minus implied variance?
What does a 100 bps move in the 10-year Treasury yield typically do to a 30-year fixed-rate mortgage rate?

Answers and Explanations

Δ = N(d1) where d1 = (ln(S/K) + (r + σ²/2)T) / (σ√T). With S=K, T=1/12, σ=0.18, r=0.05: d1 ≈ (0 + (0.05 + 0.0162)·0.0833) / (0.18·0.2887) ≈ 0.106; N(0.106) ≈ 0.542. Delta ≈ 0.54.
Because investors pay a premium for downside protection (left tail) and equity returns are negatively correlated with volatility; out-of-the-money puts therefore trade rich relative to OTM calls.
Sharpe = (excess return) / (volatility). Annualization (multiply by √252 for daily returns) puts strategies of different frequencies on comparable footing — a key requirement for comparing US asset managers.
Because the hedger captures gamma·dS² over time; integrating gives Σ gamma·(dS)², and theta paid over the life is set by implied variance. Net P&L tracks σ_realized² − σ_implied² scaled by gamma exposure.
Roughly 75-100 bps move the same direction; mortgages are priced off the 10y plus a spread that includes prepayment risk and originator margin, which both move with rates.

Glossary

Delta — first derivative of option price with respect to underlying.
Gamma — second derivative; rate of change of delta.
Vega — sensitivity of option price to implied volatility.
Theta — time decay; daily P&L from holding the option as expiry approaches.
Implied volatility — the σ that, when plugged into Black-Scholes, recovers the market price.
Skew — variation of implied volatility across strikes.
Spread — the difference between two prices; a yield curve, an option spread, or a cross-instrument arb.
Sharpe ratio — annualized excess return divided by annualized volatility; the standard performance metric in US asset management.

Further Study Path

Understanding Financial Markets — Equity, fixed income, FX, derivatives — how markets actually work and where quants fit in.
Time Value of Money — Present value, future value, discounting, NPV — the concept that underpins all of finance.
Bonds and Fixed Income — Pricing, yield to maturity, duration, convexity — the fixed-income concepts behind interest-rate modeling.
Python for Quant Finance: Fundamentals — Variables, functions, data structures, classes, and error handling — the core Python every quant role expects.
Advanced Python for Financial Applications — Decorators, generators, and context managers — the patterns that separate beginner Python from production quant code.

Key Learning Outcomes

Explain what to expect from a pn0 interview.
Apply pn0 vs pn1 __pn2__urities - what's the difference.
Recognize the interview process - timeline and stages.
Describe how interviews differ by role.
Walk through types of questions asked.
Identify how to prepare.
Articulate what pn0 looks for beyond technical ability.
Trace interviews as it applies to pn0 interview guide.
Map pn0 as it applies to pn0 interview guide.
Pinpoint how pn0 interview guide surfaces at Citadel, Two Sigma, Jane Street, or HRT.
Explain the US regulatory framing — SEC, CFTC, FINRA — relevant to pn0 interview guide.
Apply a single-paragraph elevator pitch for pn0 interview guide suitable for an interviewer.
Recognize one common production failure mode of the techniques in pn0 interview guide.
Describe when pn0 interview guide is the wrong tool and what to use instead.
Walk through how pn0 interview guide interacts with the order management and risk gates in a US trading stack.
Identify a back-of-the-envelope sanity check that proves your implementation of pn0 interview guide is roughly right.
Articulate which US firms publicly hire against the skills covered in pn0 interview guide.
Trace a follow-up topic from this knowledge base that deepens pn0 interview guide.
Map how pn0 interview guide would appear on a phone screen or onsite interview at a US quant shop.
Pinpoint the day-one mistake a junior would make on pn0 interview guide and the senior's fix.