Getting an Interview
Getting an Interview
Interviews for Top Jobs at Microsoft
- Software Development Engineer (713)
- Software Development Engineer In Test (SDET) (493)
- Program Manager (321)
- Intern (245)
- Software Developer (119)
- Software Development Engineer Intern (67)
- Software Engineer (66)
- Software Development Engineer In Test (SDET) II (57)
- Software Development Engineer II (53)
- Technical Account Manager (46)
- Program Manager Intern (44)
- Senior Program Manager (42)
- Project Manager (41)
- Associate Consultant (39)
- Senior Software Development Engineer (38)
- Product Manager (37)
- Product Advisor (32)
- Hardware Engineer (29)
- Account Manager (26)
- Marketing Manager (25)
- Software Development Engineer I (25)
- Technical Support Engineer (23)
- Engineering (20)
- Sales (20)
- Software Engineer II (19)
- Support Engineer (19)
- Program Manager II (18)
- Marketing (18)
- Software Development Engineer In Test (18)
- Premier Field Engineer (18)
Network Engineer Interview
The process took 1 day – interviewed at Microsoft (Redmond, WA) in February 2012.
Process was pretty straight forward. The team I interviewed with was in the games division. First interview was with teh manager. He asked a couple light technical questions, which I did well on. He handed me off to the next guy who was very technically savvy. I choked, and he was less than tactful. The point of this review: Be prepared. I wasn't and was quickly exposed. Prepare to answer high-level questions and the be prepared to whiteboard and answer some deeper questions. Prepare!
- Given a very large existing network with thousands of external connections, how would you add an additional few hundred connections? 2 Answers
Other Interview Reviews for Microsoft
Network Engineer InterviewNo OfferNeutral ExperienceEasy Interview
The process took 1 day – interviewed at Microsoft (Redmond, WA) in June 2011.
Got an email from Contracting recruiter about the Network Engineer position. Next week later, I got a P2P interview at Redmond. It was pleasant; arrived early so I can walk around. Finally, met with he interviewer - cool guy.
Told him about my limited dev. and testing skills from the Get-Go, more involved in Cisco IOS CLI and network configuration.
Asked me very, easy questions like - if my VOIP call dropped, what happened? how to backup running-config's on router? how would you troubleshoot a router if ICMP is turned off.
About the last question: who would be stupid enough to turn ICMP off? After he said that, I already knew the Interview was a waste of time and probably the Interview was to only make it seem like he was "busy."
Network Engineer InterviewNo OfferPositive ExperienceAverage Interview
I applied through a recruiter. The process took 1 day – interviewed at Microsoft (Redmond, WA) in October 2010.
Microsoft's network engineering team does a fast, efficient, day long (five hours) team interview. You may well meet three other candidates there for the same round of interviews in a different order. In my case, the people I interviewed with asked a variety of intelligent questions - it was a good technical interview without any of the legendary MS questions. Watch yourself at lunch. On the whole, expect a thorough interview about networking with intelligent people and leave the rest for the fit.
- explain the ospf adjacency process. Answer Question
Network Engineer InterviewNo OfferPositive ExperienceDifficult Interview
I applied through college or university. The process took 2 weeks – interviewed at Microsoft (Dallas, TX) in February 2009.
I was interviewed on college campus and then they invited me for a office visit where I got a technical interview, then met the manager for the final interview. Be ready for trouble shooting questions and answer following the question: If Bill Gates is sitting across this table, why would he hire you?
- How would you deal with an agry customer? Answer Question