Citadel · Phone screen → Onsite
Not reportedCitadel SWE Intern Later Rounds and Superday: 13 Experiences
Citadel and Citadel Securities SWE intern later rounds, 2025–2026: 13 reports on order books, heaps, streams, object design and a superday.
At a glance
- Process: after the first round, two to four more 45-minute interviews (R2–R4 or a superday), each with a short resume chat and one coding or design task; some candidates then had a leadership call (07).
- Asked recently: heaps and priority queues in 3 of 13 reports (01, 02, 07), stream processing in 3 (01, 02, 05), and the BBO/NBBO order book twice (02, 06).
- Difficulty: superday tasks were called about LeetCode Medium (01); several candidates struggled with interviewer-written or open-ended tasks (08, 10, 13).
- Practise first: Exchange BBO and Market-Wide NBBO, Merge Price-Delta Feeds, Cancellable Priority Task Queue and Running Stream Medians.
Coverage: 13 Citadel and Citadel Securities SWE intern candidates (Summer 2026 and 2027 cohorts, one PhD intern), interviews from Q2 2025 to Q3 2026. Rounds after R1, superdays, and a few screens whose round number was never stated. Employer labels follow each report: 01 and 02's R3 were Citadel Securities, and 12 was Commodities Engineering.
What came up
Live market-data tasks (order books, price feeds, exchange alerts) and heap-based designs were the clearest thread. Counts are out of 13; a report can sit in several rows.
| Topic | Reports | Last seen |
|---|---|---|
| Heaps and priority queues | 3 of 13 | Q3 2026 |
| Streams and feeds | 3 of 13 | Q3 2026 |
| Stateful class APIs | 3 of 13 | Q3 2026 |
| Order books (BBO/NBBO) | 2 of 13 | Jul 2026 |
| Probability and math formulas | 2 of 13 | Q3 2026 |
| Trees and indexed sampling | 2 of 13 | Q1 2026 |
| Object design and simulation | 2 of 13 | Q1 2026 |
| Greedy and string tasks | 1 of 13 | Sep 2026 |
| Graph ordering | 1 of 13 | Q4 2025 |
| File I/O and grid metrics | 1 of 13 | Dec 2025 |
| C++, OS and data-structure knowledge | 1 of 13 | Q3 2025 |
| System and API design | 1 of 13 | Q2 2025 |
| Server scheduling | 1 of 13 | Q2 2025 |
Questions we found
Algorithms / Data Structures
| Question | Reports | Last seen |
|---|---|---|
| Exchange BBO and Market-Wide NBBO | 2 | Jul 2026 |
| Merge Price-Delta Feeds | 1 | Q3 2026 |
| Maximize Workday Earnings | 1 | Sep 2026 (report date) |
| Minimum Changes for Palindromic Blocks | 1 | Sep 2026 (report date) |
| Dynamic Weighted Sampling | 1 | Q1 2026 |
| Exchange Connection Alerts | 1 | Q1 2026 |
| Cancellable Priority Task Queue | 1 | Q1 2026 |
| Reverse File Lines | 1 | Dec 2025 |
| Department Seating Metrics | 1 | Dec 2025 |
| Binary Search Tree Operations | 1 | Q4 2025 |
| Alien Dictionary (LC 269) | 1 | Q4 2025 |
| Running Stream Medians (LC 295) | 1 | Q3 2025 |
| Find the Busiest Servers (LC 1606) | 1 | Q2 2025 |
Low-Level Design (LLD/OOD)
| Question | Reports | Last seen |
|---|---|---|
| Four-Exit Roundabout Simulator | 1 | Dec 2025 |
System Design
| Question | Reports | Last seen |
|---|---|---|
| Authenticated Shopping Platform | 1 | Q2 2025 |
Behavioral (BQ)
| Question | Reports | Last seen |
|---|---|---|
| Why Citadel? | 1 | Q2 2025 |
| Your internship project and its impact | 1 | Q2 2025 |
| A challenge you faced and how you solved it | 1 | Q2 2025 |
13 detailed candidate timelines, loops, and screens
01: A Securities superday built on heaps
Interviews: Q3 2025 · Report date: August 11, 2025 · Role: Citadel Securities Summer 2026 SWE intern · Result: Rejected after the superday
- Two days after the first technical screen, the candidate was booking three superday interviews.
- Each coding task felt about LeetCode Medium. Two were interviewer-written and not shared; the third was LC 295, medians from a data stream.
- All three solutions used min-heaps or max-heaps. The rejection came three days after the last interview.
02: An order book in R2 and a feed merge in R3
Interviews: R2 mid-July 2026, R3 Q3 2026 · Report dates: September 13 and 20, 2026 · Role: SWE intern (year not stated)
The R1 and R2 invites arrived together; this candidate's R1 is in the linked first-round post.
R2: exchange BBO and market-wide NBBO
- The order book stored exchange, price, quantity and side, with
add(exchange, price, quantity, side),get_exchange_bbo(exchange)andget_nbbo(). BBO is one exchange's best bid and ask; NBBO is the best across exchanges. - In Python: per-side dictionaries summing quantity by price, a bid max-heap and an ask min-heap per exchange, and two global heaps of
(price, exchange). Zero-quantity levels stayed in the heaps until a query popped them; global queries dropped stale tops that no longer matched an exchange's best. - The candidate called a cleaned top read constant time. Stale pops really cost amortized time, and repeated updates can leave more entries than prices. No cancel API was given.
R3: chronological price deltas (Citadel Securities interviewer)
- Merge K sorted price-delta feeds, starting at price 0 and returning the running price after each event. Ties across feeds go by feed index; within a feed, source order. Negative deltas and prices are allowed; empty feeds are skipped.
- A
heapqof(timestamp, feed_index, delta, event_pointer), one event per non-empty feed at first; each pop adds its delta, emits the price and pushes that feed's next event. O(N log K) time and O(K) heap space.
03: Summer 2027: two questions in 75 minutes
Report date: September 11, 2026 · Cohort: 2027 · Stage: Called an OA in the title and a technical phone in the details
- Maximize Workday Earnings: each workday earns fixed pay and each pair of adjacent workdays adds a bonus. Turn at most
koriginal rest days into workdays (never the reverse) to maximize the total. - Minimum Changes for Palindromic Blocks: split a password left to right into blocks of
k(the last block may be shorter) and change as few characters as possible so every block is a palindrome. This is block by block, not making the whole string periodic.
04: A PhD intern screen with deletion and probability
Interviews: Q3 2026 · Report date: September 1, 2026 · Role: PhD SWE intern · Format: Video; round not stated
- About 15 minutes on research, then a deletion-related coding task and a probability question. Neither prompt was kept.
- The Removal Pool practice version adds its own deletion indices and swap-with-last rule; the report does not confirm either.
05: A formula task that grew into MapReduce
Interviews: Q1 2026 · Report date: September 3, 2026 · Role: SWE intern ("Intern 27" in the title) · Result: Rejected
- Two back-to-back VOs, each with introductions, a resume chat, coding and the candidate's questions.
- The second 45-minute VO's coding resembled the first's supplied math formula, then moved to streaming input, a distributed version and MapReduce. The formula was not shared; the Python-only, no-libraries rule was stated for the first VO.
- An AI tool was available at some point in the VOs. Its code drew questions about its choices, and the candidate found it overcomplicated.
06: BBO and NBBO from given records
Interviews: Q1 2026 · Report date: January 28, 2026 · Role: SWE intern · Education: Master's · Result: Waitlisted, then did not advance
- About 20 minutes on the resume, in more detail than elsewhere.
- A BBO/NBBO class built from a list of
(exchange_id, price, quantity, order_type)records, withget_exchange_bbo(exchange_id) -> (best_bid, best_ask)andget_nbbo() -> (best_bid, best_ask). Noaddmethod, and no heap approach was described. - The coding felt manageable, but the candidate felt rushed to answer. Results came about a week later; they did not advance.
07: Weighted sampling, exchange alerts and a cancellable queue
Interviews: Q1 2026 · Report date: January 27, 2026 · Role: US SWE intern · Status: Passed; leadership call scheduled
The candidate labeled the rounds R2–R4; one interviewer missed a session and it was held last, so the labels may not match the calendar.
- R2: insert or delete weights and sample in proportion to the current weights. They used a Fenwick (binary indexed) tree that grows on demand, and noted the range bookkeeping when extending it.
- R3 (less certain memory): simulation and object design. Application-to-exchange links arrive in order, one app can link to many exchanges, and too many connections should raise an alert; the candidate decided when. After a hint they used a sliding window (Exchange Connection Alerts). Follow-ups: parallel and distributed processing, and several control conditions.
- R4: a cancellable priority task queue supporting insert, remove and execute, built with a priority queue and lazy deletion.
- A few days later they passed and booked a final leadership call; its outcome was not shared.
08: A BST from scratch in C++
Interviews: Q4 2025 · Report date: January 22, 2026 · Role: SWE intern · Result: Rejected
- After passing an earlier stock-profit screen, the second phone screen asked for a binary search tree class with
insert,searchanddelete. - Follow-ups: complexity, the worst case, balancing, and changes for AVL or red-black trees.
- The candidate struggled but finished the operations. No reason was given for the rejection.
09: Alien Dictionary after 20 minutes of BQ
Interviews: Q4 2025 · Report date: December 29, 2025 · Role: Summer 2026 SWE intern · Format: Technical phone; round not stated
- About 20 minutes of behavioral questions, then Alien Dictionary (LC 269).
- With one hint, the candidate finished it; there was no follow-up.
10: Three R2 sessions: a roundabout, tac and seating
Interview: December 2 (2025, inferred) · Update: January 16, 2026 · Role: SWE intern · Result: Rejected
After a C++ R1 (in the linked first-round post), three 45-minute R2 sessions brought more object design than expected.
- Session 1: after ten minutes of intro, a four-exit roundabout traffic simulator with statistics. The candidate had to frame the questions, pick a simple model, explain how it differs from real traffic and sketch the code. A misunderstanding stalled the talk, and they ended with little pseudocode.
- Session 2: print a file from its last line to its first. The interviewer kept asking for better: first O(1) extra space, then faster still. The candidate did not know the
ifstreamlength andseekgAPIs, asked whether such calls existed, and got guidance. - Session 3: after ten minutes on the resume, compare two matrices of department IDs before and after a seat move. More connected department groups and closer colleagues are better; the candidate designs the distance measure (Department Seating Metrics).
11: A knowledge round with no coding
Interviews: Q3 2025 · Report date: November 17, 2025 · Role: Summer 2026 SWE intern · Length: 45 minutes · Round: Not stated
- No programming. Questions covered memory layouts of data structures, operation complexity, properties of different trees, C++ and operating systems.
12: Commodities Engineering R2: shopping and logins
Interviews: Q2 2025 · Report date: August 22, 2026 · Role: SWE intern · Team: Commodities Engineering
- After a course-registration R1 (in the linked first-round post), R2 was to design a shopping system with user authentication, focused on system design and APIs, not coding.
- Across the process the candidate explained design choices and answered behavioral questions, including a challenge they faced and how they solved it (round not given).
13: Busiest servers in the first VO
Interviews: Q2 2025 · Report date: April 25, 2025 · Role: SWE intern · Status: Third interviewer missed the session
- A phone screen came first; the OA-to-phone invite took about five days. That task was not shared.
- VO1: introductions, an internship project and its impact, then Find the Busiest Servers (LC 1606), which the candidate did not finish.
- VO2: resume and internship again, why Citadel, and an unnamed medium-to-hard coding task that also went poorly.
- VO3 did not happen because the interviewer was absent; the recruiter said it would be rescheduled.
Patterns across the reports
- Order books twice, in two shapes. Entry 02 had live updates and local/global heaps; entry 06 got supplied records and two query methods.
- Scale-out follow-ups. Streaming or distributed follow-ups came after different tasks: the formula VO in 05 and the exchange alerts in 07.
- Heaps under the hood. Entries 01, 02 and 07 all solved their tasks with heaps or priority queues.
- Resume time before coding. Entries 06, 09, 10 and 13 spent 10–20 minutes on the resume or behavioral questions before the task.
Common questions
What is the Citadel SWE intern superday like?
Entry 01 had three interviews, each about LeetCode Medium, all solved with heaps; entry 10's three 45-minute R2 sessions leaned on object design.
Does Citadel ask order-book questions to interns?
Yes, in two reports: BBO and NBBO queries across exchanges (02, 06).
How long are Citadel intern interviews?
45 minutes per session in entries 05, 10, 11 and 13; entry 03 had two questions in 75 minutes.
How fast does Citadel reply after later rounds?
Three days after the superday in 01, about a week in 06, and a few days in 07.
Keep practicing
- Exchange BBO and Market-Wide NBBO (02, 06) and Merge Price-Delta Feeds (02).
- Dynamic Weighted Sampling, Exchange Connection Alerts and Cancellable Priority Task Queue: entry 07's three rounds.
- Four-Exit Roundabout Simulator, Reverse File Lines and Department Seating Metrics: entry 10's R2.
- Citadel question banks (sign-in needed): coding, low-level design and system design.
- Citadel interview guide and Citadel hiring insights: the stages and recent hiring signals.
- Related Citadel posts: Citadel intern and new grad first round, Citadel Securities intern first round and Citadel Securities experienced SWE.
- Experience feed: more interview reports from other companies and roles.
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.