There are two things about Microsoft that make it top-notch for software engineering.
The first is the focus on the business. This may seem counterintuitive, but the business focus is an excellent lens through which to look at software design and execution. I previously worked at a company which was arguably a better engineering company, but the lack of business focus led to software projects not having longevity and ultimately to the collapse of the company.
The second is the people. It's said that if you are a jazz musician and you're the best in your band, you need to change bands. There is very little danger of topping out at Microsoft. There are always excellent, skilled engineers to challenge you.
Microsoft leadership stalled for a decade or so, where more focus was paid to business rather than a balance of business and engineering.
The top echelons of compensation are epic. Competition is fierce, and winning is defined by profitability, which has led to thinning of the product herd to only the most obviously profitable (or necessary) investments.
Satya's leadership offers hope of changing this, but when you see references to Microsoft's environment being "toxic," this is the root cause, with the old stack-ranking system in a supporting role.
Work-life balance is clearly your problem. If you are ambitious and/or energetic, there is always benefit to trading work/life balance for work, but it can eat you alive.
Do not look for your organization to guard your own work/life balance; it's up to you (as it should be, but be cautioned).
Stop the focus on profit, even if it has negative ramifications on stock price. Use a lower stock price to reacquire ownership of the company in a stock buyback. The competition is growth and share focused, not profit focused.
Microsoft's infamous "interview loop" consists of three one-hour-ish interviews with current MSFT employees, followed by another interview with a general manager. The interview structure is nothing peculiar, featuring standard algorithm construction
I went on a site interview. The interviewers were nice, and the recruiter prepared me and calmed me for the upcoming interviews. I went through five interviews but did not get an offer. The interview questions ranged from algorithmic questions to des
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
Microsoft's infamous "interview loop" consists of three one-hour-ish interviews with current MSFT employees, followed by another interview with a general manager. The interview structure is nothing peculiar, featuring standard algorithm construction
I went on a site interview. The interviewers were nice, and the recruiter prepared me and calmed me for the upcoming interviews. I went through five interviews but did not get an offer. The interview questions ranged from algorithmic questions to des
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