
One candidate describes the Morgan Stanley Solutions Engineer interview as mostly behavioral. It covered a phone screen, competency questions, a product-knowledge discussion and a final round on difficult clients and internal growth goals.
$160K
Avg. Base Comp
$205K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
One candidate who interviewed for the Morgan Stanley Solutions Engineer role expected a technical loop and instead found the process almost entirely behavioral. It began with a phone screen and a behavioral and competency round. That round focused on past work, including whether the candidate had led anyone and whether they were comfortable with project management tools such as JIRA.
A product-knowledge discussion followed. The candidate was asked to talk through the firm's offerings and how they would position them for a client. They found it manageable but said it rewards plain, clear explanations.
The final round covered client communication, problem-solving and regulatory awareness. The interviewer kept returning to a difficult-client story, and also asked about the candidate's ambition for internal growth. The candidate was rejected and believes their example did not go far enough into their own reasoning.
If you prepare for this role, build a STAR story that shows your judgment rather than just the sequence of events. Have an honest answer about leadership, even if it was informal. Know how you would describe the firm's products to a client, and be ready to say where you want to grow in a few years. This guide rests on a single candidate's account.
Synthesized from 1 candidate report by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Morgan Stanley process.
I went into the Morgan Stanley Solutions Engineer process expecting a technical loop, and for me it was almost entirely behavioral. The first step was a phone screen, followed by a round of behavioral and competency questions. Much of it was about my past work, especially whether I'd led anyone. The interviewer asked about my team lead experience, if I had any, and whether I was comfortable with project management tools like JIRA. If you've mostly been an individual contributor, have an honest answer ready rather than hoping it won't come up.
Next came a product-knowledge discussion, where I had to talk through the firm's offerings and how I'd position them for a client. I didn't find this one hard, but I'd recommend reviewing the basics before you go in, since they were clearly checking that I could explain things plainly.
The final round was the one that decided it. It covered client communication, problem-solving, and regulatory awareness, and the interviewer kept returning to one question: tell me about a difficult client and how you resolved the situation. I gave a real example, but I didn't push far enough into my own reasoning, and I think that showed. The interviewer also spent a good amount of time on my personal ambition for internal growth, so you should be ready to say concretely where you want to be in a few years.
I didn't get an offer, and I don't have a clear explanation from the firm. Looking back, I'd treat every behavioral answer as a chance to show judgment, not just to describe what happened.
Prep tip from this candidate
Prepare a specific STAR story about handling a difficult client, plus a concrete answer about your internal growth goals, since the final round pressed hard on both. Be ready to discuss project management tools like JIRA and any team lead experience, even if it was informal.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Morgan Stanley
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| Find the Missing Number | |
| Get Top N Frequent Words | |
| Size of Joins | |
| Maximum Profit | |
| Coin Dispenser | |
| Sort Strings | |
| Shortest Path Algorithms | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| LRU Cache 1 | |
| Cyclic Detection | |
| Seasonal Product Performance Analysis | |
| Last Element of a Singly Linked List | |
| Hurdles In Data Projects | |
| RAG Strict Source Control | |
| Text Editor With OOP | |
| Fixed-Length Arrays: Deletion | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Employee Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Comments Histogram | |
| Top Three Salaries | |
| Last Transaction | |
| Slacking Employees Salaries | |
| Cumulative Distribution |
Synthesized from candidate reports. Individual experiences may vary.
The candidate describes a phone screen as the first step. The account gives no details about what it covered, so treat it as the entry point to the behavioral rounds that followed.
The candidate reports questions about past work, especially whether they had led anyone. They were also asked about team lead experience and comfort with project management tools like JIRA. Candidates without formal leadership experience may want an honest, specific answer ready.
The candidate reports talking through the firm's offerings and how they would position them for a client. They found it not hard but noted that interviewers seemed to check that they could explain things plainly. Reviewing the basics of the firm's products beforehand would likely help.
The candidate describes the final round as covering client communication, problem-solving and regulatory awareness. The interviewer repeatedly asked for a difficult-client example and its resolution, then spent time on personal ambition for internal growth. The candidate says they did not show enough of their own reasoning and was rejected.