Morgan Stanley Interview Guide 2026

Verified against Morgan Stanley career resources on July 26, 2026.

TL;DR

Morgan Stanley runs no universal loop: expect a recruiter or initial interview, then role-specific competency, strengths, skills, or technical rounds, with extra interviews or an assessment for some programs. Interviews differ substantially across investment banking, markets, wealth management, technology, risk, and operations, so prepare for the division, build evidence beyond finance interest, and compare guaranteed pay separately from bonus or deferred awards. OphyAI Interview Practice returns a scored rubric and transcript, and OphyAI Interview Copilot keeps deal, project, and metric detail organised in live rounds.

Quick Answer: Morgan Stanley Interview Process

Stage	What to prepare
Application and resume review	A resume tailored to one job family, where every bullet survives two levels of follow-up.
Recruiter contact or initial interview	A 90-second career narrative and a motivation answer that names the division, not just the firm.
Role-specific technical, competency, or strengths-based interviews	Your track’s fundamentals plus examples with clear personal action and relevant results.
Additional interviews or an assessment	Stamina across formats, and a method for reasoning aloud when you do not know the answer.
Decision and pre-employment checks	Consistent application detail and questions that separate guaranteed cash from deferred value.

Action Plan: Prepare for Morgan Stanley by Round

Round	What Morgan Stanley tests	What to do before the interview
Application and resume review	Whether you can explain everything on your resume	Audit each bullet for the problem, your decision, the method, and the measurable result, and remove claims that need internal jargon
Initial conversation	Motivation and resume depth	Prepare a 90-second narrative with three transitions, and ask the recruiter which competencies and technical topics are assessed and whether a case, presentation, or coding environment is involved
Role-specific interviews	Competencies, strengths, skills, and technical knowledge	Prepare all four styles, and rehearse the technical notebook or design drills for your business
Additional interviews or assessment	How you work through a scenario, not only the final answer	Practise stating assumptions and testing whether a result is reasonable when you are stuck
Questions you ask	Whether you are evaluating the actual work	Bring questions on decision ownership, judgment that separates strong performers, and how feedback is delivered

If you only have a week, keep the order and compress it: days 1-2, break the job description into required skills and match each to one proof point; days 3-4, review the technical foundation for your track, practising valuation aloud, coding under time constraints, or rehearsing recommendation conversations; day 5, research the division, recent company activity, and two market developments, forming your own view rather than memorizing headlines; day 6, build six behavioral stories covering ownership, teamwork, judgment, failure, pressure, and learning using the STAR answer guide, keeping the result relevant to the target role; day 7, run a full mock interview.

What Makes Morgan Stanley Different

Morgan Stanley does not use one universal interview loop. The sequence changes by business, seniority, office, and whether you apply to a student program or an experienced role. That makes the job description, not a generic bank question list, your primary syllabus.

• Four question styles, not one. Official preparation material says interviews may assess competencies, strengths, skills, and technical knowledge, and a single loop can mix them.
• Your resume is the exam. Morgan Stanley advises candidates to know their resume and tell an authentic story, which means every line should survive two levels of follow-up: what you personally did, and why your decision produced the result.
• Reasoning counts as much as the answer. The firm notes that it does not always expect an immediate correct answer and may care about how you work through a scenario.
• Division decides everything. An investment-banking team, a technology platform group, and wealth management do not share one daily rhythm or one interview.

Many candidates use the AI Interview Copilot during Morgan Stanley-style practice and live rounds to keep deal detail, project metrics, and follow-up questions organised when interviewers change the angle.

Interview Process Overview

Morgan Stanley does not publish a fixed round count. Its official preparation material says interviews may assess competencies, strengths, skills, and technical knowledge, and the sequence changes by business, seniority, and office.

Stage	Format	Duration	Timeline
Application and resume review	Online application	Not published	Start of the process
Recruiter contact or initial interview	Call or video conversation	Not published	First contact stage
Role-specific interviews	Technical, competency, or strengths-based interviews	Not published	Core of the loop
Additional interviews or assessment	Extra interviews or an assessment for some programs	Not published	Varies by program and office
Decision and pre-employment checks	Offer and checks	Not published	Final stage

Treat that as a planning model, not a guaranteed number of rounds. Your invitation and recruiter instructions are authoritative.

Application and Resume Review

Morgan Stanley’s own guidance tells candidates to know everything on their resume. Audit each bullet before applying: identify the problem, your personal decision, the technical or commercial method, and the measurable result. Remove claims you cannot explain without internal jargon. For banking roles, make transaction exposure and modeling work precise. For technology roles, name the system boundary, scale, reliability requirement, and what you actually shipped.

Your application should also make the division choice coherent. A candidate applying to investment banking, wealth management, and backend engineering with the same generic resume creates an unclear story. Tailor the top third of the resume to the job family and move the most relevant evidence into the first two bullets of each role.

Initial Conversation

Expect motivation and resume depth to matter early. Prepare a 90-second career narrative with three transitions: where your relevant interest began, how your experiences built the required skill, and why this role is the logical next step. Your answer to “Why Morgan Stanley?” should distinguish the firm, but it should also distinguish the particular division.

Ask the recruiter which competencies and technical topics will be assessed, whether later conversations are consecutive, and whether a case, presentation, or coding environment is involved. These questions improve preparation without trying to obtain private interview content.

The Four Interview Styles

Interviewers may use competency, strengths-based, skills-based, or technical questions. Prepare for all four:

Interview style	What a strong response demonstrates
Competency	A past example with clear personal action and a relevant result
Strengths	What energizes you, supported by repeated behavior rather than adjectives
Skills	A realistic task completed accurately and explained clearly
Technical	Fundamentals, assumptions, working, and judgment under follow-up

Morgan Stanley notes that it does not always expect an immediate correct answer and may care about how you work through a scenario. When stuck, define what is known, state an assumption, choose a method, and test whether the result is reasonable.

Role-Specific Breakdowns

Investment Banking and Capital Markets

Prepare accounting links, valuation, transaction logic, market awareness, and concise deal discussion. You should be able to explain how the three financial statements connect, when one valuation method is more useful than another, and what currently matters in your chosen sector.

Build a compact technical notebook covering the three statements, enterprise versus equity value, DCF, comparable companies, precedent transactions, accretion and dilution, and basic leveraged-buyout logic. Do not memorize definitions alone. Practice explaining what would change the output and why.

For a deal or company discussion, use this structure: business model and value drivers; transaction or strategic question; valuation or financial logic; principal risks; and the fact that could change your conclusion.

Markets and Research

Choose one or two market themes you can defend. Prepare the mechanism, affected instruments or companies, counterargument, catalyst, and risk to your view. Interviewers can distinguish a thesis from a headline summary by asking what evidence would make you change your mind.

Technology and Engineering

Expect the technical depth to follow the role. Software candidates should prepare data structures, coding, debugging, APIs, databases, and system design at the appropriate level. Data and infrastructure roles may emphasize SQL, data pipelines, reliability, controls, or cloud architecture. Use our software-engineering interview guide and system-design framework as supporting practice.

Practice coding and design in financial-system contexts: an order event stream, entitlements service, audit log, position calculation, or client reporting pipeline. Address correctness, access control, data lineage, recovery, and operational visibility. A design that scales but cannot be reconciled or audited is incomplete for a financial institution.

Wealth and Investment Management

Demonstrate investment judgment, client communication, risk awareness, and an understanding of the relevant products. Strong answers translate analysis into a clear recommendation without hiding uncertainty.

Practice discovering a client’s objective before recommending a product. Separate risk capacity from risk tolerance, identify liquidity and time-horizon constraints, and explain recommendations without implying certainty. Senior roles should prepare examples of relationship development and suitability judgment.

Operations, Risk, and Compliance

Be ready to map a process, identify failure points, prioritize controls, and explain an escalation. Answers should balance commercial outcomes with operational and regulatory risk.

Common Questions with Frameworks

These are practice prompts, not reported Morgan Stanley interview questions.

1. “Why Morgan Stanley, and why this division?” (Motivation)

Approach: Start with the work, not the logo. Name a specific capability or client problem, connect it to one relevant experience, then explain the contribution you want to make. Finish with why the division’s environment is a better match than adjacent paths.

2. “Walk me through a DCF.” (Technical, Banking)

Approach: Explain the objective, forecast unlevered free cash flow, estimate terminal value, discount both using WACC, bridge enterprise value to equity value, and divide by diluted shares. Then discuss the assumptions most likely to dominate the result. The sensitivity discussion is where judgment becomes visible.

3. “Design a reliable trade-notification system.” (System Design)

Approach: Clarify event sources, recipients, latency, delivery guarantees, and regulatory retention. Propose durable ingestion, idempotent processing, preference and entitlement checks, channel workers, retry and dead-letter handling, audit records, and monitoring. Explicitly distinguish delivery accepted by a provider from delivery seen by a user.

4. “Tell me about a judgment call under pressure.” (Behavioural)

Approach: State the decision and stakes quickly. Explain which facts you obtained, what you could not know, which risk you protected against, and how you communicated. Close with the outcome and the principle you would reuse.

More prompts to drill:

• Why Morgan Stanley, and why this business rather than another financial institution?
• Walk me through one experience that best predicts your performance in this role.
• Explain a recent market development and how it affects this team or its clients.
• Tell me about a time you made a decision with incomplete information.
• Describe a disagreement where you changed either the decision or your own position.
• For banking: walk through a DCF and identify its most sensitive assumptions.
• For engineering: design a resilient service for a high-volume financial workflow.
• For risk: how would you investigate a control breach without disrupting the business?

Prepare for resume follow-ups. Morgan Stanley advises candidates to know their resume and tell an authentic story, so prepare at least two follow-ups for every important bullet: What was the baseline? What alternative did you reject? What part did you own? What went wrong? How would the result change at ten times the scale? What did a teammate contribute that you could not have done alone? This depth is more valuable than adding another generic achievement, and it protects you from sounding rehearsed when an interviewer changes the angle.

Culture Fit: Is Morgan Stanley Right for You?

High standards and visible consequences. Morgan Stanley can suit candidates who enjoy detailed review and work where judgment has visible consequences.

The division sets the daily rhythm. An investment-banking team, a technology platform group, and wealth management do not feel the same. If you prefer loosely defined ownership, establish how much autonomy this specific team gives before accepting. Ask how decisions are reviewed, how junior employees receive feedback, and what strong performance looks like after six months.

Questions worth asking your interviewers:

• What decisions would this role own in its first six months?
• Which technical or commercial judgment separates strong performers on this team?
• How does the division coordinate with the functions most important to this role?
• What has changed most about the team’s priorities during the last year?
• How is feedback delivered after a major project or transaction?

Ask questions whose answers help you evaluate the actual work. Avoid asking for information available on the first page of the company website.

What interviewers screen for: ownership you can evidence, judgment under follow-up, authentic motivation for one division, and the ability to reason aloud rather than guess.

Compensation Overview (2026 Estimates, USD)

Figures below reflect New York data from levels.fyi, Glassdoor, and street compensation surveys.

Role	Base Salary	Total Compensation (Base + Bonus)
Investment Banking Analyst	$110,000 - $135,000	$185,000 - $300,000
Investment Banking Associate	$175,000 - $225,000	$300,000 - $450,000
Vice President (Investment Banking)	$250,000 - $300,000	$525,000 - $800,000
Software Engineer	$105,000 - $145,000	$115,000 - $165,000
Senior Software Engineer / VP Technology	$175,000 - $225,000	$250,000 - $300,000
Executive Director Technology	$230,000 - $280,000	$330,000 - $400,000

Morgan Stanley sits in the top bonus tier alongside Goldman Sachs and JPMorgan: analyst bases run $110,000 / $125,000 / $135,000 for Years 1-3 with cash bonuses of roughly $75,000 - $165,000, so Year 3 all-in reaches $240,000 - $300,000. Bases have not moved since the 2022 reset; every increase since has come through the year-end discretionary bonus. Deferral starts at 20-30% of bonus for Associates and VPs, mostly in restricted stock vesting over three years. Technology pay is the strongest of the US banks covered here, though senior big tech roles still clear $550,000. Compare guaranteed first-year cash separately from bonus and deferred value, and use the salary negotiation guide to prepare an evidence-based discussion.

Preparation Timeline: 4-6 Weeks

Week	Focus	Activities
1	Division and role research	Build a role map, a targeted resume, and a specific motivation answer
2	Technical foundation	Run finance drills, coding practice, a market thesis, or client scenarios
3	Evidence and communication	Write eight stories and rehearse two deep resume walkthroughs
4	Interview simulation	Complete two full mocks, review errors, and finalise your question list

For early-career programs, include coursework and extracurricular evidence but apply the same ownership standard. For experienced hiring, expect the interview to test the level at which you operated, not merely the number of years worked.

OphyAI Interview Practice can return a scored rubric and transcript; Interview Copilot can help organize your final notes.

Common Mistakes

Giving a generic “prestige” answer. Reputation is not a reason to want this division, this team, or this work.

Preparing the wrong syllabus. Finance questions for a technology role, or coding questions for an operations role, waste the only preparation time you have.

Reciting market news. An observation that never connects to the team or its clients shows reading, not judgment.

Claiming a team result. If your personal contribution is not identifiable, the achievement cannot be credited to you.

Guessing when you do not know. State your assumptions and reason from them; the firm cares how you work through a scenario.

Prepare for Morgan Stanley with OphyAI

Morgan Stanley can mix competency, strengths, skills, and technical questions in the same loop, and it expects you to keep reasoning aloud when the answer is not immediate. That is a rehearsal skill, and it improves fastest with feedback on structure rather than more reading.

Turn the division-specific modules in this guide into mock rounds. Use Interview Practice to rehearse finance, behavioral, or technical answers, then use Interview Copilot to organize the metrics, deal or project details, and follow-up questions you want available before the call. Start practicing →

---

Start Your Morgan Stanley Application

Ready to apply? OphyAI can help at every stage:

• Search for open roles at Morgan Stanley and similar companies with AI-powered job matching
• Generate a tailored cover letter that highlights your fit for the role, plus follow-up emails and thank-you notes for after your interviews
• Track your application status alongside every other role you’re pursuing

Pair these with Interview Copilot for structured live interviews, or practise first with OphyAI Interview Practice.

Related company guides

• Goldman Sachs interview guide
• JPMorgan interview guide
• Citi interview guide

Frequently Asked Questions

Does Morgan Stanley ask technical questions?

Yes, when technical knowledge is relevant to the position. “Technical” can mean valuation for banking, coding for software engineering, investment analysis for research, or control knowledge for risk. The content varies substantially by role.

How many Morgan Stanley interview rounds are there?

Morgan Stanley does not publish one fixed count for every position. Plan for an initial conversation followed by one or more role-specific interviews, but use your recruiter’s schedule as the source of truth.

What is the best answer to “Why Morgan Stanley?”

Connect a specific business, type of work, and part of your background. A good answer explains why the match is unusually strong; it does not rely on reputation alone.

Sources and verification notes

• Morgan Stanley interview preparation
• Morgan Stanley students and graduates

Hiring steps change by role and location. Check the live job posting and recruiter instructions before every round.