Morgan Stanley Software Engineer interviews, as candidates describe them, mix Java and core CS fundamentals, resume deep-dives and behavioral rounds. Some candidates also report online assessments and a Superday.
$125K
Avg. Base Comp
$135K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe the Morgan Stanley Software Engineer interview as fundamentals-heavy, but the format varies by team and hiring track. Several report Java-centered technical rounds covering Java basics, Java 8, OOP principles like abstraction and encapsulation, and Spring Boot. One candidate described six rounds focused on Java, Spring Boot, microservices and Kafka. Others describe a campus-style path: an online assessment mixing aptitude, debugging and coding, followed by a technical one-on-one and an HR conversation.
Core CS topics come up repeatedly in these reports: operating systems, DBMS, computer networks, linked lists, easy tree problems and memory management basics. Language depth can matter too. One candidate was asked about C++ lambda expressions and coroutines, and another about the .NET compilation process. Coding reports range from simple tasks, like reversing a string while screen sharing, to whiteboard problems where interviewers wanted the approach drawn out clearly.
For design, candidates report prompts such as a URL shortener and Uber. Resume depth also matters: one offer-holder says resume projects came up in a technical round and again in a later project-fit conversation. Another candidate had a round on agile and was asked to explain the four scrum meetings. Round counts vary by report, and one candidate waited months without closure, so expect variation. Prepare to explain Java and Spring Boot clearly, practice basic data structures, and rehearse concise stories about your own projects and how you handle conflict.
Synthesized from 73 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Morgan Stanley process.
I didn't make it through, so treat this as a look at what they tested rather than a success story. I applied through my college for the Technology Division apprenticeship, and the first gate was an online assessment on the SHL platform. It wasn't only coding. There was an aptitude section, data interpretation questions built on charts and graphs, and scheduling problems that were essentially calendar-based logic puzzles. Two coding questions were mixed in with the rest. Don't let the non-coding sections slide, since they eat real time and you can't make that time up later.
After clearing the assessment, I had a virtual one-on-one technical interview. The interviewer was friendly, and the whole session centered on two DSA questions that I'd place around medium difficulty. The first was Asteroid Collision: given an array of asteroids moving in opposite directions, determine the state of the asteroids once all collisions have played out. The second was Zigzag Level Order Traversal of a binary tree, where you return the nodes level by level but alternate the direction on each row. Both are classic problems, and the coding was the sharpest part of the process. Overall I'd call the difficulty average, but the DSA questions were where the bar felt real.
I wasn't selected after that interview. If you're preparing, I'd spend serious time on stack-based simulation problems and BFS variants, and I'd run the SHL-style aptitude and logic questions under timed conditions so the first gate doesn't catch you off guard.
Prep tip from this candidate
The two coding questions were a stack-based collision simulation and a zigzag variant of level-order BFS, so drill those patterns specifically. Also practice the SHL data interpretation and calendar logic questions under timed conditions, since they share the same assessment as the coding section.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Morgan Stanley
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| Find the Missing Number | |
| Maximum Profit | |
| Size of Joins | |
| Get Top N Frequent Words | |
| Cyclic Detection | |
| Sort Strings | |
| Hurdles In Data Projects | |
| Success Measurement | |
| Coin Dispenser | |
| RAG Strict Source Control | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Last Element of a Singly Linked List | |
| Shortest Path Algorithms | |
| Fixed-Length Arrays: Deletion | |
| Text Editor With OOP | |
| Ranking Metrics | |
| Why Do You Want to Work With Us | |
| Justify a Neural Network | |
| Your Strengths and Weaknesses | |
| LRU Cache 1 | |
| Parking Application System Design | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter call or a phone screen of roughly 20 to 30 minutes. Reports describe it as a background discussion with basic behavioral and light technical or Java questions. Be ready to summarize your experience concisely.
Some candidates report an online assessment in the campus process, covering debugging, aptitude and coding. This step may depend on the hiring track, so it will not apply to everyone.
Candidates typically describe technical conversations on Java, Spring Boot, OOP, SQL or DBMS, operating systems and data structures. Coding tasks reported include string reversal, linked list problems and easy tree problems. Some interviews use a whiteboard or screen share, so practice explaining your reasoning aloud.
Some candidates report design prompts such as a URL shortener or Uber. Others were asked to explain their resume projects in detail. Prepare to describe components, tradeoffs and your own role.
Final stages reported include a hiring-manager conversation, a virtual Superday with three 30-minute interviews, an engineering director-style conversation and an HR round. Expect questions about project fit, hypothetical situations and conflict, and expect the format and timing to vary.
