
Software Engineer II Interview Experience
Interview process
The process was quick with all interview rounds initially scheduled in the same week. The technical interviews were adapted to real world code implementations and didn't directly relate to Leetcode style problems. The system design round was very open-ended with no definite question and highly ambiguous requirements.
- Recruiter screen
- Technical interview
- Final round
Interview rounds
10 questions across 3 roundsRecruiter screen
2 questionsQuestion types asked
Specific questions asked
What timeline do you have in the interview process?
Technical interview
5 questionsQuestion types asked
Specific questions asked
What data structure would you use for a write heavy system that does not need to look up data too much.
What data structure would you use with additional requirements of finding the smallest and largest values of elements in the data so far?
How would you create a system to run A/B tests - to run a test on 10% of random users?
If you're developing a file storage system - upload and get files APIs - how would you do the design?
Code review with high focus on security bugs.
Final round
3 questionsQuestion types asked
Specific questions asked
Implement a method to crawl webpages given a utility function that reads HTTP/HTTPS web pages.
Design a system that receives notifications from multiple producer services, processes them and then publishes notifications to downstream users.
Interview tips
Would have helped to know more about the system design round and the general expectations of interviewer's for this round.
Company culture
Overall felt pretty good with the interview process. The team adapted the interview process as SDEs spend less time on writing code and use more AI tools in their workflows.
Get full access with a membership, or share your experience to try it free.
More Microsoft interview experiences

“In my binary tree round, I was not even leaning on BFS or DFS terminology, and they still liked my solution because I kept reasoning it out. That was the moment where Microsoft felt more about logical thinking than memorized interview patterns.”

“It was basically graphs in the OA, then two back-to-back coding rounds where I didn't even run my code, just walked through an interval merge problem and a first-occurrence string question.”
See all 27 Microsoft Software Engineer interview experiences →