← Back to Directory

Hudson River Trading

Mid-sized

Screna has 11 Hudson River Trading interview write-ups. The most reported round is the technical phone screen (11).

11 interview notes · updated Jun 2026

Hudson River Trading·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed for a quant researcher role at Hudson River Trading and got hit with a C++ template design problem that was way more involved than I expected. The whole thing centered on building a generic map wrapper and explaining the design tradeoffs, which felt more like a systems coding round than anything quant-flavored.
  • Design and implement a C++ template class that wraps either std::map or std::unordered_map, where both key and value types can each be int or string. The class should support insert/update, lookup, remove, size, and iteration with correct output formatting, and handle empty containers properly. Be prepared to discuss template specialization and how you keep behavior consistent across both container types.

“This one took me a minute to even parse.”

View Post

Hudson River Trading·Software Engineer·Technical Phone Screen

Jun 2026
HRT quant researcher technical screen, one meaty low-level coding problem about reading typed values out of a raw byte buffer. Felt more like a systems/infra question than what I expected from a quant role, which threw me a bit.
  • Given a raw byte buffer containing a sequence of mixed-type values (characters, integers, and strings) packed back-to-back, implement three functions: read_char, read_int, and read_string. Each takes a buffer and a pointer, reads the next value of its type, and returns both the value and the updated pointer. Also write tests covering reads in arbitrary order.

“This one took me a second to parse.”

View Post

Hudson River Trading·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed for a full-stack role at Hudson River Trading. One behavioral/motivation question about why full-stack over specialization. Pretty standard stuff but it made me think harder than I expected about how I actually articulate my own preferences.
  • Why do you want to work across the full stack rather than specializing in frontend or backend?

“I rambled a bit at first, said something generic about 'liking variety' which felt weak the moment it came out.”

View Post

Hudson River Trading·Software Engineer·Technical Phone Screen

May 2026
System performance debugging question at Hudson River Trading for a full-stack role. Pretty open-ended and they clearly wanted to see how you think through ambiguity under pressure, not just whether you know the right tools.
  • You're on-call and a colleague tells you the app is rendering slowly. Walk through how you'd investigate and fix it from start to finish.

“I jumped straight into browser tooling and React Profiler stuff, which felt right, but I glossed over the triage part way too fast.”

View Post

Hudson River Trading·Software Engineer·Technical Phone Screen

May 2026
Technical phone screen for a full-stack role at Hudson River Trading, focused almost entirely on Python context managers. Pretty deep dive for a single topic, they really wanted to see if you understood the mechanics under the hood, not just that you'd used `with` statements before.
  • Walk me through how the context manager protocol works in Python. What do __enter__ and __exit__ actually do, and what happens when an exception is raised inside a `with` block?
  • Implement a context manager as a class using __enter__ and __exit__, then implement the same thing using contextlib.contextmanager with a generator. What are the differences?
  • Write a timing context manager that records and prints elapsed time when the block finishes.
  • How would you use contextlib.ExitStack to handle nested or re-entrant context managers? Give a concrete scenario where you'd need it.
  • What are the pitfalls of context managers in practice? Things like idempotency of __exit__, deciding when to suppress vs re-raise exceptions, and forgetting cleanup on exceptions.

“This part went okay.”

View Post

Hudson River Trading·Software Engineer·Technical Phone Screen

Apr 2026
HRT coding interview with a simulation-style problem involving watchers and players on a 1D array. Pretty niche problem that felt more like a competitive programming puzzle than a typical algo question.
  • Given a 1D array of length L, watchers and players move at speed 1 per unit time. Watchers start facing left and reverse direction at given (unsorted) timestamps. A player is frozen whenever a watcher occupies the same position. Return how many players successfully reach position L by time T.

“The unsorted timestamps thing tripped me up at first, I just assumed they'd be sorted and almost skipped the sort step entirely.”

View Post

Hudson River Trading·Machine Learning Engineer·Technical Phone Screen

Apr 2026
HRT MLE interview, got a simulation problem described verbally with no written spec which was a bit of a curveball. The problem itself wasn't impossibly hard but keeping track of all the moving pieces while someone is just talking at you is its own challenge.
  • N people start at given positions on a number line and all move right by 1 unit each time step. A watcher also on the number line moves back and forth according to a schedule. Any person the watcher is currently facing cannot move that step. After T time steps, how many people have reached or passed a target position L?

“The problem was described verbally, no written version, so I spent the first few minutes just scribbling notes trying to make sure I had the rules right.”

View Post

Hudson River Trading·Machine Learning Engineer·Technical Phone Screen

Apr 2026
HRT ML Engineer interview, got a continuous-time simulation problem that felt more like competitive programming than anything ML-adjacent. The geometry angle threw me off more than I expected.
  • A watcher and N people all move along a line at unit speed. The watcher changes direction at known timestamps. Anyone in the watcher's line of sight gets frozen in place; otherwise they advance normally. Compute each person's final position at time T.

“My first instinct was to simulate tick by tick, which is obviously wrong at scale.”

View Post

Hudson River Trading·Software Engineer·Technical Phone Screen

Apr 2026
HRT quant engineer interview with some linear algebra that felt more like a math exam than a typical quant screen. The follow-up questions escalated fast and I wasn't fully prepared for where it went.
  • You have an m by n matrix where every row sums to 1 and every column sums to 1. Does this force the matrix to be square?
  • Given that the matrix is square and satisfies those row/column sum conditions, is it necessarily invertible?
  • What if the matrix satisfies those same conditions but also A to the power of 7 equals the zero matrix? Is that possible?

“Got this one and immediately started counting.”

View Post

Hudson River Trading·Software Engineer·Technical Phone Screen

Apr 2026
Technical phone screen for a full-stack role at Hudson River Trading, focused almost entirely on React performance. One long deep-dive question that kept branching into follow-ups. Felt more like a conversation than an interview, which was either a good sign or they were just being polite.
  • Walk through when React decides to re-render a component. How do changes to props, state, and context each factor in?
  • Explain React.memo, useMemo, and useCallback. What does each one actually do and when would you reach for each?
  • What are the downsides of memoization? When does it actually hurt more than it helps?
  • How do you diagnose unnecessary re-renders in a React app? What tools and patterns do you use?
  • A parent component re-renders on every keystroke. How do you prevent expensive child components from re-rendering unnecessarily?

“Started fine, talked through state changes triggering re-renders, parent re-renders pulling children along.”

View Post