Microsoft

• Pay and benefits are okay.
• The company isn't going to go belly-up anytime soon.
• There are some real "world-class" technical problems to solve.

• Pay and benefits are only okay for the size of the company.
• Work-life balance is highly dependent on your specific team.
• Technical problems also include working on legacy code that no one touches until they're forced to by some kind of policy review.

I see tons of examples that demonstrate the truism: "a measure ceases to be a good measurement when it becomes a goal."

KPIs like "no policy violations in code" become "push fixes/hacks and make the violations go away on the report."

Sometimes these types of issues are indications that there are gaps in processes, not that certain teams are just "bad" at their jobs.