An AI interview assistant helps with a Citadel onsite only before the day: scored mock interviews for the fit conversations, Coding mode drills with Big-O and edge cases, and spoken practice of probability and systems answers. During the onsite itself, whether in a Citadel office or on a video setup with proctoring norms, it stays closed. That is our firm position for every quant firm, not a hedge. Below: what a Citadel onsite tends to cover as publicly described, a preparation plan for each block, and why the policy line sits where it does.
What a Citadel onsite tends to cover
Candidates describe a half day to a full day of back-to-back sessions, each with one or two interviewers, after a recruiter screen and one or more technical phone or video rounds. For software engineering roles the blocks are coding (data structures, algorithms, performance, often in C++ or Python), systems (concurrency, memory, latency, operating systems and networking), a mathematics and probability block, and conversations with team leads about fit and past work. Quantitative research candidates see more probability, statistics and modeling and less systems. The onsite happens in a Citadel office or on video with camera on, identity checks and screen sharing; details vary between Citadel and Citadel Securities, by team and by level, and nothing here is a confirmed question list.
The Citadel coding interview page covers the problem families candidates report, and our quant interview prep guide covers the mathematics side.
Why the assistant stays closed during the onsite
Three reasons, and any one would be enough. First, quant firms state their rules plainly: onsites are closed-book, candidates sign confidentiality terms, and video onsites follow proctoring norms. Our page on AI interview assistants and proctored assessments explains why we treat any proctored setting as off limits. Second, an in-person onsite is physically closed to a desktop assistant anyway; our in-person interview page covers what preparation looks like when nothing comes into the room with you. Third, the interviewers are grading how you think under pressure, which is the job. A drafted answer on your screen would not help you do that job later. Follow your employer's rules; here they are not ambiguous.
Preparation plan by block
Coding. Three or four weeks of daily problems. Turn Coding mode on (Ctrl+Shift+C) for practice problems to get a solution with Big-O and edge cases, then rewrite it yourself without looking and explain the complexity aloud with Talk answer (Ctrl+Shift+E). Time yourself at 35 minutes per problem.
Mathematics and probability. Expected value, conditional probability, combinatorics, Markov chains, basic statistics and mental arithmetic under time. Work problems on paper, then explain the solution to the mock interviewer aloud; being graded on the explanation is what the onsite feels like.
Systems. For engineering roles, rehearse spoken answers on caches, locks and lock-free structures, memory layout, kernel bypass and what happens between a packet arriving and an order going out. Use the system design mix.
Fit. Why Citadel, why this team, a project you owned end to end, a time you were wrong. Run the behavioral mix at your level until each answer is under two minutes.
Block by block: practice first, closed on the day
| Block | What it tests | Practice with the assistant | During the onsite |
|---|---|---|---|
| Coding | Algorithms, performance, clean code | Coding mode on practice problems; explain complexity aloud | Closed |
| Mathematics and probability | Reasoning under time, clear explanation | Solve on paper, then narrate to the mock interviewer | Closed |
| Systems | Concurrency, latency, memory, networking | System design mix; spoken answers | Closed |
| Fit with team leads | Motivation, ownership, honesty | Behavioral mix at your level | Closed |
| Recruiter logistics calls | Scheduling, compensation expectations | Rehearse the standard set | Captions only if the recruiter explicitly permits it |
Where CoPilot Interview fits
CoPilot Interview is a desktop AI interview assistant for Windows 10 and 11 and macOS 12 and later, with a practice-first iPhone build on TestFlight and an Android companion in beta. For a Citadel onsite it is a preparation tool and nothing else: Coding mode and Talk answer for practice problems, scored mock interviews across the technical, system design and behavioral mixes on the free plan, and a four-week routine that ends the night before the onsite with the app closed. Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
Can I use an AI interview assistant during a Citadel onsite?
No. Citadel onsites are closed-book, run in an office or on video with proctoring norms, and covered by confidentiality terms. The assistant is a preparation tool for the weeks before: Coding mode drills, probability practice explained aloud and scored mock interviews for the fit conversations.
What does a Citadel onsite cover?
Candidates describe back-to-back sessions on coding, systems, mathematics and probability, and fit with team leads, with quantitative research roles weighted toward probability and modeling. It varies between Citadel and Citadel Securities, by team and by level, and no confirmed question list exists.
Does the same rule apply to a video onsite with a proctor?
Yes. A video onsite with camera on, identity checks and screen sharing is a proctored setting, and we treat every proctored setting as off limits for live help. Prepare beforehand with practice problems and mock interviews, then close the app before you join.
How long should I prepare for a Citadel onsite?
Three to four weeks of daily work is typical: one timed coding problem a day, probability on paper explained aloud, spoken systems answers twice a week, and a scored mock interview for fit once a week. Stop the night before and sleep.
Drill the blocks before the day
Coding mode, probability explained aloud and scored mock interviews on the free plan; then close the app and walk in.
Try a practice question