SDE / SDE I (New Grad) Interview Prep
Entry-level prep for Microsoft's SDE I loop - balanced coding fundamentals, light system design, and Growth Mindset framing.
About this loop
Microsoft's entry-level SDE rung (sometimes called just SDE, sometimes SDE I) targets new grads and engineers with under two years of experience. The loop is one of the most predictable in the industry: a recruiter screen, a technical phone screen with one Medium coding problem, and 4 onsite rounds covering coding (typically 2 rounds), behavioral / 'as-app' (the hiring manager round), and either a third coding round or a very bounded design discussion. System design as a full round is typically not required at SDE I - if it appears, it's a guided conversation about basic concepts (caching, load balancing, simple service design) rather than a 60-minute design round. The cultural framing is consistent across every round: Growth Mindset, the value Satya Nadella has made central to Microsoft's identity. Even at SDE I, expect 'tell me about a time you learned from failure' and 'how do you approach ambiguous problems' woven throughout. School projects, internships, and side projects are all valid STAR material at this level.
The interview loop
- 1Recruiter screen30 minutes. Background, university timeline, motivation. Recruiter often previews Growth Mindset framing as a culture indicator.
- 2Phone screen (technical)45-60 minutes. One coding problem at Medium difficulty. Behavioral framing woven in. Pass to advance to onsite.
- 3Onsite: Coding round 160 minutes. One to two algorithmic problems. Working code with edge cases handled and clean implementation expected. Code quality matters - Microsoft codebases are large and maintained.
- 4Onsite: Coding round 260 minutes. Second coding round with a different interviewer. Different topics from round 1. Often more open-ended or design-shaped (e.g., design a small class hierarchy, build a basic data processor).
- 5Onsite: Coding or bounded design60 minutes. Third coding round at most loops, or a very bounded design discussion (e.g., 'how would you build a basic chat service?') with the interviewer guiding actively.
- 6Onsite: As-app (hiring manager)60 minutes. Behavioral-heavy with role and team fit. Heavy Growth Mindset framing - learning from failure, handling ambiguity, collaborating across teams. The hiring manager has significant influence on the offer decision even at SDE I.
What Microsoft actually evaluates
- →Growth Mindset - stories about learning from school project failures, changing your approach based on feedback, embracing critique
- →Collaboration - school group projects, internship cross-functional work, club leadership all count
- →Clean, readable code - even at SDE I, Microsoft codebases are maintained by many people
- →Customer focus - tying technical decisions to user impact even in academic contexts
- →Ownership - taking initiative on ambiguous problems, school-project or internship-scale
- →Honest self-assessment - 'what would I do differently' is a sincere question
Topics tested
Algorithms
Medium difficulty across coding rounds. Two to three rounds means multiple chances to demonstrate consistency. Edge cases and clean implementation matter as much as the algorithm.
Data Structures
Trees, graphs, hash maps, queues, stacks. Microsoft's coding rounds consistently surface these. Know your tree traversals (in-order, BFS, DFS) and graph BFS/DFS cold.
Behavioral
Growth Mindset framing in every round. Prepare 4-5 STAR stories from school projects, internships, hackathons, club leadership, side projects. Specific incidents beat generic narratives.
Object-Oriented Design
Sometimes appears in a coding round (parking lot, library system). Clean class boundaries are enough at SDE I.
System Design
Not always a full round at SDE I. If it appears, expect a very bounded design discussion with the interviewer guiding actively. Basic service design (chat, URL shortener) at most.
Databases
Comes up if system design appears. SQL basics, indexes, normalization enough at SDE I level.
System design topics tested in this loop
Curated walkthroughs for the bounded designs that show up in Microsoft's system design rounds. Capacity estimation, architecture, deep-dives, and trade-offs.
URL Shortener
MediumThe canonical bounded system design problem. Read-heavy, hot-key prone, and a great vehicle for hashing, caching, and capacity estimation.
Chat
HardLong-lived connections, ordering guarantees, presence, and the difference between 1:1 chat and a 50K-member group.
Rate Limiter
MediumFive algorithms, three sharding strategies, one fail-open vs fail-closed decision. The bounded design that surfaces in every backend interview loop.
Behavioral themes tested in this loop
Sample STAR answers, common prompts, pitfalls, and follow-up strategies for the behavioral themes that decide Microsoft's loop.
Learning from Failure
MicrosoftMicrosoft's Growth Mindset core. Also tested at Google, Anthropic, and any company that screens for self-awareness. The signal is whether you actually changed.
Ownership
Amazon LPTested at every level, scored harder at senior. Did you take responsibility for outcomes - or just for tasks?
Ambiguity
GeneralTested at Google, Anthropic, OpenAI, and any senior+ loop. Strong candidates show how they get curious; weak candidates show how they get anxious.
Compensation at Microsoft BETA
Total comp ranges, base, equity, and bonus across the levels tested in this loop. Aggregated from public sources.
Microsoft compensation by level
5 SWE levels covered. Updated 2026-04-29.
Curated practice questions
333 MCQs and 100 coding challenges, grouped by topic. Free preview shows question titles - premium unlocks full content.
Algorithms · 77 MCQs
Browse all in Algorithms →Data Structures · 44 MCQs
Browse all in Data Structures →Behavioral · 63 MCQs
Browse all in Behavioral →Object-Oriented Design · 32 MCQs
Browse all in Object-Oriented Design →System Design · 68 MCQs
Browse all in System Design →Databases · 49 MCQs
Browse all in Databases →Algorithms - Coding challenges · 71 challenges
Browse all coding challenges →Data Structures - Coding challenges · 29 challenges
Browse all coding challenges →Practice in mock interview format
Behavioral and system design rounds reward practice with a live AI interviewer that probes follow-ups, not silent reading.
Start an AI mock interview →Frequently asked questions
What is Growth Mindset and why does it come up at SDE I?
Growth Mindset is Carol Dweck's framework: believing abilities develop through effort rather than being fixed. Satya Nadella made it Microsoft's core cultural value starting in 2014, and it's evaluated across every round - even at SDE I. The interviewer is looking for candidates who talk concretely about learning from mistakes, seeking feedback, and changing their approach based on new information. Have specific stories ready: a school project that failed and what you learned, an internship feedback you initially disagreed with but later applied, a time you changed your mind based on data.
How do I prepare STAR stories without industry experience?
Use school projects (especially group projects with disagreement and resolution), internships, hackathons, club leadership, side projects, even significant volunteer work. Pick 5-7 specific incidents and identify which behavioral themes each demonstrates. Practice telling each in 90 seconds: Situation, Task, Action (heavy on this), Result with metrics where you have them. Microsoft recruiters explicitly tell candidates that academic and personal projects are valid material at SDE I.
Is system design tested at Microsoft SDE I?
Usually not as a full round. Most SDE I loops include 2-3 coding rounds plus the as-app behavioral round. If a design conversation appears, it's bounded ('how would you build a basic chat service?') with the interviewer guiding actively. Knowing system design vocabulary (caching, load balancers, basic service architecture) is useful background but you won't be expected to drive a full design conversation.
What's the as-app round really evaluating?
'As-app' stands for 'as appropriate' - it's typically the hiring manager. This round is behavioral-first with role and team fit discussion. The hiring manager has significant influence on the offer decision even at SDE I. They're assessing: do you fit the team culture, do you demonstrate Growth Mindset, do your background and interests match what the team needs. Treat it as seriously as a coding round.
How does Microsoft SDE I compare to Google L3 or Amazon SDE I?
All three are entry-level new grad rungs. The technical bar is similar - Medium coding with edge cases and clean code. The cultural framing differs: Microsoft heavily weights Growth Mindset, Amazon heavily weights Leadership Principles, Google weights Googleyness. Microsoft's loop is the most predictable and often the most approachable; Amazon's is the most behavioral-intensive; Google's is the most variable based on team. Compensation is broadly comparable across the three.
How long is the Microsoft SDE I process?
Recruiter screen to onsite is typically 2-4 weeks - faster than Google or Amazon. After the onsite, decisions come in 1-2 weeks. Team matching can add 1-3 weeks. Plan for 6-10 weeks end to end. Microsoft also runs University hiring cycles (fall and spring) with slightly different timelines for new grad roles.