Inside a Morgan Stanley VP Interview: What They Ask

William, an NYU finance student and competitive table tennis player, sits across from Tate, a VP in Morgan Stanley's M&A group. For the next 30 minutes, William will field questions designed to stress-test everything from his motivations to his ability to calculate enterprise value under pressure. Exponent, an interview prep platform, filmed this mock interview to show candidates what they're walking into.

The choreography is familiar to anyone who's survived these gauntlets: behavioral questions that probe for leadership and conflict resolution, technical questions that separate those who memorized formulas from those who understand what the formulas mean, and the omnipresent "why this firm?" question that requires candidates to demonstrate they've done their homework without sounding like they're reciting a brochure.

What's interesting isn't that this interview exists—Morgan Stanley and its peers have been running this playbook for decades—but what it reveals about how candidates are trained to perform.

The Three-Point Framework

William deploys a consistent rhetorical structure: three reasons for everything. Why investment banking? "The challenging industry, the unique positioning of the sell side, and the ability to make an impact." Why Morgan Stanley specifically? "My passion for learning, global reach with diverse product offerings, and culture and mentorship."

This isn't accident. It's strategic architecture. Three points are enough to seem thorough without testing the interviewer's patience. They create a rhythm. They're memorable.

But there's a tension here. The formula works because it works—it's been refined through thousands of successful interviews. Yet that same ubiquity creates risk. When every candidate structures answers identically, differentiation has to come from content, not form. William tries to solve this by weaving in personal narrative: his father's biotech company in China, his table tennis career, his mentor Arjun who works in Morgan Stanley's tech group.

These details do the real work. The structure is scaffolding. The personal material is the building.

When Behavioral Questions Get Technical

The behavioral portion reveals something about how finance firms think about soft skills. Tate asks William about conflict resolution, and William tells a story about a table tennis teammate with anger management issues. Instead of confronting him directly, William spent weeks warming up with him before and after practice, building trust before addressing the behavior.

"Leadership isn't always just about telling other people what to do," William says. "But sometimes it starts with listening first. And especially in banking, you're going to be working with a lot of people with strong personalities under a lot of pressure."

This answer does what good behavioral answers must: it extracts a principle from a specific experience and maps it onto the target environment. But there's an underlying question the interview format doesn't allow: does investment banking actually select for this kind of emotional intelligence, or does it select for people who can talk about emotional intelligence in interviews?

The industry's reputation suggests the latter. Banking culture has historically rewarded aggression, endurance, and technical precision more than collaborative problem-solving. That might be changing—firms certainly say it's changing—but the gap between stated values and lived experience persists across the industry.

The Technical Gauntlet

Then come the technical questions, where the performance shifts entirely. Tate asks William to walk through valuation methods (DCF, trading comps, precedent transactions), explain how to unlever and relever beta, calculate enterprise value from equity value.

William handles these cleanly, though with the slight hesitation of someone who knows the answer but is mentally double-checking before speaking. This is probably smart—wrong answers to technical questions are harder to recover from than awkward pauses.

What's notable is the pedagogical approach embedded in Tate's questions. He doesn't just ask for the enterprise value calculation; he asks why you add debt and subtract cash. This tests whether candidates understand the logic underneath the mechanics. Anyone can memorize that EV = equity value + debt - cash. Fewer people can explain that debt gets added because acquirers assume those obligations, while cash gets subtracted because it offsets the purchase price.

Tate mentions he's "actually doing this right now on the job"—finding unlevered betas for a valuation pack. It's a small moment of humanity in an otherwise formal exchange, a reminder that the interviewer was recently in the candidate's position and will return to similar work after this conversation ends.

The Deal Discussion

When asked about a deal he's been following, William discusses Johnson & Johnson's acquisition of V-Wave, an Israeli cardiovascular device company, for $1.7 billion with a $600 million earnout. He explains the strategic rationale (TAM expansion, consolidation in cardiovascular devices) before pivoting to the complication: V-Wave failed to get FDA approval in 2025.

"I think it really just goes to show why Johnson and Johnson decided to pursue an earnout structure here rather than just paying all upfront in cash," William says.

This is the kind of observation that makes deal discussions work in interviews. He's not just recapping what happened—he's connecting deal structure to risk management. The earnout protected J&J from overpaying for an asset that might not clear regulatory hurdles.

But here's what the interview doesn't probe: what happens to V-Wave now? What does failure to get FDA approval mean for the earnout terms? Did J&J have an exit clause? These are the questions that would come up in an actual deal team meeting, but interview candidates aren't expected to have those answers. They're expected to demonstrate they know how to think about deals, not that they've done the full due diligence.

What the Performance Reveals

Mock interviews like this one exist in a strange space. They're simultaneously authentic (these are real questions asked in real interviews) and artificial (William knows this isn't binding, Tate knows his evaluation doesn't matter). That artificial quality might actually help candidates. The psychological weight of a real interview—where a wrong answer could cost you a job that determines the next two years of your life—can scramble otherwise solid technical knowledge.

But watching this exchange, I kept thinking about what's not being tested. There's no question about whether William actually wants to work 80-100 hour weeks. No discussion of what happens when the learning curve flattens and the work becomes repetitive. No acknowledgment that many analysts leave after their two-year commitment because the lifestyle is unsustainable.

The interview selects for people who can articulate why they want the job. It doesn't—can't—select for people who will still want it 18 months in, at 2 AM on a Sunday, reformatting a pitch deck for the sixth time.

That's not a criticism of this particular interview or this candidate. It's a structural limitation of the format. Interviews are performances, and performances reward those who've rehearsed. Whether that rehearsal predicts actual job performance is a different question entirely—one that every bank is still trying to answer.