The Citadel SWE Interview Guide

See how Citadel runs its software engineer loop: a timed, auto-graded coding screen, live problems in a shared editor, and a super day that ends with systems questions pitched at a trading desk. Then drill the questions candidates report from recent loops, so the pace never rattles you in the room.

• Loop length: 2 to 4 weeks
• Expected difficulty: Hard, fast
• Online assessment: HackerRank, 60-90 min
• Focus: Speed and precision

Citadel levels & pay

• Software Engineer (Entry)
• Software Engineer (Mid)
• Senior Engineer (Senior)
• Principal Engineer (Staff+)

The Citadel SWE interview, round by round

Recruiter screen (30 min · call)

The first call is with a Citadel recruiter and is mostly fit and logistics rather than a technical test. They confirm your background, the team and level you are targeting, your work authorization, and what you expect to be paid. They will also tell you which firm you are actually interviewing with, because Citadel the multi-strategy hedge fund and Citadel Securities the market maker are separate companies that run separate loops. Citadel moves quickly, so this call usually ends with your assessment and super day already going into a calendar.

• Find out which entity you are in. Citadel is the hedge fund and Citadel Securities is the market-making firm. They share a founder and an owner but they are distinct companies with their own teams, their own interviewers, and their own offers, and which one you are in changes how much low-latency and C++ work you will face.
• Bring your availability. Recruiters here often want dates on this first call. Turning up without your calendar is the simplest way to add a week to a process that would otherwise be one of the fastest you will run.
• Talk in cash, not packages. Citadel is private and grants no public stock. Its own postings pair a base salary range with a discretionary incentive compensation program, so quote a total cash number rather than something built around vesting equity.

Online assessment (60-90 min · HackerRank)

A timed, auto-graded coding test that candidates consistently report is delivered through HackerRank, usually two or three problems in roughly sixty to ninety minutes. The problems are ordinary data-structures work wearing a trading costume: the Citadel question pool candidates report includes price checks over a stock list, best time to buy and sell, throughput maximization, consistent log records, and token expiry with lazy deletion. Grading is by hidden test cases, so a clever solution that misses an empty-input case scores zero for that problem. Quantitative research and trading candidates sit a separate timed math and probability test; software engineers usually do not, although expected-value twists do show up inside later coding rounds.

• Hidden tests decide it, not your prose. Nobody reads your reasoning at this stage. Handle empty input, single elements, duplicates and integer overflow before you submit, because there is no interviewer to give you partial credit for the right idea.
• Expect finance-flavored wording. Reported Citadel problems dress up standard algorithms in market language: price checks against a stock list, best time to buy and sell, maximum throughput, consistent log records, prime factor visitation. Read past the story and identify the underlying structure fast.
• Budget the clock per problem. Decide early which problem is the expensive one and give it the time that remains. Two problems finished cleanly is what the test-case scoring rewards.

Technical phone screens (45-60 min · shared editor)

One or two live coding conversations with a Citadel engineer in a shared editor, and candidates do report two-round screens. The problems sit at genuine interview difficulty: reported ones include merge K sorted lists with timestamps, LRU cache variants, tree diameter, regular expression matching, and shortest path with a fuel constraint. Interviewers ask for time and space complexity and then push on the cases you skipped, so state your assumptions out loud as you write. Screens for Citadel Securities low-latency teams are often explicitly in C++ and probe memory, copies and object lifetime alongside the algorithm.

• Reach optimal and prove it. The right complexity is the pass mark rather than the finish line. Say the bound, justify it, and name the edge cases you handled before the interviewer has to ask.
• C++ is real for some teams. Low-latency and market-making screens are run in C++ and will move from your algorithm to where the allocations are, how many copies you made, and when objects die. Settle with the recruiter which language you are being tested in.
• Probability arrives inside the coding. The Citadel pool includes expected-value twists on ordinary problems, such as the expected position of an element in a probabilistic LRU cache, or expected keystrokes to type a word at random. Be ready to switch from code to a clean probability setup mid-round.

The super day (4 to 5 rounds · onsite)

The main evaluation, run as four or five back-to-back rounds in a single sitting, usually onsite. The mix is two or three coding rounds, one design or systems round pitched at the team you would join, and one round about how you work. For desk-facing teams the design round is about latency, throughput, memory layout and concurrency rather than web-scale architecture, and a reported Citadel prompt is designing an order book class that computes exchange BBO and NBBO. There is no dedicated probability round in the software engineer loop; that belongs to the quant pipeline, and probability instead arrives as expected-value twists inside coding problems. The day is long and the standard does not soften in the last round, so pace yourself deliberately.

• Coding stays fast all day. Expect two or three coding rounds across hash maps, trees, heaps, sliding window, intervals and graph traversal. Optimal complexity is assumed and edge cases are expected without prompting, in round four as much as round one.
• Systems here means microseconds. The design round asks where time and bytes go: queueing, contention, cache behavior, allocation, and what happens when a market data feed falls behind. Reported prompts include designing an order book and computing best bid and offer across venues.
• The behavioral round is a real gate. Interviewers ask what you personally owned, what broke, and what you decided when the answer was not obvious. Bring two or three stories with your specific role and a measurable outcome, because at a firm this size individual ownership is the thing being checked.

Debrief and offer (Days, not weeks · decision)

Your interviewers write up feedback and meet, and this is where Citadel is unusually quick. There is no hiring committee sitting once a week and no team-matching queue to join, so a decision often lands within a few days of the super day and sometimes in the same week. The bar is consistency across the whole day: a strong coding round paired with a weak systems or behavioral round is a common reason for a no. Offers are a base salary plus a discretionary annual cash bonus, and junior offers often include a one-time sign-on.

• The turnaround is genuinely short. Most candidates hear back within days of the super day. Line up your other processes first, because Citadel may want an answer on a timeline a big-tech loop would still be scheduling around.
• Consistency clears the bar. Feedback is read across all the rounds together. One shaky round in a five-round day is enough to end it even when the coding went well, which is why the design and behavioral rounds deserve real preparation.
• The offer is cash. Citadel's own postings pair a base salary range with a discretionary incentive compensation program. Model the bonus as cash and any sign-on as a one-time payment, because there is no public stock and nothing vests.

How to prepare

Keep a daily timed coding rhythm (Weeks 1 to 4)

Code every day for the whole month, always against a clock on a shared editor. Rotate through the patterns Citadel leans on, hash maps, trees, heaps, sliding window, and interval logic, starting at medium and climbing into hard, and force yourself to reach optimal complexity fast.

Drill probability and mental math (Weeks 1 to 3)

Start these early so they are automatic by the onsite. Practice expected value, conditional probability, combinatorics, and fast arithmetic without a calculator, under a tight per-question clock, so the quickfire feels like recognition rather than derivation.

Layer in low-latency and systems reps (Weeks 2 to 3)

Once your coding is warm, add systems thinking for trading-adjacent teams. Work through how latency, throughput, memory layout, and concurrency shape a design, saying each decision aloud and preparing for pointed follow-ups on your trade-offs.

Run full mock super days (Week 4)

In the last week, put it together: sit a few complete loops back to back, coding, probability, and systems in one session each, so your focus and speed hold across four or five rounds in a row without the clock breaking you.

Recently asked

Weighted random sampling with insert and delete

About Citadel

Citadel is one of the world's leading alternative investment firms, founded by Ken Griffin in 1990 and headquartered in Miami. It runs a multi-strategy hedge fund across equities, fixed income, commodities, credit, and quantitative strategies, and its affiliate Citadel Securities is one of the largest market makers in the world, trading across global equities, options, and other asset classes.

Engineering sits at the center of both businesses, building the low-latency systems, data platforms, and research tools that the desks and market-making engines depend on. The culture is intensely high-performance and meritocratic: the firm hires a small number of exceptional engineers, holds a high bar, and rewards results directly through a large discretionary cash bonus rather than equity.

Frequently asked

How many rounds is the Citadel interview?

Typically four to five stages: a recruiter screen, an online assessment, one or more technical phone screens, and an onsite super day of four to five back-to-back rounds, followed by a debrief and offer. Every technical stage moves fast and expects precise reasoning.

How hard is the Citadel SWE interview?

Hard, and fast. The coding bar sits at the level of the strongest tech loops, and the differentiator is pace: an auto-graded screen, live problems that expect optimal complexity, and a four-to-five-round super day with no soft round in the middle. Candidates most often report the sustained speed and the systems round as the surprise rather than any single exotic question.

Does Citadel test probability and mental math for software engineers?

Less than its reputation suggests. The famous timed math test, many short probability and mental-arithmetic questions against a very tight per-question clock, is aimed at quantitative research and trading candidates. Software engineers usually sit a coding assessment instead. Probability still appears, but it appears inside coding rounds as expected-value twists, for example the expected position of an element in a probabilistic LRU cache. Comfort with expected value and conditional probability helps; a dedicated quickfire drill is optional for a pure SWE loop.

How is Citadel compensation structured?

Pay is a competitive base plus a large discretionary annual cash bonus, not equity. Citadel is a private firm with no public stock, so there are no RSUs. The bonus is performance-driven and can be a large multiple of base at senior levels, and junior offers often include a real one-time sign-on bonus.

Does Citadel give equity or stock?

No. Citadel is privately held, so there is no public stock and no RSU grants. Compensation is base plus a discretionary cash bonus. When you compare Citadel offers against public tech companies, model the bonus as cash rather than vesting equity.

What is the difference between quant and software engineering roles at Citadel?

Quantitative researchers and quantitative developers work on models, signals and strategy; software engineers build the platforms, low-latency systems and tools those strategies run on. The interview pipelines differ too: quant candidates get a timed math and probability assessment, while software engineers get a coding assessment and then coding, systems and behavioral rounds. It is also worth separating the firms. Citadel is the multi-strategy hedge fund and Citadel Securities is the market maker. They are legally separate companies under common ownership, and they hire, interview and pay separately.

Does Citadel ask low-latency or systems questions?

For many trading-adjacent teams, yes. Expect questions on latency, throughput, memory layout, concurrency, and how those shape a design. The emphasis is on reasoning about where time and resources go, not on naming technologies. Teams further from the trading path weight this less.

What is the Citadel online assessment?

A timed, auto-graded coding test, which candidates consistently report is delivered on HackerRank, with two or three problems in roughly sixty to ninety minutes. Scoring is by hidden test cases, so correctness on edge cases matters more than how the code reads. The problems are standard data structures dressed in market language: price checks over a stock list, best time to buy and sell, throughput maximization, consistent log records, token expiry with lazy deletion. Treat it as a real elimination round, because it filters before any engineer reads your name.

What is the Citadel super day?

The onsite: four or five back-to-back rounds in a single sitting. It mixes two or three coding rounds, a design or systems round pitched at the team you would join, and a behavioral round. For trading-adjacent teams the systems round is about latency, throughput, memory and concurrency, with reported prompts like designing an order book that computes best bid and offer across venues. There is no separate quantitative round in the software engineer loop. The day measures whether your standard holds in round five as well as round one.

How long does the Citadel interview process take?

Usually two to four weeks from the recruiter screen to a signed offer, which makes it one of the fastest processes at this level of prestige. There is no team-matching queue and no weekly hiring committee, so decisions after the super day frequently land within days. What stretches the calendar is scheduling: the assessment window, and finding a day when four or five interviewers are free at once. Candidates who can clear their calendar sometimes move faster than the range suggests.

What coding topics does Citadel focus on?

Core data structures and algorithms at speed: hash maps, trees, heaps, sliding window, interval logic and graph traversal. Reported Citadel problems include merge K sorted lists with timestamps, LRU cache variants, tree diameter, regular expression matching, shortest path with a fuel constraint, and designing an order book. The differentiator is reaching an optimal, correct solution quickly and defending the complexity, rather than knowing exotic algorithms.

How should I prepare for the Citadel interview?

Drill timed data-structures coding daily until optimal complexity is your first instinct rather than your second pass. Add systems reps for trading-adjacent teams, reasoning out loud about latency, throughput, memory layout and concurrency, and practice designing something market-shaped like an order book. Keep expected value and conditional probability warm, since they show up as twists inside coding problems. Then run full mock super days so your focus holds across four or five fast rounds. Karavine's Citadel pack is exactly this plan with worked solutions.

How much math do I need for a Citadel SWE role?

Less than for a quant role, more than for a typical product engineering interview. You do not need research-level statistics, and the timed mental-math quickfire is aimed at trading and quantitative research candidates rather than software engineers. What does help is comfort with expected value, conditional probability and combinatorics, because Citadel likes to bolt those onto ordinary coding problems, and comfort with the arithmetic of latency and throughput for desk-facing teams.

Is the Citadel interview harder than a big tech interview?

In pace, usually yes. The coding bar is comparable to the strongest tech loops, but Citadel compresses the whole thing into two to four weeks, auto-grades the first filter on hidden tests, and expects optimal complexity in every round of a four-to-five-round day. For trading-adjacent teams it also adds low-latency systems reasoning and, on some Citadel Securities screens, C++ specifics like memory layout and object lifetime. The speed and the systems round are what candidates report as the surprise.

Can I reapply to Citadel after a rejection?

Yes. Citadel does not publish a fixed waiting period, and candidates typically wait several months before trying again. Ask the recruiter which stage ended it, since feedback is read across the whole loop and the useful thing to fix is the specific round that fell short rather than the process in general. Coming back for a different team, or for the other entity, Citadel versus Citadel Securities, is also normal.

Where does Citadel hire software engineers?

Citadel's own engineering job board lists Chicago, Greenwich, Houston, Miami and New York in the Americas, Dublin, London, Paris and Zurich in Europe, and Hong Kong, Singapore, Sydney and Tokyo in Asia-Pacific. On the live postings, the experienced Software Engineer role covers Greenwich, Houston, London, New York and Singapore; the US intern and university-graduate roles cover Greenwich, Houston, Miami and New York; and the Asia intern role covers Hong Kong and Singapore. Citadel Securities, the separate market-making firm, has its own footprint that adds Shanghai and Gurugram and drops Greenwich and Houston. Miami is the headquarters for both since the 2022 relocation, and team plus location together shape how much low-latency work the role involves.

Citadel interview questions on Karavine