Interview Playbook / Quant Trading & Hedge Funds

How Citadel Interviews in 2026: Process, Questions & What They Score

HOW TO READ THIS PLAYBOOK

Compiled from 34 public sources: candidate interview reports, coaching guides, and Citadel's own hiring pages. Interview processes change and vary by role, team, level, and region. This is one well-documented shape of Citadel's interviews to prepare against, not a script of what your interview will be. Confirm specifics with your recruiter. SupaCV is not affiliated with or endorsed by Citadel.

Medium confidenceLast verified JUL 202634 sourcesSources

Important disambiguation: "Citadel" the hedge fund (multi-strategy, founded by Ken Griffin) and "Citadel Securities" (the market-making/electronic-trading firm) are affiliated but distinct entities with separate but structurally similar hiring processes; job postings and career-perspective pages are published under both citadel.com and citadelsecurities.com. ("The Citadel" military college in South Carolina is an unrelated institution that surfaces in searches, but is not the subject of this report.) Correction to a common misconception: both firms DO publish a named, titled core-values framework on their "Our Culture" pages; it's just not branded or structured like Amazon's numbered Leadership Principles, and there's no public evidence it's used as a formal per-interviewer scoring rubric. Citadel (the fund) names five values: Integrity, Winning, Meritocracy, Learning, and Extraordinary Colleagues, under a "Guided by Our Core Values" framing; Citadel Securities names six: the same five plus Mutuality. Both pages also open with the shared tagline "The Best Idea Wins" (contribution matters regardless of title or tenure), presented as a philosophy rather than a numbered value. The process differs meaningfully by track (Software Engineering, Quantitative Research, Quantitative/Discretionary Trading, and internship programs like Launch and the Data Open datathon), and specifics (number of onsite rounds, use of online coding tests, presentation of past work) vary by team, desk, seniority level, and even between the two entities. Notably, Citadel (the fund, not Securities) has stated through its own head of graduate recruitment that it skips automated "scaled" coding tests for many quant candidates in favor of an all-human interview loop, while Citadel Securities and quant/trading-track candidates elsewhere more consistently report HackerRank-style online assessments. Also note that Citadel's own official interview-process pages describe a simplified ~4-step framework (first interview, panel/superday, team-match, offer) and don't separately break out a recruiter screen or online assessment by name; the more granular stage list below layers in those steps from consistent third-party candidate reports (Glassdoor, Wall Street Oasis, prep guides). Treat all round counts and timelines below as typical ranges reported by multiple sources, not fixed guarantees.

The Process

  1. 1

    Resume/application screen · Ongoing/rolling; days to a couple weeks

    Selective, fast initial screen. Recruiters and referrals matter; for engineering, reviewers look for evidence of technically demanding work (systems coursework, performance-critical internships, competitive programming) rather than generic software experience. For quant roles, strong quantitative pedigree (math/physics/CS/stats, competition results, research) is weighted heavily.

  2. 2

    Recruiter phone screen · 15-30 minutes

    Short introductory call covering background, motivation, logistics, and general fit; not deeply technical. Not separately named on Citadel's own official process pages, but consistently reported by candidates ahead of the first technical round.

  3. 3

    Online assessment (OA) · 60-120 minutes when it applies

    Not universal: reports diverge by entity and track. For engineering: commonly a timed HackerRank/CoderPad test with 2-3 algorithmic/data-structure problems (arrays, trees, graphs, DP), often around 60-90 minutes, with a competitive bar (hidden test cases, limited partial credit). For quant research/trading: Citadel Securities and many quant/trading-track candidates describe a HackerRank-style test mixing Python coding with probability, statistics, and quantitative-reasoning questions (roughly a 2-hour, mid-to-hard-LeetCode-difficulty test); however, Citadel (the hedge fund) has publicly said it skips this kind of automated test for many quant candidates, relying instead on human-led interviews. Confirm with your recruiter whether an OA applies to your specific role.

  4. 4

    Technical phone screen(s) · 45-60 minutes per call

    One (sometimes two) 45-60 minute video/phone interviews with a team member or engineer/researcher/trader. Engineering: coding, data structures/algorithms, problem-solving, plus questions about technical interests, past projects/internships, and motivation for Citadel. Quant/trading: probability and statistics problems solved out loud, sometimes paired with light coding (Python or C++) or a take-home modeling exercise; 2-3 problems mixing brainteasers, expected value, and applied trading scenarios are typical.

  5. 5

    Onsite / virtual superday · Half a day to a full day (3-5 hours of interviewing)

    The core loop: typically 3-5 back-to-back interviews (45-60 minutes each) assessing technical depth and behavioral/fit. Engineering supersets: 3-4 rounds of coding/data structures, with more senior candidates also getting system design, low-latency, and concurrency questions. Quant research/trading supersets: additional probability/stats/brainteaser rounds, sometimes a case study or a request to present a past research project in real time, and for trading roles a market-making/trading simulation game (candidate quotes bid-ask prices as the interviewer or a group of candidates reveal new information, managing simulated P&L) run individually or in small groups.

  6. 6

    Team-match / hiring-manager round · 45 minutes per team; can mean 1-3 extra calls

    After the core loop, hiring managers across teams review resume and interview feedback to decide team fit; if a team is interested, a further 45-minute conversation follows, probing a specific resume project in real depth (what was built, why specific decisions were made, what went wrong, what they'd change) plus behavioral/culture-fit questions. If multiple teams are interested, candidates may do more than one such round.

  7. 7

    Final round / senior leader or PM conversation · 30-45 minutes, plus internal committee review time

    Some candidates (particularly quant research/PM-track roles) have a final conversation with a senior portfolio manager or business leader focused on fit, judgment, and long-term career goals, followed by an internal hiring-committee review of all feedback before an offer decision.

Evaluation Framework

Named core values exist, but not an Amazon-style numbered interview rubric

Citadel (the hedge fund) names five core values under a "Guided by Our Core Values" framing on citadel.com/who-we-are/our-culture: Integrity, Winning, Meritocracy, Learning, and Extraordinary Colleagues.Citadel Securities names six core values on citadelsecurities.com/who-we-are/our-culture: the same five plus a sixth, Mutuality (partnering with clients/counterparties so that "our success is their success").Both culture pages also open with a shared guiding tagline, "The Best Idea Wins" (contribution matters regardless of title or tenure), presented as a philosophy, not a seventh named value.These are real, consistently repeated across both firms' own materials (and echoed piecemeal in secondary sources like Built In), so a claim that no named framework exists at all would be incorrect.What remains true: there is no public evidence Citadel or Citadel Securities map specific interviewers to specific values the way Amazon assigns Leadership Principles per interviewer, and no evidence interview scorecards are explicitly organized around these labels. For engineering specifically, a Citadel Securities engineering leader has been quoted on the careers site emphasizing "a willingness to learn, understand, and grow" given a constantly changing environment, consistent with the "Learning" value but not a separate framework.

Know these values cold: Integrity, Winning, Meritocracy, Learning, Extraordinary Colleagues, and (Citadel Securities only) Mutuality, and be ready to illustrate each with a real story, especially meritocracy/ownership and learning/adaptability, which come up constantly in behavioral rounds. But don't expect, or perform, an Amazon-style loop where each interviewer is visibly grading you against one labeled value; weave the themes into your stories naturally rather than name-dropping the values verbatim.

Sample Interview Questions

Probability, statistics & quant brainteasers (Quant Research / Quant Trading tracks)8 questions
  • Classic conditional-probability/Bayes' rule problems (e.g., disease-testing or similar base-rate scenarios).
  • Place three dots at random along the four edges of a square: what is the probability the dots lie on three distinct edges? (A classic puzzle that circulates across quant firms, including Citadel and Jane Street; don't assume it's exclusive to one shop.)
  • 10 people are in a room and everyone shakes hands with everyone else once: how many total handshakes?
  • Markov chain / random walk problems (e.g., expected number of steps to reach an absorbing state).
  • Explain the bias-variance tradeoff, and when/why you would apply regularization (L1 vs L2) in a regression model.
  • Walk through linear regression assumptions, and how you would detect and handle data leakage or overfitting in a model.
  • Mental-math drills done under time pressure (e.g., quickly factoring or determining primality of a multi-digit number, computing expected values or odds in your head while narrating each step).
  • Law-of-total-probability / geometric-series style problems that build on a simpler Bayes' rule question.
Coding & software engineering (Software Engineer track)6 questions
  • Find Median from a Data Stream: implement using two heaps (max-heap for the lower half, min-heap for the upper half).
  • Implement a fixed-capacity ring buffer (e.g., in C++) for a single-producer, multiple-consumer setting.
  • Design a system to maintain the running top-K elements over a large data stream.
  • Find the shortest path in a graph under additional constraints (e.g., limited edge weights or a budget/step cap).
  • Standard LeetCode medium-to-hard problems on arrays, trees, graphs, and dynamic programming, with follow-up questions on time/space complexity and edge cases.
  • For more senior/experienced candidates: system-design questions involving low-latency systems and concurrency (e.g., designing a component of a trading system that must handle high-throughput, low-latency data).
Trading-floor / market-making simulation (Quant Trader track)4 questions
  • Live market-making game: the interviewer (or a group of candidates) reveals incremental information about an unknown quantity or asset; the candidate must continuously quote bid-ask prices and manage simulated P&L as new information arrives.
  • "Market of Cards": a group market-making exercise specifically reported in Citadel Securities' superday, where candidates must communicate and coordinate pricing decisions with peers under time pressure.
  • 'Make me a market' / guesstimate exercises: quickly frame and price an uncertain quantity (e.g., a Fermi-style estimation) and defend the spread you'd quote.
  • Explain how implied volatility and time to expiration affect the price of both calls and puts, and other options-pricing intuition checks embedded in trading-scenario questions.
Behavioral & fit (all tracks)7 questions
  • Tell me about a time you had to communicate a technically complex result to a non-technical stakeholder.
  • Describe a disagreement within your team and how you resolved it.
  • Walk me through a difficult technical decision where you weighed competing tradeoffs: what did you decide and why?
  • Tell me about a project you owned end-to-end; be ready to go deep: what exactly did you build, why did you make specific design choices, what went wrong, and what would you change in retrospect?
  • Tell me about a time you worked in a fast-paced or high-pressure environment.
  • Describe a time you failed or made a mistake: how did you realize it, communicate it, fix it, and what changed afterward?
  • Why Citadel / why this desk or team, and what are your long-term career goals? (often asked in the final senior-leader conversation)

Coach's Tips

Narrate your reasoning step by step on quant/probability problems rather than computing silently and blurting a final number; multiple sources report that candidates who show their work score better than those who arrive at the same correct answer silently.

For any 'tell me about a project' question, prepare to go far deeper than a generic tech-company answer: interviewers pick a specific resume project and drill into why you made specific technical decisions, what broke, and what you'd change; surface-level summaries do not hold up.

Structure behavioral answers so most of your airtime goes to the 'action' section, told in first person ('I', not 'we'): a brief situation/task, most of the story on your specific decisions and judgment calls, then a clear result. Candidate accounts consistently describe interviewers probing for individual ownership and reasoning, not just team outcomes, so don't let your specific contribution hide inside a group narrative, but treat this as a general shape to aim for, not a fixed formula or timed script.

For trading roles, treat the market-making/trading game (including group formats like 'Market of Cards') as a real skill to rehearse with a partner or coach in mock sessions weeks in advance rather than something you can prep by reading about it; several prep sites emphasize live practice as the differentiator.

Confirm which programming language is acceptable before the technical rounds; some candidates have reported being told Python was fine but then being pushed toward C++ in the actual interview, so clarify expectations with the recruiter beforehand.

Don't assume there's no values framework to prepare against: Citadel and Citadel Securities do name theirs (Integrity, Winning, Meritocracy, Learning, Extraordinary Colleagues, and for Citadel Securities, Mutuality). Ground your fit answers in genuine stories that naturally demonstrate ownership, rigor under pressure, direct/accountable communication, and comfort in a fast-changing environment; reciting 'I demonstrated meritocracy' will read as coached, while a concrete story that happens to show meritocratic thinking will land.

Ask your recruiter early whether your specific role/track includes a formal online assessment: reports genuinely diverge (Citadel the hedge fund has said it skips automated coding tests for many quant candidates, while Citadel Securities and other quant/trading candidates more often report a HackerRank-style test), so don't over- or under-prepare based on one prep site's description.

Common questions

How many stages are in Citadel's interview process?+

Citadel's process has 7 stages, in order: Resume/application screen, Recruiter phone screen, Online assessment (OA), Technical phone screen(s), Onsite / virtual superday, Team-match / hiring-manager round, Final round / senior leader or PM conversation.

What framework does Citadel use to evaluate candidates?+

Citadel evaluates candidates against Named core values exist, but not an Amazon-style numbered interview rubric: Citadel (the hedge fund) names five core values under a "Guided by Our Core Values" framing on citadel.com/who-we-are/our-culture: Integrity, Winning, Meritocracy, Learning, and Extraordinary Colleagues., Citadel Securities names six core values on citadelsecurities.com/who-we-are/our-culture: the same five plus a sixth, Mutuality (partnering with clients/counterparties so that "our success is their success")., Both culture pages also open with a shared guiding tagline, "The Best Idea Wins" (contribution matters regardless of title or tenure), presented as a philosophy, not a seventh named value., These are real, consistently repeated across both firms' own materials (and echoed piecemeal in secondary sources like Built In), so a claim that no named framework exists at all would be incorrect., What remains true: there is no public evidence Citadel or Citadel Securities map specific interviewers to specific values the way Amazon assigns Leadership Principles per interviewer, and no evidence interview scorecards are explicitly organized around these labels. For engineering specifically, a Citadel Securities engineering leader has been quoted on the careers site emphasizing "a willingness to learn, understand, and grow" given a constantly changing environment, consistent with the "Learning" value but not a separate framework..

What kinds of questions does Citadel ask?+

Citadel's question bank spans 4 categories: Probability, statistics & quant brainteasers (Quant Research / Quant Trading tracks); Coding & software engineering (Software Engineer track); Trading-floor / market-making simulation (Quant Trader track); Behavioral & fit (all tracks).

How reliable is this Citadel interview playbook?+

This playbook is medium confidence, compiled from 34 public sources, and last verified July 7, 2026. It describes one well-documented shape of Citadel's interviews, not a guarantee of what any individual loop will look like.

Sources

Interviewing at Citadel?

Add it as a Target Role and tailor your resume against the actual job description.

Add Citadel as a Target Role