Microsoft Interview Experiences

Overview

How Microsoft’s SDE loop actually runs, based on aggregated candidate reports (GeeksforGeeks, Blind, Glassdoor, Reddit) and public hiring guides. Team and level change the details, so treat this as a prep map, not a script.

Learning from these experiences

Microsoft interviews weight DSA and CS fundamentals heavily in the early rounds, then shift toward culture and judgment in the As Appropriate (AA) round. Use the round table below first, then read the experiences for how that actually plays out end to end.

Reported fresher SDE total compensation in India commonly falls in the roughly Rs 28-40 LPA range (base plus bonus and stock), concentrated at Microsoft’s Hyderabad, Bangalore, and Noida development centers - treat any specific figure as a self-reported approximation, not a guarantee, since it varies by level, college tier, and location.

Microsoft interview process overview

Round	Duration	What it tests
Online Assessment (OA)	60-90 min	2-4 DSA problems on HackerRank/Codility
Technical Interview 1	45-60 min	DSA, live coding, problem-solving approach
Technical Interview 2-3	45-60 min each	CS fundamentals, LLD/OOD, light system design for senior roles
As Appropriate (AA) round	45-60 min	Culture fit, growth mindset, leadership signal - senior leader, veto power
HR / offer discussion	20-30 min	Logistics, compensation, closing questions

Real interview experiences

Experience 1: SDE-1, campus hire (2025)

Profile: B.Tech CSE, ~8.3 CGPA, tier-1 college, one internship, consistent LeetCode practice, hired through campus placement in Hyderabad

Online Assessment

• 90 minutes, 3 problems on HackerRank: a two-pointer array problem, a binary tree path-sum variant, and a harder graph problem (shortest transformation sequence). Cleared with all test cases passing on the first two, partial on the third.

Technical Interview 1

• Live coding on Microsoft Teams: design an LRU cache with O(1) get/put. Interviewer pushed on thread-safety as a follow-up after the base solution worked.
• A second, shorter problem: number of islands in a grid (DFS), then a follow-up asking for the Union-Find version.

Technical Interview 2

• Word ladder-style shortest-path problem (BFS), followed by CS fundamentals: paging and virtual memory, then a database question on transaction isolation levels.
• A short discussion of the candidate’s internship project - architecture choices and one specific performance fix.

As Appropriate (AA) round

• Interviewer: a Principal Engineer from an unrelated product group.
• “Tell me about a project you’re most proud of, and one thing you’d change about it.”
• “Describe a time you disagreed with your team’s technical approach.”
• “Tell me about a time you didn’t know something you needed to - how did you close that gap?”
• Kept every answer to a clear situation, action, and a specific change made afterward rather than a polished success story.

HR / offer

• Short call: location confirmation, notice period (not applicable for a fresher), and “why Microsoft.”

Result: Selected. Reported package in the mid-30s LPA range (base plus stock and bonus), Hyderabad. Takeaway: The AA round rewarded a specific, honest answer about a technical disagreement over a rehearsed leadership anecdote - preparing “what changed afterward” mattered more than preparing a flawless story.

Experience 2: SDE-2, off-campus/lateral hire (2024-2025)

Profile: ~3 years at a mid-size product company, applied off-campus through a referral, strong system design background

Online Assessment

• Skipped for this experience level; the loop began directly with technical interviews.

Technical Interview 1

• Merge k sorted lists (min-heap), then a discussion of time/space trade-offs versus a divide-and-conquer merge approach.
• Follow-up: how would this change if the lists were too large to fit in memory?

Technical Interview 2 (System design)

• Design a URL shortener, then extended into rate limiting for the write path.
• Discussion of consistency versus availability trade-offs and how the candidate would monitor the system in production.

Technical Interview 3

• LLD: design a parking lot system with proper class relationships, followed by a short DSA warm-up (valid parentheses variant with multiple bracket types).

As Appropriate (AA) round

• Interviewer: a Director from a different business group.
• Leaned almost entirely behavioural: a time the candidate pushed back on a manager’s decision, how they mentor more junior engineers, and a time they had to learn an unfamiliar part of a codebase quickly.
• The interviewer probed follow-ups on what the candidate would do differently, more than on the outcome itself.

Result: Selected after a loop with one technical round rated only “lean hire” - the strong AA round is what the candidate believes tipped the decision. Takeaway: A single average technical round did not sink the loop; a clearly strong AA performance can offset it, which matches how the AA round is reported to work as a final, override-capable check.

Questions that come up often

Coding / technical

1. Design an LRU cache - HashMap + doubly linked list, thread-safety follow-up
2. Number of islands - DFS, then Union-Find follow-up
3. Word ladder / shortest transformation sequence - BFS
4. Merge k sorted lists - min-heap
5. Binary tree path-sum variants
6. Valid parentheses with multiple bracket types
7. CS fundamentals: paging/virtual memory, database transactions and isolation levels, TCP handshake

System design / LLD

1. Design a URL shortener, then extend to rate limiting
2. Design a parking lot system (LLD/OOD, class relationships)
3. Design an LRU/LFU cache as a standalone system
4. Design a notification or messaging service

Behavioural (technical rounds and AA round)

1. Tell me about a project you’re most proud of, and what you’d change about it
2. Describe a time you disagreed with your team’s technical direction
3. Tell me about a time you didn’t know something you needed to - how did you close that gap?
4. Tell me about a time you failed at something and what changed afterward
5. Why Microsoft?

Practical tips for Microsoft

• Practice explaining trade-offs out loud, not just reaching a working solution - Microsoft interviewers probe the “why” behind a choice as much as the code itself.
• Don’t skip CS fundamentals assuming only DSA gets tested; paging, transactions, and networking basics show up across technical rounds.
• For the AA round, prepare 2-3 stories that each end with a concrete change you made, not just an honest account of what went wrong - that closing beat is what growth-mindset framing rewards.
• Treat an AA invite as encouraging, not as the interview being over - it is a real, veto-capable evaluation.
• If a technical round feels average, don’t assume the loop is lost - candidates report the AA round can offset a mixed earlier round.

HR interview

After the technical rounds and the As Appropriate round, Microsoft usually closes with a short HR conversation covering logistics, motivation, and a couple of closing behavioural questions. Prepare those answers on the dedicated page rather than cramming them into this hub.

HR interview questions→

Common Microsoft HR questions, sample answer frames, and STAR tips.

Similar companies

Google · Amazon · Meta · TCS · Infosys · Wipro