Applied online. The recruiter reached out in a couple of weeks for a basic introduction covering projects, "why Microsoft?", and role expectations.
Next was an online coding assessment on Codility. It consisted of 3-4 questions on strings, arrays, and recursion, typical LeetCode-style problems.
Then, a technical phone screen with an engineer (45 minutes) covered data structures, OOP, DBMS, and a live coding exercise. The thought process seemed important, and the interviewer provided helpful hints.
The Super Day (onsite) had 4 rounds: 3 technical and 1 HR, each lasting 45 minutes. Technical rounds covered OS, networks, data structures, OOP, algorithms, system design, and project discussions. Coding questions involved arrays, trees, DP, debugging, and recursion. Examples included implementing Tic-Tac-Toe and writing code to check if a Sudoku is valid. The HR round focused on behavioral questions, such as challenging projects and crisis handling, without deep dives.
Recommendations: Use the STARR framework. Prepare using LeetCode. Conduct mock interviews on Prepfully (with an ex-Microsoft coach), Reddit, Blind, and Glassdoor to understand the experience.
Check whether a given string is a pangram.
The following metrics were computed from 187 interview experiences for the Microsoft Software Engineer role in Redmond, Washington.
Microsoft's interview process for their Software Engineer roles in Redmond, Washington is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Microsoft's Software Engineer interview process in Redmond, Washington.