Real, anonymous reports from people who interviewed for Software Engineer at Morgan Stanley, newest first and distilled into what to expect across the loop.
I ended up with a super-day format that was basically two hours of back-to-back one-hour interviews. The overall vibe was pretty chill, and the questions were split around OOP plus a mix of Java and Python topics.
My first in-person interview was tough mainly because it was my first time going through the format, not because the material felt impossible. I did enjoy learning more about the team and the company, and I appreciated the effort the interviewers put into the conversation.
Candidates typically experience a multi-stage interview process, often starting with a phone screen followed by a series of technical interviews that can last several hours, including both coding and behavioral assessments. The format can vary, with some candidates reporting back-to-back sessions and others experiencing longer, segmented interviews.
The interviews heavily emphasize data structures and algorithms (DSA), with many candidates facing coding challenges that require a solid understanding of Java, OOP principles, and system design. Candidates should prepare for practical coding problems, often in a live coding format, and may also encounter SQL and design questions.
Behavioral questions are a significant component of the interviews, with a focus on candidates' past experiences and how they align with the company's values. Many candidates reported using the STAR method to structure their responses, highlighting the importance of clear communication and cultural fit.
Candidates generally found the interviews to be challenging, with a mix of easy to hard questions that tested both technical skills and problem-solving abilities. Some candidates noted a disconnect between their expectations and the actual difficulty of the questions, suggesting a need for thorough preparation.
Effective communication is crucial throughout the interview process, as candidates are expected to articulate their thought processes clearly while solving problems. Interviewers often probe deeper into candidates' resumes and past projects, making it essential for candidates to connect their experiences to the technical questions asked.
Several candidates expressed frustration with the lack of timely feedback and closure following their interviews, with some experiencing long waits for responses. This uncertainty can be demotivating, highlighting the importance of candidates following up to seek clarity on their application status.