Start free
All interview guides

Sources checked

Citadel Securities

An engineering onsite built as one real problem that keeps evolving as constraints are added, design, build, defend, extend, with the same interviewer. The point is not to defend your code, it is to evolve it.

The Citadel Securities process

3 of 5 stages you can practise here

  1. 01
    Recruiter Screen30 minchill

    Conversational recruiter call covering background, motivation, and level fit

    motivationbackground fitcommunication
  2. 02
    Online assessment (OA)

    SWE: HackerRank (occasionally CodeSignal), typically 2-3 hard algorithmic problems, ~60-90 min, strong DS&A bar. QR: heavier probability/statistics/math plus some Python. Format and vendor vary by cycle and campus.

  3. 03

    One problem in a shared editor with the interviewer watching you think

    correctnesscomplexityedge cases
  4. 04
    Onsite / Superday

    Multiple back-to-back rounds. SWE commonly: the signature 'evolving problem' coding round, one or more DS&A rounds, a systems / low-level fundamentals conversation (C++ / memory / concurrency), and a behavioral / motivation round. QR: probability & statistics deep-dive, a Python/data coding round, a stats/ML modeling conversation, and a fit round.

    4 rounds you can practise

    Citadel Securities' signature SWE round

    extensible designcode qualityadaptability

    A pure LeetCode medium-to-hard problem-solving round

    problem solvingcomplexitycorrectness

    A spoken deep-dive on low-level fundamentals, C++-flavored given Citadel Securities' low-latency stack

    low-level depthconcurrencyperformance intuition

    A shorter fit conversation on how you work, handle ambiguity, and why this firm

    ownershiphandling ambiguitycollaboration
  5. 05
    Hiring decision / committee

    Debrief and hiring decision. Bar is high; strong DS&A and clean, adaptable design are consistently emphasized.

Common questions

Is Citadel Securities the same as Citadel the hedge fund?
No. Citadel Securities is a global market maker and liquidity provider; Citadel (Citadel LLC) is a separate hedge fund. Both were founded by Ken Griffin and share a high-bar, technology-driven culture, but they are distinct firms with different (overlapping) interview loops. Software engineering exists in both; at the market maker, quant research skews toward alpha/signal and execution research.
What is the 'evolving problem' coding round?
It is Citadel Securities' signature onsite SWE round. The interviewer starts you with a small, concrete program and then keeps adding new requirements throughout the session. It tests whether you can keep your design extensible so each change is a clean, small addition rather than a rewrite, plus your debugging, testing, and communication under pressure.
How hard is the coding bar and what language should I use?
The data-structures-and-algorithms bar is high, from a hard online assessment through onsite algorithm and evolving-problem rounds. You generally code in the language you are strongest in; C++ is prominent given the low-latency stack, and Python is common for quant research coding. Expect complexity analysis and edge cases to be scrutinized, not just a passing solution.
What does the quant research loop emphasize?
Probability and statistics above all: expected-value reasoning, brainteasers, mental math, regression and model validation, and an open-ended research/modeling case, plus Python for simulation and data work. Many probability prompts are classic across the quant industry rather than unique to Citadel Securities, so practice the reasoning patterns, not memorized answers.

Sources

Built from what Citadel Securities publishes about its own process and from real interview data. No leaked question lists. The questions you get are generated against your own resume, so they are not from anyone else's interview.

Sources last checked . Hiring loops change, so this date is the honest limit on everything above.