A lot of things are taken care of so that developers can focus on coding. Program Managers handle requirement facing customers, talking to other teams, etc. Priority is given so that you can focus on programming and producing results.
For the technical/non-manager types: If you are patient, can deal with occasional politics at the office, and have potential to be a product architect, there is really room to grow here. I hear at other companies that there is a ceiling for technical types, but here there isn't. They have career stages set up all the way from Senior SDE, to Architect, Distinguished Engineer, to Technical Fellow. Of course, extremely few people amongst the talented employees of Microsoft make it to a level beyond Architect, but that path is there.
In general, if you are proactive, there is a lot of support you can get to learn how to grow and succeed at Microsoft, in the form of mentoring.
The review system is not fair. The leadership team makes decisions based on their impressions of a team member's contribution, whereas your manager and colleagues you work with on a project may know a lot better about your level of performance. Coupled with the brutal stack ranking system and rewarding the top 20% the most, this means that you will get really burned if you think all you need to do is churn out great code and work well with your teammates to release a good product. You need to actually spend time with the leadership team, letting everyone know what you are doing, so that you stay on the radar of the leadership team.
This also means that very driven, smart people end up focusing more on career growth rather than releasing a great product.
The company is very big, so a fair number of employees are bound to be quite mediocre. They really try to make sure that is not the case with developers, but you can always find some useless testers or test leads in every team.
Program Managers are not product-focused but spend more time and energy on pleasing the leadership with presentations.
Please, please focus on having a good product strategy and avoid having similar products and then canceling them after spending millions.
As other postings on this site have indicated, the standard hiring process for engineering roles typically involves one technical phone screen, followed by a full day of on-site interviews if the phone screen is successful. This was my second intervi
The regular interview cycle for MS includes: * One HR round for introductions. * A technical phone screening. * One full day of technical interviews (five in all). Technical interviews required whiteboard skills. In the phone screening, I was
Pretty typical of what else is on here, but with a different twist. I met with three engineers and then the final interviewer, which they called the "as appropriate." Other questions were around linked list traversal and working with arrays and index
As other postings on this site have indicated, the standard hiring process for engineering roles typically involves one technical phone screen, followed by a full day of on-site interviews if the phone screen is successful. This was my second intervi
The regular interview cycle for MS includes: * One HR round for introductions. * A technical phone screening. * One full day of technical interviews (five in all). Technical interviews required whiteboard skills. In the phone screening, I was
Pretty typical of what else is on here, but with a different twist. I met with three engineers and then the final interviewer, which they called the "as appropriate." Other questions were around linked list traversal and working with arrays and index