Microsoft Software Engineer Interviews: Questions to Practise
A preparation guide based on Microsoft's current official advice, with original coding, testing, design and behavioural exercises.
For a Microsoft software engineer interview, use the recruiter instructions for your role and Microsoft's official technical-interview guide. Checked on 21 November 2026, that guide describes problem solving, design, coding and testing, with technical areas depending on the role.
Source: Microsoft Careers technical interviewing
This is a current preparation guide, not a list of leaked or verified recently asked questions. Every exercise below is our own practice prompt. There is no public evidence here establishing which questions are most frequent, and your role's format may differ.
What Microsoft's guidance means for your practice
Practise clarifying an ambiguous problem, explaining a plan and writing runnable code in a language you know well. Include tests before declaring the solution finished. Prepare to discuss tradeoffs and the complexity of your approach. Use your interview invitation to prioritise the relevant topics.
1. Find a duplicate event without losing useful order
Practice prompt: given a sequence of event IDs, return the first ID encountered for a second time. Ask what to return if there is none, whether IDs can be empty and whether the input fits in memory. Explain a set-based approach, its expected time and space costs, and an alternative if extra memory is constrained.
2. Merge overlapping intervals
Practice prompt: combine overlapping meeting intervals. Clarify whether touching endpoints count as an overlap. Describe sorting and maintaining the current interval, then test empty input, nested intervals, identical starts and separate intervals. State your sort cost and storage assumptions.
3. Debug a function that passes the happy path
Take either exercise and deliberately introduce an edge-case bug. Describe how a small test exposes it, what invariant was violated and how you would avoid the same mistake. The point is to demonstrate verification, rather than claiming that a few passing examples prove all inputs work.
4. Design a notification service
Practice prompt: a product must notify users when a background task finishes. First ask about users, delivery channels, latency, expected load and privacy. Sketch the task event, queue, delivery worker and status store. Discuss duplicate events, retry limits and what happens when a provider is unavailable. Choose a level of detail appropriate to the role.
5. Explain a difficult engineering decision
Choose a real project. What options did you compare? What constraint mattered? What did you implement yourself? What failed or surprised you, and what did you change? If you have no production experience, use a course or personal project and describe its actual scope.
6. Respond to a disagreement in a code review
Explain how you would restate the concern, compare the alternatives with a test or clear criterion, and document the decision. Use a real example if you have one. Do not invent a Microsoft incident or present someone else's experience as your own.
A focused preparation plan
- 1Read the vacancy and recruiter instructions, and list the skills they name.
- 2Solve a small coding exercise aloud, with clarifying questions and complexity analysis.
- 3Test it with boundaries, invalid inputs where relevant and a case that breaks a naive solution.
- 4Discuss one design and one real project decision.
- 5Ask your recruiter about any format or tooling detail the invitation leaves unclear.
More coding practice for early-career roles
Frequently asked questions
Are these the latest actual Microsoft interview questions?
No. These are original practice exercises informed by Microsoft's official preparation guidance, checked on 21 November 2026. They are not a verified question bank or a promise about your interview.
Should I prepare system design for Microsoft?
Prepare for the responsibilities and level of your specific role. Microsoft's official technical guide includes design; ask your recruiter which areas and format apply to your interview.
Which coding language should I use?
Microsoft's guidance recommends coding in a language you are strong in. Confirm any specific constraints in your interview instructions and practise running and testing code in advance.