Scale a Quant Optimization Workflow (Project Deep Dive)
In July 2026 a Quantitative Software Engineer candidate had an order matching screen on HackerRank first. Round 2 was with a senior interviewer, who asked for a complete walk through the resume and then went deep on two projects from it. On a tax-loss harvesting optimizer, the questions were about the math inside it. On a multi-period asset-location backtest, they started with the setup: Monte Carlo paths or not, how often it rebalanced, which metrics it optimized, how much history and which data sources. Then came the engineering. How do you get through 30,000 optimizer runs? Single machine or many? They asked about shared inputs, serialization, scheduling overhead, the real runtime per path and how to profile the bottleneck. There's no prompt to memorize here, because the system is yours. What you can prepare is the reasoning the interviewer pulls on. So we'll build one version of such a system from scratch, a Monte Carlo backtest that calls an optimizer at every rebalance date, and scale it the way that round asked. After that comes how to present your own system under the same questioning.
Two SigmaPremium lesson · System design round
The Two Sigma design, worked end to end.
- Requirements and scopeSystem design
- The API and data model
- The design, drawn out1 diagram
- 6 deep divesWith the tradeoffs
$49 a year · all 107 companies · instant access
20,000+ candidate reports
Two Sigma interview guideKnow what Two Sigma asks before you walk in.
21 coding · 4 system design · 13 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.