I've been thinking about getting this printed on stickers and handing them out at tech meetups.
We're using the Phoenix framework http://www.phoenixframework.org/ as a backend for a web app written in Angular, and also as part of a data publication service. Phoenix makes a couple of great design choices influenced by its erlang heritage. Most notably it is really just one of the erlang "applications" you run, so it doesn't dominate or dictate the rest of your project structure. You can easily integrate it as just the web component of an application that has behind the scenes data processing or whatever else it is you'd want to do.
The only gotcha we've run into so far is that a lot of erlang libraries expect strings for configuration text (list of chars) whereas the convention in Elixir is to use binaries.This hasn't resulted in any real issues though, just a perplexed minute from time to time.
If you have any particular questions I'd be happy to try to answer them.
[0] http://www.erlang.org/download/armstrong_thesis_2003.pdf
The erlang syntactic is really quite good. IT's new, yes, it's not lisp, it's not C, you have to learn a new syntax. Get over yourself, it's not that hard.
And once you learn it, it's nice and consistent and comprehinsible.
But elixir is even better. Elixir brings a lot of great features to erlang, while retaining interoperability, and one of the things about elixir is its syntax is much nicer (in my opinion) and it's certainly more accessible to most people.
Learn elixir.