Katkat

Company

Citadel interview questions

90 practice questions in the style of Citadel's interviews, covering Machine Learning, Software Engineering Fundamentals, ML System Design, Statistics & Math, Coding & Algorithms, Behavioral & Leadership, System Design, Analytics & Experimentation.

Questions90

9 easy61 medium20 hard

Your progress0/90

Citadel interview questions by the numbers

Last updated

Katkat has 90 Citadel interview questions. The largest topics are Coding & Algorithms (43%), Machine Learning (13%) and Statistics & Math (12%). By difficulty: 10% easy, 68% medium and 22% hard. The most common round is Technical Screen (66%). Frequent concepts include arrays, Heap, Data Structures and algorithms.

Difficulty

  • Easy10% · 9
  • Medium68% · 61
  • Hard22% · 20

Interview rounds

  • Technical Screen66% · 59
  • Onsite19% · 17
  • Online Assessment12% · 11
  • HR Screen3% · 3

Roles

  • Software Engineer61% · 55
  • Data Scientist36% · 32
  • Frontend Engineer1% · 1
  • Machine Learning Engineer1% · 1
  • Site Reliability Engineer1% · 1

Frequent concepts

  • arrays6% · 5
  • Heap6% · 5
  • Data Structures4% · 4
  • algorithms3% · 3
  • Hash Map3% · 3
  • Optimization3% · 3

Showing 31–60 of 90 results

  • Design an authenticated online shopping service with secure signup and login, user-owned carts, product browsing, and retry-safe order creation. The solution covers password hashing, session rotation, CSRF defenses, resource-level authorization, idempotency keys, immutable order snapshots, recovery tokens, and horizontal-access tests.

    CitadelSoftware EngineerSystem DesignOnsite
  • This question evaluates proficiency in end-to-end machine learning system design for geospatial property price prediction, covering skills such as feature engineering, time- and spatial-aware validation, model selection, interpretability, fairness/compliance, deployment, monitoring, and error analysis.

    CitadelData ScientistMachine LearningTechnical Screen
  • This question evaluates a candidate's ability to design and analyze dynamic data structures that support weighted random sampling with inserts and deletes, testing skills in algorithm design, complexity analysis, and randomized sampling under large numeric constraints.

    CitadelSoftware EngineerCoding & AlgorithmsOnsite
  • This question evaluates understanding of quadratic optimization, linear algebra, and convexity concepts—particularly properties of quadratic forms, matrix symmetry, and conditions for boundedness in real-valued unconstrained minimization—and why these properties matter for existence of minima.

    CitadelData ScientistMachine LearningTechnical Screen
  • Work through regression model validation from split design and leakage prevention to residual analysis and segment-level error checks. The solution explains MAE versus RMSE, multicollinearity, coefficient limits, and when added model complexity is worth the operational cost.

    CitadelData ScientistStatistics & MathTechnical Screen
  • This question evaluates a data scientist's competency in diagnosing outliers, high-leverage points, influential observations, and Cook's distance in ordinary least squares regression, including recognition of robust alternatives and rationale for reporting model-review decisions.

    CitadelData ScientistMachine LearningTechnical Screen
  • This question evaluates a candidate's foundations in empirical modeling, ability to learn from failed approaches, incorporation of feedback, and skill in quantifying research impact within a research or product context.

    CitadelData ScientistBehavioral & LeadershipTechnical Screen
  • Use one truthful project to explain what you are proud of, what changed in your thinking, and how you organize a normal workday. Connect personal decisions and measurable impact to later behavior while showing realistic prioritization, collaboration, focused work, and adaptability.

    CitadelSoftware EngineerBehavioral & LeadershipTechnical Screen
  • This question evaluates understanding of distributed messaging systems, delivery semantics, push versus pull consumption models, NoSQL versus relational storage trade-offs, and concurrency control including deadlock concepts.

    CitadelSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates proficiency in streaming/out-of-core linear regression, including computing sufficient statistics with an intercept, assessing numerical stability of normal equations versus QR/SVD or incremental methods, incorporating ridge penalties, and designing parallel fault-tolerant computations.

    CitadelData ScientistMachine LearningTechnical Screen
  • Evaluate an alternative dataset for an investment pitch through provenance checks, a falsifiable signal hypothesis, and point-in-time validation. Test incremental value, selection bias, revisions, robustness, and costs before presenting the thesis, risks, and invalidation criteria.

    CitadelData ScientistAnalytics & ExperimentationTechnical Screen
  • A coding problem about memory blocks with values below n: using at most one increment of a single value, never raising a value to n, list every minimum excluded value (MEX) the array can end up with. It tests careful case analysis of how one increment can open or fill a gap, handling duplicate values, and returning the sorted answer efficiently.

    CitadelSoftware EngineerCoding & AlgorithmsOnline Assessment
  • Given n network ports each tagged with a priority code below n, find every value the lowest unused priority code could take after at most one bounded increment. Tests careful case analysis of how a single bump opens or closes a gap, and returning the answer efficiently.

    CitadelSoftware EngineerCoding & AlgorithmsOnline Assessment
  • Explain JS types, Promises, Maps, WebSockets evaluates requirements, assumptions, structured reasoning, trade-offs, and verification in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    CitadelSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates self-awareness, career motivation, role-fit, decision-making, and communication skills for a Software Engineer by probing career values, educational and internship choices, and motivation for entering the finance industry.

    CitadelSoftware EngineerBehavioral & LeadershipTechnical Screen
  • This question tests the conceptual understanding of signal quality metrics and the practical steps required to prevent look-ahead bias and overfitting when developing quantitative trading factors.

    CitadelData ScientistMachine LearningTechnical Screen
  • Explain multicollinearity and OLS assumptions evaluates statistical assumptions, formulas, estimation strategy, uncertainty, edge cases, and interpretation in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    CitadelData ScientistStatistics & MathTechnical Screen
  • This question tests the understanding of L1 loss minimization and the statistical property that the median is the optimal point estimator under absolute error loss.

    CitadelData ScientistStatistics & MathTechnical Screen
  • This question evaluates proficiency with interval manipulation, timeline merging, and algorithmic reasoning for scheduling constraints, measuring competency in handling sorted interval lists, edge-case sanitization, and complexity analysis.

    CitadelSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Implement an algorithm to find the first and last index of a target value in a sorted array in O(log n) time.

    CitadelSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This problem tests your ability to navigate binary trees using recursion or iterative traversal while maintaining state to find a path that meets a specific sum criteria with the smallest number of nodes.

    CitadelSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Given locker tags in [0, n-1], list every possible smallest missing tag after at most one capped +1 adjustment. Tests MEX reasoning, careful case analysis around duplicates, and an O(n) solution.

    CitadelSoftware EngineerCoding & AlgorithmsOnline Assessment
  • Generate up to three lexicographically smallest product suggestions for every prefix of a search word, with efficient handling once a prefix has no matches.

    CitadelSoftware EngineerCoding & AlgorithmsOnsite
  • Write a runnable two-player hidden-fleet game for the terminal: captains place vessels via typed commands with full validation, then alternate firing until one fleet is sunk; tests modeling, parsing, turn flow and shipping working code fast.

    CitadelSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates interpersonal skills such as conflict resolution, communication, accountability, and leadership by asking about a concrete disagreement with a teammate in a software engineering context.

    CitadelSoftware EngineerBehavioral & LeadershipOnsite
  • This question evaluates understanding of lazy evaluation and Python generator semantics, testing a candidate's ability to work with iterative sequence production and manage state across iterations.

    CitadelData ScientistCoding & AlgorithmsTechnical Screen
  • This problem tests your ability to design a generic cache structure that supports interchangeable eviction strategies, requiring efficient lookup and metadata management.

    CitadelSoftware EngineerCoding & AlgorithmsTechnical Screen
  • Implement piecewise linear interpolation from unsorted knots, including exact-knot behavior and endpoint extrapolation. Practice paired sorting, binary search, and numerical edge cases.

    CitadelData ScientistCoding & AlgorithmsTechnical Screen
  • This question evaluates understanding of ring-buffer data structures, circular indexing, fixed-capacity storage, and object-oriented design for a single-producer, multi-consumer implementation in C++.

    CitadelSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This problem tests your ability to design an in-memory data structure for an order book using efficient data structures to support order management and price-level aggregation.

    CitadelSoftware EngineerCoding & AlgorithmsTechnical Screen

Citadel interview experiences

All 15 →
  • A Deep Dive on the Classic Orderbook ProblemCitadel · Software Engineer · Intern · Technical Screen · Sep 2026

    This was my second round for the Citadel SWE intern process. The technical part was the classic orderbook problem. The question was the classic orderbook problem. Problem description: Design and implement an order book data structure that maintains order records containing the exchange name, price, quantity, and side (bid or ask). It needs to support three core APIs: add(exchange, price, quantity…

  • File Deduplication, Size Checks, and Reference CountsCitadel · Software Engineer · Intern · Technical Screen · Sep 2026

    My first Citadel SWE interview. The interviewer was on the hedge fund side. I gave a brief introduction. Before I had a chance to tell the behavioral stories I'd prepared, he went straight into technical questions. The interview was basically 100% coding and system design. Problem: Suppose a file system contains files with identical contents. For example, /a/b/c.txt and /a/b/e.txt both contain th…

  • Merging K Timestamped Price Feeds into a Running Price in Technical Round 3Citadel · Software Engineer · Intern · Technical Screen · Sep 2026

    Citadel SWE intern technical interview. The interviewer was from Citadel Securities. Problem description: You are given K data streams (feeds), and each feed is already sorted by timestamp in ascending order. Each event has two fields: a timestamp and a price delta. Requirement: merge the events from all the feeds in time order, and after processing each event, output the current cumulative absol…

  • A Course Schedule Variant That Didn't Quite RunCitadel · Software Engineer · Intern · Technical Screen · Aug 2026

    This was for a 2027 summer internship, interviewing in the summer before my junior year. The first 15 minutes were self-introduction plus resume questions. The resume question was pretty vague — the interviewer only asked one question, but it actually bundled two things together: my most technically challenging experience, and whether I had a feature that directly helped with product commercializ…

  • A Maddeningly Vague Data Sampling QuestionCitadel · Software Engineer · Technical Screen · Aug 2026

    Citadel is out of their minds. The first half was fine — a normal self-introduction, project walkthrough, basic behavioral questions. Then the coding part started and that's where the craziness began: The interviewer was mumbling and couldn't speak clearly, and gave me a purely verbal problem: "we have millions of data points that need to be labeled," and told me to find the useful data. I kept f…

More companies