Assessment tips
- Confirm the current Morgan Stanley pattern from the drive mail before practising old papers
- Finish one problem or section fully before starting the next
- Revise the fundamentals listed in the round table on this page
Morgan Stanley Interview Experience 2026
Overview
How Morgan Stanley Technology Analyst and campus tech loops actually run, synthesized from recent candidate reports and Morgan Stanley public hiring guides. We reorganized rounds and added prep notes. Some India drives compress phone screen and HireVue; investment-banking Superdays differ from technology Superdays - treat your drive mail as source of truth.
Reported fresher Technology Analyst total compensation in India commonly falls in the ₹25–35 LPA band (candidate-reported) - confirm on your offer letter. Eligibility often cited: ~7.0+ CGPA, no active backlogs across 10th, 12th, and graduation.
Morgan Stanley interview process overview
| Round | Duration | What it tests |
|---|---|---|
| Timed coding test | 60–90 min (sometimes 90–120) | 2–3 HackerRank/Codility problems + quant/aptitude on many campus drives |
| Phone screen | ~30 min | Resume, why finance/why MS, light technical |
| HireVue video interview | 48–72 hrs to complete | 3–5 recorded behavioral prompts; content scored, not facial AI |
| Superday | 4–5 × 30–45 min | DSA, trading/risk system design, behavioral fit, hiring manager |
Real interview experiences
Experience 1: Technology Analyst, campus (IIT), Mumbai (2025)
Profile: B.Tech CS, ~8.5 CGPA, two fintech internships, strong system-design prep
Timed coding test
- 90 minutes: longest increasing subsequence (O(n log n) expected) and LRU cache design-style implementation; partial credit on a third graph problem.
- Quant section: probability and mental-math style aptitude (time-boxed).
Phone screen
- Walk through resume; why Morgan Stanley vs other banks; light discussion on internship trade-capture tool.
HireVue
- ~4 questions: why technology in a bank, pressure deadline STAR, disagreement with teammate, which core value you relate to (Put Clients First - candidate tied to disclosing a data bug before demo).
Superday (virtual, 5 sessions)
- Tech 1: Valid parentheses variant + cycle detection in directed graph (three-color DFS); SQL question on indexing a large trades table.
- Tech 2: Design real-time risk calculation - Kafka-style event stream, incremental greeks, batch VaR offline; interviewer probed audit trail.
- Tech 3: Project deep dive on internship order-book simulator; follow-up on failure modes at scale.
- Behavioral / ED: Why finance, five-year commitment, conflict STAR.
- Hiring manager: Team rituals, on-call expectations, location confirm.
Result: Selected. Reported ~₹32 LPA Technology Analyst (candidate-reported, Mumbai).
Takeaways
- What decided it: Superday stamina across DSA, real-time risk design with audit trail, and STAR stories without long pauses between modes
- Common fail: Strong OA then flat HireVue; finance design answers that ignore event streams and replay
- How to practise: LIS + LRU timed sets; Kafka-style risk design aloud; record four 90-second HireVue answers
Experience 2: Technology Analyst, off-campus, Bangalore (2024–2025)
Profile: B.Tech IT from NIT, ~8.0 CGPA, ~1 year backend experience
Timed coding test
- Three coding problems - solved two fully, one partial; aptitude cleared comfortably.
HireVue (phone screen skipped for this candidate)
- Recorded answers on why MS, leadership under deadline, inclusive teamwork story; kept each answer ~90 seconds with explicit Result line.
Superday
- Round 1: Graph DP + database slow-query diagnosis (EXPLAIN plan, composite index).
- Round 2: Design low-latency order matching engine - in-memory book, price-time priority, event journal for replay.
- Round 3: Distributed consistency discussion tied to previous employer’s payment service.
- Round 4: Managerial - tight deadline, ownership without being asked.
- HR: Notice period, relocation, background-check timeline.
Result: Selected. Reported ~₹28 LPA (candidate-reported, Bangalore).
Takeaways
- What decided it: Finance-flavored designs (order matching, EXPLAIN/index diagnosis) plus ownership stories after a compressed HireVue path
- Common fail: Generic social-feed system design; rambling HireVue without an explicit Result line
- How to practise: In-memory order book with price-time priority; slow-query diagnosis drills; 90-second Why MS recordings
Experience 3: Campus drive - rejected after HireVue (2025)
Profile: B.Tech ECE, ~7.2 CGPA, strong DSA, weak structured speaking
Timed coding test
- Cleared with two complete solutions and decent aptitude score.
HireVue
- Same question bank as peers (why MS, challenge overcome, disagreement); candidate gave one-sentence answers and rambled on retakes.
Result: Rejected before Superday - no technical rounds. Takeaway: Public reports emphasize HireVue as a real filter for technology campus tracks; rehearse timed 2-minute STAR recordings, not only LeetCode.
Experience 4: Technology Analyst intern → FTE, Hyderabad (2024)
Profile: B.Tech CSE, ~7.8 CGPA, summer intern in operations technology
Internship
- Worked on batch reconciliation tooling; final presentation to manager and HR partner.
FTE loop (shortened)
- One technical: monotonic stack / next greater element on price arrays + SQL joins on positions table.
- One design discussion: market-data fan-out - subscribers, slow consumers, replay.
- HR: conversion motivation, return offer vs other banks.
Result: FTE offer at intern band uplift; candidate-reported package in high-20s LPA (confirm offer letter). Takeaway: Intern return offers still test markets vocabulary - know inputs/outputs of market-data feeds in plain language.
Experience 5: Superday - technical strong, behavioral gap (2025)
Profile: B.Tech CS, ~8.1 CGPA, 300+ LeetCode problems
Through HireVue
- Standard behavioral set; advanced.
Superday
- Coding rounds: LRU cache, merge k sorted lists, SQL window-function question - rated strong.
- Design: risk system - candidate gave generic microservices diagram without latency or audit specifics; interviewer asked twice for regulatory traceability.
- Final MD round: vague “why banking” answer referencing “brand name only.”
Result: Rejected post-Superday. Takeaway: MS technology Superday is not LeetCode-only - client/regulatory framing and authentic finance motivation decide borderline cases.
Pre-interview checklist (Morgan Stanley technology)
| Stage | What to verify | Common miss |
|---|---|---|
| OA | HackerRank link, aptitude section, camera/proctor rules | Starting coding before reading full quant section |
| HireVue | Deadline (48–72h), quiet room, full STAR answers | 20-second replies and retake fatigue |
| Superday | Schedule, interviewers’ titles, virtual whiteboard tool | No story for “why finance” |
| Compliance | Background check documents, gap explanations | Surprises in HR after strong tech |
Questions that come up often
Coding / technical
- Longest increasing subsequence - patience sorting / binary search on tails
- Design LRU cache - hash map + doubly linked list; concurrency follow-up
- Directed graph cycle detection - three-color DFS or Kahn’s algorithm
- Next greater element / monotonic stack on price arrays
- Valid parentheses and expression evaluation - stack
- SQL: slow query diagnosis, indexes, isolation levels, ACID in ledger context
- System design: real-time risk engine, order matching, market-data distribution
HR / behavioural
- Why Morgan Stanley and why finance / bank technology?
- Tell me about a time you did the right thing when it cost you time
- Disagreement with teammate - STAR with listening and outcome
- Pressure / tight deadline - trading-day or release-week story
- Which core value resonates - tie to example
- Relocation, background verification, career goals (commitment past training)
Practical tips for Morgan Stanley
- Clear the timed coding test first - unsupervised accuracy beats last-minute topic hopping.
- For domain questions, explain market data as inputs, consumers, latency, and what breaks at scale - one diagram helps.
- Superday: expect follow-up probes; one-sentence answers fail in public MD-round reports.
- Align stories with Put Clients First - integrity beats heroics.
- If stuck technically, outline how you’d find the answer under compliance constraints - Morgan Stanley’s own interview guidance rewards honest reasoning.
HR interview
After Superday, a short HR or offer call covers logistics, compensation bands, and start dates. Deeper STAR prep lives on the dedicated HR page - keep motivation consistent with HireVue and Superday.
Sample answers for high-frequency questions
Use these as frames, not scripts - interviewers probe follow-ups.
Q. How do you find the Longest Increasing Subsequence efficiently?
A. The classic dynamic-programming solution defines dp[i] as the length of the longest increasing subsequence ending at index i, computed by scanning all earlier indices with a smaller value and taking the best plus one - that is O(n squared) time and O(n) space. The optimal solution is patience sorting: maintain an array tails where tails[k] is the smallest possible tail value of an increasing subsequence of length k+1. For each element, binary search for the first tail that is greater than or equal to it and overwrite it, or append if the element exceeds every tail. The length of tails is the answer, giving O(n log n) time. Note that tails is not itself a valid subsequence - to reconstruct the actual sequence you must store predecessor indices alongside.
Q. How do you design an LRU cache with O(1) get and put?
A. Combine a hash map with a doubly linked list. The hash map maps key to node, giving O(1) lookup; the doubly linked list keeps nodes in recency order with the most recently used at the head and the least recently used at the tail. On get, find the node through the map and move it to the head. On put, either update and move to the head, or insert a new node at the head and, if capacity is exceeded, remove the tail node and delete its key from the map. A doubly linked list is required because eviction and re-linking need O(1) access to a node’s predecessor, which a singly linked list cannot give. Sentinel head and tail nodes remove most of the null-handling edge cases, and in production you would also need locking or a concurrent variant since a cache is shared across threads.
Q. How would you design a low-latency order matching engine?
A. Keep the whole book in memory and avoid anything that touches disk on the hot path. Model each side of the book as a price-ordered structure - typically a sorted map, or an array of price levels for the tight range around the touch - where each price level holds a FIFO queue of resting orders, so matching follows price-time priority: best price first, and within a price, the earliest order first. An incoming aggressive order walks the opposite side from the best price, filling against resting orders until its limit price is passed or its quantity is exhausted; the remainder rests in the book. Keep a hash map from order id to its node so a cancel is O(1) rather than a scan. Single-threaded matching per instrument fed by a lock-free ring buffer usually beats a multi-threaded design because it removes lock contention and keeps the book in cache; durability comes from writing the input event stream to a replicated journal before matching, so state can be rebuilt by replay.
Tips from successful candidates
Interview tips
- Narrate trade-offs; expect “why” after every answer
- Only list projects you can defend under follow-ups
- Prepare 3-4 STAR stories for behavioural prompts
HR tips
- Know why Morgan Stanley, not just why the industry
- Be clear on location / notice period / background checks
- Practise answers on the dedicated HR page
Sources
Round-wise notes on this page are curated from public candidate reports, then reorganized with prep takeaways and outcome context (GeeksforGeeks, Glassdoor, placement forums) and Morgan Stanley’s published interview preparation guidance. Cross-check the current drive mail for timings. For OA practice, see Morgan Stanley placement papers.
Related resources
Similar companies
Goldman Sachs · JP Morgan · Bank of America · Wells Fargo · HSBC · Barclays