Pros: As an intern, there were great benefits geared towards college students, which basically meant free stuff like mini fridges, shirts, Zunes, etc. As far as DevDiv (Developer Division) is concerned, I was very happy with how my team worked and treated interns. They did their best to help you learn, such as even sending interns to conferences, which I was quite surprised about. If I had to do it again, I would definitely accept the offer. What was really awesome was working on a project that would actually get released to millions of users, which is something that can't usually be said for most places. The random events that they host for interns is the best part. Make sure to go to as many as you can.
Cons:
Hide what it is really like to interns (which makes sense, but still...). Horror stories are heard about teams who treat their interns badly or give them projects that are basically useless. Also, they pressure you about taking an offer at the end of the internship (which you want to be paid $10,000 less is not a very good idea). Also prevalent is an email discussion list that was made to distract interns from doing work. Kind of backstabby in my opinion. Not very impressed with the idea. If they would fix a lot of these issues, it would be much better.
I would tell them to spread out from just the Redmond campus. Get some Seattle presence, etc.
Lots of brain puzzles and escalating interviews with different people on the team. Read the books on brain puzzles asked at MS interviews. They're not wrong. Most people interview with multiple teams. However, if all your interviews are with one te
The interview process was good. The interview was mainly based on coding. There were no specific testing questions. The interview covered: * A question on arrays. * A question on Linked Lists, specifically how to insert a node. * A question o
Initially, I was contacted by a recruiter. I had a quick phone screening and then was called for an onsite interview. The onsite interview was horrible because one of the interviewers was jumping randomly between questions. I believe the interviewer
Lots of brain puzzles and escalating interviews with different people on the team. Read the books on brain puzzles asked at MS interviews. They're not wrong. Most people interview with multiple teams. However, if all your interviews are with one te
The interview process was good. The interview was mainly based on coding. There were no specific testing questions. The interview covered: * A question on arrays. * A question on Linked Lists, specifically how to insert a node. * A question o
Initially, I was contacted by a recruiter. I had a quick phone screening and then was called for an onsite interview. The onsite interview was horrible because one of the interviewers was jumping randomly between questions. I believe the interviewer