You will be working with some of the smartest people if you are in the right group here. You will have an opportunity to learn so much about software engineering.
Good facilities and perks.
Too big a company and too many re-orgs. It hampers an individual contributor's growth.
You will be learning Microsoft technologies a lot. These don't help if you look for opportunities outside Microsoft. You will basically be a person who knows only about Microsoft technologies and nothing about open-source technology stacks. A Microsoft engineer might not be that highly regarded in other big companies simply because of the technologies learned while in Microsoft.
Another issue is that you will be as good as your lead projects you in front of everyone else. So if your lead doesn't like you, you are screwed. This lead might not be the one who interviewed you and hired you because of a re-org. So basically, it is something like you interviewed for team A, but when you join, because of re-orgs, you end up working for team B and a totally different person who you did not meet during the interview time.
Another thing is SDET careers are not good at all. Anyone who joins as SDET is just wasting their career here.
Less re-orgs, please. Review the management.
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