Dataford
Dataford
H
Hudson River TradingQuantitative Researcher
Updated Apr 16, 2026

Hudson River Trading Quantitative Researcher Interview Experiences 2026

Real, anonymous reports from people who interviewed for Quantitative Researcher at Hudson River Trading, newest first and distilled into what to expect across the loop.

Get your personalized Hudson River Trading Quantitative Researcher prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Build my free plan
Hot & recentNewest first
6 months ago
Difficult Positive New York, NY

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.

Across my session, the questions leaned toward medium-to-hard problem solving, and the scoring seemed to be based on correctness of the full solution, not partial progress. I finished what I could, passed all the visible tests, but the experience still felt like it hinged on hidden constraints. It ended with a rejection after I completed the assessment, and the hardest part wasn’t syntax or logic—it was the feeling that performance and completeness under a timer were everything.
11 months ago
Difficult Positive New York, NY

My process kicked off with something that felt almost resume-based at first—high-level questions and conversation before things turned clearly technical. Eventually, the rounds shifted into probability and statistics, and then back into coding, with technical performance carrying most of the weight as the interview sequence went on.

After the early phone-style screening, I had an OA and then multiple live rounds. The live portion mixed probability/statistics with coding questions that were more problem-solving than open-ended engineering, and the difficulty felt pretty demanding but not chaotic. One round was short—around 45 minutes—with a LeetCode-medium flavor, and the interviewers were generally nice and straightforward. I also remember being surprised by how quickly the whole loop moved to a decision; the final rejection came the next day after my last interview.

Unlock every Quantitative Researcher interview experience

Real Quantitative Researcher interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.