First, I attended a job fair at my college, Arizona State University, where I handed my resume to Microsoft.
I was then called into the school career center for my first interview. I was so nervous, but I was able to answer the questions I was asked. Even though I didn't finish writing the code, the interviewer saw my thought process and agreed that, given the time, I could code the solution.
A few weeks later, I received an email to set a date for an in-person interview. I arrived in Seattle and went for my interview the next day. Upon arriving at Microsoft, I met some other candidates who were also interviewing that day. We all were in the receiving area, playing with the Surface, Xbox, Guitar Hero, and some other games.
I had applied for an internship but asked them right there to change it to a job. I was told that I might not get the best fit. Thinking back, I guess I should have stuck with the internship.
I met with three people that day, each interview lasting about an hour, except the third which was about an hour and a half due to lunch. I was asked some tough questions, and I was able to answer some really well, and others not so well. Overall, it was a good interviewing experience, but I was so drained at the end of the day.
Design a memory management system.
The following metrics were computed from 214 interview experiences for the Microsoft Software Development Engineer role in Redmond, Washington.
Microsoft's interview process for their Software Development 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 Development Engineer interview process in Redmond, Washington.