Real, anonymous reports from people who interviewed for Quantitative Analyst at Hudson River Trading, newest first and distilled into what to expect across the loop.
The path I went through felt very math-first, then coding/verification second. After a recruiter touchpoint, I ended up with technical rounds where probability and strategy questions came up early, and the sessions were intense enough that it didn’t feel like I could “wing it.”
I started with an online coding assessment on platforms like CodeSignal or HackerRank. The format felt consistent: a couple of problems under strict time limits, where I had to write efficient, well-optimized code rather than just a working solution. In my head, I was prepared for normal debugging, but the time pressure and the “edge” nature of the tasks made it feel closer to LeetCode-style competition than typical SWE practice.
The interview process typically begins with an online assessment followed by multiple technical rounds focusing on math, probability, and coding, often culminating in a decision within a month. Candidates noted that the early stages felt heavily evaluative, with less emphasis on casual conversation.
Candidates complete an online assessment that includes multiple coding questions under strict time constraints, often resembling competitive coding challenges rather than typical software engineering tasks. The focus is on correctness and efficiency, with scoring based on complete solutions rather than partial progress.
The interviews emphasize a mix of probability, statistics, and coding, with a strong expectation for candidates to demonstrate clear reasoning and problem-solving skills. Questions often require deriving strategies or solutions rather than simply coding them, reflecting the role's quantitative nature.
Candidates report that coding challenges are typically medium to hard in difficulty, with a significant emphasis on clean coding and the ability to explain one's thought process. The challenges are designed to test not just technical skills but also strategic reasoning under pressure.
While the technical rounds are rigorous, some candidates experienced friendly and supportive communication during initial screenings, which may help ease the pressure. However, the overall tone remains firm regarding performance expectations.
Candidates often reflect on the importance of mastering core requirements and the need for clear reasoning under timed conditions. Many wished they had focused more on strategic thinking and problem-solving rather than just coding proficiency.