Banking has a reputation for hiring developers who wear ties and got the job by proving that they could spell "Python." I interned as a developer at a bank. We

Banking has a reputation for hiring developers who wear ties and got the job by proving that they could spell "Python." I interned as a developer at a bank. We lied about security and development practices to auditors. We had some PCI compliance stuff to do and they turned on a bunch of features and created a change request form for a day for audit purposes. We pointed a develop server at production for several hours, allowing anyone to login to accounts. We turned off our tests rather than fix Jenkins. A friend is currently with a bank you have heard of. He is not quite a developer, but on a team that does dev work. They have standards for reliability and productivity. He fakes them. He gets to toss any bad data as a "outlier" and sends the rest up to management for its rubber stamp. He is upfront about it in the way that bankers are (a pile of weasel words), but realizes that VPs are Banks are not technical. Having worked for a bank, I would not hire someone who had spent a very long time there. I would expect to be getting someone who viewed the solution to security issues as releasing a memo proclaiming there are no security issues or just bleating about best practices. As that is what we did.