I received an email from a recruiter setting up a 45-minute phone interview with the hiring manager. The following week, I had an on-site interview at the Redmond location.
The first round of interviews went very smoothly. I was asked a number of basic computer science fundamental and data structure questions. I had to describe these concepts as if I were explaining them to someone non-technical. I believe the interviewer was looking to see if I could communicate my thoughts clearly. Then, I was given an algorithm problem.
The second round was with a senior engineer who focused more on my projects and how everything worked. We went into more depth regarding why I used specific frameworks and databases. Then, we discussed basic web security topics, and the interview concluded with another algorithm problem.
After lunch, I had a long interview with another senior engineer. This was more focused on my skills and knowledge of object-oriented programming. He provided a vague description of what I was supposed to design and expected me to talk through the entire process. The interview ended with a few data structure questions.
My last interview was with the hiring manager. We talked more about how teams are structured and how everyone works together. It wasn't too technical.
Overall, I had a great interview process. I didn't get the offer, but everyone was super nice and always willing to help.
Fibonacci, string compression, object-oriented design, etc...
The following metrics were computed from 207 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.