U.S. dates and the eligibility conflict
The October 1 check confirms the published U.S. schedule below. Neither the overview nor the U.S. application gives a cutoff time or timezone, and neither names the exact April event days. Submit before the final day rather than assuming a local-midnight cutoff.
| Question | Answer |
|---|---|
| Format | Two-day discovery event, not an internship offer. |
| U.S. event | Early April 2027 in New York; exact days not published. |
| U.S. application deadline | March 5, 2027; cutoff time and zone not supplied. |
| Eligibility conflict | Overview: December 2027–June 2029 graduation. U.S. application/terms: December 2028–June 2030. Clarify your actual standing and graduation date before applying. |
| Materials | Résumé with cumulative GPA; no minimum published. Follow the official application and Applicant Content terms. |
| Item | Requirement or date |
|---|---|
| Application deadline | March 5, 2027 |
| Notification | By March 12, 2027 |
| Event | In person, New York; early April 2027 |
| Résumé | Include cumulative GPA; the overview does not state a minimum GPA |
| Source | Academic requirement | University or regional scope | Sources |
|---|---|---|---|
| Program overview | First- or second-year students; graduation December 2027–June 2029 | Based in the U.S. states, D.C. or Canada: considered only for the U.S. event | |
| U.S. application | Undergraduate in good standing, age 18 or older; graduation December 2028–June 2030 | University in the U.S. states, U.S. territories, D.C. or Canada | |
| Linked 2026/27 terms | First- or second-year undergraduate, age 18 or older; graduation December 2028–June 2030 | Good standing at an accredited university in the U.S., its territories, D.C. or Canada |
The official overview and U.S. application disagree on graduation dates. The linked 2026/27 terms agree with the application’s later window and also require first- or second-year standing. Compare your actual university year and expected graduation with both; if they do not align, ask Citadel which rule applies rather than changing your academic information.
The terms say the applicable program site governs a discrepancy with the terms, and Citadel resolves ambiguities. That does not resolve the disagreement between these two official web pages for you. The comparison records what each source says at this check.
What the U.S. application asks you to provide
The form asks for contact information, education history, a résumé, role interest and preferred work region. It accepts DOCX, DOC, PDF or TXT résumé files up to 10MB. The overview separately instructs applicants to include cumulative GPA; it states no minimum.
It also asks about summer-internship return offers and late-stage competing processes, and provides fields for links to academic or technical work. Report your actual situation. Publicly readable fields do not establish which later questions or selection steps will apply to you.
Before submitting, check that the file opens, dates match your education record and any work link leads to your own accessible project. A portfolio should make your contribution clear; include work you can explain.
What travel is covered, and what remains your responsibility?
The U.S. application lists economy return flights, airport transfers, a single-occupancy hotel for two nights and program-day meals. The approximate $750 benefit value is not a cash stipend. Participants are responsible for taxes on benefits.
The terms require booking through Citadel’s travel agency. Nearby participants may receive ground transport instead of airfare and no hotel; uncovered costs remain theirs. Confirm your itinerary and spending arrangements before booking independently.
The linked terms prohibit generative AI content, data, inputs or outputs in preparing Applicant Content; basic grammar checking is permitted. The independent exercises in this guide are for learning, not material to reuse in a Citadel application. Read the official terms and prepare your own applicant content.
Give one reason to explore a particular kind of work
The event introduces quantitative research, software engineering and trading. Your preparation should give you a question about at least one of them.
For example: “In a class project, a promising result weakened when I changed the sample. I want to understand how researchers decide what evidence is strong enough to use.” Or: “I enjoyed debugging a data import and would like to learn how software teams test changes before others depend on them.” These are fictional examples; use work you have done.
When your class standing and graduation date do not tell the same story, ask which rule the organizer applies. An accelerated timetable is a reason to clarify the application, not to alter your academic record.
Sources[1]
A positive average can depend heavily on one observation
Practice example, not a Citadel assessment: a toy method scores +8, +7, −6, −7 and +8 units across five test periods. The average is +2, and a teammate recommends using it immediately.
The arithmetic is right: the scores sum to +10, and +10 ÷ 5 = +2. But the worst period is −7, and the five observations do not tell you how the method was chosen or whether these were also the observations used to tune it.
As a sensitivity check, the first four observations sum to +2 and average +0.5. Removing the final observation cuts the average sharply. That does not justify deleting it; it tells you the sample result is sensitive to one observation.
A defensible answer is: “The five-period average is positive, but I would not rely on it yet. I need to know how the sample was selected, which costs were included and how the method performs on a separate test under fixed rules.” That states the observed result without turning it into an unsupported forecast.
Bring a project another person can inspect
Choose one project with a clear question, method, check and limitation. For code, show how to run a small example and what the tests cover. For analysis, explain the data definitions and any excluded records.
A résumé bullet can be modest and useful: “Tested a forecasting prototype on a public dataset; compared results across time windows and documented where the conclusion changed.” Use that only when it describes your work. A classroom result is not evidence of a production improvement.
Prepare to discuss one failed approach. Explain what contradicted your expectation and what you changed. That conversation shows more understanding than adding another tool name to the skills section.
Use the event to choose your next application
Ask for an example of a junior assignment and how it is reviewed. Then compare that work with the part of your own project you wanted to keep doing: investigating a pattern, building the system, or making a decision under uncertainty.
Keep Citadel and Citadel Securities distinct when you later choose roles. The event includes both; a job application names a particular organization and team.
A useful outcome is a more precise target and a better explanation of fit. Record the actual program title and dates if you list attendance, rather than describing a two-day event as employment.