Real, anonymous reports from people who interviewed for Software Engineer at Morgan Stanley, newest first and distilled into what to expect across the loop.
My process felt very DSA-heavy from the start. After the early screening stage, I ended up in a difficult DSA-based round where I was asked standard medium-to-hard problems like the kind you’d see on common “striver sheet” topics. The interview also moved beyond pure practice questions into an applied design problem: I had to design a rate limiter.
After an initial orientation round, I had a technical interview that lasted about two hours with three interviewers joining one after another. Each segment ran roughly 40 minutes, and the topics rotated between front-end, back-end, and system design. The format was live coding with screen sharing the whole time, so I was writing code while explaining my thinking.
Candidates can expect multiple technical interviews focusing on data structures, algorithms, and system design, often involving live coding and problem-solving under pressure. The interviews may cover a range of topics including Java, Spring Boot, microservices, and SQL, with a mix of theoretical and practical questions.
Behavioral interviews are a key component, assessing candidates on teamwork, conflict resolution, and alignment with company values. Expect questions structured around past experiences and situational responses, often using the STAR method.
The interview process typically consists of several rounds, often including an HR screen followed by technical assessments and a cultural fit round. The format may vary, with some candidates experiencing a mix of live coding, presentations, and informal discussions.
The overall difficulty of the interviews is generally moderate to high, with a strong emphasis on foundational knowledge in computer science and practical coding skills. Candidates should be prepared for rigorous questioning and a fast-paced interview environment.
Candidates have reported varying timelines for the interview process, with some experiencing delays or a lack of closure after multiple rounds. Clear communication regarding the process and expectations is important, but some candidates noted uncertainty during waiting periods.
Candidates wish they had focused more on specific technical areas such as concurrency in Java, data structures, and system design principles. Practicing coding under time constraints and preparing for behavioral questions can enhance performance.
