I gave my resume to a recruiter at my school. A week later, in the evening, I received an email and a phone call stating I had an interview on my college campus. I had to accept within the hour, and the interview was scheduled for 9 AM the following morning.
I attended the interview, where we mostly discussed my experience and a conceptual tech question.
A couple of weeks later, I was invited to go to Redmond. Unfortunately, I had to reschedule due to midterms.
I was assigned a new scheduler, and it took him a month to fit me into the "perfect interview experience" after I had to keep reminding him via email. Finally, I flew out to Redmond, which was awesome since it was completely free.
At 9 PM the night before the interview, I still didn't know what team I was interviewing for or what time I was meeting with my recruiter. Apparently, the email with all that information was never sent to me.
I figured all that out and learned right before the interviews that I was interviewing with a team whose product I had never used. During the interviews, they didn't seem to like that my experience was focused on programming or interfacing with devices. This wasn't my fault, as HR should have scheduled me with a team better suited for my resume.
They said I would receive my decision within a week. Surprise, surprise – over a week went by, and I had to remind the recruiter to deliver the bad news.
Print all permutations of a string
The following metrics were computed from 33 interview experiences for the Microsoft SWE role in United States.
Microsoft's interview process for their SWE roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Microsoft's SWE interview process in United States.