We use technical cookies and Zorky's de-identified visit log. Yandex Metrica (data is stored on servers in Russia) runs only with your consent. We never sell data. More about cookies and statistics.
Zorky is in test mode — everything is free. Jobs and company pages are open to everyone; links to postings and your personal feed open after you sign up. Sign up →

Elixir / Erlang: market

Data as of November 19, 2026: 39 open Elixir / Erlang jobs, 53% remote among jobs that state a work format. Source: Zorky, updated daily.

Elixir / Erlang — backend development in functional languages running on the BEAM (Erlang VM) virtual machine: systems with massive concurrency, fault tolerance and soft real-time. Erlang — the original language created at Ericsson for telecom systems («let it crash» philosophy + the OTP library). Elixir — a modern language on top of the same BEAM (author — José Valim) with a pleasant Ruby-like syntax, metaprogramming and a fast-growing ecosystem; it's Elixir that forms the bulk of new vacancies in the segment. The key value of the platform — the actor model: millions of isolated lightweight BEAM processes that pass messages to each other, and supervisors (supervision tree) that automatically restart fallen parts of the system without taking down the whole — hence the legendary fault tolerance (telecom-grade «nine nines» reliability). Role family: Elixir Backend Engineer (general — Phoenix APIs and services), Elixir / Phoenix LiveView Developer (interactive real-time applications), Erlang Engineer (telecom, messaging, legacy systems — a narrow niche), BEAM Backend Engineer (high-load and distributed systems). Stack 2026: Elixir (must — 1.16+), Erlang / OTP, Phoenix (web framework), Phoenix LiveView (rich interactive UI almost without writing JavaScript — killer feature), Ecto (DB work), PostgreSQL, GenServer / Supervisor / GenStage (OTP abstractions), Broadway (data pipelines), Oban (background jobs), ExUnit (tests), Dialyzer + typespecs (static analysis), Nx / Bumblebee (growing Elixir ML ecosystem), Mix (build tool), Docker + Kubernetes. Top stack: elixir, postgresql, elasticsearch, python, rabbitmq. Among jobs with a stated work format, 53% are remote. Elixir / Erlang — one of the narrowest backend segments in CIS: small developer pool, but thanks to the shortage and complexity — high salaries; the main market is international full-remote (Discord on Elixir, WhatsApp legacy on Erlang, hundreds of SaaS on Phoenix).

Data as of:

Key numbers for the Elixir / Erlang market: open jobs, median salary, observed talent pool and remote share.

39
open jobs — by job title, reposts merged
53%
remote

The Elixir / Erlang market currently has 39 open roles, 33 of them freshly observed.

Among jobs with a stated work format, 53% are remote. For Elixir remote — not a bonus, but the main mode: few local vacancies, the market is international.

⚠ salary known for 1 of 39 jobs; remote share from 34 with a stated format; 33 counted as fresh observations; trend and hiring difficulty are not shown

Timeline: postings and sources

How many Elixir / Erlang postings appeared each week since Jun 1, and from how many sources. The lower chart separates market growth from coverage growth: a jump in the week new sources were connected means we started seeing more, not that the market grew.

New postings per week

Chart data
New postings per week. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodNew postings per week
2026-06-011
2026-06-081
2026-06-152
2026-06-221
2026-06-292
2026-07-067
2026-07-136
2026-07-201
2026-07-277
2026-08-034
2026-08-103
2026-08-171
2026-08-242
2026-08-310
2026-09-070
2026-09-143
2026-09-213
2026-09-285
2026-10-0510
2026-10-1218
2026-10-1912
2026-10-2616
2026-11-026
2026-11-0910

Active sources per week

Sources over the period: 34. ▲ — a week with a large batch of new sources.

Chart data
Active sources per week. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodActive sources
2026-06-011
2026-06-081
2026-06-151
2026-06-221
2026-06-292
2026-07-064
2026-07-135
2026-07-201
2026-07-275
2026-08-034
2026-08-103
2026-08-171
2026-08-242
2026-08-310
2026-09-070
2026-09-143
2026-09-211
2026-09-285
2026-10-057
2026-10-1210
2026-10-198
2026-10-269
2026-11-025
2026-11-098
New sources connected: Jul 6 +4 · Oct 12 +4 · all weeks (16) in the table
WeekNew sourcesNew postings
Jun 8+11
Jun 15+12
Jun 22+11
Jun 29+22
Jul 6+47
Jul 13+36
Jul 20+11
Jul 27+27
Aug 24+12
Sep 28+35
Oct 5+210
Oct 12+418
Oct 19+312
Oct 26+216
Nov 2+16
Nov 9+210

The current week is not over yet and is not shown: an incomplete week would look like a drop.

Week = posting first-seen date, all statuses; postings are selected by the same rule as this page's counter. Sources are distinct collection channels; their names are not published.

Chart data
Timeline: postings and sources — Elixir / Erlang. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekNew postings per weekActive sources
2026-06-0111
2026-06-0811
2026-06-1521
2026-06-2211
2026-06-2922
2026-07-0674
2026-07-1365
2026-07-2011
2026-07-2775
2026-08-0344
2026-08-1033
2026-08-1711
2026-08-2422
2026-08-3100
2026-09-0700
2026-09-1433
2026-09-2131
2026-09-2855
2026-10-05107
2026-10-121810
2026-10-19128
2026-10-26169
2026-11-0265
2026-11-09108

Remote work over time

Share of Elixir / Erlang postings offering fully remote work, per week.

Remote postings, %

Chart data
Remote postings, %. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodRemote
2026-10-1254.5
2026-10-1990.9
2026-10-2645.5
2026-11-02—
2026-11-09—

The series starts on Oct 12: there is no data before that.

The share is among postings that state a format (remote, hybrid, office). Weeks with fewer than 10 such postings are left blank.

Chart data
Remote work over time — Elixir / Erlang. Block data table. A missing value is not zero; units and sample are stated in the metric description.
WeekRemote
2026-06-01—
2026-06-08—
2026-06-15—
2026-06-22—
2026-06-29—
2026-07-06—
2026-07-13—
2026-07-20—
2026-07-27—
2026-08-03—
2026-08-10—
2026-08-17—
2026-08-24—
2026-08-31—
2026-09-07—
2026-09-14—
2026-09-21—
2026-09-28—
2026-10-05—
2026-10-1254.5
2026-10-1990.9
2026-10-2645.5
2026-11-02—
2026-11-09—

Clean market: hiring index

The same 7,505 employer job boards; the posting count comes from the board itself. Connecting new sources does not move this index — it shows the market, not our coverage. This is the whole panel market, not just Elixir / Erlang.

Hiring index, Oct 16 = 100

Chart data
Hiring index, Oct 16 = 100. Block data table. A missing value is not zero; units and sample are stated in the metric description.
PeriodHiring index
2026-10-16100
2026-10-17100.03
2026-10-1899.76
2026-10-1999.68
2026-10-2099.27
2026-10-2198.6
2026-10-2299.07
2026-10-2397.4
2026-10-2497.41
2026-10-2697.33
2026-10-2796.76
2026-10-2896.21
2026-10-2995.17
2026-10-3095.13
2026-10-3193.65
2026-11-0193.33
2026-11-0292.67
2026-11-0392.65
2026-11-0492.41
2026-11-0592.13
2026-11-0690.44
2026-11-0790.48
2026-11-0890.45
2026-11-1090.29
2026-11-1190.22
2026-11-1390.12
2026-11-1489.7
2026-11-1589.68
2026-11-1689.62
2026-11-1888.91
2026-11-1988.02

Chain index: each day compares only boards polled on both that day and the previous one; outliers and platform-wide polling outages are excluded. Days with no comparable pairs are left blank.

Chart data
Clean market: hiring index — Elixir / Erlang. Block data table. A missing value is not zero; units and sample are stated in the metric description.
DayHiring index
2026-10-16100
2026-10-17100.03
2026-10-1899.76
2026-10-1999.68
2026-10-2099.27
2026-10-2198.6
2026-10-2299.07
2026-10-2397.4
2026-10-2497.41
2026-10-2697.33
2026-10-2796.76
2026-10-2896.21
2026-10-2995.17
2026-10-3095.13
2026-10-3193.65
2026-11-0193.33
2026-11-0292.67
2026-11-0392.65
2026-11-0492.41
2026-11-0592.13
2026-11-0690.44
2026-11-0790.48
2026-11-0890.45
2026-11-1090.29
2026-11-1190.22
2026-11-1390.12
2026-11-1489.7
2026-11-1589.68
2026-11-1689.62
2026-11-1888.91
2026-11-1988.02

How many open Elixir / Erlang jobs there are and how many matching specialists Zorky observes.

Demand and observed supply

Chart data
Block data table. A missing value is not zero; units and sample are stated in the metric description.
MetricValue
Open demand39
Open demand39
Observed supply— not published

Elixir / Erlang — one of the narrowest backend segments: few vacancies, but demand is stable, and staff shortage keeps salaries high. Drivers 2026: growth of Phoenix LiveView (real-time UI without JS), high-load cases (Discord), growing Elixir ML ecosystem (Nx / Bumblebee). The market is international by nature — the main growth in the full-remote segment.

⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown

Salary distribution

Acute engineer shortage makes the segment one of the highest-paid at the same grade.

The chart will appear once enough observations accumulate for this breakdown.

Which countries have the most open Elixir / Erlang jobs.

Demand geography

countryjobsshare
United States827.6%
Poland310.3%
United Kingdom310.3%
Canada310.3%
Spain26.9%
Germany26.9%
Brazil26.9%
India13.4%
Costa Rica13.4%
Romania13.4%
Other countries310.3%

Leader by Elixir job count — the US (8 positions). Local demand in any CIS country is small — the market is international by nature. Germany (Berlin — notable Elixir community, ElixirConf EU). The main volume for a Russian-speaking Elixir engineer — international full-remote.

⚠ job counts only: salary by country is not published

Chart data
Demand geography — Elixir / Erlang. Block data table. A missing value is not zero; units and sample are stated in the metric description.
CountryJobs
US8
PL3
GB3
CA3
ES2
DE2
BR2
IN1
CR1
RO1

Which technologies are most often required in the same job as Elixir / Erlang.

Used together with

elixir
3897.4%
react
1230.8%
postgresql
1128.2%
aws
717.9%
cloud
717.9%
python
615.4%
rabbitmq
410.3%
docker
410.3%
ruby
410.3%

Share — how many of the 39 jobs in the Elixir / Erlang market mention this technology. Ordered by job count, not by “strength of association”. Umbrella terms like cloud are not a specific cloud (AWS, Azure).

Top Elixir stack 2026: Elixir 1.16+ (and Erlang / OTP underneath), Phoenix (web framework), Phoenix LiveView (real-time UI without JS — killer feature), Ecto (DB work), PostgreSQL, OTP abstractions (GenServer / Supervisor / GenStage), Broadway (data pipelines), Oban (background jobs), ExUnit (tests), Dialyzer + typespecs, Nx / Bumblebee (Elixir ML ecosystem), Mix, Docker + Kubernetes.

Common pairs: Elixir + Phoenix, Phoenix + LiveView, Elixir + Ecto + PostgreSQL, Elixir + OTP (GenServer / Supervisor), Elixir + Oban / Broadway. Learning roadmap: language → functional basics (pattern matching, immutability, pipe) → processes and OTP (GenServer / Supervisor) → Mix + ExUnit → Ecto → Phoenix → Phoenix LiveView → pet project with deploy.

Chart data
Used together with — Elixir / Erlang. Block data table. A missing value is not zero; units and sample are stated in the metric description.
NameCount
elixir38
react12
postgresql11
aws7
cloud7
typescript7
python6
rabbitmq4
docker4
ruby4
kubernetes3
angular2

How many Elixir / Erlang jobs there are at each level, from junior to principal.

Demand by grade

gradejobs
senior22
principal5
middle1

Junior vacancies almost don't exist — the market expects an experienced backend engineer. Career flow: backend developer from another language (often Ruby / Python / Go) → Elixir Middle in 4-8 months (the main thing — paradigm shift to functional + OTP) → Senior → Staff / Tech Lead / distributed systems. Staff shortage lifts salaries above backend average.

⚠ demand side only: the grade of the observed pool is unknown for most of it

Chart data
Demand by grade — Elixir / Erlang. Block data table. A missing value is not zero; units and sample are stated in the metric description.
LevelCount
senior22
principal5
middle1

Who hires the most for Elixir / Erlang and how concentrated demand is among the largest companies.

Employers

Demand is spread across 30 employers. The largest accounts for 8.6%, the top ten for 42.9%; the remaining 57.1% is long tail.

largest 8.6%2nd–3rd 11.4%4th–10th 22.9%the rest 57.1%
sharevalue
top-18.6%
top-320.0%
top-1042.9%
long tail57.1%

Largest Elixir / Erlang employers — international BEAM flagships: Discord (millions of simultaneous users on Elixir), Remote.com (itself on Elixir, all-remote), Supabase (real-time layer), Duffel, Cars.com, Bleacher Report, Felt, many SaaS startups. On Erlang — WhatsApp (historically), RabbitMQ, telecom. In CIS — individual product, fintech and high-load teams.

⚠ names are not shown: staffing agencies and end employers are not yet told apart by the classifier

Which company sites and job boards Zorky collects Elixir / Erlang jobs from.

Where Zorky sees this market

Observed across 19 sources; the largest accounts for 17.9% — this market does not rest on a single channel.

The real market for a Russian-speaking Elixir engineer — primarily international remote, local vacancies are few.

Chart data
Where Zorky sees this market — Elixir / Erlang. Block data table. A missing value is not zero; units and sample are stated in the metric description.
ClassNameEnglish nameCountShare
atsATS и карьерные сайтыATS & career sites230.5897
boardджоб-борды и агрегаторыjob boards & aggregators100.2564
telegramTelegramTelegram40.1026
communityсообщества и публичные профилиcommunity & public profiles20.0513

The newest Elixir / Erlang jobs from company career sites.

Recent openings

All jobs →

Latest open Elixir / Erlang jobs — most recent 10 positions with adequate description quality. Full list — in our CRM or via the «see all» link below.

How this is measured
Vacancy
an open job that cleared the quality gate and lists at least two technologies
Observed candidate
a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter
Matchable candidate
not counted yet
Window
jobs open at the moment the snapshot was built

About the data

  • Some breakdowns are hidden: their data coverage is not yet sufficient.
  • Statistics are shown only where the sample clears a quality gate.
  • A missing block does not mean a value of zero.

Breakdowns currently hidden: 9.

Direction: Backend

Related specializations

Inside Elixir / Erlang: Elixir Backend Engineer (general — Phoenix APIs and services), Elixir / Phoenix LiveView Developer (interactive real-time applications), Erlang Engineer (telecom, messaging, legacy systems — a narrow niche), BEAM Backend Engineer (high-load and distributed systems). Neighboring segment for comparison — Ruby on Rails (syntactically related). Comparison — in the bar below.

.NET / C#Go / GolangJava BackendNode.jsPHPPython BackendRuby on RailsRustScala / Kotlin

Frequently asked questions

The most common questions about Elixir / Erlang: pay, grades (Junior almost none), stack, what BEAM / OTP / actor model are, what Phoenix LiveView is, Elixir vs Go, Elixir vs Erlang (learn Elixir), remote (main work mode), companies, how to start (4-8 months for an experienced backend), Senior skills. Answers recompute automatically.

What stack is most often required from an Elixir developer?

Top 5: elixir, postgresql, elasticsearch, python, rabbitmq. Elixir (must — 1.16+) and understanding of Erlang / OTP underneath. Phoenix — the main web framework. Phoenix LiveView — rich interactive UI almost without JavaScript (de-facto frontend standard in the Elixir world 2024–2026). Ecto — DB work (not a classic ORM, but a set of composable tools: schemas, changesets, query DSL). PostgreSQL. OTP abstractions: GenServer (processes with state), Supervisor (supervision trees), GenStage / Flow, Task, Agent. Broadway — concurrent data pipelines (Kafka / RabbitMQ / SQS). Oban — reliable background jobs on PostgreSQL. ExUnit — tests. Dialyzer + typespecs — static type analysis. Telemetry — metrics and observability. Nx / Bumblebee — the growing Elixir ML ecosystem (José Valim investing in this direction). Mix — build and dependencies. Docker + Kubernetes. Knowledge of distributed Erlang (nodes, clustering — libcluster) — Senior must for high-load.

What are BEAM, OTP and the actor model — why does Elixir need them?

BEAM — the Erlang virtual machine, on which both Erlang and Elixir execute. Its key feature — the actor model: a program consists of many extremely lightweight processes (not OS processes — BEAM's own processes, you can create millions of them) that are fully isolated from each other (don't share memory) and communicate only by passing messages. This gives: concurrency (BEAM efficiently distributes processes across all CPU cores), fault tolerance (a fallen process doesn't take down the others), soft real-time (the scheduler doesn't let one process block the system). OTP (Open Telecom Platform) — a library of time-tested abstractions on top of this: GenServer (process with state and standard behavior), Supervisor (a process whose job is to watch children and restart fallen ones by a given strategy), supervision tree (a tree of supervisors — the structure of the entire application). The «let it crash» philosophy: don't try to handle every conceivable error with defensive code, but allow the problematic process to crash and be restarted into a clean known state by the supervisor. It's precisely the combination of BEAM + OTP that makes Elixir / Erlang a uniquely good choice for systems that must hold many simultaneous connections and not fall.

What is Phoenix LiveView and why is it a killer feature?

Phoenix LiveView — a Phoenix framework technology for building rich interactive user interfaces almost without writing JavaScript. How it works: the page is rendered on the server, after loading a persistent WebSocket connection is held between browser and server; on user action (click, input) the server recomputes state, calculates the minimum diff of changed HTML and sends it to the browser, which precisely updates the DOM. Result — SPA-level interactivity (live forms, on-the-fly validation, real-time updates, chats, dashboards), but all logic on the server, in one language, without a separate frontend application and without duplication of business logic between front and back. Why a killer feature: LiveView is especially good precisely on Elixir, because it relies on BEAM's strengths — holding a huge number of simultaneous WebSocket connections with minimal resources (one BEAM process per connection) and reacting instantly. For a backend engineer this means the ability to do a modern real-time UI without going into full SPA frontend development. LiveView — the main reason many choose Phoenix, and the de-facto UI standard in Elixir projects 2024–2026. Limitation — needs stable connection and low latency; for complex offline scenarios classic SPA may still be chosen.

When to choose Elixir over Go or Node.js?

Elixir / BEAM wins: (1) systems with massive simultaneous connections and per-connection state — chats, messengers, presence, notifications, multiplayer, real-time dashboards (the classic example — Discord serves millions of simultaneous users on Elixir). (2) When fault tolerance is critical — supervision trees and «let it crash» give reliability that's hard to replicate. (3) Real-time UI via Phoenix LiveView without a separate frontend. (4) Distributed systems — clustering is built into the platform. Go: easier to hire, better for CPU-bound and cloud-native / DevOps tooling, faster «cold» performance on number crunching, lower entry barrier. Node.js: single language front+back, huge market and ecosystem, good for I/O-bound APIs. The main downside of Elixir — not technical, but staffing: very narrow specialist market (both vacancies and candidates), functional paradigm + OTP require re-learning thinking. Strategy for CIS: Go or Node for market capacity and entry into the profession; Elixir — a conscious choice as a second language for a specific class of tasks (real-time, fault-tolerance) and for international remote with a shortage premium.

Elixir vs Erlang — what to learn in 2026?

Elixir and Erlang — two languages on the same BEAM virtual machine, fully compatible (from Elixir you can call any Erlang library and vice versa). The difference — in syntax and the ecosystem around them. Erlang — the original (since 1986, Ericsson): pragmatic, minimalist, specific Prolog-like syntax; used in telecom, messaging (WhatsApp historically — Erlang), infrastructure (RabbitMQ written in Erlang), in legacy systems. Elixir (since 2012, José Valim) — a modern language on the same BEAM: pleasant Ruby-like syntax, metaprogramming, powerful Mix build tool, rich modern ecosystem (Phoenix, LiveView, Ecto, Nx). What to learn: in 2026 the answer is almost unambiguous — learn Elixir. Practically all new vacancies, new projects, new content, conferences and community — around Elixir; it's Elixir that forms the labor market of the segment. Erlang should be learned «along the way» at the level of understanding — because OTP, supervision, processes, many libraries and the platform's mental model itself — that's Erlang under Elixir. Pure Erlang as a separate career goal makes sense to consider only for a specific niche (telecom, supporting large Erlang systems). Conclusion: write in Elixir — understand Erlang / OTP under the hood.

What share of jobs are remote?

Among jobs with a stated work format, 53% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.

How to start in Elixir in 2026?

Assumes backend experience in another language (Elixir is almost never taken as a first). The main difficulty of entry — not syntax, but paradigm shift: functional thinking (immutability, pattern matching, recursion instead of loops, pipe operator) and the process / OTP model. Roadmap: 1) Language — official getting-started guide at elixir-lang.org, book «Programming Elixir» (Dave Thomas), «Elixir in Action» (Saša Jurić — the best book on thinking in OTP). 2) Functional basics — pattern matching, immutability, pipe, work with collections (Enum / Stream). 3) Processes and OTP — spawn, message passing, then GenServer, Supervisor, supervision tree; this is the heart of Elixir, without it knowing the language is useless. 4) Mix — projects, dependencies, tests (ExUnit). 5) Ecto — schemas, changesets, queries to PostgreSQL. 6) Phoenix — routing, contexts, controllers. 7) Phoenix LiveView — mandatory for 2026. 8) End-to-end pet project: Phoenix application with LiveView UI + Ecto + PostgreSQL + GenServer for background logic + Oban + tests + deploy (Elixir releases / Docker). 9) Distribution — nodes, clustering. Resources: Saša Jurić's books, Pragmatic Studio courses (Elixir / LiveView — excellent), Exercism (Elixir track — free), Elixir Forum (very friendly community), Elixir Radar newsletter, ElixirConf talks on YouTube. A backend developer from another language masters productive Elixir in 4-8 months — most time goes to getting used to OTP thinking.

What skills does a Senior Elixir developer need?

Senior Elixir owns the language, BEAM platform and design of fault-tolerant concurrent systems. Functional thinking: immutability, pattern matching at the reflex level, function composition, proper recursion, conscious use of metaprogramming (macros — and understanding when NOT to apply them). OTP expertise: designing supervision trees and restart strategies, GenServer and its pitfalls (when a process becomes a bottleneck), GenStage / Broadway for back-pressure, proper decision «what should be a process and what — a regular module». BEAM: understanding of scheduler, process mailbox, ETS (in-memory tables), profiling, diagnosing production issues (observer, recon), memory management. Distribution: clustering (libcluster), inter-node communication, and understanding of its limitations (network partitions, consistency). Phoenix / LiveView: contexts, production-level design, LiveView under load. Ecto: changesets, complex queries, migrations, transactions, multi. PostgreSQL: advanced SQL, indexes, query plans. Testing: ExUnit, testing concurrent code, property-based (StreamData). Type safety: typespecs + Dialyzer. Observability: Telemetry, metrics, tracing. DevOps: Elixir releases, Docker, Kubernetes, hot-code-upgrade (rarely, but Senior must understand). Soft: code review, mentoring (Elixir newcomers struggle with OTP), communication with product. English for Senior+ — mandatory: the main Elixir market — international remote, without English it's inaccessible.

Leave a request

Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.

By submitting, you agree to the privacy policy.