Real, anonymous reports from people who interviewed for Software Engineer at Hudson River Trading, newest first and distilled into what to expect across the loop.
My process leaned hard into “under-the-hood” depth. I remember getting questions that weren’t just algorithmic—they dug into how operating systems actually behave, including implementation-level ideas, and how low-level details affect what your code does under the hood. There were also discussions that tied back to data structures and networking, plus a deeper follow-up on my prior project and what exactly I’d done.
After a recruiter call, I had a short technical round where the interviewer moved very slowly and I had to take notes while the problem was being delivered, just to make sure I didn’t miss anything before I could fully understand what they were asking. It felt like the expectation was that once I finally got it, I’d be able to execute cleanly and essentially “one-shot” the solution within the tight time window.
The interview process typically begins with a rigorous online assessment that includes multiple coding problems, often in a LeetCode-style format, with a strict time limit. Candidates report that performance on the OA is critical, as it can determine whether they progress to the next stages.
Following the OA, candidates usually undergo one or more technical phone screens that focus on systems fundamentals, C++ specifics, and problem-solving skills. These interviews often require candidates to articulate their thought processes clearly and demonstrate a deep understanding of technical concepts.
Some candidates experience discussions that delve into their past projects and relevant experience, often assessing cultural fit and motivation for the role. These conversations can vary in tone, with some being more structured and others feeling more conversational.
The onsite interviews typically consist of multiple back-to-back sessions that cover a mix of technical assessments, system design, and behavioral questions. Candidates note that the pace can be intense, and the focus is often on maintaining alignment with the interviewers' expectations throughout the rounds.
Candidates describe the interview process as challenging, with a high bar for precision and depth in technical discussions. Small misunderstandings can lead to significant setbacks, and many candidates feel that the process is unforgiving, especially in the early rounds.
Some candidates report experiencing scheduling challenges and communication issues throughout the interview process, which can lead to frustration and a sense of disorganization. These factors can impact the overall candidate experience and perception of the company.