Good pay and benefits. Good brand name. Ability to work on cutting-edge consumer products before they are released in the market.
Highly political work environment. After working for over a year, you will realize that brilliance alone won't get you to the next level.
Managers highly advocate the concept of independent work rather than teamwork. I've had one manager asking other team members to not help me in my work so that I start working independently (really ??).
Bad performance review system - Stack ranking is fine, but there is a concept of being visible across teams. Doing well and exceeding expectations in your team isn't enough. You need to be able to impress managers in other teams to get a better rating/promotions during annual performance calibrations.
Very high turnover (in this office specifically) - Mainly due to the internal politics and the review system. The other thing is management will make you work those extra hours when people leave or when other teams lose resources. But don't expect to get rewarded for working those extra hours. Those activities do not fall in the category of being visible across other teams.
Work/life balance - Management keeps discussing this every year during the MS Polls if the results are bad. I haven't seen any concrete steps in this direction, at least until I worked there.
Skill set development - If you are working as an SDET, it might be a bit difficult to develop skill sets which are marketable outside. Most of the tools/technologies used are internal to Microsoft and hardly any are used outside Microsoft, except C# / .NET.
Underskilled managers - MS needs to do some work on hiring good managers. Some of them are just there based on the amount of years spent in the company and may not be good at coaching ICs. If you get a good manager, you might be in luck and may have a better experience working here.
Put a new review system in place. Allow for easier movement across teams. Hire good managers. Teach them what teamwork is.
There were a total of 5 interviews. The first one was over the phone and was relatively simple. An Asian girl interviewed me for about half an hour and asked some basic questions, such as how I would test a keyboard and how to find the heavier of ni
Remember to prepare yourself on how to test random objects, like staplers and water balloons. Also, make sure you revise all that you learned in your data structures class. String manipulation is also very important. And Google to learn about brai
I had an on-campus interview at my university, where the interviewer focused on design issues and basic algorithmic questions. I can recall a couple of questions: how to determine if two circles intersect, and how a server should behave if it has to
There were a total of 5 interviews. The first one was over the phone and was relatively simple. An Asian girl interviewed me for about half an hour and asked some basic questions, such as how I would test a keyboard and how to find the heavier of ni
Remember to prepare yourself on how to test random objects, like staplers and water balloons. Also, make sure you revise all that you learned in your data structures class. String manipulation is also very important. And Google to learn about brai
I had an on-campus interview at my university, where the interviewer focused on design issues and basic algorithmic questions. I can recall a couple of questions: how to determine if two circles intersect, and how a server should behave if it has to