Citadel Interview Process & Rounds

Citadel's loop spans 6 round types: Usually 45 minutes to an hour: resume questions, then one coding problem, often with staged follow-ups. Merging K sorted lists or feeds, stock trading DP, LRU cache, topological sort and trapping rain water lead the reports. An SRE screen was five short Python functions followed by a verbal design question., Campus intern and new-grad loops: two coding problems in 75 minutes on HackerRank. The k-periodic palindrome, the four-way array split, the hackathon team, the prefix/suffix match score and distinct palindromic substrings recur. NXT and backend loops: eight to fifteen multiple-choice questions on caching, locks, message queues, proxies, complexity and debugging, plus coding, most often the earliest free meeting slot; the two most recent reports list two coding problems., Intern final rounds are usually three 45-minute interviews, each a short resume segment and one problem; one candidate says medium-level problems are rare. Intern technical rounds reported in 2026 include an order book with exchange BBO and NBBO, merged price feeds and a deduplicating file system. Citadel Securities onsites for experienced engineers run longer: one described four one-hour rounds in a day, with a second day for those who pass; another listed a design round, two hours of coding, a code review and a project deep dive., Resume deep dives that ask why each design choice was made, and fundamentals questions that often need no code, such as implementing tail on a very large file or, for frontend roles, JavaScript promises, Map versus WeakMap and message ordering over WebSockets., Asked on some screens as well as onsites: a metrics and alerting system, e-commerce inventory with pessimistic and optimistic concurrency control, a stock price tracking service, and configuration and deployment at scale with rollback. One commodities engineering intern loop was two design rounds on schema and APIs with no coding., Mostly folded into the screens: why finance, why Citadel, your most challenging or most impactful project, and why you are leaving your current job. One Citadel Securities candidate was told the onsite ends with a behavioral round..

Citadel's software loop varies more by role and by firm than most. The forum label covers both Citadel and Citadel Securities; one forum reply says the two recruit through the same process and only separate at team match, and another was asked in the screen what the difference between them is. Campus intern and new-grad candidates usually start with a HackerRank assessment of two coding problems in 75 minutes, then a 45-minute technical screen, then a final round of three 45-minute interviews. Experienced candidates on the NXT backend track report a HackerRank assessment that mixes multiple-choice questions on caching, locks, message queues, complexity and debugging with a coding problem, most often finding the earliest free meeting slot. Screens often spend 10 to 30 minutes on your resume before one coding problem, and one candidate found the resume questions more detailed than at other companies while another found them more stressful than the coding. The problems lean toward trading-flavoured data structures, such as order books with best bid and offer, merging sorted price feeds, LRU caches and ring buffers, alongside standard LeetCode problems. Citadel Securities reports frequently specify C++, and its experienced-hire onsites run as a day of four or five one-hour rounds; one candidate describes being sent home partway through the day. Frontend candidates report JavaScript fundamentals and a React trade-event dashboard.

It's reconstructed from candidate reports spanning Jan 2025 – Sep 2026 and refreshed monthly as new reports come in.