Company really invests in you! The quantity and quality of courses available really allow anyone to grow and improve their understanding.
Lots of people who help you succeed! I was lucky to have an amazing mentor and a fantastic manager.
If you get bored with one problem, you can always move on to something else that is equally interesting. Microsoft really offers a wide variety of problems to work on (from games to enterprise software to search to mobile phones to operating systems to...).
People are really competitive here. If you are in a team of more senior people, then you don't have to worry much. However, if you are in a team with more junior people (i.e., ones who are closer to your level), then it can get messy really quick, as everyone is trying to prove how their contributions matter the most.
Frequent reorgs and changes in strategy. If you are one of those people who can switch directions fast, then you can thrive over here. However, if you are one of those people who get really attached to your work, then the reorgs will take a toll on you.
Due to the organization hierarchy, there are more people at the grass roots level who know what direction the company really should be moving in. Provide easier and more accessible channels for them to lead the company in those directions. It doesn't make sense to ignore them and then, after a few months, move in that direction because another competitor has implemented that concept into a working product.
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