I'm working on automotive safety-critical security-critical stuff. There is structure and bureaucracy around this stuff.

For example, a project gets a safety managers assigned who has to sign off the release. Project management is explicitly not superior to this safety manager. In most cases these safety managers are just there review stuff according to some process guidelines. If there is pressure (project is late, etc), there are more senior safety managers to call in and they will usually make more nuanced safety arguments (in this specific case, violate this guideline, but at least do X as mitigation).

In the end there is bureaucracy. Things need to be signed and archived for potential law suits. Not having archived things will be even worse in the law suits.

The upside: As a programmer, you don't need to argue that you need some time for unit testing.

The downside: 100% test coverage is mandatory and it really gets enforced.