I do, at somewhat medium scale. My experience was similar to other posters here, where we ran into production issues that were incredibly difficult to pin down.

If you'd like, you can attribute that to lack of Erlang experience or skill on my part. But in practice, we instead replaced that system with Go running on a Kube cluster and it's now been rock solid.

I've run high scale, high availability Go clusters involving thousands of nodes, dozens of eng teams, and it leveraged k8s. I've also worked at an Elixer shop with a few dozen engineers at a low scale ecommerce solution. The Go system was doing around 100k api calls a second, the Elixir system peaked at about 3k rps.

I would choose Go every single time. It has a better story for teams working together, largely due to better typing. Lacking types (and specs don't cut it), I still found I had to go up multiple function calls to understand what the parameters were, how they could be used, etc. so much state has to stay in your head, which I did not expect from a functional language