← Hudson River Trading Interview Insights

Hudson River Trading·Software Engineer·Technical Phone Screen·Intermediate

IntermediatePrefer not to say
Apr 2026

Summary

HRT algo dev interview, one big coding exercise where they hand you a real-ish C++ trading system codebase and ask you to extend it. Not a leetcode grind, more like 'here's production-ish code, go figure it out and add a feature.' Appreciated the format but it was stressful in a different way.

Questions Asked (1)

Q1

You're given an existing C++ trading system codebase with client/server architecture that already supports add and cancel order operations. Extend it to support a modify order operation, end-to-end, following the same patterns already in the code.

System DesignAPI & IntegrationsTechnical Trade-offs
Author's notes

This was the whole interview basically.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying the existing patterns for add and cancel operations, then map the modify operation onto those patterns end-to-end. Walk through the client API, network protocol, server-side handling, and order book update, highlighting any differences and edge cases. Emphasize consistency with the codebase and discuss trade-offs where the modify semantics diverge from add/cancel.

Pro tip: Modify is often implemented as cancel-replace, but that can break order priority and introduce race conditions; explicitly discuss whether the exchange or internal system supports true modify semantics and how you'd handle partial modifications.

1. Clarify requirements and existing patterns

Ask questions to understand the modify operation's semantics (e.g., can price/quantity change? Is it cancel-replace or in-place?) and review how add/cancel are implemented across client, protocol, and server.

2. Design the client API and protocol changes

Extend the client interface and network message format to include a modify request, mirroring the structure of add/cancel messages. Consider versioning and backward compatibility.

3. Implement server-side handling and order book update

Add a handler for modify messages that validates the request, locates the order, and updates the order book. Decide whether to treat it as cancel-replace or a true modify, and handle concurrency and consistency.

4. Address edge cases and error handling

Cover scenarios like modifying a non-existent order, invalid parameters, partial fills, and race conditions with concurrent operations. Ensure proper error responses and logging.

5. Test and validate end-to-end

Write unit and integration tests for the new operation, including failure cases. Verify that the modify operation behaves consistently with add/cancel and meets performance requirements.

Key Points to Mention

  • Consistency with existing add/cancel patterns in API, protocol, and server logic
  • Semantics of modify: cancel-replace vs. in-place modification and impact on order priority
  • Concurrency and thread-safety in the order book and server handlers
  • Error handling and validation for invalid or stale modify requests
  • Backward compatibility and protocol versioning if applicable
  • Testing strategy including unit, integration, and performance tests

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.