I applied through college or university and the process took 4+ weeks - interviewed at Microsoft in November 2013.
Interview Details – The whole process was very smooth. I first had a 30 min interview on campus. Two technical questions: reversing a linked list and least common ancestor in a binary tree. Then flown to Redmond for onsite interview. I got four interviews, each for 45 min. They all asked sorting and string manipulation questions. They also ask to come up with all test cases after you write your code.
Interview Question –
There was no difficult or unexpected questions.
-sort an array with just two types of elements, optimize your algorithm
-find common letters in two strings and put them in a sorted order
-compare sorting algorithms Answer Question
Negotiation Details – No negotiation
I applied through college or university and the process took 3 months - interviewed at Microsoft.
Interview Details –
On-campus interview: reverse a number e.g. 12345 -> 54321 (just use arithmetic and a loop), talk about your projects
3 back to back on-site interviews: print out a BST in-order, partition an array of integers with odd integers to the left and even integers to the right, create a queue data structure with 2 stacks
Phone interview with a higher-up manager: the pirate game (see wikipedia entry)
Hiring process took a bit longer than expected, otherwise things went smoothly.
Interview Question – Implement an online LRU cache to keep track of browser history (not worded in that way, but after the interview, I realized this was effectively what they were asking) e.g. keep track of the 5 most recently seen items without duplicates. View Answer
I applied through college or university and the process took 6 weeks - interviewed at Microsoft in November 2013.
Interview Details – Have a friend who works for Microsoft. He came to my campus as a campus recruiter, so I submitted my resume to him. Had a phone interview later that week. Heard back that they wanted me to fly out to Seattle a week or two later. Flew out, and had a great trip. 4 interviews, 45 minutes long, focusing on problem-solving skills, coding skills, and comfort with Java and C++. Heard back the next day that I got the offer. Since then, Microsoft has been great throughout the whole process. I'm excited to intern there Summer 2014!
Interview Question – There was a question about delimiters that was tough. View Answer
Negotiation Details – I was blown away by the offer, honestly. I couldn't bring myself to negotiate haha.
I applied through an employee referral and the process took 4 weeks - interviewed at Microsoft in November 2013.
Interview Details – Internal Employee Referral - Phone Screen with HR, Phone Screen with Hiring Manager, and then onsite "Loop" process. Process was smooth and it was a very enjoyable set of conversations with very smart folks about fit for the role and future job/career desires.
Interview Question – If I spoke to coworkers of you over the years, what are the 3 things they would say are positives, and the 3 things they would say are negatives of you? Answer Question
Negotiation Details – Was able to negotiate stock award, salary was above expectations and at the top of the range, so I did not negotiate that.
I applied through college or university and the process took 2 months - interviewed at Microsoft in December 2013.
Interview Details –
I had my on-campus interview at the end of October. The process was relatively smooth and they kept in contact throughout the process. About 2-3 weeks after that, they told me I made it to the final round. Due to scheduling conflicts, class projects, Thanksgiving etc. I only scheduled my on-site interview for the beginning of December. I had my on-site interview on a Monday, the recruiter called me that Wednesday with an offer. I had 5 interviews during my onsite - 3 were pre-scheduled and 2 additional interviews were tacked on as the day progressed. I would say you have better chances if you had 5 interviews, my 5th interviewer was my 1st interviewer's boss - so I knew it was a good sign.
Don't be discouraged by answering things correctly or needing to have to do a lot of technical things on the spot. Since I myself am a UX/UI designer, they mainly drilled me on design challenges and when I had my more technical interview - I was able to show some of my past projects and code. Not all PM's are super technical, I spoke to other PM candidates and everyone had a really unique background and major - seemed like there was no cookie cut for what a PM has done in the past or what track they are on.
Also, you go to lunch with one of your interviewers, don't mistake that for chit chat - and be strategic about what you get to eat - it is hard to discuss your background while eating pizza for example.
Interview Question – Design a vending machine for an airport. What challenges or considerations are there? View Answer
Negotiation Details – No negotiation, the recruiter said there was no negotiation on the offer, which is understandable as a college hire and I had no other offers that were more than what they were willing to give. It was very competitive and I was pleasantly surprised.
I applied through college or university and the process took 4+ weeks - interviewed at Microsoft.
Interview Details – Coding questions are not difficult at all.
Interview Question – The most difficult question is a brain teaser. Answer Question
Negotiation Details – Not negotiable
I applied through college or university and the process took 2 weeks - interviewed at Microsoft in February 2013.
Interview Details –
Total 6 round of interviews
1. College Round Interview - same as SDE/SDET/PM questions
2. Phone Interview - more behavioral and cultural questions
Final Round interviews
3. Interviewer 1 - Explain programming projects that I have done in school, Basic questions on data structures, scripting etc.
4. Lunch Interview - resume walkthrough, about microsoft, and microsoft products
5. Interviewer 3 - Networking related question, Questions on TCP/IP, OSI model and a case/scenario based question
6. Interviewer 4 - Troubleshooting questions, How would you fix a router type of questions, Database questions
Interview Question – Service Engineer roles at Microsoft varies so much. SE is a broad discipline. So it is essential to have knowledge on fundamental data structures, scripting, networking, and databases. Questions were tricky but they were interested in knowing your thought process more than wrong/right answer. Answer Question
Negotiation Details – No need to for negotiation. I heard they pay the most in industry for this role. Similar roles are Service engineers at yahoo, and site reliability engineers are Google, facebook, linkedin.
Very Difficult Interview
I applied through college or university and the process took 4+ weeks - interviewed at Microsoft in December 2013.
Interview Details –
On-campus interview, Redmond interview. Hiring process felt disorganized - I interviewed with Enterprise and Cloud after I had expressed interest in different areas.
Interviewed with a director and engineering manager. Sense was engineering focused culture. Very 'big company' feel.
How would you test a pen?
Implement atoi in C++. Now test it.
You have a balance, 9 balls, one weighs less, find the smallest ball in fewest steps.
Feedback: finish working through the problem and finding the algorithm before starting to write code.
Interview Question – Search a string to see if it contains a given substring. The given substring can have a '*' - a wild card character which corresponds to skipping one or more characters in the string being searched. Asked qualifiers: Can there be a wildcard character in the string being searched? [yes] ascii? [unicode] Answer Question
I applied online - interviewed at Microsoft in December 2013.
Interview Details – One none technical phone interview from a recruiter. Four rounds of interviews for onsite. Three people are grouped together interviewing with the same 4 interviewers. The questions are easy. My friend told me they ask easy questions to make you feel good for interviews if they don't want you. But one interviewer told me that they try to ask questions with same difficulty to make comparisons. They don't provided feedback to you anyway.
Interview Question – I think all the questions are not hard. Answer Question
I applied through a recruiter and the process took 2+ weeks - interviewed at Microsoft in May 2009.
Interview Details – 9 interviews in one day. they forgot to get me lunch. pretty weird in some ways. Interviews got better as I progressed. First interviews were very confrontational I thought (maybe because I was coming from 'the Valley'. Two people asked me some of the famous questions (why are manholes round), and I was like 'are you kidding me?' Later interviews focused more on business and relevance of my previous experiences.
Interview Question – I was asked how many french fries McDonalds produces in a day. View Answer
Negotiation Details – It was ok. The recruiter was actually really good. I negotiated most on my relocation package, and I felt like I was successful. One thing nobody tells you about Microsoft is that they have these very arcane levels and corresponding pay/perks, including the magical 'partner' level. I learned all of that after I came to Microsoft.
What do you want in a job? Do you want more than a paycheck? At Microsoft, you can discover potential you didn’t know you had, push your limits, turn your ideas into reality and make a real impact on the industry and… — Full Overview
Provided by employer [?]
This is the employer's chance to tell you why you should work for them. The information provided is from their perspective.
Your feedback has been sent to the team and we'll look into it.
The difficulty rating is the average interview difficulty rating across all interview candidates.
The interview experience is the percentage of all interview candidates that said their interview experience was positive, neutral, or negative.
Your response will be removed from the review – this cannot be undone.
Simply post an anonymous review for a recent interview experience or current/former employer. Your post is anonymous – and if you're worried someone will be able to identify your review, you can even post without telling us your job title and location. Learn More.
No thanks –