each team is essentially autonomous, and they pick the tools they wish to use.
yes, there is lots of paperwork, e.g. getting anything deployed requires multiple people from across the firm to agree, but it's mostly automated and doesn't take more a few hours of background time, and it's understandable: the amount of money the firm would lose if something went drastically wrong is eye boggling.
the problems are challenging and interesting, I get to experiment with extremely high end equipment that isn't available for general purchase, and the hours are good (as is the pay).
(though I admit there are parts of the organisation that don't have this freedom: you have to be careful when interviewing)
This will lead to a maintenance problem shortly. I worked in similar environments. Technically clueless managers think that they only have to throw requirements over the wall and let the developers figure out how to implement them. When someone leaves the team the replacement needs to become acquainted with totally unfamiliar code, libraries and tools.