Sources checked 2026-08-10
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.
3 of 5 stages you can practise here
Conversational recruiter call covering background, motivation, and level fit
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.
One problem in a shared editor with the interviewer watching you think
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
A pure LeetCode medium-to-hard problem-solving round
A spoken deep-dive on low-level fundamentals, C++-flavored given Citadel Securities' low-latency stack
A shorter fit conversation on how you work, handle ambiguity, and why this firm
Debrief and hiring decision. Bar is high; strong DS&A and clean, adaptable design are consistently emphasized.
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.
Official hiring process, tracks (SWE vs Quant Research), and values/competency language
New-grad/intern loop structure, online assessment, and Superday format
Level ladder and interview-process signal for SWE
Sources last checked . Hiring loops change, so this date is the honest limit on everything above.