The process started with my campus recruiter re-sending an email about a potential phone interview. Turns out the first email had been sent straight to spam (bad Google! Folks, check your spam folder now and then).
I replied, and she set up a phone interview for me a few weeks later.
Phone Interview:
This was a morning phone call with some pretty standard questions. The Microsoft employee was fairly nice and wanted me to code the questions (I can't remember, but I'd guess they were string searches and character counting programs) and send them to his microsoft.com email address. A few days later, I got an email from my campus recruiter saying I did well and that she'd like to know some teams I might be interested in interviewing with.
Redmond:
On the morning of the interview, I met with my recruiter at the recruiting building 111. She handed me details of my first interview and what team I was interviewing for. What followed was the standard Microsoft interview loop: meet with a person, interview for an hour, then be asked to wait in the coffee lounge while the interviewer goes to talk to the next person.
After meeting three people, I was asked to meet their manager, and after that, his manager!
A few days later, I got an email saying that they would like to move ahead with an offer!
Nothing really out of the ordinary.
If you practice with "Cracking the Coding Interview" and similar books (practice with, mind you, not learn from), you should be golden.
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.