I've worked at a consulting firm as a dev where we used React for our all of our projects. Given the nature of the industry, we had a fairly high turnover rate with new devs constantly onboarding and older devs moving out. That, coupled with lack of engineering culture, resulted in our project architecture unfolding into what felt like a variety of different brain dumps in a codebase that was difficult to reason with.

It's my opinion that Angular would have safeguarded those projects from a scattered architecture with its opinionated framework, and ultimately resulted in less overhead associated with onboarding new resources and getting them up to speed.

The types of companies you listed aren't necessarily known as being engineering focused, and for a React project to really scale, I think that you need a good engineering culture to make that happen. Choosing Angular alleviates some of that work, and that's exactly what some companies need.

It’s extremely popular with C# and .Net developers. They’re more likely to work at those places.

Angular, to me, feels like it was designed by Java developers - classes and bloat* everywhere. Most code, when compared to a React etc. version, just seems like a wall of text on my screen. But, this might make it more approachable to developers that come from a Java background - I see this at my current employer.

(*) By bloat I mean that I often feel like I should have been able to implement whatever feature I just implemented in half the amount of code.

I've worked at a shop largely split between .Net and Angular, so I can anecdotally confirm this. It makes a lot of sense given the enterprisey background.