
Morgan Stanley Data Engineer candidates report an online assessment, then technical interviews on SQL, Python, Spark and Azure. Reports also include sliding-window, math and behavioral questions. Here is what to prepare for.
$108K
Avg. Base Comp
$120K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Two Data Engineer candidates describe an online assessment followed by technical conversations. Both reported no offer, so these accounts show where preparation fell short.
The assessment is where SQL and Python logic show up first. One candidate reported deleting duplicates from a table and tracking student absences across consecutive days. Another described a bundled aptitude, logical reasoning and medium-difficulty coding test. Practice deduplication, consecutive-event and time-series SQL, and watch edge cases.
The technical rounds differed between the two accounts. One candidate met two developers who asked about projects, DSA level, core Python, SQL optimization and Azure. A later round in that account covered Apache Spark and Azure architecture, a duplicate-log sorting problem by timestamp, and Flask. That candidate said weak Spark and Azure fundamentals were the main gap. The other candidate was asked about Python, SQL and Scala, and was given a sliding-window problem to talk through. That candidate also got matrix rank, linear algebra, probability and statistics questions. Expect to explain your reasoning aloud.
The behavioral element in the second account was light, with questions on why Morgan Stanley and why the IED program. One candidate reported three rounds over about two weeks. Timing may vary by team.
Synthesized from 3 candidate reports 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.
The process moved quickly—I went through three rounds over about two weeks, and Morgan Stanley kept communication tight with results coming back within a few days after each stage. First came an online assessment with a mix of SQL and Python questions focused on logic building. I remember one SQL question asked me to delete duplicates from a table, and another involved tracking student absences across consecutive days. There was also a Python component, though the exact focus escapes me now. The whole assessment felt straightforward but required careful attention to edge cases.
The second round was a technical interview with two developers from the company. They dug into my projects and tech stack, asking about my DSA level and diving deeper into Python core concepts and SQL optimization. They also touched on Azure since the role involves cloud work. This round felt collaborative—they wanted to understand how I approach problems and whether I could articulate my thinking clearly.
The final round shifted focus. They brought in questions about Apache Spark and Azure cloud architecture, which were more framework and infrastructure heavy. There was also a coding problem about duplicate logs that needed to be sorted by timestamp—less about the algorithm itself and more about handling real-world data quality issues. Flask came up too, suggesting they care about how you'd actually build and deploy things, not just pass LeetCode. All three rounds were professional and well-structured, but ultimately I didn't move forward. In hindsight, I wish I'd spent more time on Spark fundamentals and Azure specifics before the later rounds—those felt like the areas where I was least prepared, and they clearly mattered to the team.
Prep tip from this candidate
Focus heavily on Apache Spark and Azure cloud services—these came up in the later technical rounds and were clearly important to the role. For the first-round assessment, practice SQL queries on data deduplication and time-series problems like tracking consecutive events, and be ready to explain your Python approach during the technical interview.
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 | |
| Size of Joins | |
| Maximum Profit | |
| Get Top N Frequent Words | |
| Ranking Metrics | |
| Cyclic Detection | |
| Justify a Neural Network | |
| Sort Strings | |
| Assumptions of Linear Regression | |
| Hurdles In Data Projects | |
| RAG Strict Source Control | |
| Success Measurement | |
| Coin Dispenser | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Shortest Path Algorithms | |
| Fixed-Length Arrays: Deletion | |
| Text Editor With OOP | |
| Last Element of a Singly Linked List | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| LRU Cache 1 | |
| Parking Application System Design | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Employee Salaries | |
| Subscription Overlap | |
| Comments Histogram | |
| Top Three Salaries |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an online screen before any live interview. One described SQL and Python logic questions, including deleting duplicates and tracking absences across consecutive days. Another described aptitude, logical reasoning and a medium-difficulty coding test. One candidate said careful attention to edge cases mattered.
One candidate met two developers who probed projects, tech stack, DSA level, core Python, SQL optimization and Azure. Another was asked about Python, SQL and Scala and solved a sliding-window problem verbally. Interviewers appeared to want clear step-by-step reasoning.
One candidate reported unexpected math in the technical stage: matrix rank, basic linear algebra, probability and statistics. This was reported by one person, so it may not appear in every loop. It is worth a brief refresher alongside your core SQL and Python preparation.
One candidate reported a final round on Apache Spark, Azure cloud architecture, Flask and a coding task that sorted duplicate logs by timestamp. The emphasis was on messy real-world data and deployment awareness. That candidate named Spark and Azure as the weakest areas.
One candidate described a calm, non-aggressive behavioral segment that asked why they wanted Morgan Stanley and the IED program. Be ready with a specific, role-linked answer. This was a single report, so the exact format may differ by team.