I submitted my resume at a campus career fair and got an on-campus interview. After two weeks, I received a notification from HR stating there would be an on-site interview in Redmond, WA. So, I flew to Seattle at the end of that month.
I had only three interviews over that time, so I knew I wouldn't have a chance to be selected. The first one went well, I think. We talked about some of my experience and why I wanted to become an SDET. The question was how to find differences in two arrays of integers.
The second interview was the start of my screw-up. I was asked to design a piggy bank for coins and write functions for a queue, like enqueue and dequeue. I didn't feel well during this time because I thought my interviewer was always staring at me with his poker face, which made me very nervous. I also failed to find a bug in my function during this interview.
In my last interview, I spent time with a very senior USB test software engineer. We talked about Microsoft's history and some of my project experience. I realized then that I was not that interested in testing at that moment. Afterward, we returned to his office, and he asked me a coding question.
Enqueue and Dequeue
How to find the differing parts of two arrays of integers.
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.