Jane Street vs Citadel Interview: Two Firms, Opposite Tests

You're applying to quant trading firms. Jane Street and Citadel are both on the short list. Both pay absurdly well. Both are brutally selective. Both will test you harder than any FAANG loop you've survived. Past that, the similarity ends.

The Jane Street vs Citadel interview split starts at round one. Jane Street runs collaborative coding sessions that push functional reasoning and recursive thinking. Citadel's loop looks like a FAANG loop crossed with a C++ oral exam, with a finance-specific system design round bolted on. The prep paths are different enough that conflating them will cost you. Not a little. A lot.

---

The Firm Distinction That Matters

Jane Street is a principal trading firm. It builds its own technology to trade for its own account. Traders, researchers, and engineers are deeply integrated, and the trading desk drives strategy.

Citadel is a hedge fund. Citadel Securities is a separate entity and one of the world's largest market makers. They share branding but operate independently. Engineers at Citadel Securities have more direct influence over the technology stack than their counterparts at Jane Street.

Knowing which entity you're interviewing with matters. The process and expectations differ significantly. Also worth knowing upfront: Jane Street has no non-compete. Citadel's can run up to two years. File that away before you sign anything.

---

Two Loops, One Table

Stage	Jane Street	Citadel / Citadel Securities
Resume review	Human, no AI scanner	Recruiter screen
Online assessment	60-minute coding test	Timed HackerRank/online assessment
Phone screens	1-2 live coding rounds, conversational	1-2 rounds, LeetCode-style
On-site	4-5 rounds, ~5-6 hours	3+ technical rounds, committee review
System design	Rarely, for senior roles	Yes, finance-specific (order books, pricing engines)
Language	Any (OCaml culture internally)	C++ strongly preferred; Python secondary
Non-compete	None	Up to 2 years

---

Same Role, Different Definition of Good

Jane Street: You're Being Hired to Think Recursively

Jane Street's online assessment runs 60 minutes with two to three algorithmic problems. You can use any language, though the problems are designed to reward functional thinking: list manipulation, recursive data structures, subset enumeration. There's no single correct solution. They're designed to branch into follow-ups.

The live phone screens follow the same format. One or two engineers join, you write real code, and you talk through every step. Jane Street's interviewers are measuring how you think, not just whether you land on the right answer. A candidate who reaches an elegant O(n) solution in silence after 50 minutes loses to a candidate who narrated a messier path.

The on-site is five to six hours across four to five rounds. Typical territory: tree traversals, memoization and caching, small parsers, functional data transformations, interval merging. You might implement a memoized version of an expensive function, reason through why a garbage collection scheme fails, or design a small stateful system with clean invariants.

Jane Street's own blog is explicit: they do not ask software engineers to do mental math, logic puzzles, or olympiad problems. That's the trading desk interview. Not yours.

Citadel Securities: You're Being Hired for the Hot Path

Citadel Securities' engineering interview looks FAANG-ish in structure but tilts hard toward performance. The online assessment is a standard timed challenge. Live technical rounds go two to three problems per session, 45 to 60 minutes each.

Then it gets finance-specific. Candidates report getting grilled on C++ internals: iterators, STL containers, std::variant, move semantics, memory management. System design questions ask you to build things like order books, ring buffers with a single producer and multiple consumers, or real-time pricing engines. Lock-free programming comes up regularly. The interviewers want to know what you'd do when a mutex is too slow.

The question isn't "does it work." It's "does it work when the exchange is ticking 10 million events per second."

Citadel wants you fluent in the language that defeats description.

---

Both Firms Hire Quants. That's Where the Brain-Teaser Reputation Lives.

If you've heard about Jane Street and probability puzzles and expected-value games, that's from the quant and trading track, not the SWE track. Two completely different loops. Worth separating clearly.

For quant and trading roles, the typical Jane Street first round is 30 to 45 minutes of probability puzzles and a betting game. The final round is mock market-making: you quote prices, manage risk in real time, and reason out loud about your edge. Thinking fast and narrating why are both scored dimensions.

Citadel's quant interviews cover four areas: probability and brain-teasers (about 35%), market knowledge (25%), mental math and estimation (25%), and behavioral (15%). Classic question: "What's the expected number of flips of a fair coin to get two heads in a row?" Citadel quants often skip the online coding assessment entirely and go straight to technical conversations.

The interview content for quant roles is meaningfully similar between the firms. The tone differs. Jane Street's quant interviews feel like a poker game where you're expected to defend positions and probe your interviewer's assumptions. Citadel's feel more like a graded exam. Same subject, very different energy.

---

What Jane Street Actually Wants

Jane Street is transparent about its bar: collaborative problem-solving, curiosity, and intellectual humility. The smartest candidate who won't talk through their thinking won't get an offer. This is not a company that rewards lone-wolf technical brilliance.

In practice:

• Think out loud constantly. Not a monologue. A dialogue. Ask your interviewer questions. The mechanics of thinking out loud under pressure are a trainable skill, not a personality trait.
• When you're stuck, say so and say why. "I'm not sure this handles the empty tree case" is better than a long silence followed by a fix.
• Follow-up questions are normal and expected. Problems are designed to extend.
• Culture fit is a scored dimension. Honesty, intellectual humility, and a willingness to say "I don't know" all count.

What happens when you spend six weeks grinding hard LeetCode and zero hours practicing narration. You get to Jane Street. You have no idea what to do.

For SWE, the most common prep mistake is over-rotating on hard LeetCode. The problems are medium in difficulty. The more damaging mistake is under-investing in recursive thinking. Practice writing clean recursive solutions, extend them with memoization, then convert to iterative when asked. The full breakdown is in the Jane Street interview guide.

---

What Citadel Actually Wants

Citadel wants engineers who can write high-performance code in a domain where a microsecond of latency has a dollar cost.

The differentiator in Citadel interviews is depth, not breadth. They don't want you to sketch a ring buffer. They want you to implement one, explain why your locking strategy is correct under concurrent access, and then explain what you'd change if you needed to drop the mutex entirely.

In practice:

• Know C++ well below the surface. Not just syntax. How std::vector reallocation works, when a move constructor fires versus a copy, and what happens to your cache line when you use a linked list in a latency-sensitive context.
• For system design, anchor everything in finance: order book design, tick-by-tick processing, cold/hot data separation for time-series storage.
• Concurrency is not optional. std::atomic, memory ordering, compare-and-swap, and the scenarios where lock-free is worth the complexity.
• LeetCode prep should focus on DP, DFS/BFS, and two-pointer problems at medium-to-hard difficulty.

---

Jane Street vs Citadel Interview Prep: Who Should Apply Where First

If your background is strong on algorithms and functional programming but light on systems, apply to Jane Street first. The interview values reasoning and communication over deep systems knowledge.

If you've done low-latency work, have C++ depth, or come from a performance engineering background, Citadel is the natural fit.

If you're targeting both, do Jane Street first. The skills that transfer are recursion and collaborative communication. The Citadel-specific material (C++ internals, finance system design) takes longer to build and is narrower.

For quant and trading roles at either firm, your probability prep is the same. Work through expected value, Markov chains, Bayes, and classic brain-teasers until they feel automatic. Brush up on basic market microstructure. Then practice narrating your reasoning under pressure, because that's the differentiator. If you come from competitive programming, read why CP habits backfire before you start. The instincts that win on Codeforces actively hurt you in a Jane Street trading interview.

SpaceComplexity runs voice-based mock interviews that simulate exactly this: a problem you reason through out loud, with feedback on where you went quiet. That's the gap neither LeetCode nor flashcards closes.

---

How Long to Prep

Jane Street SWE: 4 to 6 weeks if your algorithms base is solid. Focus on recursive thinking, memoization, functional patterns, and talking through solutions. Read Jane Street's own blog posts on what the interviews look like.

Citadel SWE: 6 to 8 weeks if your C++ is rusty, plus 2 to 3 more if you need to build the systems foundation. Focus on C++ internals, concurrency, finance-flavored system design, and medium-hard LeetCode.

Quant or trading roles at either firm: 8 to 10 weeks minimum. Probability drills, mental math, market microstructure basics, mock trading games. Maybe longer if mental math under pressure is not currently your idea of a good time.

---

Further Reading

• Jane Street: Preparing for a Software Engineering Interview
• Jane Street Blog: What a Jane Street Dev Interview Is Like
• Jane Street: Functional Programming
• Citadel: Our Engineering Interview Process
• eFinancialCareers: Citadel Securities vs. Jane Street