Download 2026 Morgan Stanley placement papers
Morgan Stanley Placement Papers 2026
Morgan Stanley is a leading global financial services firm providing investment banking, wealth management, and trading services. Founded in 1935, Morgan Stanley operates in 40+ countries. Morgan Stanley India has technology divisions working on trading platforms, risk systems, and financial applications, making it a top recruiter for software engineers in India with a focus on financial technology and innovation.
Explore: Online Assessment · Coding Questions · Interview Experience · Preparation Guide · Certifications & Career · Download PDF
Morgan Stanley fresher eligibility for campus drives
Section titled “Morgan Stanley fresher eligibility for campus drives”Morgan Stanley does not publish one universal CGPA cutoff for every India Technology Analyst drive. What students see depends on campus JD wording vs careers portal / referral posts. Treat the numbers below as candidate-reported (placement cells, job posts, interview write-ups as of August 2026) - not a guarantee from Morgan Stanley HR.
On-campus vs off-campus vs intern paths
Section titled “On-campus vs off-campus vs intern paths”| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA window, PPT timing, college list | Coding + quant bar |
| Careers / referral | Resume volume; published CGPA language varies | Still expect OA + loop |
| Summer Analyst → return | Conversion interviews may skip a stage | You still defend code and projects |
Off-campus does not mean easier coding. It often means more applicants on the same HackerRank/Codility filter.
Documents and portal hygiene
Section titled “Documents and portal hygiene”- Keep mark sheets consistent with the portal - BV is serious in finance firms.
- Screenshot invite duration, platform (HackerRank vs Codility), and quant section size.
- Prepare a public project story if internships had NDAs.
- Mumbai and Bangalore both appear in India tech chatter - know which location your JD names.
Detailed eligibility criteria breakdown
Section titled “Detailed eligibility criteria breakdown”| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 7.0+ CGPA / ~70% across 10th, 12th, graduation | Top-college drives may feel stricter in practice |
| Degree | B.Tech / B.E. / M.Tech | CS, IT, ECE, related |
| Year | Final year + recent grads (~1 year) | Intern conversion paths appear |
| Backlogs | No active backlogs | Hard filter in most reports |
| Gap | Max ~1 year | Need a clean story |
| Coding languages | C++, Java, Python | Stick to one for OA + interviews |
Selection feel by CGPA band
Section titled “Selection feel by CGPA band”| CGPA range | Rough chances | Reality check |
|---|---|---|
| 7.0-7.4 | Meets many reported floors | Need strong OA coding + quant |
| 7.5-8.0 | Common in shortlisted chatter | Helps resume screen; OA still decides |
| 8.0-8.5+ | Strong at IIT/NIT/IIIT pools | Still fail without clean DSA narration |
| Below printed floor | Often filtered before OA | Target drives where you qualify |
Is 7 CGPA enough?
Section titled “Is 7 CGPA enough?”Yes as a reported floor - not as a selection guarantee. A 7.2 who finishes two OA coding problems and explains an order-matching sketch beats an 8.9 who freezes on DP. Technology Analyst hiring cares about problem-solving under time and systems intuition, not CGPA cosplay.
Technology analyst vs banking tracks
Section titled “Technology analyst vs banking tracks”This hub focuses on Technology Analyst / tech fresher loops: OA coding + quant → DSA → systems → managerial → HR. Some year-page narratives describe HireVue + Associate/VP/MD style banking interviews with valuation talk. Those can be role-dependent. If your invite is Technology, do not pivot your entire prep into DCF flashcards. If your invite is banking, treat HireVue as real and verify separately.
Morgan Stanley placement papers - last few years
Section titled “Morgan Stanley placement papers - last few years”Morgan Stanley does not publish one permanent official paper set. “Previous year papers” on placementpapers.app are pattern trainers - not leaked live assessments.
| Round (typical) | What to practice |
|---|---|
| Online assessment | Timed DSA (2-3) + quant aptitude speed |
| Technical 1 | Live coding narration with complexity |
| Technical 2 / design | Low-latency order path, risk pipelines, reliability |
| Managerial / HR | Integrity, ownership, Why MS Technology, location |
Themes that keep repeating (2024-2026)
Section titled “Themes that keep repeating (2024-2026)”- 2024 cycles: DSA + math aptitude together on OA. DP/graphs in coding; trading and risk system design in interviews; low-latency vocabulary already present. Summer Analyst OAs sometimes look AMCAT-like (debug + apt + programming) - campus TA drives still centre coding + quant.
- 2025 loops: Stronger “optimal solution” pressure; distributed/low-latency chatter in Round 2. Year pages also market HireVue/IB topics - use those only if your track matches. Practice banks still include rotate array, Kadane, climb stairs, two-sum style cousins labeled as styled practice, not official dumps.
- 2026 prep expectation: OA remains the volume filter. Keep medium-hard DSA and probability/quant warm. Design rounds stay fresher-depth latency and controls - not staff trading-architect theater. Treat PDF packs as pattern catalogs.
How to use one paper set in a single sitting
Section titled “How to use one paper set in a single sitting”- Timed: coding block first (or as your invite orders), then quant under a clock.
- Untimed review: rewrite cleaner code; list three edge cases; redo every wrong quant item.
- Map coding misses to themes (DP / graph / tree / greedy) via coding questions.
- Spend 15 minutes explaining an order → match → confirm path out loud with one failure mode.
- Log one STAR story about pressure, deadline, or integrity.
Related problems to practice
Section titled “Related problems to practice”| Theme you saw in a set | What to drill next | Why MS asks it |
|---|---|---|
| Max profit with ≤k trades | DP on stocks | Classic finance-flavoured DSA |
| Order matching intuition | Heaps / priority queues | Matching engine mental model |
| Risk aggregation | Prefix / streaming sums | Portfolio risk sketches |
| Graph dependencies | Topo sort / DFS | Downstream risk / calc graphs |
| Low-latency talk | Profiling bottlenecks | Round 2 vocabulary |
| Probability puzzles | Bayes / expected value drills | OA quant block |
2024 PDFs often drill “best time to buy/sell with cooldown.” Own the DP state template, then drill a related problem. Memorising story text does not transfer.
What a good Morgan Stanley PDF is for
Section titled “What a good Morgan Stanley PDF is for”Students search “Morgan Stanley previous year paper PDF download” expecting a leaked Codility set. Useful packs give timed DSA cousins, quant drills, and design prompts. Ignore “exact cutoff 81%” Telegram claims - Morgan Stanley does not publish those numbers. Nested OA pages also admit limited verified public write-ups - practice still helps; treat absolute pattern claims with humility.
Papers - year pages as maps
Section titled “Papers - year pages as maps”When you open /morgan-stanley/2024/, /2025/, or /2026/, treat salary lines and HireVue notes as signals to verify, not locked truth. Prefer this hub’s Technology Analyst process for campus tech drives. If a year page mixes DCF/M&A questions, label that as a possible banking track and do not derail TA prep.
Mock review ritual (15 minutes)
Section titled “Mock review ritual (15 minutes)”- Which coding problem first, and why?
- First failing test you missed?
- Quant items missed - concept or speed?
- Complexity claimed vs coded?
- One STAR trigger from the frustration?
Next week’s plan comes from that log.
Quant count conflict - how to handle IT
Section titled “Quant count conflict - how to handle IT”Some hub notes say 10-15 quant questions; some year pages say 5-7 in 15-20 minutes. Both can be true across invites. Your move: practice both a short dense set and a longer set once each, then trust your mailer.
Morgan Stanley placement process, round by round
Section titled “Morgan Stanley placement process, round by round”Morgan Stanley hires Technology Analyst freshers through campus cells, the careers portal, referrals, and internship conversion. After resume screen: timed OA (coding + quant), DSA, systems/low-latency, managerial, HR.
Application methods
Section titled “Application methods”Campus recruitment
Through college placement cells - PPT, then OA and interviews on a batch timeline.
Online applications
Apply on Morgan Stanley careers for early-career tech roles; follow the invite for platform and duration.
Referrals / intern return
Referrals and Summer Analyst conversions exist. You still defend code, quant, and projects.
1. Resume / eligibility screen
Section titled “1. Resume / eligibility screen”Checks degree, CGPA floor when printed (7.0+ / 70% commonly reported), backlogs, and year of passing. Fintech internships and systems projects help. Gate only - OA is the hard filter.
2. Online Assessment - ~90 min
Section titled “2. Online Assessment - ~90 min”| Component | Typical shape (reported) | Focus |
|---|---|---|
| Coding | 2-3 medium-hard | Arrays, trees, graphs, DP, greedy |
| Quant / math aptitude | ~5-15 Q (invite-dependent) | Probability, speed quant, reasoning |
| Platform | HackerRank or Codility | Confirm mailer |
| Languages | C, C++, Java, Python | Pick one |
| Advance bar (reported) | Often ≥2 coding clears | Optimal complexity helps |
Student tip: Do not skip quant to “save time for coding” if both are scored. Skim coding prompts first, bank a medium, keep 15-20 minutes sacred for quant if your paper is structured that way - adjust to your invite order.
Example timing for a 90-minute OA
Section titled “Example timing for a 90-minute OA”| Minute | Move |
|---|---|
| 0-5 | Skim coding + quant sizes; plan |
| 5-55 | Fully solve coding 1-2 with tests |
| 55-75 | Attempt coding 3 only if 1-2 solid |
| 75-90 | Quant block with skip rules |
Deeper notes: Morgan Stanley Online Assessment.
Why quant shows up even for “pure coding” students
Section titled “Why quant shows up even for “pure coding” students”Morgan Stanley builds systems where probability, distributions, and expected outcomes are not academic toys. The OA quant block is a cheap filter for numerical comfort. You do not need contest-math olympiad skills. You do need to finish a short set without panic. Students who proudly “only do DSA” and leave quant for the last ten minutes often miss the shortlist by a thin margin.
Practice set shape that works:
- 10 mixed probability / combinations items in 15 minutes, twice a week
- 10 speed percentage / ratio items in 10 minutes, once a week
- After each set, rewrite the two you missed until you can teach them
Coding section - worked student approach
Section titled “Coding section - worked student approach”Prompt flavour: “maximum profit with at most two transactions” or “design LRU.” Approach:
- Restate constraints and money units (integers).
- State brute force and why it fails at n.
- Name the target complexity before coding.
- Implement, then dry-run one sample and one edge case.
- Only then open the next prompt.
Banking two full greens beats one clever partial and one empty editor.
Summer analyst OA colour
Section titled “Summer analyst OA colour”GfG-linked intern paths describe AMCAT-style mixes: debugging + aptitude + programming, sometimes 7 easy debugging plus hard apt plus 3 medium-hard coding where partial still cleared. Useful as a vibe check - do not replace your TA invite plan with it.
3. Technical interview 1 - DSA (~45-60 min)
Section titled “3. Technical interview 1 - DSA (~45-60 min)”Shared editor. Expect 1-2 DSA problems (LIS, LRU, graphs, DP, strings) plus project warm-up. Narrate brute → optimize → edge cases → complexity. Silent staring after a failed test case is a reject signal.
Warm-up: one easy array/hash problem in your interview language so syntax is warm.
4. Technical interview 2 - systems / low-latency (~45-60 min)
Section titled “4. Technical interview 2 - systems / low-latency (~45-60 min)”Fresher depth prompts:
- Order matching / exchange path at toy scale
- Market data fan-out and latency budgets
- Risk calculation pipeline (inputs → aggregates → alerts)
- What breaks at 10× throughput
- Reliability and controls (audit logs, kill switches - plain words)
Worked mini-outline - matching engine intuition:
- Actors: clients, gateway, matching engine, market-data bus, risk check.
- Happy path: new order → risk checks → match against book → fills → confirmations.
- Latency: where microseconds go (network vs matching vs downstream).
- Failure: downstream risk service timeout - fail closed vs open? Say your choice.
- Scale later: sharding symbols, sequencing - only after the happy path is clear.
5. Managerial round - ~45 min
Section titled “5. Managerial round - ~45 min”Behavioral + light technical depth. Integrity, client focus, excellence under pressure, conflict, and sometimes a revisit of your design. STAR format. Finance tech cultures listen for whether you hide errors.
6. HR round - ~20-30 min
Section titled “6. HR round - ~20-30 min”Why Morgan Stanley Technology (platforms, not “banking prestige” only), Mumbai/Bangalore logistics, notice/exams, CTC context around ₹25-35 LPA, joining timelines.
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | OA (coding + quant) | ~90 min | Timed correctness |
| 2 | Technical 1 | 45-60 min | DSA + narration |
| 3 | Technical 2 | 45-60 min | Low-latency / systems |
| 4 | Managerial | ~45 min | Ownership + integrity |
| 5 | HR | 20-30 min | Fit + logistics |
Managerial - what “excellence” means for a fresher
Section titled “Managerial - what “excellence” means for a fresher”You will not have a production trading outage story. You will have a project where quality almost slipped. Practice naming the control you added (tests, checklist, code review, monitoring). Morgan Stanley values language around controls more than “I worked hard.”
Timeline from application to offer
Section titled “Timeline from application to offer”| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | Sometimes multi-week app windows |
| OA → shortlist | About a week common | Competitive |
| Interview loop | 1-2 weeks | Tech → managerial → HR |
| Offer / paperwork | Days after final round | Written offer wins |
| End to end | ~3-4 weeks | Off-campus can stretch |
Intern offer stories sometimes move faster after final chats - still budget patiently.
OA pattern cheat-sheet
Section titled “OA pattern cheat-sheet”| Component | Focus | Prep move this week |
|---|---|---|
| Coding Q1-Q3 | DP, graphs, trees, greedy | Two timed mediums |
| Quant | Probability + speed | Timed mock quiz |
| Design | Order path, risk, latency | 3-minute aloud sketch |
| HR | Why MS Tech, city | Two STAR stories |
Morgan Stanley aptitude, coding & interview practice
Section titled “Morgan Stanley aptitude, coding & interview practice”Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
How to train for Morgan Stanley this season
Section titled “How to train for Morgan Stanley this season”If a Morgan Stanley invite is 3-8 weeks out, treat this hub as the map and the nested pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Morgan Stanley sits around ₹25-35 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Morgan Stanley eligibility for freshers 2026 is candidate-reported, not one official published cutoff. Common baseline: 70% or 7.0+ CGPA across 10th, 12th, and graduation; B.Tech/B.E./M.Tech in CS, IT, ECE, or related fields; final-year students and recent graduates (within ~1 year); no active backlogs; max ~1 year education gap. Strong C++, Java, or Python skills are preferred. Always verify the careers posting or c.
What you are training for: Technology Analyst fresher loops commonly run: Online Assessment (~90 minutes, sometimes 90-120) with 2-3 coding problems plus quantitative aptitude → Technical Round 1 (DSA, ~45-60 min) → Technical Round 2 (system design / low-latency depth, ~45-60 min) → Managerial (~45 min) → HR (~20-30 min). End-to-end is often about 3-4 weeks. Some banking tracks add HireVue - confirm your invite.
Short version of the prep split: Split prep roughly 40% DSA, 30% timed coding mocks, 15% low-latency / trading-flavored system design, 10% quantitative aptitude, 5% behavioral. Clear OA coding plus quant first. Languages: C++, Java, or Python.
A four-week plan that actually gets used
Section titled “A four-week plan that actually gets used”Week 1 - pattern, not vibes. Timed aptitude + one easy coding problem a day, plus a one-page cs fundamentals sheet. Open the Morgan Stanley previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Morgan Stanley drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Morgan Stanley usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Morgan Stanley?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Two full mocks, then only error-log topics - no new patterns. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
Section titled “Where the hours should go”| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Morgan Stanley-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Nested pages to open this week
Section titled “Nested pages to open this week”- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the Morgan Stanley story (eligibility, rounds, salary). Use those pages for reps. If a card 404s on your campus mirror, the explore links at the top of this page are the same destinations.
Common ways students waste a month
Section titled “Common ways students waste a month”- Collecting 12 Morgan Stanley PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed Morgan Stanley papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
Section titled “If you are starting from a service-company prep base”A TCS/Infosys aptitude deck still helps the quant/logic slice of many Morgan Stanley papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Morgan Stanley-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
10-day crash version
Section titled “10-day crash version”Days 1-3: one timed Morgan Stanley paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Morgan Stanley. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
What to carry into the interview room
Section titled “What to carry into the interview room”Know your project at the level of what broke and what you changed, not only the tech list on the resume. For Morgan Stanley, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
Tracking that does not become a second job
Section titled “Tracking that does not become a second job”A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three Morgan Stanley mistakes, you are collecting content, not preparing.
Extra drill block (1)
Section titled “Extra drill block (1)”Sit one more mixed Morgan Stanley set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
Morgan Stanley compensation & benefits
Section titled “Morgan Stanley compensation & benefits”Figures below are candidate-reported India bands (as of August 2026). Actual offers depend on level, Mumbai / Bangalore, college tier, and written components.
Technology analyst and related bands
Section titled “Technology analyst and related bands”| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Technology Analyst (fresher) | ₹25-35 LPA | Primary hub band |
| Exceptional / top-college stories | ₹35-45 LPA | Not the default |
| Associate (1-2 YOE) | ~₹30-40 LPA total | Indicative |
| Offer anecdotes | ~₹32 LPA, ~₹28 LPA | Individual stories |
Confirm base, bonus, and benefits on the written offer. Morgan Stanley does not officially publish fresher salary bands.
CS fundamentals checklist
Section titled “CS fundamentals checklist”- Explain ACID with a trade-booking example.
- Process vs thread for a market-data fan-out service.
- Why might you choose a ring buffer or queue between gateway and engine (plain words)?
- SQL: index a
(symbol, ts)query for recent trades. - What is backpressure when downstream is slow?
Two evenings on this list softens Round 2 follow-ups.
Location talk without drama
Section titled “Location talk without drama”If the JD says Bangalore and you prefer Mumbai, say so early with a reason (family, housing). Panels prefer honesty over “anywhere!” energy that collapses at offer time. Ask about hybrid norms - do not invent them from Reddit.
Benefits students care about
Section titled “Benefits students care about”Health coverage, learning support, and location norms vary by year and BU. Ignore copy-paste “401(k)” noise on random blogs for India offers - ask HR what actually applies to your letter.
How to talk CTC in HR
Section titled “How to talk CTC in HR”Know the ₹25-35 LPA Technology Analyst context, ask how the package splits, and clarify joining vs exams. Calm clarity beats aggressive negotiation without anchors.
Offer letter hygiene
Section titled “Offer letter hygiene”Compare fixed vs variable with peers using the same fields. Finance BV is strict - fix name/mark mismatches early. If juggling GS/JPM timelines, be honest.
Recent Morgan Stanley placement trends
Section titled “Recent Morgan Stanley placement trends”- Virtual interviews remain common alongside campus loops.
- OA coding + quant still the fresher volume filter for Technology Analyst paths.
- Low-latency / controls vocabulary shows up more consistently in Round 2 write-ups.
- HireVue appears on some 2024-2025 year-page banking narratives - verify track before over-prepping.
- Treat ₹25-35 LPA as a reported TA band, not a promise for every role.
- India tech footprint chatter continues around Mumbai and Bangalore - read your JD.
What has not changed
Section titled “What has not changed”- No active backlogs remains a hard expectation in reports.
- Silent coding without complexity talk still fails.
- Invented “official CGPA cutoff” PDFs remain unofficial.
Morgan Stanley placement FAQs
Section titled “Morgan Stanley placement FAQs”Process & papers
Section titled “Process & papers”What is the Morgan Stanley placement process?
Typical Technology Analyst fresher path: OA (~90 min, coding + quant) → Technical 1 (DSA) → Technical 2 (systems / low-latency) → Managerial → HR. Often about 3-4 weeks end-to-end. Confirm round names on your invite.
How many rounds are there in Morgan Stanley interview?
Most TA fresher loops report five stages. Some tracks add HireVue or merge rounds. Count the mailer.
Can I download Morgan Stanley placement papers PDF for free?
Yes. Free Morgan Stanley placement papers PDF and 2024-2026 style practice are on placementpapers.app - pattern trainers, not leaked live papers. Start with the 2026 PDF or the archive.
What does the Morgan Stanley Online Assessment look like?
Often ~90 minutes with 2-3 coding problems and a quant block (question count varies by invite). Platforms: HackerRank or Codility. Aim to fully solve at least two coding problems.
Eligibility & offer
Section titled “Eligibility & offer”What is Morgan Stanley eligibility criteria for freshers 2026?
Commonly reported: 7.0+ CGPA / 70%, CS/IT/ECE-related degrees, final-year or recent grads (~1 year), no active backlogs. Not an official universal cutoff - your JD wins.
What is Morgan Stanley salary for freshers in 2026?
Candidate-reported Technology Analyst total CTC often ₹25-35 LPA (as of August 2026). Exceptional stories run higher. Written offer letter wins.
Do I need to relocate to Mumbai or Bangalore?
Both cities appear in India tech reports. HR checks location willingness against your JD. Be honest early.
Prep & ms-specific
Section titled “Prep & ms-specific”How to prepare for Morgan Stanley placement?
Split roughly 40% DSA, 30% timed mocks, 15% low-latency design, 10% quant, 5% behavioral. Details: preparation guide.
Which programming languages are allowed?
C, C++, Java, Python are typical. Confirm invite. Do not switch languages the week of the drive.
What is the Technology Analyst role?
Primary fresher tech track candidates discuss - trading platforms, risk systems, financial applications. Selected via the OA + interview loop; CTC commonly discussed in the ₹25-35 LPA band (reported).
What system design topics should I revise?
Order matching intuition, market-data paths, risk pipelines, latency budgets, and failure modes at fresher depth. Plain sketches beat buzzwords.
Morgan Stanley vs Goldman Sachs vs JP Morgan?
All strong. Compare written offers, team, and location. Interview flavour differs - MS TA loops emphasise coding + quant + platform thinking. See also Goldman Sachs and JP Morgan.
Is HireVue always part of the process?
No. It shows up in some banking-oriented year narratives. Technology Analyst campus invites may skip it. Trust your mailer.
Any pro tip that actually changes outcomes?
Bank two fully passing OA coding solutions, keep probability warm, and rehearse one low-latency order-path explanation before Round 2. Narrate complexity out loud.
Where can I read real interview experiences?
Start with Morgan Stanley interview experience on placementpapers.app, then cross-check community write-ups as maps, not scripts.
Morgan Stanley - recent candidate experiences
Section titled “Morgan Stanley - recent candidate experiences”Technology analyst fresher stories
Section titled “Technology analyst fresher stories”IIT CS (~8.5 CGPA, fintech internships): Tech1 - LIS + LRU Cache (~45m). Tech2 - real-time risk system plus internship deep-dive. Managerial STAR. HR → about ₹32 LPA in that write-up. Takeaway: classic DSA plus a risk-systems story.
NIT IT (~8.0 CGPA, ~1y backend): OA - 3 coding (2 full + 1 partial) + ~15 math. Tech1 graphs/DP/DB. Tech2 low-latency order matching. Managerial deadlines/leadership. HR → about ₹28 LPA. Takeaway: partial third coding can still work if two are solid and quant holds.
Summer analyst / off-campus colour
Section titled “Summer analyst / off-campus colour”Off-campus Technology Summer Analyst (GfG): Applied Oct 2023 → Feb 2024 AMCAT-like OA (~100 min debug+apt+prog) → Zoom tech + HR/HM → offer about a week after final chat. Another path (apply Oct 2024; interview Mar 2025): OA with 7 debug + hard apt + 3 coding (incomplete still cleared) → ~1h tech (arrays/strings, SQL, OS, DNS, OOPs) → ~30m tech+HR → offer. Useful for patience budgeting; not a promise your campus TA paper matches.
What hurt other candidates: skipping quant; buzzword latency talk with no bottleneck; hiding mistakes in managerial; treating HR as a formality after two technical clears.
How to read conflicting process maps
Section titled “How to read conflicting process maps”If one PDF shows HireVue + MD rounds and another shows five TA stages, they may be different jobs. Align prep to your invite. Then return to timed mocks on placementpapers.app.
Week-of-drive checklist
Section titled “Week-of-drive checklist”- Confirm platform (HackerRank/Codility) and quant size
- Light DSA + short probability set in the morning
- Rehearse 60-second Why MS Technology + order-path sketch
- Sleep; OA punishes all-nighters
Giving back after you clear
Section titled “Giving back after you clear”Post round-wise notes: OA duration, quant count, whether Round 2 asked matching vs risk, and location. Juniors need specifics more than motivation.
Eligibility nuance for tier-1 vs tier-2 campuses
Section titled “Eligibility nuance for tier-1 vs tier-2 campuses”On some top-campus drives, practically everyone already clears 7.0, so CGPA stops differentiating and OA becomes everything. On mixed pools, a printed 7.0 floor still filters resumes before the test link goes out. Either way, once you have the link, CGPA cannot save a weak coding section. Plan study hours accordingly: fewer hours arguing cutoffs, more hours on timed mocks.
If you sit at 7.0-7.2, write a one-page “why me” for referrals: projects with measurable outcomes, contest ranks if any, and internship impact. Referrals help visibility; they do not rewrite Codility scoreboards.
Deep dive - technical round 1 narration habits
Section titled “Deep dive - technical round 1 narration habits”Interviewers reward a predictable rhythm:
- Clarify input/output and constraints (null books, duplicate orders, integer money).
- Offer brute force in one breath.
- Identify the bottleneck.
- Propose the structure (hash map, DP table, heap).
- Code while narrating decisions.
- Test a sample and an edge case.
- State final complexity.
Practise this rhythm on easy problems until it is muscle memory. Saving the rhythm only for hard problems is why people go silent under stress.
Deep dive - risk pipeline sketch you can reuse
Section titled “Deep dive - risk pipeline sketch you can reuse”When Round 2 asks “how would you compute portfolio risk?”, try:
- Inputs: positions, prices, risk factors, limits.
- Compute: per-position exposures → aggregate by book/desk.
- Latency: batch vs streaming; what is acceptable delay for your toy design.
- Controls: limit breach alerts, kill switch, audit log.
- Failure: stale prices - show last-good with a warning vs fail closed.
That outline beats naming three databases you have never operated.
Trends - virtual process logistics
Section titled “Trends - virtual process logistics”Camera, ID, and stable network are part of the exam now. Do a dry run of your interview setup: lighting, headphones, shared-editor permissions, and a backup hotspot. Students lose loops to logistics more often than they admit on LinkedIn.
Also expect email delays between rounds. Use the waiting days for error-log revision, not for opening five new GitHub repos of “MS questions.”
Candidate stories - what to steal, what to ignore
Section titled “Candidate stories - what to steal, what to ignore”Steal: problem names that match your prep themes (LIS, LRU, matching), the emotional budget for multi-week waits, and the reminder that partial OA coding can still advance. Ignore: exact CTC as your entitlement, and any claim that one college’s paper is universal.
If your story ends in rejection, write down the first question you failed to clarify. That single note improves the next loop more than rereading salary tables.
On-campus PPT week - what to do the night before
Section titled “On-campus PPT week - what to do the night before”If your college hosts a Morgan Stanley PPT, treat it as intel gathering, not entertainment. Note the role name (Technology Analyst vs other), locations mentioned, and whether they emphasise coding contests or academic filters. Ask one concrete question if there is a Q&A - “What does a first-year Technology Analyst build in Bangalore/Mumbai teams?” beats “What is the culture?” Take notes; reuse them in HR as specific motivation.
After PPT, do not start a new DSA topic at midnight. Sleep, then one light mock in the morning if OA is the next day.
Offer comparison sheet
Section titled “Offer comparison sheet”When multiple finance-tech offers arrive, compare:
- Total CTC and fixed portion
- Joining date vs exam constraints
- Location and relocation support
- Team clarity (trading tech vs risk vs wealth platforms)
- Bond/notice language if any
A slightly lower CTC on a team you understand can beat a higher number on a mystery rotation. Write the comparison down so FOMO does not decide for you.
After rejection - 48-hour protocol
Section titled “After rejection - 48-hour protocol”- Write the questions you saw while memory is fresh.
- Mark which failures were speed vs concept vs communication.
- Schedule two focused drills only on those gaps.
- Do not apply to eight firms in panic the same night.
Rejection from Morgan Stanley is common in competitive pools. The students who clear next cycle are usually the ones who kept an error log, not the ones who only posted a sad story.
Quant warm-up bank
Section titled “Quant warm-up bank”Keep a tiny personal set: conditional probability one-liners, expected value of a simple game, combinations with constraints, and percentage change under time. Rotate ten items in fifteen minutes. When the OA quant block feels “easy but long,” that is success - you want boredom under time, not novelty.
Java comfort note for India tech centres
Section titled “Java comfort note for India tech centres”Many Bangalore/Mumbai tech stories mention Java in production. You can still clear OA in C++ or Python. Just be ready to read a short Java snippet or discuss OOP in Java terms during interviews. One weekend of Java syntax refresh is enough; do not rebuild your entire prep stack mid-season.
Same-week interview stacking
Section titled “Same-week interview stacking”Technology Analyst loops can schedule two technicals close together. Keep LIS/LRU/graph templates warm, and reread your order-path sketch the night before Round 2. If managerial follows the next day, sleep beats cramming a new system-design YouTube playlist.
When HR discusses joining dates against final exams, bring calendar facts - not vibes. Finance onboarding batches are real constraints; honest constraints are easier to accommodate than last-minute surprises.
Related companies to compare
Section titled “Related companies to compare”Goldman Sachs · JP Morgan · Bank of America · Wells Fargo · HSBC · Barclays