The hiring process
| Round | Format | What's tested |
|---|---|---|
| HackerRank Online Assessment | ~90–120 min | Aptitude + debugging + coding |
| Technical Interview(s) | ~45–60 min each | DS/algorithms + CS depth |
| Superday / Final Panel | ~2–4 hours (multiple) | Combined technical + behavioral |
Process and cutoffs vary by drive/team and change over time — confirm on the official careers page.
Round-by-round: exactly what's asked & how to prepare
HackerRank Online Assessment
~90–120 minA timed multi-section test typically split into aptitude MCQs, a debugging segment, and two to three coding problems. Each section is separately timed, so pacing is critical. Coding ranges from easy to medium, sometimes with finance-flavored framing.
- Quantitative aptitude and logical reasoning
- Debugging pre-written buggy functions
- Array, string, and hash-map coding
- Basic dynamic programming or greedy
- Trees or linked-list manipulation
- Practice aptitude and logical reasoning under time (free: IndiaBix)
- Do targeted debugging drills, since many candidates neglect this
- Solve medium array, string, and tree problems on HackerRank/LeetCode
- Simulate the sectioned timing so no section drains your clock
- Underpreparing debugging and aptitude, which cost easy points
- Spending too long on one coding problem and starving the rest
- Balanced scoring across all three sections
- Efficient time management under separate timers
Technical Interview(s)
~45–60 min eachOne or more live rounds probing data structures, algorithms, OOP, and computer-science fundamentals, plus a deep dive into your projects. Interviewers push on why you made design choices and on edge cases. Concurrency, databases, and OS basics can appear for tech-analyst roles.
- Trees, graphs, and recursion
- OOP design of a small system or class hierarchy
- Concurrency and multithreading basics
- SQL and data-modeling reasoning
- Detailed project design and trade-off defense
- Practice trees, graphs, and DP mediums explaining aloud
- Revise OOP, threading, DBMS, and OS fundamentals (free: GeeksforGeeks)
- Prepare to defend every design choice in your top project
- Rehearse discussing edge cases proactively
- Thin project knowledge that collapses under follow-ups
- Ignoring concurrency and OS basics that tech roles probe
- Depth on fundamentals, not just memorized solutions
- Well-defended design and edge-case awareness
Superday / Final Panel
~2–4 hours (multiple)A set of back-to-back interviews mixing further coding or design with behavioral and motivation questions. Panels assess consistency, resilience, and cultural fit alongside technical depth. Expect questions on why finance and why Morgan Stanley.
- Additional medium coding or a small design task
- Why technology in finance and why Morgan Stanley
- Handling pressure, failure, and tight deadlines
- Collaboration across teams and stakeholders
- Ethics and diligence in high-stakes systems
- Prepare five STAR stories including pressure and failure
- Craft a specific reason for finance-tech and Morgan Stanley
- Keep energy and clarity consistent across multiple rounds
- Prepare sharp questions for each interviewer
- Fading in later rounds after a strong start
- Generic motivation with no finance-specific reasoning
- Consistent performance across the full day
- Clear motivation and composure under pressure
What to master
- Arrays, strings, and hashing
- Trees, graphs, and recursion
- Dynamic programming and greedy
- Object-oriented design
- Concurrency and multithreading basics
- Databases and SQL
- Operating systems fundamentals
- Aptitude, logical reasoning, and debugging
Eligibility
Role-based: the Technology Analyst Program targets final-year and recent graduates in CS, IT, or related fields with strong coding fundamentals; specific eligibility (batch year, academic thresholds) is set per campus and region.
Morgan Stanley salary & compensation (2026)
Front-office (strats/quant dev) pays far more via cash bonus than the technology track; India GCC (Bengaluru/Mumbai) is strong for tech but below NY front-office.
| Role / Level | Experience | India — total CTC | US — total comp | What to know |
|---|---|---|---|---|
| Analyst/Associate Dev | 0–3 yrs | ₹18–32 LPA | $140K–200K | tech track; bonus ~15–25% |
| Senior Associate / VP Dev | 3–7 yrs | ₹35–60 LPA | $220K–320K | VP is a major cash-bonus jump |
| VP (Technology) | 7–11 yrs | ₹60 LPA–1 Cr | $330K–450K | large discretionary bonus |
| Executive Director | 11–15 yrs | ₹1–1.6 Cr | $500K–750K | bonus-heavy; front-office much higher |
| Managing Director | 15+ yrs | ₹1.8 Cr+ | $800K–1.5M+ | front-office MDs far exceed tech MDs |
How the package is structured
- Front-office roles (quant strats, trading tech) earn much larger discretionary bonuses than pure technology-division roles at the same title.
- Comp is cash-bonus-heavy with deferred stock; the VP milestone is the biggest early step.
- India GCC tech comp is competitive but sits well below NY front-office totals.
- Title progression (VP → ED → MD) plus desk/P&L proximity drives the largest comp gains.
Indicative 2026 market ranges aggregated from public sources (levels.fyi, Glassdoor, AmbitionBox, candidate reports). Compensation varies widely by location, team, level calibration, and negotiation — use these as directional benchmarks, not guarantees.
Your prep plan
- Days 1–2: aptitude, logical reasoning, and debugging under time
- Days 3–5: array, string, tree, and graph mediums explaining aloud
- Days 6–7: dynamic programming and greedy patterns
- Days 8–9: OOP, concurrency, DBMS, and OS revision
- Days 10–11: sectioned mock HackerRank tests for pacing
- Days 12–14: STAR stories, project defense, and finance-tech motivation
Want this plan dated to your interview?
Upload your resume and tell Whis your interview date — get a personalized, day-by-day plan built around your gaps, then run Whis live in the interview.
Get my personalized planFrequently asked questions
Why is the HackerRank round considered tricky?
It is broad and separately timed across aptitude, debugging, and coding, so candidates who only prep LeetCode often lose points on the other sections.
Do I need finance knowledge?
Deep finance knowledge is not required, but showing genuine interest in technology within finance and in Morgan Stanley strengthens the behavioral and final rounds.
How deep do project questions go?
Quite deep. Interviewers probe design choices, edge cases, and trade-offs, so surface-level familiarity with your own work is a common failure point.