Skip to main content

How Hudson River Trading Interviews in 2026: Process, Questions & What They Score

The complete process, reported questions, and what interviewers score.

Hudson River Trading / Interview snapshot

6

stages from
application to offer

34

reported questions

19

public sources

Last verifiedOct 2026
HOW TO READ THIS PLAYBOOK

Independent: SupaCV is not affiliated with or endorsed by Hudson River Trading. This is one well-documented shape of Hudson River Trading's interviews, not a script: processes change and vary by role, team, level, and region, so confirm specifics with your recruiter.

Medium confidenceSources
On this page

01 / For every Hudson River Trading candidate

The process, start to finish.

Hudson River Trading (HRT) is an engineering-first algorithmic trading firm. It is best known for hiring Software Engineers (including the low-level Software Engineer (Core Development) role) and Algorithm Developers (quant researchers who build trading models). This playbook covers both technical tracks, because HRT's own student page describes one shared process for them.

The official outline is a coding test, one or two technical phone screens, and an onsite multi-round final interview, and HRT notes that interview length and topics vary by role. HRT also says it may take up to 2 weeks to review an application, asks candidates to apply to only one posting, and has Algorithm Developer applicants choose C++ or Python. Software Engineering applicants state a C++ or Python preference.

Two HRT Beat blog posts add official detail: a September 2021 post written for the 2021-2022 campus season (a timed take-home test, roughly two phone interviews, and a full-day onsite) and an October 2025 post (the process starts with Zoom calls, and onsite rounds are coding and debugging, technical design discussions and team fit). Everything beyond those official pages comes from third-party prep sites and candidate reports, and they do not always agree.

Two guides describe a recruiter call of about 30 minutes, and most name a timed online assessment on HackerRank, Codility or CodeSignal; one prep site calls that assessment HRT's biggest cut. Next come one or two live screens of 45 to 60 minutes. For Algorithm Developers these are usually one probability or statistics screen and one coding screen. The final round is reported as roughly 4 to 6 rounds in one day.

For engineers it covers hard algorithmic coding plus C++, OS and low-latency systems fundamentals. For Algorithm Developers, reports describe probability and expected value, data analysis in a Python notebook, and work in an existing C++ codebase, and several guides add a behavioral or project deep dive. Reported timelines from first contact to offer run from about 3 weeks to 2 months.

HRT publishes no formal scoring rubric, but its September 2021 HRT Beat post lists six areas it evaluates in onsite interviews, and those six are used as the framework here. That post was written for one past campus recruiting season and covers Software Engineering and Algo Engineering interviews, so it may not describe the current Algorithm Developer process.

Stage 1:

Application review

up to 2 weeks

HRT says it may take up to 2 weeks to review an application and that it reaches out by email about next steps. Candidates may apply to only one posting and can say in the application questions whether they are interested in other offices or roles. Algorithm Developer applicants choose C++ or Python. SWE applicants state a C++ or Python preference at the application stage, and HRT's October 2025 engineering post says some roles also offer Typescript/Python (Fullstack). Third-party guides say this step routes engineers into a General SWE or Core Developer track; HRT's interview pages do not describe that routing, although its Work at HRT page does list a Software Engineer (Core Development) role.

Stage 2:

Recruiter screen

about 30 minutes

Two third-party guides describe a short call about background, motivation and logistics, and put it at about 30 minutes; HRT gives no length. HRT's student page does not list this stage, but HRT's October 2025 engineering post says the process begins with a series of Zoom calls that can be exploratory conversations or go straight to technical phone screens. TraderMath says recruiter and fit conversations are often interleaved with the technical rounds, so this may not be a separate early call for every candidate.

Not in HRT's student-page stage list; the 30-minute length is third-party only

Stage 3:

Online coding test

varies (about 70 to 150 minutes)

HRT officially lists a coding test. HRT's 2021 interview post says take-home tests are usually timed with a deadline and typically run on HackerRank or Codility; third-party reports name HackerRank and CodeSignal. Length and content depend on role and year. Algorithm Developer sets are about 150 minutes with 3 problems. SWE intern sets are about 70 to 90 minutes with roughly 4 LeetCode-style problems. One quant analyst variant is a 30-minute, C++-only test. Difficulty is reported anywhere from easy-medium (a Singapore intern report) to several LeetCode Hard equivalents. One prep site calls this stage HRT's biggest cut, and Quantt and a Blind post report rejections before any screen, but no source gives pass rates. HRT's October 2025 post says some candidates try to cheat the earlier stages with LLMs and that cheating candidates are not welcome to interview again later.

Stage 4:

Technical phone screens (1 to 2)

45 to 60 minutes each

HRT officially says there are 1-2 technical phone screens. HRT's 2021 post describes roughly two phone interviews: a technical discussion, usually about 45 minutes, on systems knowledge, data structures or problem solving, and a programming interview aimed at the team's skills. Engineering screens are reported as live coding in a shared editor such as CoderPad, on a medium-to-hard problem, with follow-ups on edge cases and complexity (TechPrep and DesignGurus describe a single 60-minute screen). One Software Engineer candidate report describes C++ and OS screens on pointers, references and internals without naming the track; third-party guides say Core Developer loops go deeper on low-level systems. Algorithm Developer candidates usually get one probability, statistics or brainteaser screen (about 45 minutes) and one programming screen (45 to 60 minutes) in C++ or Python, although one Algorithm Developer intern report describes two online math interviews instead. One intern candidate reports being rejected after the first coding round, which was a LeetCode medium.

Stage 5:

Onsite final round (multi-round)

varies (about 4 to 6 rounds in one day)

HRT officially calls this an onsite multi-round final interview. HRT's 2021 post describes a full day of back-to-back interviews, virtual or in person, and gives no round count. HRT's October 2025 post says onsite rounds are generally coding and debugging, technical design discussions and team fit, and that HRT prefers at least some of them in person. Third-party guides give 4 to 6 rounds (TraderMath says around five) and add hard coding rounds, a C++, OS or low-latency systems round, and a behavioral or past-project deep dive. Per-round length is only partly reported: TechInterview gives 60 minutes for coding rounds, and one Algorithm Developer intern report describes four one-hour rounds: programming in an existing C++ trading codebase, data analysis in a notebook, system design, and math. In that report lunch sat between the morning and afternoon sessions, and the candidate was cut after the morning rounds. Round count and mix vary by track and level.

Stage 6:

Decision and offer

varies (about 3 weeks to 2 months end to end)

HRT publishes no overall timeline. Third-party estimates are 4 to 8 weeks from first contact to offer (onsite scheduling can add 1 to 2 weeks), 1 to 2 months from application to decision, or 3 to 5 weeks across 3 rounds. One Algorithm Developer review cited by Quantt took about 3 weeks. DesignGurus says recruiters generally share the outcome within days of the onsite, though timing varies by team. Two 2022 Blind posters report waiting a week or more for replies between stages.

Reported interview time, one scale in minutes

Where the minutes go

  • Recruiter screen~30 min
  • Online coding test~150 min
  • Technical phone screens60 min

Not drawn: Application review, Onsite final round and Decision and offer, whose durations are not given in minutes.

02 / What Hudson River Trading scores

The framework.

Onsite interview evaluation areas (HRT Beat, September 2021)

  1. 01

    Programming skills

  2. 02

    Systems-level knowledge

  3. 03

    Problem-solving skills

  4. 04

    Collaboration

  5. 05

    Teachability

  6. 06

    Communication

Source is an official HRT Beat blog post dated Sep 15, 2021 by Dani Ortiz (the post does not state the author's role), under its Onsite Interviews heading. The first three items follow a line about looking at your programming skills. The last three follow a line saying these are areas HRT is evaluating, after a sentence that technical skills are not the only thing evaluated. The post is not a formal scoring rubric.

It was written for the 2021-2022 full-time campus recruiting season and covers Software Engineering and Algo Engineering interviews, says internship processes are similar but slightly abridged, and says HRT is constantly iterating on the process, so it may not match the current process or the Algorithm Developer track; recruiter guidance takes precedence. HRT's October 2025 engineering post separately says engineers are rated as much on communication as on technical ability and names no formal rubric.

03 / Coach's notes

Coach's tips.

  1. 01

    Pick your language on purpose when you apply. HRT has Algorithm Developer applicants choose C++ or Python, SWE applicants state a preference, and its October 2025 post adds a Typescript/Python (Fullstack) option for some roles. Third-party guides say Core Developer and low-latency loops go deep on C++ and OS topics (pointers and references, memory layout, concurrency, cache effects), and one Software Engineer report describes screens on how pointers, references and OS internals work under the hood. Choose C++ only if you can explain how it works underneath, not just write it.

  2. 02

    Apply to one posting only, as HRT asks, and use the application questions to name other roles or offices. Expect the online assessment to be a hard filter: one prep site calls it HRT's biggest cut, and some candidates report rejections before any screen. Practice timed medium and hard problems with simulations and data processing. HRT's own 2021 advice is that the sample test cases are not comprehensive, so think through corner cases and submit clean code that handles them. HRT's October 2025 post says it tries to avoid burst-of-insight LeetCode-style questions, so fundamentals matter more than tricks.

  3. 03

    Check probability answers with code. A January 2026 first-round report, a Glassdoor pattern for quant analyst screens, and strategy-game onsite rounds all pair a statistics or strategy question with writing a simulation to check it. Practice expected value and probability problems alongside quick Python Monte Carlo scripts.

  4. 04

    Algorithm Developer finalists should practice two less common formats: adding a feature to an unfamiliar C++ client and server codebase (order modify on top of add and cancel), and open-ended data analysis in a notebook with pandas. One intern was cut after the morning rounds, so the first rounds matter as much as the last.

  5. 05

    Talk through your reasoning and state your assumptions as you code. HRT says it rates engineers as much on communication as on technical ability. Its 2021 post says it is ok to need hints, guidance and to make mistakes, and suggests working a small example on paper before coding. Its October 2025 post lists not fully understanding the problem before diving in as a common failure in interview feedback. Third-party guides add that interviewers value narrated reasoning and that an off-by-one error can still lead to rejection, so trace your code on empty and one-element inputs before you say you are done.

  6. 06

    For the behavioral or fit conversation, prepare two or three real project deep dives and one technical disagreement. HRT's 2021 post says it looks at how you work with others (taking hints, openness to a different approach) and whether you explain past work at the right level of detail and check that the interviewer is following. For the disagreement story, be ready to name the evidence you brought and how you committed to the final decision, rather than telling a story where you were simply right.

  7. 07

    Do the early assessments on your own. HRT's October 2025 post says some candidates try to cheat the earlier stages with LLMs, that later stages are much harder to cheat in, and that cheating candidates are not welcome to interview again later.

04 / The research

Where this page comes from.

Compiled from public sources across 11 sites. Hudson River Trading's own page is among them: hudsonrivertrading.com/student-opportunities.

sites
11
coaching and prep guides
13
Hudson River Trading's own pages
5
candidate reports and forums
1

Source composition

Where the research comes from

Grouped by the kind of site that published each source: Hudson River Trading's own domain, candidate forums, and everything else.

  • Coaching and prep guides13
  • Hudson River Trading's own pages5
  • Candidate reports and forums1

05 / The questions

Reported questions, by category.

Showing questions for

Roles are grouped by the category each question fits, not by the source.

Coding and Algorithms

14 questions

  1. Count the positive integers below n (n up to 10^9) whose base-4 digits are all 0 or 1 (the 'fancy numbers' problem).

    Digit-based counting over the base-4 digits of n, since checking every number is too slow at 10^9.

  2. Implement a game simulation such as 2048 or Reversi/Othello.

    Careful board-state simulation and rule edge cases, written correctly under a clock.

  3. Implement a class that supports add(x) and median(), both with sub-O(n) complexity per call.

    Data structure design, such as two heaps or an order-statistic tree, for sub-linear add and median.

  4. Write code that finds the best poker hand, live, in 45 minutes.

    Hand-ranking logic with counting and sorting of ranks and suits, coded live while narrating.

  5. Filter sets of timestamped trades and calculate the resulting profits.

    Data processing: filtering timestamped records and aggregating profit correctly within the time limit.

  6. Design a deque with O(1) push and pop at both ends and O(1) random access.

    Circular buffer or chunked array design that keeps end operations and indexing at O(1).

  7. Given street lamps on a one-dimensional line, find how many lamps light each point, or the smallest integer point lit by the most lamps.

    Sweep line or difference array to count overlapping coverage intervals along a line.

  8. How would you implement a hashmap, handle collisions, and keep amortized time complexity during resizing?

    Hash table internals: collision handling, load factor and the amortized cost of resizing.

  9. Given N large sorted log files that do not fit in memory, merge them into a single sorted file.

    External k-way merge with a min-heap and buffered reads when the data exceeds memory.

  10. Design a scheduler that triggers a callback after T milliseconds and supports cancelling it.

    Timer scheduling with a min-heap or timing wheel, plus bookkeeping for cancellation.

  11. Implement a pool allocator in C++.

    Low-level C++ memory management: fixed-size blocks, a free list and alignment.

  12. Wrap a stream reader that returns fixed-size chunks so that it supports reads of arbitrary length.

    Buffering and leftover-state handling to turn fixed-size chunk reads into arbitrary-length reads.

  13. Find a local minimum in a one-dimensional array and then in a two-dimensional grid.

    Binary search on the local-minimum property, extended from one dimension to a grid.

  14. Solve a tree path problem involving minimum excluded primes.

    Tree traversal combined with number theory, such as primes and minimum-excluded values on a path.

Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.

C++, Systems and CS Fundamentals

8 questions

  1. Explain the amortized complexity of std::vector push_back.

    Amortized analysis of dynamic array growth, capacity doubling and reallocation cost.

  2. Explain threads versus processes and how virtual memory works.

    OS internals: isolation and sharing in threads versus processes, and paging in virtual memory.

  3. What is the difference between stack and heap memory, and what is the memory layout of a process?

    Process memory layout and the lifetime and cost differences of stack versus heap allocation.

  4. How does memory alignment affect struct sizes, and what is Small String Optimization?

    Struct padding and alignment rules, plus the small-buffer optimization in std::string.

  5. What commonly causes segmentation faults in high-performance C++ code, and how do you handle them?

    Debugging C++ memory errors such as dangling pointers, out-of-bounds access and stack overflow.

  6. Analyze the potential causes of latency spikes in a low-latency trading system.

    Systems diagnosis: cache misses, page faults, lock contention, allocation and scheduler jitter.

  7. Two threads each increment a shared counter 1 million times, and the counter ends below 2 million. Why?

    Data races on non-atomic increments, and the fix with atomics or locks.

  8. Design a service that consumes a real-time order flow feed, computes per-trader and per-strategy P&L and risk exposures, and alerts when limits are breached, within a 1 millisecond latency budget.

    Low-latency system design: event pipeline, in-memory aggregation state and a strict latency budget.

Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.

Algorithm Developer Practical Rounds

2 questions

  1. You are given an existing C++ client and server trading codebase that supports adding and cancelling orders. Implement order modification.

    Reading an unfamiliar C++ client and server codebase and extending it by adapting the add and cancel code.

  2. Explore a provided dataset in a Python notebook using pandas and plotting (one intern report: a heart disease prediction dataset, documentation allowed).

    Exploratory data analysis with pandas and plots in a Jupyter notebook, reasoning about real data.

Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.

Every role

Behavioral and Fit

3 questions

  1. Tell me about a time you disagreed with a technical direction. How did you challenge it, and how did you resolve it?

  2. Walk me through the most complex system you have built, including the trade-offs you made.

  3. Walk me through your background and why you want to work at HRT.

Your next step

Interviewing at Hudson River Trading?

Make sure your resume gets you to the first round.

Practicing for Hudson River Trading against your resume is in Interview Prep on Career.

Common questions

Quick answers.

How many stages are in Hudson River Trading's interview process?

Hudson River Trading has 6 stages, set out in The process.

What framework does Hudson River Trading use to evaluate candidates?

Hudson River Trading evaluates candidates against Onsite interview evaluation areas (HRT Beat, September 2021), set out in What Hudson River Trading scores.

What kinds of questions does Hudson River Trading ask?

Hudson River Trading's questions fall into 5 categories, grouped in The questions.

How reliable is this Hudson River Trading interview playbook?

It is compiled from public sources, and the evidence is in The research.

Sources (19)

Every public source this page was compiled from. Links open in a new tab.

11 sites, by sources

  • hudsonrivertrading.com5
  • prachub.com4
  • jointaro.com2
  • tradermath.org1
  • quantvault.org1
  • techprep.app1
  • quantt.co.uk1
  • designgurus.io1
  • techinterview.org1
  • teamblind.com1
  • everythingquant.com1
  1. 01hudsonrivertrading.com/student-opportunities
  2. 02hudsonrivertrading.com/hrtbeat/interview-at-hrt
  3. 03hudsonrivertrading.com/hrtbeat/engineering-and-interviewing-at-hrt
  4. 04hudsonrivertrading.com/careers
  5. 05hudsonrivertrading.com/work-at-hrt
  6. 06tradermath.org/articles/hudson-river-trading-interview-guide
  7. 07quantvault.org/hrt-interview-process.html
  8. 08techprep.app/blog/hudson-river-trading-interview-process
  9. 09quantt.co.uk/resources/hudson-river-trading-interview
  10. 10designgurus.io/answers/detail/what-is-the-hudson-river-trading-interv…
  11. 11prachub.com/interview-guide/hudson-river-trading-software-engineer…
  12. 12prachub.com/companies/hudson-river-trading
  13. 13prachub.com/interview-experiences/hudson-river-trading-intern-algo…
  14. 14prachub.com/interview-experiences/hudson-river-trading-software-en…
  15. 15jointaro.com/interviews/companies/hudson-river-trading/experiences/…
  16. 16jointaro.com/interviews/companies/hudson-river-trading/experiences/…
  17. 17techinterview.org/companies/hudson-river-trading
  18. 18teamblind.com/company/Hudson-River-Trading/posts/hudson-river-tradin…
  19. 19everythingquant.com/interview-prep/hudson-river-trading/interview-questions