Online Numerical test: Not difficult, but I did lots of tests from assessmentday.co.uk beforehand. Video Interview: pre-recorded questions. The questions were quite unusual, many people fail at this stage. I was expecting to fail as well, but I guess I wasn't as bad as thought. Make sure you know about cloud, windows features, etc. Competency questions about when you helped others, how you discover issues, how you'd prepare if you had to change jobs in less than 3 days, when you analysed data to discover an issue. To prepare, make sure you have lots of examples prepared of any skill they could throw at you. Skype interview: Typical competency questions (where do you see yourself in 5 years, etc), test knowledge of Microsoft products, your passion for working at Microsoft (Why Microsoft? why this internship?). The purpose of the interview is to work out what you are passionate about, and based on that they will try to assign you to a role suitable for you. For example, I mentioned that I was quite passionate about the program manager role, and the guys for HR really helped me get it. It's very important to know what you would like to do in your role, and what products you would like to work on and communicate that during the interview, but try to be flexible at the same time. Technical Phone Interview: Not difficult, but make sure you know about Agile (know about user stories, user features, etc.), User-Centered Design (know about Scenarios, Personas, thinks you'd learn in HCI modules), they asked me about a piece of technology I am passionate about and how I'd improve it. Also, some brain teasers such as convert 20 to hex (I actually messed up that question, but they were fine with it, most important try to explain how you'd go about solving it), how many numbers can be represented in 4 bits. They also had a number of role specific questions, to test your understanding of the role. For every question be prepared for follow-up questions. Assessment Centre: 2 parts, competency and technical. The competency interview will include the exact same questions from the video interview, only more. The technical interview will test your basic programming skills (code to reverse a string, palindromes etc.). Its quite easy, but I suggest doing some mock white-board interviews with a friend, rehearse debugging on the white-board, explaining your code before you write it, etc. To prepare, checkout first exercises from careercup book. For PM role, good communication skills while you write the code are very important. For program managers, the technical interview also includes a creativity exercise (e.g. design a remote, design an alarm clock for blind), make sure you ask questions to identify requirements, prioritise requirements. At the end you they will ask you if you think your design is good, and this is where I could have done better - I wasn't very confident in my design. Telephone Interview with your prospective manager (optional): If you have the assessment centre with a different team to the one you'll be working with, you might need to go through a telephone interview with your prospective manager. I wound't call it an interview, more like a chat where the manager is trying to get familiar with your technical experience, your knowledge of programming languages and other computer science related concepts. Other tips: - Make sure you're nice to HR, they have quite a lot of say in the interview process, and they are very helpful. - If you don't hear from them in a while, it's worth writing them an email, but don't be annoying - don't write too many emails. They will read it, but probably you won't get a reply via email. Still, it serves as a reminder that you're still interested. I did that, and got scheduled for an interview a week later. - Apply to other places, the interview process is very long, so it's best to have a back-up plan if things don't work out