I am curious how that is useful at all? I imagine prototyping and the set of libraries that you have is quite limited compared to something like Python. You're also limiting yourself to a much smaller pool of developers which have to intersect both finance and Haskell! I suppose that last point is an advantage of some sort since that filters out a huge portion of "normie" applications.

I work at one of those fintech companies using Haskell in production.

Hiring was actually Haskell’s strong side. I managed to hire 6 engineers in only one month. There were more than 50 applicants to the position. Just the idea of using Haskell in production is attractive to many.

It’s been a great experience overall. I worked at a python company before this one and it’s been refreshing not having unexpected runtime errors. Moving money around requires more robustness than your typical app.

My understanding is "safety". You need to cover all cases of enums, you can't implicitly coerce a number to a string, you can ensure that there's no side-effects in company code, etc.