Hudson River Trading Interview Experiences

12 results

• 

  An OA and a Mean-versus-Median Estimation InterviewHudson River Trading · Data Scientist · Technical Screen · Sep 2026

  In progress

  I recently finished HRT's OA and first Zoom interview. Sharing the questions here—hope this helps people interviewing later! OA I received the coding OA invitation a few days ago and finished it today. There were three questions: Fancy Number A fancy number is a number that contains only 0 and 1 when written in base 4. Given n, return the count of fancy numbers smaller than n. This probably needs…

• 

  An OA on Budgeted Item PurchasesHudson River Trading · Software Engineer · Online Assessment · Sep 2026

  Input: prices[]: An array of length n, where prices[i] is the price of item i. queries[]: A two-dimensional array whose elements are [start_i, budget_i]. Each query means that only items with indices greater than or equal to start_i may be purchased, with a total budget of budget_i. Rules: Each item may be purchased at most once. The order or positions of the items do not matter; they do not have…

• 

  30 Minutes, Misread One Rule, No Time to FixHudson River Trading · Software Engineer · Technical Screen · Aug 2026

  Rejected

  My HRT interview had the same question as this other post (the link I'm referring to is dropped here). Their bar is really high. In half an hour you need to understand the problem, explain the problem, explain your approach, write the code, explain the code, and run it. I went straight to the optimized solution: record the capacity in each of the four directions (up, down, left, right) for every…

• 

  Rejected After Answering Every QuestionHudson River Trading · Site Reliability Engineer · Technical Screen · Aug 2026

  Rejected

  Role: Site Reliability Engineer I had found a really useful interview report on the forum before mine, and the overlap with what I actually got asked was pretty high. This is also my own area of work, so going into the interview I felt like I had a 100% chance of passing, but I still failed. I'm not really sure why. Let me write up roughly what was asked — honestly you can just ask AI what kinds…

• 

  A LeetCode-Easy Tree Path Question With No C++ TriviaHudson River Trading · Software Engineer · Intern · Technical Screen · Jul 2026

  In progress

  Fresh C++ SWE (Intern) first-round interview report Last week I had my first round for the C++ SWE (intern) position, a 1-hour Zoom coding interview. We spent a few minutes at the start briefly chatting about background, then moved into the problem. The question: given a binary tree where each node has an integer value, and a target, determine whether there's a path from root to leaf where the su…

• 

  A Watcher-and-Players Puzzle in the Technical ScreenHudson River Trading · Software Engineer · Technical Screen · Jul 2026

  This is the problem the interviewer described to me verbally during the technical screen, done in a coderpad environment. They also gave an example along with it. There is a game with multiple players. The road starts at position 0 and ends at position L. Each player has a starting position, and players can only move to the right, one unit per second. There is a watcher, starting at position W, i…

• 

  Hudson River Trading Software Engineer interviewHudson River Trading · Software Engineer · Take-home Project · Jul 2026

  After a recruiter screen, I entered a long technical process centered on a take-home. The lack of feedback was difficult. I spent hours trying to meet the expected behavior without useful checkpoints. The RTL and verification assignment was ambiguous. I adapted my scoreboard to match the buggy RTL behavior, even though I thought a model should stay more abstract and respond only to the specified…

• 

  Hudson River Trading Software Engineer interview on OS and C++Hudson River Trading · Software Engineer · Online Assessment · Jul 2026

  The process was low-level from the start. After an initial online assessment or coding step, I entered live rounds that demanded deep knowledge rather than surface familiarity. I was asked how things work under the hood, down to memory and kernel operation, with an emphasis on the kind of understanding that gives a developer full control. One screen focused on OS topics at an implementation level…

• 

  Perfect OA, Then a Rejection After One 30-Minute Coding RoundHudson River Trading · Software Engineer · New Grad · Technical Screen · Jul 2026

  Rejected

  OA 70 minutes, 4 problems. The first two were super easy. The third one: given an m*n array, you define a diamond by its center point and radius, compute the sum of all the numbers inside the diamond, and return the largest sum among all valid diamonds. The fourth one was street lamps: given a set of lamps, each lamp has a center c and a radius r, so the segment [c-r, c+r] is lit by that lamp. Fi…

• 

  Two Verbal Technical Screens, No Test CasesHudson River Trading · Software Engineer · Technical Screen · Apr 2026

  Both rounds were the interviewer dictating the problem out loud, so I had to take notes — miss one parameter and you're in trouble. Round 1: a one-dimensional array, N players walking to the right. A watcher starts at an initial position and watches the players. A player being watched can't move. The watcher switches direction according to a given list of timestamps. Given a termination time T, f…

• 

  Rejected After the Morning Onsite RoundsHudson River Trading · Algorithm Developer · Intern · Onsite · Mar 2026

  Rejected

  I went to the onsite around October or November last year — sharing my experience getting rejected. I'm a US undergrad. I went through one coding OA and two math online interviews before getting to the onsite. The math rounds covered some probability and combinatorics questions — you need a solid grasp of the Central Limit Theorem and basic probability. The onsite has four rounds: programming, da…

• 

  an OA with almost no test cases givenHudson River Trading · Software Engineer · Online Assessment · Sep 2025

  Just finished the SWE OA, same setup as the reports people have posted in past years. Overall it wasn't that hard — compared to some other trading companies it wasn't especially hard, but the OA email did say you need to write your own test cases, and that turned out to be true. They give very, very few test cases, and there are a lot of edge cases you have to figure out and test yourself. On one…