There just is no other company like this in the world. You have the ability to do truly global, groundbreaking development work that will be deployed by thousands or millions of customers and make their daily lives better or different.
Also, the internal atmosphere in Microsoft Redmond is just incredible. You have the best of the best working with you. The atmosphere is relaxed, you do things and influence people based on what you know (not your title or who you know). Information is shared liberally and you are part of an incredible team.
However, there is no bitter fighting or competition amongst peers, so I don't know what else to ask for. The environment is also very international and diverse, so you get to see how people around the world think. It's a very productive environment where you are pushed to do your very best and rewarded for it accordingly.
Opportunities for remote work are slim for SDEs and SDETs. Almost all of the product development happens in Redmond, and if you can't live there, you're out of it. (If you want to know why I no longer work at MS, this is the reason: I had to move out of the country for family reasons and did not find a way to continue my work with product teams and did not want to go back to the field.)
Also, you need to be a person that can manage your own time. If you don't, you will get exhausted and be overworked. However, if you can manage that, you will be fine with 40-45 hour weeks in reasonable pressure.
From what I have heard, teams can vary very much and (like in any large org) if you land under a poor manager, you are in trouble.
Also, the MS field organization is a very different place, and anything I say here does not apply for any of the subsidiaries (had some bad experience there).
Keep up the good work. There are issues both within the company and external to it, related to e.g. HR strategy, business strategy in general, etc. For the most part, I haven't seen as good senior leadership in a company this size, especially one going through so many cycles. It is easy to think you have a dream team managing any small startup as long as things grow, but wait until the first problems come, and most of those "dream teams" are very bad. Microsoft does not have that problem; the senior management has been through a lot of cycles already.
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