Microsoft

You'll learn a lot, especially from the technical area. There are a lot of challenging tasks, and the level of expected quality is quite high.

They also really expect you to deliver by the deadline, so pressure is high, but it might push you above your limit. If you want to learn, there are a handful of resources and smart people to learn from.

Also, engineers get a lot of freedom in how they accomplish their goals; it's mostly delivering them that counts, not the path you select.

It’s mostly delivering that counts, so some people don't care that much about quality.

There doesn't seem to be a good mechanism for (technical) quality validation.

Again, this is a very large company, and things probably look different in other teams, especially in states where they do all the really important stuff.

There is also this weird culture, where people are mostly concerned about who will look bad on their year-end review and not taking any risks to help others if it might make them look bad.

Do something to make cross-team collaboration work better. Perhaps the review system should reward the best without necessarily throwing the worst to the wolves at the same time. Less bureaucracy, more power to the engineers.