I talked to a recruiter who set me up for an in-person, one-on-one interview when Microsoft recruited on campus. It took about 45 minutes and was mostly chat, except for one programming question. I was told to expect email from a recruiter within three weeks, and sure enough, within three weeks, I was contacted by a scheduler for an onsite interview.
A day or two before the onsite, I was told which team I would be interviewing with. (I'm still rather unsatisfied with this part because I felt that I had no choice in the matter.)
The onsite started out with a briefing with yet another recruiter who told me what to expect. Then I went into four successive interviews, each with a technical and a people skills portion. At the end of the day, I met with the recruiter again to debrief. At that point, I knew better than to expect an offer because I knew I'd messed up several times early on in the interviews.
If you're collaborating with a member of another team, how would you resolve a conflict?
The following metrics were computed from 27 interview experiences for the Microsoft Software Developer role in Redmond, Washington.
Microsoft's interview process for their Software Developer roles in Redmond, Washington is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Microsoft's Software Developer interview process in Redmond, Washington.