Elixir Hiring Is Its Own Problem
There is no big pool of Elixir engineers. There is a small one, and most of it is not looking.
Elixir is a deliberate choice. Teams pick it for concurrency, fault tolerance and the kind of uptime that the BEAM gives you almost for free. The trade-off is the hiring market. Nobody is producing Elixir engineers at volume. Most came to it from Ruby, taught themselves OTP properly, and are now happily building something they believe in. They are not refreshing job boards.
That is why a generic agency struggles. They search for the keyword, surface a Ruby developer who once shipped a side project in Phoenix, and call it a match. I work the actual Elixir community, I can tell real OTP depth from a CV that name-drops GenServer, and I know what makes a happy Elixir engineer take a call.
Talk to ArjWhat teams tell me
"The role has been open five months. Every CV is a Ruby dev who read one Phoenix tutorial."
"Every recruiter we briefed clearly googled Elixir the same morning. None of them understood the stack."
"We found someone good and lost them to another offer while we were still booking the second interview."