Microsoft
The Azure-and-growth-mindset giant - structured loops, polite interviewers, and a heavy values filter.
hybrid — Most teams land on 3 on-site days; policy is team-dependent. Confirm with recruiting.
- 1975 (by Bill Gates and Paul Allen)
- Redmond, Washington, USA
- ~228,000
Levels
What each level changes about your loop
SDE 59/60
0–2 years
Coding-only loop; design skipped. Behavioral probes for growth-mindset stories.
Base-heavy comp, modest stock refreshers.
SDE II 61/62
2–5 years
Full loop with one design round; long follow-up chains on coding.
Balanced base + RSU; sign-on negotiable.
Senior 63–65 / Principal 66+
5–10+ years
Design becomes decisive - Azure-scale trade-off defense and cross-org influence probes.
Equity-dominated comp above 65; wide negotiation room.
Interview process
How the Microsoft pipeline runs
An online Codility assessment opens most pipelines, then one or two phone screens, then a virtual onsite of four interviews: two coding, one system or OO design (L61+), and one behavioral round built around culture keywords - growth mindset, customer obsession, One Microsoft. Interviewers are famously collaborative; the bar still bites through deep follow-up chains.
2–5 weeks end to end
- 1
Online Assessment
90–120 minTwo timed Codility problems; university tracks add an aptitude section.
- 2
Phone screen(s)
45–60 min × 1–2One problem with progressive follow-ups rather than many separate questions.
- 3
Onsite: Coding rounds
55 min × 2DSA with chained follow-ups. You drive: state assumptions, self-test edge cases.
- 4
Onsite: Design + Behavioral
55 min eachSystem/OO design for L61+; behavioral digs into learning-from-failure and collaboration.
- Weave 'growth mindset' vocabulary into failure stories - the most-probed value.
- Follow-ups chain: optimize out loud instead of stopping at brute force.
- Self-test with edge cases before declaring done - verification habits are scored.
- Ask about the team's product area; genuine curiosity about Azure/Windows/Gaming lands well.
Question bank
Questions they actually ask
- 01
LRU Cache - a perennial favorite across levels.
Hash map + doubly linked list for O(1) get/put; expect thread-safety follow-ups.
Practice this trace → - 02
Course Schedule - dependency cycles as build ordering.
Topological sort via Kahn's or three-color DFS; follow-up returns the actual order.
Practice this trace → - 03
Number of Islands - grid traversal staple.
Flood fill counting components; union-find is the standard extension.
Practice this trace → - 04
Valid Parentheses - the classic screen opener.
Stack matching; handle lone closers, leftover openers, empty input.
Practice this trace → - 05
Top K Frequent Elements - heap vs bucket under questioning.
Hash-map counts then size-k min-heap or bucket sort; justify the trade-off.
Practice this trace → - 06
Merge Two Sorted Lists - linked-list baseline.
Dummy-head merge O(n+m); recursive variant and k-list extension follow.
Practice this trace → - 07
Two Sum - still the most common opener.
Hash-map one-pass; sorted-input two-pointer follow-up.
Practice this trace → - 08
Climbing Stairs - DP gateway for junior loops.
Fibonacci-style rolling vars; extend to blocked stairs.
Practice this trace →
Process intel
How the process works, answered
How long does the process take?
Two to five weeks: about a week after OA to schedule, then an onsite decision within three to seven business days.
University pipelines run fixed fall/spring cycles and stretch around holidays.
Is there a Bar-Raiser equivalent?
No formal veto role, but all feedback is independent and behavioral rounds weigh equal to coding - a weak values round sinks strong loops.
'As-appropriate' HR rounds appear for senior candidates probing conflict history.
What language should I use?
Any mainstream language you know cold - C#, Java, Python, JavaScript all appear. Structure and edge handling matter, not syntax novelty.
C++ appears for Windows/devices teams; confirm the stack in the recruiter call.
Do new grads get system design?
Rarely - new-grad loops swap design for a third coding round or extra behavioral hour. Intern returns often skip to a shortened loop.
PhD 'Power' programs add research presentations instead of design.
Can I reapply after rejection?
Yes - six months is the soft cooldown, but teams recruit independently, so a referral into another org restarts you sooner.
Internal transfers after joining are the fastest path up levels.
Study plan
What to focus on for Microsoft
Trees & BSTs
3 tracesRecursion fluency assumed; validation and traversal variants recur constantly.
Graphs: topo sort & flood fill
3 tracesDependencies and grids framed as everyday infrastructure.
Hash maps & sets
3 tracesWarm-up territory - speed and cleanliness over exotic tricks.
Linked lists
3 tracesIn-place pointer surgery remains the junior-loop favorite.
Azure-scale design (L61+)
4 tracesMulti-region services, partitioning, cost trade-offs anchor the design round.
Turn this guide into muscle memory.