Microsoft

There are genuinely hard, interesting problems. As an architect, you get to work across large distributed systems where design decisions matter at a scale most companies never reach.

There are solid engineering resources. Compute, internal tooling, and Azure infrastructure are a real advantage when prototyping and validating architecture.

The shift in culture over the past several years is real. There is more collaboration, less internal politics than the old reputation suggests, and a growth-mindset framing that mostly holds up in practice.

There is a good work-life balance for a company of this size, and flexible/hybrid arrangements are respected on most teams.

Compensation is competitive, with stock and bonuses that become meaningful at senior and architect levels.

There is strong internal mobility, and it's realistic to move between orgs if your team isn't the right fit.

Scale cuts both ways. Getting alignment across teams and orgs can be slow, and architectural decisions sometimes get diluted by competing priorities.

Legacy systems and technical debt are unavoidable in places; not every project is greenfield.

Impact and visibility vary a lot by org and manager. Two architects can have very different experiences depending on where they land.

Promotion beyond a certain level is as much about influence and visibility as technical depth, which isn't for everyone.

Reorgs happen, and they can reset momentum on longer-term architecture work.

Protect long-horizon architecture work from short-term reorg churn, and give architects clearer decision-making authority rather than only an advisory role. Continue investing in reducing cross-org friction.