Guide · Career
Quant recruiting is roughly twelve months ahead of the summer it is hiring for, which means the single most expensive mistake is not a bad interview. It is finding out in November that the thing you were preparing for closed in September.
Every recruiting season produces a set of dates that circulate through group chats, Discord servers, and "deadlines" spreadsheets. A meaningful share of them are wrong, and they are wrong in a specific, repeatable way: the date is real, it is published, it appears on the firm's own website, and it belongs to a different program than the one being discussed.
Three failure patterns account for almost all of it, and once you know them you can catch them in about forty seconds.
| Failure pattern | What actually happened | How to catch it |
|---|---|---|
| Wrong program. "Applications close August 31" | That is the firm's full-time analyst or graduate program deadline. The internship for the same firm opens on a completely different schedule, often months later | Read the graduation-year requirement in the req body. A full-time program asks for a graduation date roughly ten months out; an internship asks for one roughly eighteen months out |
| Wrong date type. "The program closes in August" | August is when the internship itself ends. It is the program's last day on site, not an application deadline | Look for a start date next to it. A date range like June to August is a program duration; a lone date near the word apply is a deadline |
| Wrong cycle or region. "Deadline was October 15" | That page is cached from last year, or it is the London or Amsterdam office and the US req has different dates entirely | Check the year in the program title and the office in the req header. Firms run separate reqs per office with separate calendars |
The rule that follows: a date you did not read on the firm's own careers page, in a req that names your graduation year, is not a date. It is a rumor with a number in it. Treat it as a prompt to go verify, never as something to plan around, and never as something to repeat to someone else.
Before the calendar matters at all, the eligibility string does. Quant internship reqs are unusually explicit about this because the pipeline is built around a specific conversion path: intern the summer before your final year, return full-time. So reqs commonly say something close to must be graduating in 2028 rather than "rising senior" or "undergraduate."
That string is the first thing to read on any posting, before the deadline, before the location, before the description. It decides whether the req is for you at all, and it resolves a large fraction of the confusion about why a friend at another school "got in" to something you were rejected from in twenty minutes. Different graduation year, different req, different pipeline.
Practical consequence: keep a saved search per graduation year, not per company. A firm can have four open reqs in the same week for four different graduating classes, with four different application windows, and only one of them is yours.
This is the earliest and fastest calendar in all of student recruiting, and it is the one most likely to be missed by someone applying on a normal software engineering schedule.
The strategic implication of rolling is not subtle and it is worth stating plainly: seats are consumed as the season progresses. Applying in the first two weeks a req is live versus the sixth week is one of the few genuinely large, entirely controllable factors in the whole process. It is worth more than another month of preparation, because preparation with no seat left is worth nothing.
Expect some combination of timed mental arithmetic, probability and expected-value questions, sequence or pattern reasoning, and a coding section. Some firms use a market-making simulation where you quote bid and ask on an unknown quantity and get penalized for being picked off. None of it rewards memorized trivia; all of it rewards speed on arithmetic you can already do slowly.
Slightly later, more structured, and more likely to include an actual published deadline.
The published-deadline firms in this category deserve a specific habit: put the deadline in a calendar with two alarms, one at four weeks out and one at one week out, and put the source URL in the calendar entry. When the date turns out to have moved, the URL is how you find out rather than the group chat.
The most structured calendar and the most likely to have a genuine, enforced application window.
The most common way to lose a bank application is not the posted deadline. It is the assessment clock that starts the moment you submit, runs while you are in midterms, and expires quietly. Apply when you have a free evening in the next three days, not the moment you see the link.
Names differ by firm, but the shape is consistent enough to plan around.
| Stage | Typical timing after the previous stage | What it is really testing |
|---|---|---|
| Application submitted | Day 0 | Eligibility string, resume screen, sometimes school list |
| Online assessment link | Hours to a few days, often automated | Speed and accuracy under a clock, not depth |
| OA completed | Its own expiry window, commonly a handful of days | Whether you cleared a numeric threshold |
| Recruiter or first technical call | One to three weeks | Communication, motivation, basic screening |
| Technical rounds | One to three weeks | Probability, statistics, coding, and how you think out loud when stuck |
| Final round or superday | One to four weeks | Several back-to-back interviews in a single day, often including a trading or estimation game |
| Offer | Days | Your decision speed, on a window that can be short |
Two things about that table matter more than the individual rows. First, the clock between application and assessment is short and automated, so the practical requirement is that you are ready to sit an OA within a week of applying. Preparing after the link arrives is preparing too late. Second, the total elapsed time from application to offer is commonly one to three months, which is why a firm that opens in the fall is still interviewing when a firm that opens in spring has already closed.
These are genuinely different games and running the junior playbook as a sophomore produces a lot of wasted effort.
The output of this guide should be a table you maintain, not a set of remembered dates. Six columns is enough.
That structure is the same one the tracker on the Apply OS page is built around, and it pairs directly with the sponsorship verification log described in the sponsorship verification guide, since for international students the eligibility question and the calendar question have to be answered together.
Working backwards from the earliest assessment you expect to sit.
| Weeks before your first expected OA | What to be doing |
|---|---|
| 8 or more | Resume finished and ATS-checked. Probability and expected value from a single source, worked by hand. Mental arithmetic drilled daily in short sessions |
| 6 | Timed coding practice on the patterns that recur, in the language you will actually use under pressure |
| 4 | Full-length mock assessments under a real clock, including the ones you expect to fail |
| 2 | Behavioral answers written out once, including a specific and honest answer to why quant rather than software |
| 1 | Applications submitted to the earliest rolling firms. Assessment environment tested: browser, camera, quiet room, backup internet |
| 0 | Sit the assessment on a day you chose, not on the last day of the expiry window |
The coding half of that preparation overlaps heavily with standard technical interview preparation, and the pattern-based approach in the coding interview patterns guide transfers directly. The resume half is the ATS resume guide, and it matters more here than in software recruiting because quant resume screens are notoriously terse.
Every specific date in quant recruiting moves. Firms add cycles, drop cycles, move a program earlier because a competitor did, and run different calendars per office in the same year. Any guide that names dates is out of date the season after it is written, which is exactly why this one names patterns instead.
What does not move is the structure: market makers early and rolling, funds in the middle with occasional hard dates, banks in structured windows with an assessment clock hidden inside them. Graduation year gates everything. The date you heard secondhand is probably attached to a different program. Verify from the firm's own posting, write down the req number and the date you checked, and re-check monthly.
And one thing worth saying because it does not appear on any timeline: a missed cycle is not a closed door. Firms hire off-cycle, they hire from other firms' rejection pools, and a strong project or research record shifts a resume screen more than a single missed application window does. What you are building on the record side keeps compounding regardless of which September you were ready by.
FAQ
It depends on firm type. Market makers and proprietary trading firms often open ten to fourteen months before the internship starts and run rolling. Hedge funds typically open in late summer through fall. Banks frequently open the earliest formal windows, sometimes in spring, with a fixed close date. Verify every date on the firm's own posting rather than from a shared spreadsheet.
Mostly rolling, especially at market makers and proprietary trading firms, where the req simply disappears when the class fills. Banks are the most likely to publish a genuine window, and a minority of funds publish a firm close date. Where a posting has no close date, applying in the first two weeks is worth more than another month of preparation.
Three patterns cause almost all of it: the date belongs to the firm's full-time program rather than the internship, the date is when the internship itself ends rather than when applications close, or the page is cached from a previous cycle or a different office. Check the graduation-year requirement and look for a start date next to any end date.
The graduation-year string in the requisition, which is often stated explicitly as a specific year rather than as a class standing. It decides whether the req is for you before any date does, and it explains why the same firm can have several open reqs in one week with different windows. Copy that sentence verbatim into your tracker.
Frequently within hours to a few days, sent automatically, and it usually carries its own expiry clock measured in days. That means you should be ready to sit an assessment within a week of submitting an application. The expiry clock, not the posted application deadline, is the most commonly missed deadline in the process.
Yes, to sophomore-specific programs first, since insight weeks and second-year programs are a real feeder into the junior pipeline at the same firm. Also apply to any junior req whose eligibility string does not exclude you, because the cost is one application. Sitting a real timed assessment is worth more than untimed practice even if you do not pass it.
Commonly timed mental arithmetic, probability and expected value, pattern or sequence reasoning, and a coding section, sometimes with a market-making simulation where you quote two-sided prices. It rewards speed on arithmetic you can already do slowly rather than memorized material, which is why timed practice matters more than volume of untimed problems.
Commonly one to three months from application to offer, spread across an assessment, one or two technical rounds, and a final day of back-to-back interviews. Offer decision windows can be short, so decide how you would rank competing firms before you are holding an offer rather than after.