Hudson River Trading Interview

The Hudson River Trading interview is the most coding-heavy loop in quant-trading recruiting. HRT is an algorithmic trading firm — it builds automated strategies that trade across thousands of markets, and the people it hires write the code that does it. So while peers like Optiver and Jane Street gate on a timed arithmetic test, HRT gates on algorithms. Expect a HackerRank-style coding screen up front, hard data-structures-and-algorithms problems in the loop, and probability and brainteasers layered on top. This page covers the full process end-to-end, what each round tests, the question types you will see, the firm-specific nuances of HRT's algo-dev culture, and a multi-week prep plan tuned to the loop.

The full process, end to end

A typical Hudson River Trading pipeline runs like this:

1. Application and online assessment. Most candidates start with a timed HackerRank-style coding screen — usually two to four algorithmic problems in 60 to 90 minutes, judged on correctness and passing the hidden test cases. The bar here is closer to a strong software-engineering screen than a trader's mental-math test, and it filters hard. Some trader-track candidates also see a short timed math or probability section, but the coding screen is the dominant first gate.
2. Recruiter conversation (20–30 min). A recruiter walks through the loop, confirms interest, timing, and target track (algorithm developer, core developer, or trader), and covers your background and why HRT. Fit-and-logistics, with a light touch of how you think about problems.
3. Technical phone screen(s) (45–60 min). One or two rounds with an HRT engineer or trader in a shared editor (a CoderPad-style tool). You solve an algorithms problem live, talk through complexity, and handle follow-ups that push on efficiency and edge cases. For the trader track this round often blends coding with probability and EV.
4. Onsite / virtual loop (4–6 rounds × 45–60 min). The signature stage. Multiple hard algorithms rounds, a probability-and-EV round, brainteasers, and — for the trader track — a market-making game. Some loops add a systems or low-latency discussion for core-developer seats. HRT's onsite leans heavily on raw problem-solving depth.
5. Final / team conversations and offer. A cluster combining a deeper technical or market-making conversation with behavioral and team-fit, then a level and offer discussion. HRT hires globally (New York, London, Singapore, Austin), with a broadly consistent algorithm-first loop.

The whole pipeline runs four to eight weeks for most candidates, faster for interns on a compressed loop.

What the rounds actually test

HRT is filtering for a specific profile — a strong programmer who can also reason probabilistically — and every round maps to it:

• Algorithmic depth. The headline axis. HRT asks hard data-structures-and-algorithms problems and expects clean, correct, efficient code. Where a generalist tech company might accept a working brute force, HRT wants the optimal approach and a crisp complexity argument. This is the bar candidates most often underestimate.
• Code quality and rigor. It is not enough to reach the right idea — HRT cares whether your implementation is correct on edge cases, readable, and free of off-by-one and overflow bugs. The firm runs real money on real code, and the interview reflects that.
• Probability and EV discipline. Trader-track loops test expected-value reasoning, conditional probability, and the ability to price uncertainty. The question behind the question is always: what is this worth, and how confident am I?
• Structured reasoning under pressure. Brainteasers and estimation problems test whether you can decompose an unfamiliar problem cleanly and narrate your reasoning, not whether you have memorized an answer.
• Composure and communication. Like every trading loop, HRT watches for candidates who freeze or tilt. Talking through a bug calmly and recovering is itself a positive signal.

There is no published pass rate, but HRT — like its peers — takes a small fraction of candidates who reach the onsite, and the coding bar is the most common point of failure.

Question types by round

The coding screen and algorithms rounds

This is what sets HRT apart. The online assessment and the live technical rounds center on hard algorithmic problems, weighted toward:

• Data structures and complexity — heaps, hash maps, balanced trees, union-find, and the right structure for a constraint. HRT loves problems where the naive solution is too slow and you have to find the structure that makes it fast.
• Graphs and dynamic programming — shortest paths with state, topological ordering, DP where the bottleneck is recognizing the state rather than writing the recurrence.
• Arrays, strings, and intervals — sliding-window and two-pointer problems, interval merging, and prefix sums, usually with a twist that breaks the textbook template.
• Math-flavored coding — combinatorics, modular arithmetic, number theory, and bit manipulation, reflecting HRT's quantitative bent.

The screen is judged on passing hidden test cases under time pressure; the live rounds add an interviewer watching whether you state complexity without being prompted, handle edge cases, and debug cleanly. Treat HRT's coding bar like a top-tier software engineering loop, not a trader's afterthought.

Probability and EV

Layered into the technical rounds and the onsite, especially for the trader track:

• Expected value of a game — "You pay to roll a die and receive the face value in dollars. What is the most you should pay?" (3.5.)
• Conditional probability and Bayes — disease-test false-positive setups, urn draws, coin-bias estimation, and updating on new information.
• Sequential decisions — optimal stopping, bet-sizing, and games where the right move depends on what you have already seen.
• Combinatorics and counting — problems where the clean setup matters more than brute-forcing the arithmetic.

The interviewer wants the structure of your reasoning and a correct expected value, not a memorized answer.

Mental math

HRT does not lean on a standalone timed arithmetic gate the way Optiver does, but trader-track candidates are still expected to be quick and accurate with numbers — two-digit multiplication, percentages, fractions to decimals — because you cannot compute the EV of a combinatorial problem if three-digit arithmetic slows you down. Drill it as a supporting skill, not the centerpiece.

Market-making games (trader track)

For the quant-trader seat, expect at least one market-making round. The interviewer names a quantity with a hidden value — "the sum of two dice," "the number of countries in Africa" — and you quote a two-sided market (a bid and an ask) you will trade at. You set it wide enough to avoid being picked off, tight enough to show confidence: "Sum of two dice — 6 at 8." The interviewer trades against you ("I lift your offer" — they buy at 8, leaving you short), then feeds new information ("one die is a 4," so the expected sum is now 4 + 3.5 = 7.5). You reassess P&L and requote, adjusting your spread to your confidence, and the loop repeats. The interviewer grades initial-quote quality, how fast you integrate new information, whether you always know your running position and P&L, and whether you stay composed after a losing trade.

Brainteasers and estimation

Classic structured-reasoning problems — weighing puzzles, light-bulbs-and-switches, expected flips to see three heads in a row, and Fermi-style estimates. HRT uses these to see clean decomposition and transparent assumptions, not trivia recall.

Firm-specific nuances

A few things set the HRT loop apart from its peers:

• Algorithms come first, and the bar is high. HRT is an algorithmic-trading firm built by engineers, and the interview reflects that. Where pure prop shops gate on a timed math test, HRT gates on a hard coding screen. Treat the coding rounds as secondary and you will not clear them.
• Code quality is graded, not just the idea. HRT runs real strategies on the code its people write, so correctness on edge cases, clean implementation, and efficiency carry real weight. A working-but-sloppy solution scores worse than at a generalist tech company.
• Math-and-code blend. The problems frequently sit at the intersection of mathematics and programming — modular arithmetic, combinatorics, number theory in code. A pure LeetCode grinder without quantitative reasoning can stall in the probability rounds, and a sharp probabilist who cannot implement cleanly stalls on the coding.
• Developer-led culture. HRT identifies as a technology company that trades, not a trading company with a tech team. The interview rewards genuine engineering depth over finance vocabulary or credentials.
• Global, broadly consistent loop. New York, London, Singapore, or Austin, the shape — coding screen, algorithms rounds, probability, and (for traders) market-making — is similar, though the exact mix shifts by track and location.

A multi-week preparation plan

Weeks 1–2 — Algorithms fluency. Drill 60–80 medium-to-hard problems on NeetCode 150 or Blind 75, organized by pattern — heaps, graphs, dynamic programming, intervals, union-find. Goal: classify any problem in under 90 seconds and reach the optimal approach, not just a working one. This is the highest-leverage block for HRT.

Weeks 3–4 — Hard problems and math-flavored coding. Shift toward hards, and add a steady diet of math-adjacent coding — modular arithmetic, combinatorics, bit manipulation, number theory. In parallel, start drilling 5–10 EV and probability problems a day from Heard on the Street and a quant question bank until framing any new problem as an expected value is automatic.

Weeks 5–6 — Probability depth and brainteasers (and market-making for traders). Push into harder conditional-probability, Bayes, and sequential-decision problems, plus structured brainteasers. Trader-track candidates should drill market-making games out loud with a partner or a drill that takes the other side — quote, get hit or lifted, integrate information, requote, track P&L. Keep a short daily algorithms warm-up so the coding skill does not decay.

Weeks 7–8 — Full mocks. Run 3–5 full mock loops a day chaining a timed algorithms round, a probability round, and (for traders) a live market-making game. HRT's onsite is long and fatigue-inducing; build the stamina to stay sharp and write clean code in round five. No new content in the final stretch — reinforcement and composure only.

The single biggest differentiator at HRT is the depth of the coding bar, and candidates from a trading background routinely underinvest in it because they expect a math-first loop. Prepare for it like a top-tier engineering interview.

How to practice for the Hudson River Trading loop

InterviewDen's quant-trading track simulates the HRT loop end-to-end. A voice-driven AI interviewer runs the market-making rounds the way an HRT trader would — you name a two-sided market out loud, the AI trades against your quotes, new information arrives, and you requote while it tracks your running position and P&L. The mental-math drills run against a ratcheting timer so the supporting arithmetic stays fast, and the EV and probability rounds ask live follow-ups the way an interviewer would. Every session ends in a scored debrief that flags exactly what HRT grades — hesitation, quoting too tight, losing track of P&L, and panic-widening after a bad trade. It is free to start, so you rehearse the actual skill of reasoning and pricing out loud under pressure.

For the full breakdown of mental-math bars, market-making mechanics, and the EV taxonomy across firms, read the quant trading interview guide, and warm up on the exact problem shapes with the quant trading brainteasers. Pair that with dedicated algorithms drilling for HRT's coding screen, then run a trading mock and get a scored debrief on EV discipline, speed, and composure.

Common mistakes

• Underestimating the coding bar. This is the single biggest HRT-specific failure mode. Candidates expecting a math-first loop walk in under-prepared on hard algorithms and get cut on the screen. Drill coding like a FAANG interview.
• Reaching a working solution and stopping. HRT wants the optimal approach and a clean complexity argument. A brute force that passes small cases but times out on the hidden tests fails the screen.
• Sloppy implementations. Off-by-one errors, integer overflow, and unhandled edge cases cost real signal because HRT grades code quality, not just the idea.
• Neglecting probability for code (or vice versa). HRT blends math and programming. A strong coder who freezes on EV, or a sharp probabilist who cannot implement cleanly, both stall.
• Quoting markets too tight. In the trader-track market-making round, a nervous one-wide quote gets picked off. Wider-but-defensible is a better signal than falsely tight.
• Coding in silence. Even a correct solution scores weakly when the interviewer cannot follow your reasoning. Narrate the approach, the complexity, and the edge cases out loud.

FAQ

Is HRT a coding-heavy interview?

Yes — more so than almost any other quant-trading firm. Hudson River Trading is an algorithmic-trading company built by engineers, and its interview leads with a HackerRank-style coding screen and includes multiple hard data-structures-and-algorithms rounds. The coding bar is closer to a top-tier software-engineering loop than to a trader's mental-math test, and it is the most common point at which candidates are cut. Prepare for it like a FAANG algorithms interview, not an afterthought.

What does the Hudson River Trading coding interview involve?

Usually a timed online assessment of two to four algorithmic problems on a HackerRank-style platform, judged on passing hidden test cases, followed by one or more live coding rounds in a shared editor. Problems weight toward data structures, graphs, dynamic programming, and math-flavored coding (combinatorics, modular arithmetic, bit manipulation). Interviewers expect the optimal approach, a correct edge-case-safe implementation, and a stated complexity without being prompted.

Does HRT have a mental math test like Optiver?

Not as a standalone gate. HRT does not open with the kind of timed "80 in 8" arithmetic screen Optiver is famous for. Trader-track candidates are still expected to be quick and accurate with numbers — because you cannot compute the EV of a combinatorial problem if arithmetic slows you down — but at HRT mental math is a supporting skill, and the coding screen is the dominant first filter.

What is the difference between HRT's developer and trader tracks?

The core developer and algorithm developer tracks are software-engineering-heavy — multiple hard algorithms rounds, with some systems or low-latency discussion for certain seats. The quant-trader track keeps a strong coding component but adds probability, EV, and at least one market-making game. Confirm which track you are interviewing for with your recruiter, because the prep mix shifts: developer seats lean harder on algorithms, trader seats add the market-making and probability rounds.

Do I need a finance background to interview at HRT?

No. HRT recruits heavily from math, computer science, physics, and engineering, and identifies as a technology company that trades. There is no finance-coursework requirement. The filter is genuine engineering depth plus quantitative reasoning — strong algorithms skills and clean probabilistic thinking carry far more weight than a finance major or graduate degree.

How long is the Hudson River Trading interview process?

Four to eight weeks is typical: an online coding assessment, a recruiter conversation, one or two technical phone screens, an onsite or virtual loop of four to six rounds, and a final conversation with an offer discussion. Intern loops can compress into a shorter window; full-time onsites take longer to schedule across HRT's global offices.

How hard is the Hudson River Trading interview?

It is among the most competitive in the industry and, on the coding axis, one of the hardest. The algorithms bar sits in the medium-to-hard band and the firm grades implementation quality, not just whether you reached the idea. Combined with the probability and market-making rounds for traders, the loop demands strength across both mathematics and programming. HRT takes only a small fraction of candidates who reach the onsite.

Should I drill LeetCode for HRT?

Yes, and heavily — but drill by pattern toward the optimal solution rather than memorizing specific problems. Focus on data structures, graphs, dynamic programming, and math-flavored coding, and practice stating complexity and handling edge cases out loud. For the trader track, balance that algorithms work with daily EV and market-making drilling so you are not strong in code but weak in reasoning.