Expect prompts on a market-data distribution system that fans out live prices to thousands of internal consumers, a system tracking a trade through execution, confirmation, and settlement with a full audit trail, and a reconciliation service that compares internal records against a counterparty's. Interviewers reward pub/sub design with back-pressure and slow-consumer handling, clean state-machine modelling of trade lifecycles, and scalable keyed matching for reconciliation. The finance domain makes correctness and auditability first-class concerns, not afterthoughts bolted on at the end.
Recruitment process
Online coding assessment
Technical coding round on DSA
System-design round on a market-data or trade service
Hiring-manager round, then offer
Interview rounds
Round 1 (60-90 min): online coding assessment
Round 2 (45-60 min): coding round on data structures and algorithms
Round 3 (45-60 min): system-design round on market data, trade lifecycle, or reconciliation
Round 4 (45 min): behavioral and hiring-manager round
Fan out and lifecycle framework
Design low-latency pub/sub with back-pressure for market data, model the trade lifecycle as an audited state machine, and scale reconciliation with keyed matching
Practice questions
01
Design a system to predict same-day delivery feasibility for a new pincode in tier-3 India.
2 more questionsCreate a free account to see the full set and practise any of them with scoring.Unlock all questions
Prep notes
How to walk in ready.
The typical Morgan Stanley recruitment process has 4 stages: Online coding assessment → Technical coding round on DSA → System-design round on a market-data or trade service → Hiring-manager round, then offer.
Morgan Stanley typically conducts 4 interview rounds: Round 1 (60-90 min): online coding assessment; Round 2 (45-60 min): coding round on data structures and algorithms; Round 3 (45-60 min): system-design round on market data, trade lifecycle, or reconciliation; Round 4 (45 min): behavioral and hiring-manager round.
HireStepX recommends the Fan out and lifecycle framework for this type of interview: Design low-latency pub/sub with back-pressure for market data, model the trade lifecycle as an audited state machine, and scale reconciliation with keyed matching.
Razorpay loves real production scenarios: payments failures, NPCI rate limits, settlement reconciliation. Be specific.
PhonePe engineering rounds are scale-obsessed: every answer should explicitly address throughput, latency, and cost at India scale.
Google SWE rounds prize first-principles thinking and explicit trade-off articulation. Always discuss what you're approximating.
Market-data distribution with low-latency fan-out, tracking a trade through its full lifecycle with an audit trail, and reconciliation of internal records against a counterparty's.