He's asking what his next language should be. I don't get the vibe here of a new programmer thinking he's staking his entire future on what programming language he decides to learn.
It's entirely possible to understand that the programming languages you know aren't as important as what you've built along with your knowledge of software engineering and computer science fundamentals, and yet still want input on the next PL you'll learn in your free time.
I get what you mean, but it still makes very little sense to me. If he had said I want to make a client/server chat system, then we could make a real suggestions between elixir and scala. He also wants to be able to write concurrent systems, the best way to do this is of course write concurrent systems, not learning concurrent lang structs in scala or elixir. Only when you write a distributed system are you going to encounter all the networking and data integrity problems that arise at those lower levels and these are the things that are important to know and will give him reasons to choose elixir or scala or erlang or golang or whatever works best for him while building that.
Recruiters might not get this and just ask for knowledge of X or Y but at some point in your interview process theres most likely going to be a lead engineer sitting across from as an influencer on whether to hire you or not, and if hes worth anything hes only going to care about your "building" skills not language X or Y.