Jane Street·Software Engineer·Onsite - System Design / Architecture
Jun 2026
Jane Street system design round focused entirely on order book data validation across multiple databases. Pretty brutal in scope, they wanted you to think through invariants, cross-db reconciliation, edge cases, and operationalization all in one go.
- What invariants must always hold for orders, executions, and the resulting order book state?
- How would you validate data quality within a single database, using table-level constraints and batch checks?
- How do you reconcile data across multiple databases that may only be eventually consistent?
- How do you handle edge cases like partial fills, cancellations, order replaces, out-of-order events, duplicates, and reconnect replays in your validation logic?
- How would you operationalize this validation system, including alerts, dashboards, and backfill processes?
“This is where I started strong and then trailed off.” The rest of the author's notes on Software Engineer interview at Jane Street, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.
View Post