The interview process began with a 30-minute college technical screen, which included a programming problem, test cases for it, and some basic behavioral questions. This was followed by five one-hour rounds in Redmond.
The first two rounds were with individual contributors, and the last three were with managers of increasing seniority.
Most rounds followed a format of solving one or two problems on the board and then writing test cases for them. The exception was the last round with a senior manager, who also engaged in a non-technical conversation to determine my fit with the company.
Occasionally, there was enough time left to discuss some of my projects or interests. This was particularly appropriate during the lunch interview.
Overall, it was a very pleasant interview experience, which I had expected from Microsoft based on reading other reviews.
I did not get any particularly challenging algorithms/data structures questions, but one problem had a constant-time solution that was not immediately obvious.
So, before jumping in, think whether there could be a trick that trivializes the problem.
The following metrics were computed from 128 interview experiences for the Microsoft Software Development Engineer In Test (SDET) role in Redmond, Washington.
Microsoft's interview process for their Software Development Engineer In Test (SDET) 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 Development Engineer In Test (SDET) interview process in Redmond, Washington.