I use Haskell at work. At my current job it’s my teams primary language, and almost all code we write is in Haskell. I’ve been using Haskell at work for years now, but more often as a secondary or tertiary language along side others.
Haskell, and FP generally, work well for everyday industrial programming. In my experience I’ve never found there to be an issue that was a dealbreaker- although there are tradeoffs.
That said, whenever I’ve looked for work I’ve always looked at non-FP roles in addition to FP roles because there are just fewer FP jobs out there.
A few years ago I volunteered to do mock interviews for a bunch of students who were getting ready to graduate from a bootcamp. I didn't know much about the bootcamp curriculum and I was surprised to see that all of the resumes listed functional programming as one of the key skills. I was curious, and asked the first few interviewees about their experience with FP and they made up some nonsensical answers with varying degrees of confidence. I finally asked one of them to just tell me what functional programming was, and was and they said "oh, you know, writing a program that functions!".
I made it a point of telling the students that it's a lot better to admit you don't know something rather than making something up in an interview, and reached out to the founder of the bootcamp to express my disappointment that they were sending people into interviews with blatantly false experience on their resume. I'm not sure if anything ever came of it, and from time to time I wonder how many graduates from that bootcamp are still going out into interviews with no idea that "functional programming" means anything other than writing programs that function.