Team tests
Web form · 30 min; 3 hoursWhat a team sends is the team's choice, and many send nothing and go straight to a call. Two forms are here. The coding test is one HackerRank question on a 30-minute clock. The research test is three hours of pandas on stocks and factors: deal with the missing values and outliers, fit a linear model, find the best one under stated requirements, and explain every step. Some teams set the research test after the first call, as four hours or as a week, and the next interview is about the choices you made in it.
First round
Virtual · 30 min – 1 hourA phone or video call with a researcher from the team, or the portfolio manager. The first half is one paper, project or internship in fine detail: how long and wide the data were, the variables, how well the model fits, every formula. Then about three questions on regression, probability and statistics, asked aloud and sometimes loosely worded, so ask until the set-up is clear. Some teams put three interviewers on a single 30-minute call and ask only about the CV.
Team interviews
Virtual · 1–3 × 30–60 minMore one-to-one calls with the team, days apart: five rounds in all is a full loop, two is common. Probability classics and small games; testing, regression and machine-learning concepts across a lot of ground with few derivations; one or two short coding problems with questions about C++ or pandas. Teams ask the same question of different candidates, and two teams can ask you the same one. There is no day of back-to-back interviews for interns.
Portfolio manager
Virtual · 30–45 minThe head of the team, first on some teams and last on others. Your most quantitative piece of work step by step, whether it was tested live, what you would do with more time; then an open question on turning a dataset into a forecast or building a portfolio. Candidates with trading experience are pressed for the details of past signals. A portfolio manager who likes you can make the offer after a weak technical round.
Offer: The offer comes from the team that interviewed you and the summer is spent on that team. Meeting a team in person, at the Cubist hackathon each April or at a research conference, can replace most of the loop with one conversation.