Jane Street·Software Engineer·Technical Phone Screen
May 2026
Jane Street SWE interview focused entirely on a two-part system design problem around extending a trade tracking class. The problem kept building on itself and required reasoning through correctness without running any code, which was a different kind of pressure than I expected.
- You have a Table class that tracks trades and their PnL values over time. It supports adding trades, grouping them via filters, and rendering an aggregated PnL view. How would you redesign view_result() to run in O(1) time by maintaining incremental state, while also correctly handling set_global_filter() which can change the active set of trades at any point?
- Now assume get_pnl is asynchronous and you want to avoid calling it multiple times for the same trade and time pair. How do you cache these results as class state, and how does that cache interact with set_global_filter() changes, specifically around invalidation and recomputation?
“This took me a while to even frame correctly.” The rest of the author's notes on Software Engineer interview at Jane Street, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.
View Post