Smart people; I love my team. The culture seems to be improving, but you have to be careful who you work with. I've had positive roles where I had a lot of autonomy and was well-rewarded, and dead-end-ish work that only yields frustration and poor reviews. The best I can say is that most engineering work is really positioning yourself so that you can do well and avoid toxic situations.
The company does seem to recognize that big tech companies grind people down, and it tries to dilute the politics with one-on-one's, annual reviews, sabbaticals, etc., although most feel it is only partially successful. However, I'd rate it as better than most. They also emphasize diversity, ethics, and good business practices internally.
Some groups and products are doing well and getting better.
Low autonomy and creativity. Microsoft actually missed out on a patent from me because they gave me no support for the work.
Typical big-company tendencies such as fads, not-invented-here, and blame-shifting.
Some tools have been described (in anonymous internal polls) as at least 5 years behind. It's painful to sit and watch sometimes, actually all the time.
Dogfooding instead of using the best technology. "Nobody else is using it at this scale" -- Azure support for a tool that replaced something much cheaper and higher-functioning.
Don't make technical decisions.
The recruiter reached out to me, and I scheduled a phone screen. The technical phone round was not great. I struggled to come up with a clean solution. The next day, the recruiter emailed me and said that there is another team who is interested in my
Typical FAANG interview. 4 parts, each with 1 technical question and 1 behavioral question. 1 system design question, 3 coding questions that target different things: * Requirement definition * Trade-offs in solution * A problem where the challenge
Based on the recruiter's email, I was expecting the conversation to include questions around my C++ coding skills and prior experience relevant to the role, and LeetCode-style coding in C++. However, the discussion only focused on the hiring manager
The recruiter reached out to me, and I scheduled a phone screen. The technical phone round was not great. I struggled to come up with a clean solution. The next day, the recruiter emailed me and said that there is another team who is interested in my
Typical FAANG interview. 4 parts, each with 1 technical question and 1 behavioral question. 1 system design question, 3 coding questions that target different things: * Requirement definition * Trade-offs in solution * A problem where the challenge
Based on the recruiter's email, I was expecting the conversation to include questions around my C++ coding skills and prior experience relevant to the role, and LeetCode-style coding in C++. However, the discussion only focused on the hiring manager