Last week we had five first stage interviews for a client looking to hire an Elixir Engineer. One role, one week, and candidates in the UK, Poland, Czechia and Latvia. If you are hiring Elixir developers right now, that week was a working sample of the market, and it told a clearer story than any salary survey.
The pool is small, senior, and spread across Europe
Nobody chooses Elixir by accident. Every engineer I spoke to had made a deliberate bet on the BEAM, and most had five to fifteen years of experience behind it. One had spent nearly a decade on OTP, supervision trees and distributed systems. Another started in Erlang straight out of university and never left the ecosystem.
The geography matters as much as the seniority. Of the credible candidates for one role, one was in the UK. The rest were spread across central and eastern Europe, working through their own limited companies, entirely comfortable with B2B contracts. If your Elixir vacancy is restricted to one city, you are not fishing in a small pond. You are fishing in a bucket.
Candidates are interviewing you on AI
The sharpest question of the week did not come from the client. It came from a candidate: is the company using AI only in the product, or also in day to day engineering work, in workflows and in how the team codes?
That question is a filter. Engineers with options want to know whether they will spend the next three years learning or maintaining. A vague answer reads as a warning sign, and the candidate who asked would not progress until we got her a proper one. Founders preparing for interview loops should treat “how do your engineers use AI” as a certainty, not a possibility, and have an answer that sounds like a plan.
The profile everyone suddenly wants
One candidate spent his hour long interview split between Elixir fundamentals and how to build user facing LLM systems, support chat and chat based analytics among them. The client’s reaction was immediate, because he had already built what they want to build next. He went from first conversation to progressing within three days.
That overlap, Elixir plus shipped LLM product experience, is the scarcest profile I have seen in this ecosystem. Both pools are small on their own. The intersection is tiny. If your roadmap includes AI features on the BEAM, expect to compete hard for these people, and expect speed to decide it.
What actually moves them
Across the week’s conversations, not one candidate led with compensation. Expectations ranged from roughly sixty to eighty thousand euros, and every number was stated calmly, as a fact rather than an opening position.
What they did lead with was growth, stability and trust. One engineer is leaving because her work became repetitive and no one can show her a route to senior. Another has been through repeated layoffs and contract cuts and wants somewhere to build for years. A third will only consider fully remote roles after two employers revealed relocation requirements late in the process. These are not unusual stories. They are the standard motivations of the 2026 Elixir market, and an offer that fails to address them will lose to one that does, at the same salary.
Speed is the differentiator
The week worked because the shortlist was ready before interviews began and the interviews ran as a block. The hiring manager compared candidates while impressions were fresh. Candidates felt momentum and stayed engaged. Feedback moved in days.
Most Elixir hiring fails in the gaps: the eleven days between interview and feedback, the month between first and final stage. In a market this concentrated, the company that compresses those gaps wins the candidate, and usually at no premium.
If you are planning an Elixir hire and want a realistic view of the pool, the money and the timelines, I am happy to walk you through what the market is saying this month.
Arjun Gillard
Founder, AG Talent
agtalent.co.uk
