Last updated: November 18, 2026
By Candice, KORE1
An Elixir developer job description should name the lane (Phoenix web or OTP systems), the Elixir and Erlang/OTP versions in production, and a base range, about $115,000 to $165,000 mid-level and $150,000 to $250,000 senior. Most postings print “Elixir, Phoenix, Postgres” and stop. Tools, not a job.
Here’s a composite, details changed. A logistics software company in Austin, about 90 people, ran its dispatch product on Elixir 1.13 and Erlang/OTP 24. The posting for its second backend hire read “Elixir, Phoenix, Postgres, 5+ years, remote friendly,” which was all of it, with no range, no versions, and no word on what the team would build over the following year. Thin.
The finalist we liked had spent five years on a payments team in Seattle. Her first question on the call was a short one.
Which Elixir version is production on?
“Thirteen,” the engineering manager said. “Thirteen point what?” she asked, and he opened the lockfile while four people waited on the line. Nobody spoke.
She turned the job down, politely, with one reason. She wasn’t against upgrading an old codebase, she said, but she wanted that written in the posting so she could choose it, because a seat on a release the Elixir team no longer patches starts with a migration whether anyone planned one or not. The seat stayed open another nine weeks. Nine.
We get paid when you hire through our Elixir developer staffing desk. Weigh that. A better posting costs us little anyway, since a vague one sends the wrong résumés to our recruiters first and somebody has to read every one of them before the right ones surface. Sourcing channels and the interview loop are in our guide to hiring Elixir developers. This page is the posting itself. If the work is really backend services in general, the backend developer job description template fits better.

What an Elixir Developer Is Hired to Do
An Elixir developer builds and runs back-end software on the Erlang VM, usually Phoenix web applications, data pipelines, or long-running services that have to stay up through failures. The work covers application code, database access through Ecto, deployment as a release, and the on-call habits that keep a system serving traffic.
Three neighbors share pieces of that title. A general backend developer writes services in whatever language the company picked, and the Go developer and Rust developer templates cover the same ground on other runtimes. A Rails engineer learning Phoenix on the side belongs in a Ruby posting until the first Elixir deploy. A posting that borrows duties from all of them is a team budget wearing one job title. Different jobs.
Phoenix Web, Pipelines, or OTP Systems? Pick One Before You Write a Word
Elixir isn’t one job. Pick a lane. Our Elixir staffing page screens three depths of the same runtime on three different rubrics, and candidates sort themselves the same way. A person who spent four years shipping LiveView screens reads “distributed systems” and quietly closes the tab. Fair. They should.
| The seat | A line you could print | The phrase that misleads |
|---|---|---|
| Phoenix and LiveView product work | “Phoenix app with LiveView, Ecto on PostgreSQL, six engineers shipping weekly.” | “Full-stack,” when a separate React team owns the front end |
| Pipelines and background work | “Broadway pipeline moving 4 million events a day, Oban for scheduled jobs.” | “Big data,” with no volume attached |
| OTP and distributed systems | “Clustered nodes, supervision trees you design, a page when a process tree keeps restarting.” | “Distributed,” when it means two replicas behind a load balancer |
| Embedded devices on Nerves | “Elixir firmware for a fleet of 3,000 devices, with a hardware bench in Boulder.” | “Remote,” when the bench is a room you have to sit in |
The last row hides the most expensive mistake. A bench is a bench. Hardware work on a physical bench can’t be done from a spare bedroom, and the posting that says “fully remote” anyway loses its finalist at the offer, usually after three rounds of interviews that nobody can get back.
People who write Elixir tend to like writing it. The 2025 Stack Overflow Developer Survey put it third among the most admired languages at 66%, behind Rust at 72% and Gleam at 70%. Admiration isn’t loyalty, but it’s a decent hint that the person reading your posting has other offers, reads closely, and will notice within one paragraph whether the posting was written by someone who has ever deployed an Elixir release. It cuts both ways. The hiring guide goes into what each profile costs and how long the search runs. Here, just choose.
Elixir and OTP Versions Come With Expiry Dates
Elixir 1.0 shipped on September 18, 2014, according to the project’s release blog. A new minor release lands about every six months, and v1.20 arrived on June 3, 2026. The project’s own compatibility page says bug fixes go only to the latest minor branch and security patches cover the last five. Everything older gets nothing. That’s the policy this week, in table form.
| Elixir version | What the Elixir team patches | Erlang/OTP versions it supports |
|---|---|---|
| 1.20 | Bug fixes and security patches | 27 to 29 |
| 1.19 | Security patches only | 26 to 28 |
| 1.16, 1.17, and 1.18 | Security patches only | 24 to 27, depending on the release |
| 1.15 and older | Nothing listed | 26 and lower, depending on the release |
Look at where Austin’s 1.13 lands. It’s in the bottom row, outside the branches the Elixir team patches, so the first job in that seat was an upgrade nobody had put on a roadmap. A candidate who checks the policy page can see that coming from one word in your posting, or from its absence, and the ones who’ve been burned on a stale codebase before will check it first. Everyone else just notices the silence.
The v1.20 release adds a second reason to print the version. Elixir’s announcement says the compiler now performs type inference and gradually type checks every Elixir program without any type annotations, and that it reports dead code and “verified bugs,” meaning typing violations that are guaranteed to fail at runtime if the code runs. An old codebase that finally upgrades may greet its new hire with a list of warnings. Some engineers want that job. Others want a quiet first quarter. Either one deserves to know which they’re signing up for. Both are fine.

So print two numbers and a plan. “Production runs Elixir 1.17 on Erlang/OTP 27, and we’re moving to 1.20 by March” is a sentence a finalist can plan around. Simple. If you aren’t sure what production runs, the answer is in the lockfile and the Dockerfile, and finding out takes ten minutes. Maybe less.
Elixir Developer Job Description Template
Copy this into your applicant system, replace everything in square brackets, and strip the parenthetical notes before anyone outside the company sees it. Cut any section that doesn’t apply. Those notes talk to you, not to candidates.
Job Title
[Senior Elixir Engineer, Phoenix] (Put the lane in the title when you can, such as “Senior Elixir Engineer, Data Pipelines.” Say “Senior” only if this person sets standards for others. Mostly Rails with one Elixir service? That’s a backend title that mentions Elixir.)
The Stack You’ll Inherit
- Elixir [1.x] on Erlang/OTP [2x], with a plan to reach [1.20] by [quarter]
- [Phoenix with LiveView / Phoenix as a JSON API / no web layer, just a Broadway pipeline]
- Data in [PostgreSQL through Ecto, plus anything else that matters, like Redis or ClickHouse]
- Shipped as [mix releases on Kubernetes / Fly.io / AWS ECS], about [N] deploys a week
- [N] engineers on the Elixir code, in [one repo / an umbrella project / N services]
- Tests in ExUnit, covering about [N]% of modules
- On call 1 week in [N], averaging [N] pages a month
What You’ll Own
[The dispatch service and the Phoenix app on top of it, from design through the 2 a.m. page. Roughly [N] requests per second at peak, with a p99 under [N] ms. The Oban jobs that send invoices, and the Broadway pipeline that feeds the reporting database.] (Name real things. “Maintain backend services” says nothing, while “own the invoice job that runs at 6 a.m.” tells a candidate what the week holds. Specific wins.)
Decisions You Make
- When work leaves the request path for a background job, and which tool carries it
- Which libraries get added to the approved list, and who keeps that list honest
- When to upgrade Elixir and OTP and how to stage it, with [title] signing off
- Whether a failure is handled in code or left to a supervisor to restart
What Sits Elsewhere
[Infrastructure belongs to the platform team, who run the Kubernetes clusters. The front end belongs to the React group. You’ll work with both and decide for neither.] (Finalists want to know where the job stops. Answer before they ask.)
Twelve Months In
- By day 90, one change shipped to production and one on-call week done with a second engineer behind you
- [A version result, such as production on Elixir 1.20 and Erlang/OTP 28 by month six]
- [A reliability result, like cutting pages from [N] a month to under [N]]
- [A growth result, such as the pipeline handling twice today’s volume without a bigger bill]
Background We’re Looking For
- Has run Elixir in production, meaning it served real traffic and somebody got paged at night. Side projects count for something else
- Can explain what restarted a crashed process and why that was the right choice
- Writes Ecto queries and migrations, and reads a query plan before blaming the database
- [Your lane’s specifics. LiveView in production for web seats, Broadway or GenStage for pipelines, clustering for OTP seats]
- [Experience matched to the level, often 3 to 5 years for mid and 5 to 8 for senior, counted as production years on any backend stack, with two or more of them in Elixir]
Helpful, Not Required
- A Ruby or Rails background, which is common on this team and welcome
- Telemetry and tracing set up for a live system
- A Hex package or an open-source patch with their name on it
- [Time in your industry, such as dispatch, payments, or messaging]
Pay, Benefits, and Location
The base runs $[low] to $[high] a year, a range the company fixed before this ad was written. [A bonus target of N%. Equity, if any, in one sentence, such as “stock options vesting over four years.”] Benefits cover [health insurance, a retirement plan, and paid leave, one line each]. The seat is based in [city] or [remote within N time zones, with [N] hours of overlap with the team’s day]. (Print the overlap hours. “Remote” with no hours reads as “we haven’t decided.”)
Pay Sources, and Washington’s Rule for Remote Postings
Elixir pay data is thin, and it disagrees with itself. Small samples. Glassdoor’s national figure rests on seven salaries, which is hardly a survey. Treat every average below as a rough pointer and not a price.
| Source | What it measures | Figure | The catch |
|---|---|---|---|
| Glassdoor, read Nov. 18, 2026 | Elixir Developer, United States | $117,706 average, $94,477 to $147,874 for the middle half | Seven reported salaries |
| Salary.com, Nov. 1, 2026 | Elixir Developer, United States | $108,664 average, $100,712 to $118,080 for the middle half | Its 90th percentile, $126,653, sits below our senior floor |
| Bureau of Labor Statistics, May 2025 | Software developers, all languages | $135,980 median | No line for Elixir, only the parent occupation |
| HexHire job board tally, Dec. 2025 to Feb. 2026 | 216 remote Elixir listings, 62 with a salary | Senior listings most often $150,000 to $175,000, 17 of them | A job board counting its own listings, a small sample |
Our bands start near those averages at mid-level and run well past them for senior seats. An average blends every level, every metro, and every company size into one number, while a band prices one seat at one level, which is why a posting built from the average alone can miss the seat it’s meant to fill. The job board’s senior listings, the most useful row for this decision, land inside our senior bands. These are the same working bands as our Elixir developer salary guide, which reads seven sources against each other.
| Level | Base range to post | What the posting should show |
|---|---|---|
| Mid (3 to 5 years) | $115,000 to $165,000 | Ships Phoenix features, Ecto queries, and LiveView screens inside an architecture a senior engineer already drew |
| Senior, Phoenix web (5 to 8 years) | $140,000 to $185,000 | Owns a Phoenix app in production, including the pager |
| Senior, OTP and distributed (5 to 8 years) | $170,000 to $250,000 | Designs supervision trees and clustering, and answers when a node falls over |
| Staff or lead (8+ years) | $195,000 and up | Sets the design across teams, hires the seniors, and decides when Elixir stops being the right tool |
Every figure above is a U.S. base salary with no metro adjustment, and “and up” describes our band, not how an ad should read. Post a closed range for the lead seat. Match the row to the lane you picked earlier, because a Phoenix range on an OTP seat draws applicants who price themselves accordingly. Need a single city? The salary benchmark assistant is quicker than a table.

About seven in ten of the Elixir placements we make are remote rather than hybrid, and a remote posting is read in every state at once. Some of those states regulate who has to show a range. Washington’s Department of Labor and Industries published Administrative Policy ES.E.2 on December 3, 2025, and five points from it matter here.
- Who’s covered. Employers with 15 or more employees, and the count includes people outside Washington so long as the employer has at least one Washington-based employee.
- Remote work counts. The policy requires the range on postings for remote work “that could be performed by a Washington-based employee,” and says an employer “cannot avoid” the rule by stating in the posting that it won’t accept Washington applicants.
- The range has to be real. It should “extend from the lowest to the highest pay established by the employer prior to publishing the job posting,” and an open-ended line like “$60,000/per year and up” doesn’t qualify.
- Equity belongs in the posting. Besides a general description of benefits, the policy requires a description of other compensation, which it defines to include “bonuses, commissions, profit-sharing, stock options.”
- Recruiters are covered too. A posting includes recruitment done “indirectly through a third party.”
The policy keeps an exception for jobs performed entirely outside Washington. Narrow, though. Other states have their own versions with different thresholds, and which ones reach your posting is a question for employment counsel, not a recruiter. One more number belongs here. Only 62 of those 216 remote Elixir listings, 29%, carried a salary at all. Whatever your legal footing, a posting with a range and a benefits line stands out in a field where seven of every ten remote listings said nothing about pay.
Six Things Hiring Managers Ask Before They Post
Do we need Erlang, OTP, and BEAM all in the posting?
Name Elixir and the Erlang/OTP major version, and skip BEAM unless the seat touches the VM itself. Each Elixir release supports a stated range of OTP versions, so the pair tells a candidate what they’d run.
If the work involves tuning schedulers or reading memory dumps, say that in the requirements instead. Candidates who know the runtime will say “BEAM” casually in the first call anyway. You don’t need to.
Can we write “Rails developers welcome”?
For a Phoenix web seat with a named mentor, yes. Our hiring guide puts a strong Rails engineer at three to six months to productive in Phoenix, and teams keeping a Rails app alive are running a second search, covered under Ruby on Rails staffing.
For an OTP systems seat, no. Supervision trees, process isolation, and message passing are a different way of thinking, and three months won’t cover them, which is where good Rails engineers get frustrated with themselves. Different skill.
Is ten years of Elixir a reasonable ask for a senior seat?
Ask for years of production work and name what the person will have owned. Elixir 1.0 shipped in September 2014, so a ten-year requirement reaches back to 2016 and leaves out strong engineers who came over from Rails or Erlang later.
Five to eight years of backend work with at least two in Elixir fills a senior seat more often than a number nobody can meet. Pair it with the specifics, like “has owned a clustered service” or “has run LiveView in production.” Specifics filter. Numbers don’t.
Does a remote Elixir posting need a pay range?
Often, yes, because Washington requires the range on remote postings for work a Washington-based employee could do, even if the posting refuses Washington applicants.
Other states differ on thresholds and wording, so check each one with counsel.
In practice, put the range and a one-line benefits description on every remote Elixir posting and skip the case-by-case sorting. It also helps that 71% of remote listings in that job board tally had no salary, which makes yours stand out.
We run a Rails monolith with one Elixir service. Is this an Elixir job?
Probably a backend job that mentions Elixir. Title the seat for the work that fills most of the week, and list the other language as a plus.
If 80% of the week is Rails and 20% is the Elixir service, a posting titled “Elixir Developer” draws applicants who want the 80% to be Elixir, and they leave in month four. Predictable. The backend template fits that seat better.
Contract or direct hire for a first Elixir seat?
Direct hire if the person will own the codebase for years. Contract if the work is a bounded build, like moving a service off Ruby, and contract-to-hire if you want to test fit first.
The small pool shapes this choice. Senior Elixir engineers often want to commit to a codebase they’ll shape, so a direct-hire signal draws them in, while a six-month contract works when the scope has an end date. Both work.
A Two-Question Test Before You Post
Hand the draft to the engineer who’d sit closest to the hire and ask two things. Which Elixir version are we on, and who gets paged? If the answers aren’t on the page, a candidate can’t find them either, so the good ones will spend their first call asking instead of applying, and the rest will simply keep scrolling. Simple test. Once the posting draws people, our Elixir developer interview questions cover what to ask them.
KORE1 has recruited technology talent since 2005, in 30+ U.S. metros, through recruiters who average over 15 years on the desk. Of the people we place, 92% are still in the role twelve months on. When the draft reads right, our Elixir developer staffing practice can take the search from there. Want a second read first? Send us the draft, and we’ll mark the line a finalist would push on first.

