The short answer: Citadel says Quantitative Developers are also known as Quantitative Research Engineers, and both titles are posted at Citadel, the hedge fund, and at Citadel Securities, the market maker. Campus candidates go through one engineering process for both firms: a 45-minute first round, a second round of usually three 45-minute interviews, then leadership interviews with interested teams. Those campus guides are written for engineering in general and do not name the quant developer title. For experienced engineers, Citadel Securities runs a 4 to 5 hour onsite built on one realistic problem, such as an order book. Candidate reports add an online coding assessment before the campus rounds. Last reviewed October 2026.
Citadel Quantitative Developer at a Glance
Interview Rounds
5 or more (campus) rounds
Levels
Intern - Senior Quantitative Developer
Citadel quantitative developer interview: quick answers
| Question | Short answer |
|---|---|
| How many interview rounds? | For campus hires, Citadel describes a 45-minute first round, a second round of usually three 45-minute interviews, and one or more leadership interviews. Candidate reports add an online coding assessment first. Citadel Securities' experienced process is a recruiter conversation, a technical screen and a 4 to 5 hour onsite. |
| What do the rounds test? | Campus rounds cover coding, data structures, algorithms and problem solving, with Python and C++ as the core languages, plus behavioral questions. The experienced onsite tests system design, code quality and correctness, decisions as requirements change, and communication. |
| Can I use AI tools? | Citadel does not publish a rule on AI use in interviews; ask your recruiter. Its student program terms ban generative AI for program application content, which applies to those programs and not to job interviews. |
| How much does a Citadel Quantitative Developer make? | Citadel's postings list base ranges from $200K to $350K. Citadel Securities' postings list $175K to $350K. The PhD graduate postings at both firms list $235K to $300K. Postings say pay can include more than the base salary. |
| How long does it take? | Citadel says the campus process typically takes about eight weeks. Candidate reports range from about a week to several months. |
| Is a Quantitative Research Engineer the same role? | Yes. Citadel says Quantitative Developers are also known as Quantitative Research Engineers, and its Global Quantitative Strategies postings use the Quantitative Research Engineer title. |
The Citadel quantitative developer role
What Citadel quantitative developers work on, the skills its job postings ask for, and what a week can look like. Citadel posts the role as Quantitative Developer or Quantitative Research Engineer, at both Citadel and Citadel Securities.
Primary Focus
What You Need
- Strong programming, C++ preferred (GQS)
- Linux development experience
- Expert C++ for low-latency code
- Modern CPU architecture: pipelines, caches and memory models
- C++17 or newer for performance-critical systems
- Data structures, algorithms and systems programming
- Networking and concurrency on Linux
- Production Python (Data Strategies Group)
Nice to Have
- High-frequency trading or market-making background
- Market microstructure and order books
- Cloud on AWS, GCP or Azure
- CI/CD, containers and orchestration
- Distributed computing, ML or NLP experience
Languages
Tools & Technologies
Want to ace the interview?
Practice with real questions.
A Week in the Life of a Citadel Quantitative Developer
Illustrative week · Citadel
An illustrative week for a quantitative developer, built from what Citadel says about the role in its own job postings and publications. Real weeks vary by team.
Culture notes
- Engineers work next to the investment teams. Citadel says its engineers sit on small teams embedded with quant researchers and investment professionals.
- Correctness is part of the job description. GQS says live markets demand strict standards for correctness and fail-safe design.
- New engineers get structured training. Citadel runs a two-year development path for graduates, and Citadel Securities gives early-career engineers three weeks of onboarding.
Key takeaway: Expect to build research tools and fast, correct trading systems in C++ or Python next to the researchers who use them.
Citadel quantitative developer levels and pay
Your level sets the bar you are interviewed against and the pay band of the offer.
Citadel Quantitative Developer Levels
Each level has different expectations, compensation, and interview focus.
What This Level Looks Like
An 11-week summer internship at either firm; intern profiles describe owning a project end to end.
Interview Focus at This Level
The campus engineering process: coding, data structures and algorithms, then behavioral fit.
Find your level
Practice with questions tailored to your target level.
Neither firm publishes a level ladder. Postings separate interns and PhD graduates from experienced hires, and Citadel Securities uses a Senior prefix on one London posting, so the pay table uses posting titles.
Pay in Citadel's US job postings
Postings at both firms list an annual base salary range in US dollars and say pay can include more than the base salary. Each row names the firm.
| Posting | Location | US base salary range |
|---|---|---|
| Citadel: Quantitative Developer – Data Strategies Group | New York | $200K to $250K |
| Citadel: Global Quantitative Strategies (GQS) | Quantitative Research Engineer | Hong Kong, New York, Singapore | $275K to $350K |
| Citadel: Global Quantitative Strategies (GQS) | C++ Quantitative Research Engineer | New York, Singapore | $275K to $350K |
| Citadel: Quantitative Research Engineer – PhD Graduate (US) | US | $235K to $300K |
| Citadel Securities: Quantitative Research Engineer – PhD Graduate (US) | New York, Miami | $235K to $300K |
| Citadel Securities: Quantitative Developer/Research Engineer | New York, Miami and other offices | $250K to $350K |
| Citadel Securities: Crypto Quantitative Developer | New York, London | $175K to $350K |
Some postings list offices outside the US next to New York; the range is as posted. The Senior Quantitative Developer (London) and Quantitative Research Engineer (Miami) postings at Citadel Securities show no range, and weekly PhD intern pay is left out of the table. Ranges seen October 29, 2026.
Citadel quantitative developer interview process
The campus steps follow Citadel's and Citadel Securities' campus engineering guides, which describe one process for both firms and do not name the Quantitative Developer title. The experienced steps follow Citadel Securities' own pages. The online assessment comes from candidate reports only.
5 or more (campus) rounds·~About 8 (campus) weeks end to end
Screen
4 roundsOnline coding assessment (campus, candidate reports)
A candidate guide describes two algorithm problems on topics such as arrays, strings, graphs and trees. Citadel's own process pages do not mention an assessment, so treat this step as unconfirmed.
Tips for this round
- Candidate reports describe two algorithm problems; practice medium array, string, graph and tree problems against a timer.
- Ask your recruiter whether your process includes an assessment, since Citadel does not mention one.
First round (campus)
Coding, data structures, algorithms and problem solving, plus your technical interests, past internships, school projects and motivation. Python and C++ are the core languages and others are welcome. Citadel Securities says it sends a link to a shared coding environment in advance.
Recruiter conversation (experienced, Citadel Securities)
Citadel Securities lists this as the first step and does not detail it.
Technical screen (experienced, Citadel Securities)
A coding screen. Citadel Securities does not publish a length.
Onsite
3 roundsSecond round (campus)
A mix of technical and behavioral interviews, with time for your questions. Citadel says the first two rounds are a general assessment and are not team-specific, and that next steps come within two weeks.
Tips for this round
- Expect a general assessment that is not team-specific, so prepare broad data structures and algorithms.
- Discuss trade-offs and say what you do not know. Citadel says to take hints when stuck.
- Bring questions for each interviewer; Citadel leaves time for them.
Leadership interview (campus)
Hiring managers review your resume and feedback, then a senior engineer from an interested team at Citadel or Citadel Securities interviews you for fit. If more than one team is interested, there can be several.
Onsite: one problem in four stages (experienced, Citadel Securities)
One problem drawn from systems the firm runs, such as an order book, a matching engine or a market-data pipeline. No domain knowledge is needed. You move through requirements and design, implementation, code review and discussion, and new requirements are added during the day. Many roles expect C++; others let you use your own language, editor and setup.
Tips to Stand Out
- Take time to understand a problem before coding, and ask clarifying questions, as Citadel advises.
- Share your thought process, discuss trade-offs and be clear about what you do not know. Citadel says to take hints when stuck.
- Read the firm's mission and values and prepare a personal story about how your internships drove business outcomes, as Citadel Securities suggests.
- At the experienced onsite, question the spec early, name your assumptions and outline a design you can defend.
- Write code someone else can read, and be honest about its limits in the code review stage.
- Practice scoping a system out loud. Citadel Securities says memorizing algorithm puzzles helps less than in a typical coding interview.
Common Reasons Candidates Don't Pass
- ✗Citadel Securities says candidates who race to finish the onsite problem tend to skip what it values and do worse.
- ✗Citadel Securities says candidates who treat the first ten minutes of the onsite as a passive briefing lose ground.
Based on Citadel's own pages and candidate reports.
Citadel says the campus process typically takes about eight weeks, that candidates can usually interview for only one role at a time, and that interviews run Monday to Friday in business hours. Candidate reports describe timelines from about a week to several months. Last reviewed October 2026.
What is different at Citadel
- One campus process covers two firms. Campus engineers interview with Citadel and Citadel Securities at once, interviewers say which firm they represent, and team matching across both firms comes after the second round. Placement depends on your skills, experience and business needs. One candidate guide claims the firms run separate pipelines for Quantitative Developers, which conflicts with both firms' campus guides.
- The titles vary by firm. Citadel says Quantitative Developers are also known as Quantitative Research Engineers. Citadel posts Quantitative Developer for its Data Strategies Group and Quantitative Research Engineer for Global Quantitative Strategies (GQS). Citadel Securities posts Quantitative Developer/Research Engineer, Crypto Quantitative Developer, Senior Quantitative Developer and Quantitative Research Engineer. The campus process pages are written for engineers in general (Citadel's says software engineers) and do not name the Quantitative Developer title. We use them because Citadel lists Quantitative Developer as one of its key engineering roles.
- Citadel Securities' experienced onsite is one problem all day. You take a system such as an order book or a matching engine through design, code, code review and discussion over four to five hours. You do not have to finish: Citadel Securities prefers a partial system you understand and can extend, and it calls drilling puzzles the wrong preparation.
- C++ carries most of the low-latency work. Citadel Securities says most of its production systems are in C++ and publishes articles on C++26. GQS uses C++ for low-latency data serving, research analytics libraries and trade execution. The Data Strategies Group role at Citadel is the exception: it asks for production Python, cloud and DevOps practices.
- The teams sit close to the money. Citadel engineers work on small teams embedded with quant researchers and investment professionals. Citadel Securities says its trading systems support the execution of half a trillion dollars in trades a day, and its options business quotes more than a million options series.
- Neither firm publishes an AI rule for interviews. The onsite page lets most candidates use their own editor, language and tools and does not mention AI assistants. Citadel's student program terms ban generative AI for program applications only. On the job, Citadel Securities describes large language models as an important tool in a quant development intern's research workflow.
Citadel quantitative developer interview questions
Questions from our bank, then practice prompts we wrote for this guide around Citadel's work.
Questions from our bank
From the DataInterview question bank: questions tagged to Citadel first, then questions that fit quantitative developer interviews. Open one to answer it.
Sum Exceedance Two
Fair Bounty Problem
Egg Drop Puzzle
Ship Travel Time
Second Moment Value
Random Matrix Flipping
Multinomial Coefficient Sum
Top Pair
Tower Configurations
Low-latency and C++ practice
Prompts we wrote for this guide around Citadel's work. They are not reported interview questions. Each answer is an outline or a worked solution.
A GQS research tool keeps 10 million ticks as a std::vector of 64-byte structs with eight fields, but most queries read only the timestamp and price. Why is a scan slow, and what would you change?
Sample Answer
Each struct fills a whole 64-byte cache line, so a scan that needs 16 bytes per tick still pulls in all 64. That is four times the memory traffic the query needs, and memory bandwidth is the bottleneck for a scan like this. Switch to a structure of arrays: one contiguous array of timestamps and one of prices. The scan then reads only the bytes it uses, sequentially, which the hardware prefetcher handles well and the compiler can vectorize. Say the trade-off: code that writes or reads whole ticks gets more awkward. Measure before and after with a profiler.
In an order book, why does a std::map of price levels often lose to a flat array or vector, and when would the map be the better choice?
Two threads in a market-data handler increment a shared message counter. What goes wrong, and how do you fix it without a mutex on the hot path?
An options pricing loop calls a virtual price() method on each of a million objects. What does the virtual call cost, and how could you remove it?
Systems practice
Prompts we wrote for this guide around Citadel's work. They are not reported interview questions. Each answer is an outline or a worked solution.
Design a limit order book for one symbol with add, cancel and match. Midway, the interviewer says it must handle 1 million cancels a second.
Sample Answer
Start with requirements: price-time priority, partial fills, what a trade report contains. Keep each price level as a FIFO queue of orders and track the best bid and ask. Add a hash map from order id to the order's node so a cancel finds the order in O(1), and use an intrusive doubly linked list per level so unlinking is O(1). For the cancel load, avoid heap allocation on the hot path with a preallocated pool of order nodes, and remove empty levels lazily. Write tests for invariants: the book never stays crossed, and quantities balance. This mirrors the Citadel Securities onsite, where new requirements arrive during the day.
Design a market-data pipeline that serves normalized exchange data both to the live trading system and to GQS researchers.
A pre-trade risk check sits in front of order entry. Design it to add as little latency as possible and to fail safe.
Code review stage: a colleague's matching engine stores prices as double. What do you flag, and what do you suggest?
Probability practice
Prompts we wrote for this guide around Citadel's work. They are not reported interview questions. Each answer is an outline or a worked solution.
A hash table has 1,000 buckets. You insert 50 keys, each hashed uniformly at random. What is the expected number of pairs of keys that collide?
Sample Answer
There are C(50, 2) = 50 x 49 / 2 = 1,225 pairs of keys. Each pair lands in the same bucket with probability 1/1,000. By linearity of expectation, the expected number of colliding pairs is 1,225 / 1,000 = 1.225. Linearity works even though collisions between pairs are not independent.
A feed drops each packet independently with probability 0.001. In a burst of 2,000 packets, what is the probability of at least one drop?
You roll two fair dice. What is the expected value of the larger roll?
Two orders arrive at independent uniform random times within the same 1-second window. What is the probability they arrive within 100 ms of each other?
Behavioral practice
Prompts we wrote for this guide around Citadel's work. They are not reported interview questions. Each answer is an outline or a worked solution.
Tell me about a tool you built that other people used, and how you changed it from their feedback.
Sample Answer
Citadel's quant development intern profile describes owning a project end to end and iterating with the researchers who use it. Name the users, what they asked for, what you shipped first and what you changed after watching them use it.
Describe a production bug you owned from detection to fix.
How did one of your internships or projects drive a business outcome?
Tell me about a time a requirement changed late in a project.
Practice problem: match orders in a limit order book
pythonProcess a list of events for one symbol and return the trades. An add event is ("add", id, side, price, qty) with side "buy" or "sell" and integer price in ticks. A cancel event is ("cancel", id) and removes whatever is left of that order; unknown ids are ignored. An incoming order matches resting orders on the other side while prices cross, best price first and, at the same price, oldest first. Each trade is (buy_id, sell_id, price, qty) at the resting order's price. Any unfilled quantity rests in the book. Example: [("add", 1, "sell", 101, 5), ("add", 2, "sell", 100, 5), ("add", 3, "buy", 101, 7)] gives [(3, 2, 100, 5), (3, 1, 101, 2)].
1from typing import List, Tuple
2
3def match_orders(events: List[tuple]) -> List[Tuple[int, int, int, int]]:
4 """Return trades as (buy_id, sell_id, price, qty) in the order they happen."""
5 pass700+ coding problems with a live code executor.
Practice in the EngineHow to prepare
A plan for the Citadel loop, most important first:
- Rehearse the Citadel Securities onsite: pick an order book or market-data pipeline, then spend 4 hours on requirements, code, a self code review and a discussion, adding a new requirement halfway.
- Practice medium to hard data structures and algorithms problems in Python or C++ for the 45-minute campus rounds, talking through each approach.
- Go deep on C++ performance: memory layout, cache behavior, atomics and what blocks inlining, since GQS and Citadel Securities postings ask for low-latency C++.
- Prepare short stories on your internships, school projects and the business outcome each one drove.
- Ask your recruiter which firm and team the role sits in, whether there is an online assessment and which language the onsite expects.
- Warm up on quick probability and expected value questions, which candidate reports mention.
Practice path
Courses that cover the rounds above:
- Modern C++
- Trading Systems Design
- Data Structures and Algorithms
- System Design
- Probability for Quant Interviews
Are you ready for the Citadel quantitative developer interview?
1 / 6Can you solve a medium algorithm problem in C++ or Python in about 30 minutes, with tests?
Frequently Asked Questions
Is a Citadel Quantitative Research Engineer the same as a Quantitative Developer?
Yes. Citadel says Quantitative Developers are also known as Quantitative Research Engineers. Citadel uses the Quantitative Research Engineer title in Global Quantitative Strategies and for PhD campus roles, and Quantitative Developer in its Data Strategies Group. Citadel Securities posts both titles, including a combined Quantitative Developer/Research Engineer posting. Quantitative Researcher is a separate role with its own interview process.
How much does a Citadel Quantitative Developer make?
Citadel postings seen in October 2026 list base ranges of $200K to $250K (Data Strategies Group, New York) and $275K to $350K (GQS Quantitative Research Engineer roles). Citadel Securities lists $250K to $350K for Quantitative Developer/Research Engineer and $175K to $350K for Crypto Quantitative Developer. PhD graduate roles at both firms list $235K to $300K. The PhD intern postings at both firms list a weekly base pay of $4,500 to $5,800.
Can I use AI tools in a Citadel interview?
Citadel does not publish a rule on AI use in interviews; ask your recruiter. Neither firm's engineering process pages or Quantitative Developer postings mention one. The student informational program terms say applicants may not use content generated by generative AI tools to prepare their applicant content, which covers those programs and not job interviews.
Do I apply to Citadel or Citadel Securities?
For campus engineering roles, you go through one process for both. Citadel says interviewers tell you which firm they represent and that the process is the same for both. Team matching across the two firms starts after the second round. Experienced hires apply to a specific posting at one firm.
What happens at the Citadel Securities engineering onsite?
You spend four to five hours on one problem with the same interviewers, with breaks. You gather requirements and design, write the code, review it with the interviewers and discuss it, while they add new requirements. Citadel Securities says the problem comes from systems it runs, such as an order book, and needs no domain knowledge. Many roles expect C++.
Are there internships or new-grad paths into quant development at Citadel?
Both firms post Quantitative Research Engineer PhD Intern (US) roles, 11 weeks in summer, and PhD Graduate (US) roles. Citadel's internships start with a one-week offsite. Both firms profile quant development interns, and Software Engineer intern and university graduate postings are open in the US, Europe and Asia. Citadel also runs Terminal, a team programming competition for students.
Where do Citadel Quantitative Developers work?
Postings across the two firms list New York, Miami, Chicago, Greenwich, Houston, London, Zurich, Hong Kong, Singapore and Sydney. Neither firm states an office or on-call policy for Quantitative Developers.
