← Back to Directory

Citadel

Large Enterprises

Most of these Citadel write-ups come from Software Engineers (79). The most reported rounds are the technical phone screen (62), the system design round (12), the behavioral / leadership round (2) and the onsite coding round (2).

79 interview notes · updated Jun 2026

Citadel·Software Engineer·Technical Phone Screen

Jun 2026
Citadel quant researcher interview where the main event is a deep dive into your prior research. They want everything: motivation, what you personally did vs. your collaborators, methods, failures, results, and where the work would go next. The follow-up questions are not gentle.
  • Walk through a past research project in depth: what was the research question, what motivated it, and what was your specific contribution versus what your collaborators did?
  • What was the most surprising finding from your research, and how did it change your understanding of the problem?
  • Describe something that failed during your research and how you adapted your approach as a result.
  • What are the key technical or theoretical results of your research, and how would you defend the methodological choices you made?
  • What is the real-world impact or publication outcome of your research, and how do you assess its significance?
  • If you were to continue this line of research, what would you do next and why?

“This is where people get tripped up.”

View Post

Citadel·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Citadel quant engineer interview that focused entirely on designing an orderbook from scratch. No matching logic needed, but they wanted a real API proposal with justification before touching any code, which tripped me up a bit at first.
  • Design and implement an orderbook for a trading system. Start by proposing the API surface (place order, cancel order, query orders, best bid/ask, etc.) with justification, then implement it in code. Order matching is out of scope; focus on data structures, API design, and keeping the book consistent.

“I jumped straight to data structures before they even asked me to, which was a mistake.”

View Post

Citadel·Software Engineer·Technical Phone Screen

Jun 2026
Citadel software engineer round, started with the usual intros and then jumped straight into pair coding. The problem was an order book design, which felt pretty standard for a trading firm but still required some careful thinking about constraints.
  • Design and implement a traditional order book system.

“Spent a bit of time upfront clarifying what they actually wanted before touching any code, which felt right.”

View Post

Citadel·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Citadel software engineer interview that covered a resume walkthrough and a behavioral conflict question. Nothing too surprising but the behavioral piece required more structure than I expected going in.
  • Walk me through your resume, focusing on the projects and decisions most relevant to this role.
  • Tell me about a time you had a conflict with a teammate. What was the situation, what did you do, and how did it turn out?

“I rambled a bit connecting projects together instead of just picking two or three and going deep.”

View Post

Citadel·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Citadel SWE interview with a system design question focused on scheduling. Pretty clean problem but the follow-up on deletion tripped me up more than I expected.
  • Design a task scheduler that supports inserting tasks with a priority, deleting previously inserted tasks, and executing the next task in scheduling order.

“I jumped straight to a min-heap for insert and execute, which was fine.”

View Post

Citadel·Software Engineer·Technical Phone Screen

Jun 2026
Citadel software engineer interview, got a stock trading problem that looks easy until you actually have to explain your reasoning out loud to someone who clearly knows the answer already.
  • Given an array of daily stock prices, find the maximum profit you can make by buying and selling as many times as you want, with the constraint that you must sell before buying again.

“My first instinct was to overcomplicate it.”

View Post

Citadel·Software Engineer·Technical Phone Screen

Jun 2026
Citadel software engineer interview that focused on graph problems, specifically course scheduling with topological sort. Pretty algorithmic heavy, no fluff.
  • Given a list of courses and their prerequisites, return a valid ordering in which all courses can be completed. If no valid ordering exists due to a cycle, return an empty array.

“Knew this was topological sort the second I read it, which was a relief.”

View Post

Citadel·Software Engineer·Technical Phone Screen

Jun 2026
Citadel software engineer interview with a classic dynamic programming stock problem. Pretty standard as far as quant shop coding rounds go, though the pressure of the setting made even a familiar problem feel a bit trickier than it should.
  • Given an array of daily stock prices, find the maximum profit from at most one buy-sell transaction. Return 0 if no profit is achievable.

“I've done this problem before so I wasn't totally lost, but I second-guessed myself on the edge cases (all decreasing prices, single element array) and spent more time than I should have explaining things out loud before writing any code.”

View Post

Citadel·Software Engineer·Technical Phone Screen

Jun 2026
Citadel SWE interview that went deep on range minimum queries, covering basically every implementation you can think of plus a sliding window variant. Felt like a data structures lecture but with someone watching you sweat.
  • Given an array of integers, implement range minimum queries supporting rmq(l, r). Walk through multiple approaches and their trade-offs in terms of build time, query time, memory, and whether they support updates.
  • Now implement the segment tree version for range minimum queries in code.
  • How would you handle range minimum queries over a sliding window of fixed size k as the window moves across the array?

“This one sprawled.”

View Post

Citadel·Software Engineer·Technical Phone Screen

Jun 2026
Citadel quant engineer interview that went deep on alpha model training, the kind of question where knowing the vocabulary isn't enough and they want to see if you actually understand why each choice matters for live PnL.
  • Walk me through how you train an alpha model end to end: how you define the target, what loss function you use, how you handle feature standardization, how you set up your train/validation split, and how you make sure the training objective actually connects to the PnL metric you care about in production.

“This is a single question that ate up most of the interview.”

View Post

Citadel interview FAQ

What rounds are in the Citadel interview?

Candidates most often report a technical phone screen (62 write-ups), a system design round (12), a behavioral / leadership round (2) and an onsite coding round (2).

What does the Citadel technical phone screen cover?

Across 62 technical phone screen write-ups, the most tagged question topics are Technical Trade-offs (78 questions), Algorithms & Data Structures (65) and System Design (36).

What is asked in the Citadel system design round?

Across 12 system design write-ups, the most tagged question topics are System Design (17 questions), Technical Trade-offs (14) and Algorithms & Data Structures (8).