I applied through a campus recruiter, passed a phone interview, and then took a trip to Redmond for an all-day interview. While the people I met seemed nice, the company as a whole rubbed me the wrong way. The phone interview did not feel very welcoming, and after talking to various employees during the on-site interview, I got the feeling that Microsoft was a bit too paranoid.
Developers only got to see fragments of a system at a time (in this case, Windows 8 during its development), and annual performance reviews ensured that, no matter what, a percentage of the lowest performing engineers would be laid off. This was true even if those lowest performing engineers were in fact well above average compared to those at other companies.
None of the interviewers seemed happy with where they were, and they gave off a vibe that conducting an interview was almost not worth their time. The overall environment felt a bit too competitive and hostile for my taste.
I ended up goofing on the on-site interview itself due to nervousness and being intimidated. It was not until a few days after that I realized those emotions were red flags.
These are pretty standard questions. The first interview is designed to be easy (e.g., Fibonacci sequence). Throughout the day, questions will get more complicated, mostly involving one or more data structures.
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.