My resume was forwarded to this group through a friend. The recruiter got in touch to schedule a phone screen, and then scheduled an additional one.
The first phone screen focused on a string manipulation question, basic computer science, and object-oriented concepts (such as threading basics and polymorphism). It also covered my work experience.
The second phone screen focused more on my understanding of memory allocation. I had to identify challenges and errors on a given custom memory allocator. Another question involved an array of integers.
I was called onsite a week later for five rounds of interviews.
Questions were based on a mix of understanding computer science concepts—like multi-threading, client-server behavior, HTTP basics, and scalability—along with algorithms, coding, and testing ability.
Some of the coding-related questions included:
I received the offer a week later and accepted it.
The lunch interview discussed a bit about my work. The rest of the interview, as mentioned above under the interview process.
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.