← Morgan Stanley Interview Insights

Morgan Stanley·Software Engineer·Technical Phone Screen·Intermediate

Intermediate
Jun 2026

Summary

Morgan Stanley quant engineer interview where the whole thing basically revolved around your resume projects. They pick something and dig in hard, so if you've got anything on there you can't fully explain, expect to get exposed.

Questions Asked (3)

Q1

Walk me through the projects on your resume. Pick one and explain the problem you were solving, the design decisions you made, and what trade-offs you considered.

Technical Trade-offsSystem Design
Author's notes

This is where it gets uncomfortable if you haven't thought carefully about your own work.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Select a project that aligns with the role's requirements and demonstrates your ability to handle complexity and trade-offs. Structure your answer using a clear narrative: context, problem, design decisions, trade-offs, and outcome. Focus on your specific contributions and the reasoning behind your choices.

Pro tip: Quantify the impact of your decisions (e.g., performance improvements, cost savings) and explicitly connect the trade-offs to business or user needs. This shows you think beyond technical implementation.

1. Set the Context

Briefly describe the project, your role, and the team size. Mention the tech stack and the overarching goal to orient the interviewer.

2. Define the Problem

Clearly state the problem you were solving, including any constraints (e.g., scalability, latency, budget) and why it mattered to the business or users.

3. Explain Design Decisions

Walk through the key design choices you made, such as architecture, algorithms, or technologies. Explain why you chose them over alternatives.

4. Discuss Trade-offs

Articulate the trade-offs you considered (e.g., consistency vs. availability, performance vs. cost) and how you balanced them to meet requirements.

5. Highlight Outcomes and Learnings

Summarize the results, including metrics if possible, and reflect on what you learned or would do differently. Connect back to the role.

Key Points to Mention

  • Specific technologies and tools used, and why they were appropriate
  • Scalability, performance, or reliability considerations
  • Trade-offs between competing priorities (e.g., speed vs. quality, cost vs. scalability)
  • Your individual contributions and leadership within the team
  • Quantifiable impact (e.g., reduced latency by X%, saved $Y)
  • Lessons learned and how they apply to future projects

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.

Q2

For the project you described, what specifically did you contribute versus what the rest of the team did?

Adaptability & Ambiguity
Author's notes

Tripped up here a bit.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Clearly delineate your individual contributions using specific examples and measurable outcomes, while acknowledging the team's collective effort. Focus on your unique role, the problems you solved, and how your work integrated with others to achieve the project's goals.

Pro tip: Quantify your impact where possible (e.g., 'reduced latency by 20%') and explicitly state what you learned from teammates, showing you value collaboration and can navigate ambiguity.

1. Set the Context

Briefly describe the project's goal, your role, and the team structure to orient the interviewer.

2. Highlight Your Contributions

Detail specific tasks or components you owned, using 'I' statements and concrete examples of your work.

3. Acknowledge Team Contributions

Recognize the team's efforts and how their work complemented yours, showing respect and collaboration.

4. Discuss Integration and Challenges

Explain how your work interfaced with others' and how you handled any ambiguities or dependencies.

5. Summarize Impact and Learnings

Conclude with the project's outcome, your personal growth, and what you learned from the team experience.

Key Points to Mention

  • Specific technical contributions (e.g., designed X module, implemented Y feature)
  • Quantifiable results (e.g., performance improvements, bug fixes)
  • Collaboration and communication with team members
  • How you navigated ambiguity or changing requirements
  • Your role in decision-making or problem-solving
  • Lessons learned and how you applied them

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.

Q3

What didn't work in that project, and what would you do differently now?

Technical Trade-offsRoot Cause Analysis
Author's notes

Easier than expected.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Choose a project where something genuinely didn't work as planned, and focus on the technical root cause and the trade-offs you made. Be honest about your own decisions, and clearly articulate what you learned and how you would approach it differently now, emphasizing improved engineering judgment.

Pro tip: Show that you've reflected on the business impact of the failure, not just the technical fix—this demonstrates the commercial awareness valued at Morgan Stanley.

1. Set the context

Briefly describe the project, your role, and the goal so the interviewer understands the stakes and your responsibilities.

2. Identify what didn't work

Clearly state the specific technical or process failure, avoiding vague terms, and explain how you discovered it.

3. Analyze the root cause

Use a structured method like the 5 Whys to trace the failure to its origin, distinguishing between technical and human factors.

4. Describe the impact and trade-offs

Quantify the consequences (e.g., delays, performance issues) and discuss the trade-offs you made that contributed to the outcome.

5. Propose what you'd do differently

Explain the concrete changes you would make now, such as different design patterns, testing strategies, or communication practices, and how you've applied these lessons since.

Key Points to Mention

  • Root cause analysis technique (e.g., 5 Whys, fishbone diagram)
  • Technical trade-offs made and their consequences
  • Specific alternative approach or technology you would use now
  • Lessons learned and how you've applied them in subsequent projects
  • Impact on stakeholders and how you communicated the failure
  • Ownership of the mistake and steps taken to mitigate it

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.