Morgan Stanley’s campus tech hiring runs through the Technology Analyst Program, and the first gate is a timed coding test: usually two or three HackerRank problems with 60 to 90 minutes on the clock and no interviewer watching. Clear that and you move to a phone screen, then a Superday. Experienced hires skip the assessment and start with a recruiter call and a technical phone screen instead. None of it is exotic. What trips people up is treating a bank like a big-tech shop and prepping for the wrong thing.
Three ways into Morgan Stanley tech
Almost every technology candidate lands in one of three buckets, and the interview leans differently depending on which one you’re in.
The Technology Analyst Program is the new-grad pipeline. You apply to a broad tech role, not a specific team, and get matched after you’re hired. Analysts land in application development, infrastructure, cybersecurity, or platform teams across the firm’s tech hubs (New York, Montreal, Glasgow, Budapest, Mumbai, Bangalore, Shanghai). The bar here is standard data structures and algorithms plus a behavioral read on whether you actually want to work at a bank.
Strats and Modeling is Morgan Stanley’s version of the quant-adjacent developer. Strats sit between the trading desk and the codebase: they build pricing models, risk engines, and P&L tooling, and they’re expected to reason about the math, not just implement someone else’s spec. If you’re interviewing for strats, expect probability and expected-value questions mixed in with the coding. Python and C++ dominate here, with some kdb+/q where tick data lives.
E-trading technology is the low-latency world: order management systems, matching logic, market-data handling, execution algos. The questions get more systems-flavored and more concurrency-heavy. This is where C++ still rules and where a question about an order book is a genuine test, not a warm-up.
The online assessment is a filter, not a conversation
The HackerRank round is auto-graded on hidden test cases. Nobody reads your code for style. That means two things: your solution has to actually pass the edge cases (empty input, single element, duplicates, large N that times out an O(n²) approach), and partial credit is real, so a brute-force answer that passes half the cases beats a clever one that compiles wrong. Budget your time. If a problem is fighting you at the 20-minute mark, lock in a working brute force and move on.
The problems themselves are LeetCode easy-to-medium. Arrays and hash maps, two pointers, a string-manipulation problem, sometimes a light graph or dynamic-programming question. You won’t get a research-grade hard problem in the automated round.
Phone screens and the Superday
The phone screen is 45 to 60 minutes, usually a working engineer on the other end, and it’s a live coding problem shared over a collaborative editor. Talk through your approach before you type. They care about how you narrow the problem, name your assumptions, and reason about complexity. A silent candidate who arrives at the right answer often scores below one who’s clearly thinking out loud and gets 90% of the way.
The Superday is the final round: typically three to five back-to-back interviews, a mix of technical and behavioral, sometimes with a hiring manager and a more senior engineer or executive director in the loop. For 2026 these are often virtual for early rounds with an on-site final, though it varies by office and team. Expect at least one interview that’s mostly “why Morgan Stanley, why finance, tell me about a time you disagreed with a teammate.” Banks screen hard for people who’ll bail after the training program, so a credible answer to “why here and not a startup” carries weight.
What they actually ask
The coding is bread-and-butter DSA. A representative spread for a software track:
- “Given an array of daily prices, find the maximum profit from a single buy and later sell.”
- “Return the first non-repeating character in a string, and give me the time and space complexity.”
- “Reverse a singly linked list in place. Walk me through the pointer bookkeeping.”
- “Detect whether a string of brackets is balanced.”
For experienced software and e-trading candidates, at least one round goes design-heavy. These are asked conversationally, not as a spec: “Design an in-memory limit order book. What structures give you constant-time best bid and ask plus fast cancels?” or “A market-data feed pushes millions of messages a second and a downstream consumer falls behind. What do you do?” They want to hear about ring buffers, back-pressure, dropping stale ticks, and where the latency actually goes, not a textbook recitation of load balancers.
Probability questions for strats
If you’re on the strats track, the probability questions are the differentiator, and they’re closer to a quant screen than a normal SWE loop. Nothing here needs measure theory, but you need to be fast and clean with expected value and conditioning:
- “You flip a fair coin until you see two heads in a row. What’s the expected number of flips?” (It’s 6, and they want the recurrence, not a memorized number.)
- “Two players alternate flipping a fair coin; first to flip heads wins. What’s the probability the first player wins?” (2/3.)
- “A stick is broken at two uniformly random points. What’s the probability the three pieces form a triangle?” (1/4.)
The pattern: set up the states or the geometry, write the equation, solve. If you can narrate that cleanly you’ll pass even if you fumble the arithmetic. Interviewers on strats desks have seen every canned answer, so showing the derivation matters more than sprinting to the number.
What working there is actually like
It’s a bank, and that shows up in the day-to-day. The stack skews Java across the firm, with C++ where latency matters and Python heavy in strats and data work. Some codebases are old and load-bearing; some teams have modernized onto cloud and modern tooling. Internal platforms are strong because the firm has been building them for decades, which is a double edge: powerful, well-documented systems you couldn’t get anywhere else, wrapped in process you also couldn’t get anywhere else.
The hierarchy is explicit. Analyst, associate, vice president, executive director, managing director, and the ladder moves on a schedule more than on a rocket. Promotions are title-gated and slower than the “senior in three years” pace common at big tech. As of 2026 the firm is largely back in the office most of the week, so if remote work is non-negotiable for you, weigh that going in. Work-life balance in technology is generally better than in banking or the trading floor, but engineers on production trading systems carry on-call, and a market-hours outage is a real fire.
The upside is stability, genuinely interesting problems in trading and risk, and colleagues who know the domain cold. The trade-off is that you’re one function inside a large financial firm, not the product itself. If you want to ship a consumer feature and watch a graph move, this isn’t that. If you want to build the system that prices a book of exotic derivatives, it very much is.
Comp: lower base than big tech, and the bonus carries the story
Bank technology pay trails big-tech total comp, and the gap widens as you climb because big-tech packages lean on stock that compounds while bank pay leans on cash bonus that resets each year. The base salaries are competitive; it’s the equity that’s thinner. Bonuses are a larger and more variable slice than most tech roles, and at senior levels a chunk gets deferred into stock that vests over several years.
Treat the numbers below as rough US ranges for 2026, not quotes. They swing hard by location, team, and how the firm’s year went. Check levels.fyi and recent Glassdoor entries for the specific office and level before you anchor on any figure or counter an offer.
| Level / role (Morgan Stanley technology) | Approx. US base salary, 2026 | Typical annual bonus | Bonus form |
|---|---|---|---|
| New-grad Technology Analyst | $95k–$130k | 10%–25% of base | Almost all cash |
| Associate (~3–6 years) | $130k–$180k | 15%–40% of base | Mostly cash, small deferred piece |
| Vice President | $180k–$260k | 25%–70% of base | Cash plus deferred stock |
| Strat / quant developer | Overlaps associate–VP bands, often higher variable | Wider swing, tied to desk performance | More deferred at senior levels |
For a rough comparison: a new-grad software engineer at a top big-tech firm often clears $150k–$200k+ all-in on day one thanks to a large stock grant, while a Morgan Stanley tech analyst lands closer to $110k–$160k with most of the variable piece in cash. The bank number is more predictable and less exposed to a stock price; the big-tech number has more upside and more risk. Which you prefer is a real choice, not a mistake either way.
How to prep without burning a month
Get fluent on easy-to-medium LeetCode across arrays, strings, hash maps, two pointers, linked lists, stacks, trees, and basic graph traversal. You don’t need the hard-problem grind that a big-tech loop demands; you need speed and correctness on the common patterns, since the automated round rewards passing tests over elegance. Pick one language and know it cold, including its standard collections and their complexity. For most software roles that’s Java; for e-trading, C++; for strats, Python.
If you’re going for strats, spend real time on probability. Work through expected value, conditioning, coin and dice problems, and a handful of classic brainteasers until the setup is automatic. A book like Heard on the Street or A Practical Guide to Quantitative Finance Interviews covers the exact flavor.
Then do the unglamorous part: read up on the firm’s actual businesses (wealth management, institutional securities, investment management) so your “why here” answer isn’t generic, and prepare two or three concrete stories about projects where you owned something hard. The technical bar at Morgan Stanley is passable for a prepared candidate. The people who fail the loop usually aren’t the ones who couldn’t reverse a linked list. They’re the ones who couldn’t say, convincingly, why they wanted to build software at a bank rather than anywhere else.
Similar company guides
Prepping for Morgan Stanley? Put it to work: