I found Microsoft to be a safe, supportive place to work. Everyone knows their job and sticks to it. People shouldn't take this for granted because in other places, sometimes even your job description and/or expectations are ambiguous. The benefits are great, especially free health care. I always felt like my managers and peers had my best interest and my career advancement in mind, right up alongside the team's success. I believe that MS is a company of integrity, one that supports great causes and supports the employee as far as possible.
There is always someone to learn from or some piece of technology to learn about right there in-house. So, learning and mentorship opportunities are both plentiful.
You can gain quite a bit of weight from the free drinks, affordable lunches, and frequent summer morale get-togethers. So, while all of the above is good, you need to take advantage of your ProClub pass.
The only other downside I can think of, and I am really struggling, is that you can easily get so comfortable at Microsoft that you never ever leave. I have felt like this and spoken with others who have to force themselves to see other career options/moves. It's hard to give up Microsoft's benefits and stable work environment, but having a diverse resume is also very important.
I would say to rethink Windows Live. Windows Live seems like a huge, barely used online portal that's trying too hard from the outside. From the inside, I know for a fact that Windows Live is an awesome family of groups with talented people. I want to see Windows Live become more integrated with other Microsoft properties.
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