Banking is pretty desperate for talent, probably because no one wants to suffer the complexity of the problem domain. I showed someone the models we use to track a customer implementation and they thought we were insane for even thinking this is a good business to be in.

Because the problem domain of banking sucks so much, the tooling is necessarily simple and "unsexy". We like things that fit into a single VM/folder and can be built in 1 click. Anything more complex than this is almost certainly going to fail by default under the combined weight of unnecessary technical complexity and vast (and necessary) business requirements.

It took us until the 3rd year of integration with one of our banking customers before someone in IT even gave enough of a shit to naturally ask the question "so what language/framework/technique did you write <product name> in?" Obviously, we are required to disclose this in legal materials prior to implementing our product, but our customer sees "Microsoft" and rubber-stamps it without much drama. No one else gives a shit about the tech after this phase of the project (which lasts approximately 1 phone call).