My experience with the interview process began with an on-campus interview at my university. Two weeks later I heard back that I had been given a fly-out. The Microsoft fly out process is extremely unique, and it's clear that they are very interested in you as a candidate based on how well you are compensated during your fly-out. You're given a rental car, a $75/day food budget, an access pass to the employee discount page, and a really nice hoodie (With thumb holes!). As far as the interviews go, I was very impressed with the people I ended up meeting. When you arrive at the office they put you in a room with a lot of other interview candidates, and you are left to mingle for a half-hour or so. Talking with the people there will really give you an idea of the type of person they are looking for; everyone was super smart and sociable. A lot of the intern group ended up going out to dinner later that evening and we all had a group chat going, which I would consider pretty unheard of compared to my other interview experiences. This atmosphere translated over to my interviewers, and I had a very enjoyable experience simply conversing with them. Having compared my interviews with the other candidates, it is really hard for me to suggest what your interviews are going to end up like. Some of the candidates received difficult technical questions, and some, such as myself, received little to none. My suspicion is that the technical questions you get are based on your resume; I have a lot of previous systems design experience, and so I received a lot of systems design and object oriented questions. Conversely, some of the less experienced interns received more algorithms questions. Obviously my sample size isn't that great though. I also received a LOT of behavioral questions. It's no question that the primary purpose of the fly-out, at least for me, was to evaluate whether I would fit into the Microsoft culture. This is probably an important fact to keep in mind, so make sure that you know why you fit into Microsoft before you approach these interviews. You'll find a lot of interviewers provide positive reenforcement when you are talking, so it really helps to open you up to talking about the projects you participated in as well as the mistakes you made and questions you have. All of these awesome experiences in mind, I'm afraid to say I'm a little biased against the process I went through. This is likely due to the fact that I didn't get the offer, but also partially because of my experience afterwords. It's important for you to keep in mind that the actual goal of these interviews is to evaluate yourself; nothing more. In other words, don't expect to be able to solicit any feedback from your interviewers after the process if you don't get the offer. This normally wouldn't be an issue for me, as this isn't really something that you should expect from most interviews. However, for the amount of money and time they spend on you before your interviews, it is very surprising to me that I did not get any responses to my requests for feedback. This whole interview process was a big detriment on my class performance due to the amount of time I had to dedicate, and unfortunately it is an unsaid requirement that you need to do the fly-out if you really want to be considered. So, if you do choose to do the fly-out, which I still think you should, just know that this whole process will be all-or-nothing save for your own self-reflections post-interview. I would keep this fact in mind mainly if you have any competing offers that you would seriously consider over Microsoft. The above, rather nit-picky complaint aside I really enjoyed the interview, and would highly recommend taking a look at the Microsoft interview process. I definitely learned a lot about myself during the whole thing, and I do think that it has improved my perspective for the future. Good luck!