The hiring process
| Round | Format | What's tested |
|---|---|---|
| Online Assessment | ~60-90 min | DSA coding on a platform |
| Coding Interviews (2 rounds) | ~45-60 min each | DSA plus reasoning and light behavioral |
| System Design (many roles) | ~45-60 min | Designing a scalable, reliable system |
| As Appropriate (AA) Round | ~45-60 min | Holistic final round with veto weight |
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
Online Assessment
~60-90 minAn online coding test (often via Codility/HackerRank or campus platform) with two to three DSA problems focused on data structures and algorithms. Correctness across all test cases and reasonable efficiency gate the interviews.
- Array/string manipulation with efficiency
- Tree or linked-list operations
- Graph traversal (BFS/DFS)
- Dynamic programming basics
- Hashing and sorting-based problems
- Solve medium DSA on LeetCode, focus on trees, graphs, linked lists and DP
- Practice passing all edge-case test cases
- Time yourself under platform conditions
- Use NeetCode patterns for structure
- Partial solutions failing hidden test cases
- Ignoring time-limit constraints
- Skipping DP and graph practice
- All test cases passing
- Efficient, clean solutions
- Correct complexity handling
Coding Interviews (2 rounds)
~45-60 min eachTwo interviews mixing DSA problem-solving with some fundamentals and behavioral questions. Interviewers watch how you respond to hints, learn from mistakes and communicate, valuing growth mindset alongside correctness. Trees, graphs, linked lists and DP dominate; exotic algorithms are rare.
- Tree/graph problem with follow-up optimization
- Linked-list manipulation
- Dynamic programming problem
- Explaining and improving your approach after a hint
- A behavioral prompt on teamwork or a past challenge
- Drill trees, graphs, linked lists and DP with narration
- Practice taking hints and revising gracefully
- Prepare a few STAR stories to weave in
- Do mock coding interviews (Pramp free)
- Getting defensive when corrected
- Silent coding with no communication
- Over-preparing exotic algorithms while neglecting core patterns
- Growth mindset: learning from hints
- Clear communication and collaboration
- Correct, efficient code
System Design (many roles)
~45-60 minFor many roles you get a design round scoped to your level, reasoning about components, data models, APIs, scaling and reliability at scale (Azure/Office/Windows-style platform thinking). You should drive the discussion and surface trade-offs and failure modes.
- Design a scalable service or API
- Data storage and caching choices
- Handling high traffic and failures
- Consistency and reliability trade-offs
- Monitoring and scaling strategy
- Study the free System Design Primer on GitHub
- Learn load balancing, caching, queues, sharding and replication
- Practice a requirements-first framework
- Emphasize reliability and failure handling
- Ignoring reliability and failure modes
- No trade-off discussion
- Designing before scoping requirements
- Requirement-first scoping
- Reliability-aware design
- Clear trade-off reasoning
As Appropriate (AA) Round
~45-60 minA senior interviewer (often outside the immediate team) runs a holistic round that can include a harder coding or design problem plus deep behavioral and culture-fit assessment. Their read carries effective veto, so consistency, maturity and growth mindset are decisive.
- A challenging coding or design problem
- Deep behavioral: conflict, failure, leadership
- How you learn and partner across roles
- Reasoning about ambiguity and trade-offs
- Culture and values alignment
- Bring your best consistent coding and design form
- Prepare mature STAR stories on failure and collaboration
- Practice reasoning calmly through ambiguity
- Reflect genuinely on how you learn and grow
- Treating AA as just another coding round
- Weak or blame-shifting behavioral answers
- Losing composure on a hard problem
- Consistent technical strength
- Mature growth mindset and collaboration
- Calm reasoning under pressure
What to master
- Trees, graphs and linked lists
- Dynamic programming
- Arrays, strings and hashing
- Time and space complexity
- System design fundamentals and reliability
- Growth-mindset communication
- Collaboration and cross-role partnering
- STAR behavioral storytelling
Eligibility
Entry SWE (SDE) roles hire new grads and early-career engineers; system-design depth scales with the role and level. Exact loop composition varies by team and level (flag as evolving). Confirm specifics with your recruiter.
Microsoft SWE salary & compensation (2026)
Strong comp with lower stock ratio than Meta/Google; big jump at Principal (65+).
| Role / Level | Experience | India — total CTC | US — total comp | What to know |
|---|---|---|---|---|
| SDE (59–60) | 0–2 yrs | ₹28–45 LPA | $150K–200K | base + on-hire stock + 10–20% bonus |
| SDE II (61–62) | 2–5 yrs | ₹45–75 LPA | $200K–280K | annual stock + bonus grow |
| Senior SDE (63–64) | 5–9 yrs | ₹75–130 LPA | $290K–400K | stock share rises; higher bonus target |
| Principal SDE (65–67) | 9–14 yrs | ₹130–230 LPA | $420K–650K | large stock refreshers; special stock awards |
| Partner (68+) | 14+ yrs | ₹230–380 LPA | $650K–950K+ | equity-dominant, discretionary awards |
How the package is structured
- US split ~ base 50–60%, stock 25–40%, bonus 10–20% (higher at senior)
- Annual stock refreshers plus periodic special stock awards
- India comp ~ 45–55% of US; 64→65 (Principal) is the key band jump
- Bonus target rises from ~10% (L59) to ~20%+ (Principal)
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-4: trees, graphs, linked lists and DP on LeetCode/NeetCode
- Days 5-6: mixed medium DSA under timed conditions
- Days 7-8: mock coding interviews with hint-taking practice
- Days 9-10: system-design fundamentals with one mock
- Days 11-12: STAR stories emphasizing growth mindset and collaboration
- Days 13-14: full mock loop including an AA-style holistic round
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
What is the 'As Appropriate' round?
A holistic final round run by a senior interviewer, often outside the hiring team, whose assessment carries effective veto over the decision. It blends a hard technical problem with deep behavioral evaluation.
How important is growth mindset?
Very. Microsoft explicitly values how you learn from mistakes and respond to hints, not just raw correctness, so stay open and coachable.
Which DSA topics matter most?
Trees, graphs, linked lists and dynamic programming. Exotic algorithms are rarely tested.
Is system design always included?
For many roles yes, scoped to your level, but the exact loop varies by team and seniority.
What platform is the OA on?
Often Codility, HackerRank or a campus platform, with two to three DSA problems. Passing all test cases matters.
How should I handle interviewer hints?
Welcome them, adjust your approach, and explain your revised reasoning. Coachability is a positive signal.