Developer Relations: market
Data as of November 19, 2026: 346 open Developer Relations jobs, 50% remote among jobs that state a work format; median advertised salary $14,333/mo (from 57 postings that state a salary). Source: Zorky, updated daily.
DevRel (Developer Relations, Developer Advocate, Tech Evangelist) — a hybrid role at the boundary of engineering, content, community and marketing aimed at a developer audience. The main job is to build and maintain relationships with developers who use the company's product (developer tool, API, framework, cloud service). The role family: Developer Advocate (classic DevRel — outreach, content, conferences), Developer Evangelist (focused on promoting a technology, public speaking), Technical Writer on a DevRel team (documentation + tutorials), Developer Educator (courses, workshops). Working tools: GitHub (demo projects, contributions), YouTube and Twitch (video tutorials, live streams), Twitter/X + LinkedIn (content and community), dev.to / Medium / Habr (blog posts), Discord / Slack (community management), conferences (talks, workshops). Among jobs with a stated work format, 50% are remote.
Data as of:
Key numbers for the Developer Relations market: open jobs, median salary, observed talent pool and remote share.
The Developer Relations market currently has 346 open roles, 305 of them freshly observed. Median salary $14,333/mo.
Among jobs with a stated work format, 50% are remote. DevRel is global-remote by nature: content is created asynchronously, community runs 24/7. Conference travel 4-8 times a year with budget from the company.
⚠ salary known for 57 of 346 jobs; remote share from 304 with a stated format; 305 counted as fresh observations; trend and hiring difficulty are not shown
Timeline: postings and sources
How many Developer Relations postings appeared each week over 180 days, 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
| Period | New postings per week |
|---|---|
| 2026-06-01 | 10 |
| 2026-06-08 | 2 |
| 2026-06-15 | 1 |
| 2026-06-22 | 7 |
| 2026-06-29 | 22 |
| 2026-07-06 | 102 |
| 2026-07-13 | 22 |
| 2026-07-20 | 25 |
| 2026-07-27 | 20 |
| 2026-08-03 | 35 |
| 2026-08-10 | 18 |
| 2026-08-17 | 28 |
| 2026-08-24 | 14 |
| 2026-08-31 | 13 |
| 2026-09-07 | 18 |
| 2026-09-14 | 19 |
| 2026-09-21 | 56 |
| 2026-09-28 | 39 |
| 2026-10-05 | 35 |
| 2026-10-12 | 154 |
| 2026-10-19 | 57 |
| 2026-10-26 | 40 |
| 2026-11-02 | 63 |
| 2026-11-09 | 57 |
Active sources per week
Sources over the period: 73. ▲ — a week with a large batch of new sources.
Chart data
| Period | Active sources |
|---|---|
| 2026-06-01 | 5 |
| 2026-06-08 | 2 |
| 2026-06-15 | 1 |
| 2026-06-22 | 7 |
| 2026-06-29 | 5 |
| 2026-07-06 | 9 |
| 2026-07-13 | 9 |
| 2026-07-20 | 10 |
| 2026-07-27 | 9 |
| 2026-08-03 | 12 |
| 2026-08-10 | 7 |
| 2026-08-17 | 7 |
| 2026-08-24 | 5 |
| 2026-08-31 | 7 |
| 2026-09-07 | 9 |
| 2026-09-14 | 13 |
| 2026-09-21 | 13 |
| 2026-09-28 | 16 |
| 2026-10-05 | 12 |
| 2026-10-12 | 23 |
| 2026-10-19 | 19 |
| 2026-10-26 | 11 |
| 2026-11-02 | 17 |
| 2026-11-09 | 24 |
New sources connected: Jun 22 +7 · Jul 6 +6 · Jul 13 +5 · Sep 14 +5 · Oct 12 +7 · Nov 9 +7 · all weeks (20) in the table
| Week | New sources | New postings |
|---|---|---|
| Jun 15 | +1 | 1 |
| Jun 22 | +7 | 7 |
| Jul 6 | +6 | 102 |
| Jul 13 | +5 | 22 |
| Jul 20 | +2 | 25 |
| Jul 27 | +2 | 20 |
| Aug 3 | +1 | 35 |
| Aug 10 | +2 | 18 |
| Aug 17 | +2 | 28 |
| Aug 24 | +1 | 14 |
| Aug 31 | +2 | 13 |
| Sep 7 | +1 | 18 |
| Sep 14 | +5 | 19 |
| Sep 21 | +4 | 56 |
| Sep 28 | +4 | 39 |
| Oct 5 | +2 | 35 |
| Oct 12 | +7 | 154 |
| Oct 19 | +4 | 57 |
| Nov 2 | +3 | 63 |
| Nov 9 | +7 | 57 |
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, 180 days; sources = distinct collection channels that yielded postings for the direction that week; new sources = channels that yielded their first posting for the direction that week.
Chart data
| Week | New postings per week | Active sources |
|---|---|---|
| 2026-06-01 | 10 | 5 |
| 2026-06-08 | 2 | 2 |
| 2026-06-15 | 1 | 1 |
| 2026-06-22 | 7 | 7 |
| 2026-06-29 | 22 | 5 |
| 2026-07-06 | 102 | 9 |
| 2026-07-13 | 22 | 9 |
| 2026-07-20 | 25 | 10 |
| 2026-07-27 | 20 | 9 |
| 2026-08-03 | 35 | 12 |
| 2026-08-10 | 18 | 7 |
| 2026-08-17 | 28 | 7 |
| 2026-08-24 | 14 | 5 |
| 2026-08-31 | 13 | 7 |
| 2026-09-07 | 18 | 9 |
| 2026-09-14 | 19 | 13 |
| 2026-09-21 | 56 | 13 |
| 2026-09-28 | 39 | 16 |
| 2026-10-05 | 35 | 12 |
| 2026-10-12 | 154 | 23 |
| 2026-10-19 | 57 | 19 |
| 2026-10-26 | 40 | 11 |
| 2026-11-02 | 63 | 17 |
| 2026-11-09 | 57 | 24 |
Salaries over time
Median Developer Relations salary per week, USD per month.
Median salary, USD per month
Chart data
| Period | Median | Postings with a salary per week (n) |
|---|---|---|
| 2026-10-19 | 15,625 | 21 |
| 2026-10-26 | — | 7 |
| 2026-11-02 | 11,167 | 19 |
| 2026-11-09 | 14,210 | 12 |
The series starts on Oct 19: there is no data before that.
Only postings with a USD salary and a known period (month or year), $500–$50,000 per month. Weeks with fewer than 10 such postings are left blank — that means no data, not zero.
Chart data
| Week | Median |
|---|---|
| 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-12 | — |
| 2026-10-19 | 15,625 |
| 2026-10-26 | — |
| 2026-11-02 | 11,167 |
| 2026-11-09 | 14,210 |
Remote work over time
Share of Developer Relations postings offering fully remote work, per week.
Remote postings, %
Chart data
| Period | Remote |
|---|---|
| 2026-06-29 | 61.1 |
| 2026-07-06 | 59.4 |
| 2026-07-13 | 33.3 |
| 2026-07-20 | 60 |
| 2026-07-27 | — |
| 2026-08-03 | 33.3 |
| 2026-08-10 | — |
| 2026-08-17 | 41.7 |
| 2026-08-24 | — |
| 2026-08-31 | — |
| 2026-09-07 | 66.7 |
| 2026-09-14 | 53.3 |
| 2026-09-21 | 35.3 |
| 2026-09-28 | 73.7 |
| 2026-10-05 | 58.8 |
| 2026-10-12 | 55.9 |
| 2026-10-19 | 54.5 |
| 2026-10-26 | 68.4 |
| 2026-11-02 | 63.2 |
| 2026-11-09 | 73.2 |
The series starts on Jun 29: 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
| Week | Remote |
|---|---|
| 2026-06-01 | — |
| 2026-06-08 | — |
| 2026-06-15 | — |
| 2026-06-22 | — |
| 2026-06-29 | 61.1 |
| 2026-07-06 | 59.4 |
| 2026-07-13 | 33.3 |
| 2026-07-20 | 60 |
| 2026-07-27 | — |
| 2026-08-03 | 33.3 |
| 2026-08-10 | — |
| 2026-08-17 | 41.7 |
| 2026-08-24 | — |
| 2026-08-31 | — |
| 2026-09-07 | 66.7 |
| 2026-09-14 | 53.3 |
| 2026-09-21 | 35.3 |
| 2026-09-28 | 73.7 |
| 2026-10-05 | 58.8 |
| 2026-10-12 | 55.9 |
| 2026-10-19 | 54.5 |
| 2026-10-26 | 68.4 |
| 2026-11-02 | 63.2 |
| 2026-11-09 | 73.2 |
Technologies over time
How the share of Developer Relations postings mentioning each of the top technologies changed.
Postings mentioning the technology, %
Chart data
| Period | cloud | llm | Python |
|---|---|---|---|
| 2026-08-17 | 20 | 0 | 0 |
| 2026-08-24 | — | — | — |
| 2026-08-31 | — | — | — |
| 2026-09-07 | — | — | — |
| 2026-09-14 | — | — | — |
| 2026-09-21 | 24.1 | 17.2 | 6.9 |
| 2026-09-28 | 32.1 | 14.3 | 17.9 |
| 2026-10-05 | 35 | 15 | 25 |
| 2026-10-12 | 27.3 | 10.1 | 16.2 |
| 2026-10-19 | 41.2 | 35.3 | 32.4 |
| 2026-10-26 | 30.4 | 26.1 | 8.7 |
| 2026-11-02 | 33.3 | 28.6 | 16.7 |
| 2026-11-09 | 50 | 41.7 | 22.2 |
The series starts on Aug 17: there is no data before that.
Share among postings with a tagged stack; the series starts on Aug 10: earlier stack tags were assigned differently. Weeks with fewer than 20 tagged postings are left blank.
Chart data
| Week | cloud | llm | Python | TypeScript | JavaScript |
|---|---|---|---|---|---|
| 2026-08-10 | — | — | — | — | — |
| 2026-08-17 | 20 | 0 | 0 | 0 | 0 |
| 2026-08-24 | — | — | — | — | — |
| 2026-08-31 | — | — | — | — | — |
| 2026-09-07 | — | — | — | — | — |
| 2026-09-14 | — | — | — | — | — |
| 2026-09-21 | 24.1 | 17.2 | 6.9 | 3.4 | 3.4 |
| 2026-09-28 | 32.1 | 14.3 | 17.9 | 0 | 3.6 |
| 2026-10-05 | 35 | 15 | 25 | 0 | 15 |
| 2026-10-12 | 27.3 | 10.1 | 16.2 | 5.1 | 11.1 |
| 2026-10-19 | 41.2 | 35.3 | 32.4 | 8.8 | 5.9 |
| 2026-10-26 | 30.4 | 26.1 | 8.7 | 4.3 | 8.7 |
| 2026-11-02 | 33.3 | 28.6 | 16.7 | 16.7 | 11.9 |
| 2026-11-09 | 50 | 41.7 | 22.2 | 13.9 | 8.3 |
Countries over time
How the share of Developer Relations postings in each of the top countries changed, per week.
Postings in the country, %
Chart data
| Period | USA | UK | Poland |
|---|---|---|---|
| 2026-07-06 | 59.3 | 5.1 | 0 |
| 2026-07-13 | — | — | — |
| 2026-07-20 | — | — | — |
| 2026-07-27 | — | — | — |
| 2026-08-03 | 63 | 11.1 | 0 |
| 2026-08-10 | — | — | — |
| 2026-08-17 | 80 | 4 | 0 |
| 2026-08-24 | — | — | — |
| 2026-08-31 | — | — | — |
| 2026-09-07 | — | — | — |
| 2026-09-14 | — | — | — |
| 2026-09-21 | 82 | 2 | 2 |
| 2026-09-28 | 53.8 | 15.4 | 3.8 |
| 2026-10-05 | 57.1 | 3.6 | 3.6 |
| 2026-10-12 | 43.8 | 13.5 | 5.6 |
| 2026-10-19 | 62 | 6 | 4 |
| 2026-10-26 | 50 | 18.8 | 6.2 |
| 2026-11-02 | 37.8 | 11.1 | 24.4 |
| 2026-11-09 | 47.6 | 11.9 | 14.3 |
The series starts on Jul 6: there is no data before that.
Share among postings with a known country; the chart shows the five countries with the most postings over six months. Weeks with fewer than 20 postings with a known country are left blank. A rising share can mean a newly connected source in that country rather than market growth.
Chart data
| Week | USA | UK | Poland | Canada | India |
|---|---|---|---|---|---|
| 2026-06-01 | — | — | — | — | — |
| 2026-06-08 | — | — | — | — | — |
| 2026-06-15 | — | — | — | — | — |
| 2026-06-22 | — | — | — | — | — |
| 2026-06-29 | — | — | — | — | — |
| 2026-07-06 | 59.3 | 5.1 | 0 | 3.4 | 5.1 |
| 2026-07-13 | — | — | — | — | — |
| 2026-07-20 | — | — | — | — | — |
| 2026-07-27 | — | — | — | — | — |
| 2026-08-03 | 63 | 11.1 | 0 | 3.7 | 7.4 |
| 2026-08-10 | — | — | — | — | — |
| 2026-08-17 | 80 | 4 | 0 | 4 | 0 |
| 2026-08-24 | — | — | — | — | — |
| 2026-08-31 | — | — | — | — | — |
| 2026-09-07 | — | — | — | — | — |
| 2026-09-14 | — | — | — | — | — |
| 2026-09-21 | 82 | 2 | 2 | 0 | 2 |
| 2026-09-28 | 53.8 | 15.4 | 3.8 | 0 | 3.8 |
| 2026-10-05 | 57.1 | 3.6 | 3.6 | 10.7 | 0 |
| 2026-10-12 | 43.8 | 13.5 | 5.6 | 3.4 | 5.6 |
| 2026-10-19 | 62 | 6 | 4 | 8 | 6 |
| 2026-10-26 | 50 | 18.8 | 6.2 | 0 | 0 |
| 2026-11-02 | 37.8 | 11.1 | 24.4 | 2.2 | 2.2 |
| 2026-11-09 | 47.6 | 11.9 | 14.3 | 7.1 | 2.4 |
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 Developer Relations.
Hiring index, Oct 16 = 100
Chart data
| Period | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.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
| Day | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
How many open Developer Relations jobs there are and how many matching specialists Zorky observes.
Demand and observed supply
Chart data
| Metric | Value |
|---|---|
| Open demand | 346 |
| Open demand | 346 |
| Observed supply | — not published |
Over recent weeks the DevRel direction has produced a small but steady flow of new openings — the most niche role in IT marketing. Fluctuations are normal.
⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown
How salaries in Developer Relations jobs are distributed, in US dollars per month.
Salary distribution
Chart data
| Metric | Value |
|---|---|
| <$1k | 0 |
| $1–2k | 1 |
| $2–3k | 1 |
| $3–4k | 4 |
| $4–5k | 2 |
| $5–6k | 0 |
| $6–7k | 2 |
| $7–8k | 1 |
| $8–9k | 0 |
| $9–10k | 1 |
| $10–12k | 6 |
| $12–15k | 15 |
| $15–20k | 19 |
| $20k+ | 5 |
- usable for the calculation: 57 (16.5%)
- stated but not converted to USD/month: 46 (13.3%)
- not stated: 243 (70.2%)
One in ten postings offers under $3,750, one in ten over $19,645. Half of the postings offer between $11,083 and $16,666. Sample: 57.
Chart data
| Metric | Lower bound | Upper bound | Count |
|---|---|---|---|
| <$1k | 0 | 1,000 | 0 |
| $1–2k | 1,000 | 2,000 | 1 |
| $2–3k | 2,000 | 3,000 | 1 |
| $3–4k | 3,000 | 4,000 | 4 |
| $4–5k | 4,000 | 5,000 | 2 |
| $5–6k | 5,000 | 6,000 | 0 |
| $6–7k | 6,000 | 7,000 | 2 |
| $7–8k | 7,000 | 8,000 | 1 |
| $8–9k | 8,000 | 9,000 | 0 |
| $9–10k | 9,000 | 10,000 | 1 |
| $10–12k | 10,000 | 12,000 | 6 |
| $12–15k | 12,000 | 15,000 | 15 |
| $15–20k | 15,000 | 20,000 | 19 |
| $20k+ | 20,000 | — | 5 |
Which countries have the most open Developer Relations jobs.
Demand geography
| country | jobs | share |
|---|---|---|
| United States | 163 | 57.8% |
| United Kingdom | 21 | 7.4% |
| Poland | 15 | 5.3% |
| Germany | 13 | 4.6% |
| Canada | 9 | 3.2% |
| India | 9 | 3.2% |
| Singapore | 6 | 2.1% |
| Netherlands | 6 | 2.1% |
| France | 4 | 1.4% |
| Ireland | 3 | 1.1% |
| Other countries | 33 | 11.7% |
The leader by DevRel job count is US (163 positions). Most Russian-speaking DevRel work for international dev-tool companies on remote — English C1+ opens the global market.
⚠ job counts only: salary by country is not published
Chart data
| Country | Jobs |
|---|---|
| US | 163 |
| GB | 21 |
| PL | 15 |
| DE | 13 |
| CA | 9 |
| IN | 9 |
| SG | 6 |
| NL | 6 |
| FR | 4 |
| IE | 3 |
Which technologies are most often required in the same job as Developer Relations.
Used together with
Share — how many of the 346 jobs in the Developer Relations 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 DevRel tools: GitHub (demos + OSS contributions), YouTube/Twitch (video and live-coding), Twitter/X + LinkedIn (content), dev.to/Medium/Habr (blog), Discord/Slack (community), Sessionize (conference CFPs). Engineering stack = the company's product stack.
The most common combinations in DevRel jobs: GitHub + YouTube, Twitter + blog, Discord + Slack for community, Sessionize + Notion for talk prep. A Senior DevRel owns 5-7 tools confidently.
Chart data
| Name | Count |
|---|---|
| cloud | 80 |
| llm | 60 |
| python | 48 |
| typescript | 26 |
| javascript | 24 |
| aws | 20 |
| go | 15 |
| azure | 15 |
| java | 11 |
| blockchain | 11 |
| kubernetes | 10 |
| react | 9 |
How many Developer Relations jobs there are at each level, from junior to principal.
Demand by grade
| grade | jobs |
|---|---|
| senior | 76 |
| lead | 35 |
| principal | 23 |
| middle | 7 |
| junior | 6 |
DevRel is NOT an entry role: the market expects 3-5 years of engineering experience + a community presence.
⚠ demand side only: the grade of the observed pool is unknown for most of it
Chart data
| Level | Count |
|---|---|
| senior | 76 |
| lead | 35 |
| principal | 23 |
| middle | 7 |
| junior | 6 |
Who hires the most for Developer Relations and how concentrated demand is among the largest companies.
Employers
Demand is spread across 211 employers. The largest accounts for 7.5%, the top ten for 19.7%; the remaining 80.3% is long tail.
| share | value |
|---|---|
| top-1 | 7.5% |
| top-3 | 10.6% |
| top-10 | 19.7% |
| long tail | 80.3% |
⚠ 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 Developer Relations jobs from.
Where Zorky sees this market
Observed across 45 sources; the largest accounts for 24.6% — this market does not rest on a single channel.
DevRel jobs surface across most major sources: web parsers (HH, Habr Career, Djinni, DOU, NoFluffJobs, JustJoin.it) + dedicated platforms (DevRel Collective, DevRelX Jobs). Telegram channels add announcements from international tool companies.
Chart data
| Class | Name | English name | Count | Share |
|---|---|---|---|---|
| ats | ATS и карьерные сайты | ATS & career sites | 259 | 0.7486 |
| board | джоб-борды и агрегаторы | job boards & aggregators | 71 | 0.2052 |
| telegram | Telegram | Telegram | 16 | 0.0462 |
The newest Developer Relations jobs from company career sites.
Recent openings
- Technical Solutions Engineer · US
- Developer Relations Engineer
- Senior Developer Relations Manager, EMEA AI Natives DACH · DE · $16,221
- Developer Advocate, Lune · US
- Senior Systems Engineer, Workers Authoring & Testing; Frameworks · $18,292
- Manager, EMEA Demand Generation · IE
- Developers and Creations Lead, YouTube · US
- Developer Relations, Platform · US
Latest open DevRel jobs — the most recent 10 positions with adequate description quality. The full list is available in our CRM or via the "see all" link below.
Adjacent markets
DevRel is the most niche IT marketing role, but a consistently high-paying one at international developer-tool companies. Click any direction's bar for a detailed comparison.
⚠ adjacent markets for comparison are not defined yet
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: 8.
Specializations
DevRel breaks down into 2 main sub-specialisations: Developer Advocate (classic DevRel — outreach, content, conferences) and Developer Evangelist / Tech Evangelist (focused on promoting a technology, public speaking). Plus adjacent roles: Technical Writer on a DevRel team, Developer Educator (courses).
Frequently asked questions
The most common questions about the DevRel market: pay by level, tools (GitHub/YouTube/Twitter/Discord), skills (engineering + speaking + writing + community), DevRel vs Tech Writer vs Marketing vs Engineering, remote, how to become one (after Senior Engineer + portfolio), Senior skills. Answers recompute automatically.
What tools does DevRel use?
The DevRel stack is hybrid: dev tools + content tools + community platforms. Code & demos: GitHub (demo repos, OSS contributions), Replit (live-coding demos), CodeSandbox. Content: dev.to, Medium, Habr (Russian-speaking audience), HashNode, personal blog on Vercel/Netlify. Video: YouTube (tutorials, talks), Twitch (live-coding), OBS Studio for recording, Camtasia/Final Cut for editing. Social: Twitter/X (the de-facto DevRel channel), LinkedIn, Mastodon/Bluesky (growing trends). Community: Discord, Slack communities, GitHub Discussions, Reddit AMA. Analytics: GA4, Plausible, Twitter Analytics, YouTube Analytics, GitHub Insights. Conferences: Sessionize for CFP management, Notion for talk prep. Presentation: Keynote, slidev (Markdown-based), Figma for slide design.
What skills does a Developer Advocate need?
DevRel requires a unique combination of engineering and communication skills. Engineering (must-have): a confident Senior level in the product's stack (usually one backend language + frontend basics + one cloud). Without technical depth DevRel = just marketing. Public speaking: ability to present to 100–2000+ developers at conferences, do live-coding demos without freezing under stress. Technical writing: clear tutorials, 5-15 minute reads, blog posts, documentation. Video production: recording + editing tutorials on YouTube, live streams on Twitch. Community management: running Discord/Slack, responding to GitHub Issues, moderation. Empathy for developers: understanding the pain points of the target audience (backend devs vs frontend vs DevOps need different angles). English C1+ — mandatory for international (most DevRel jobs are global). Metrics: reading DAA, MAU, conversion funnels.
What share of jobs are remote?
Among jobs with a stated work format, 50% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.
How is DevRel different from Technical Writing, Marketing, and Engineering?
DevRel is a hybrid of all three with a focus on developer audience activation. Metrics: DAA (Developer Audience Activation), community growth, content reach. Technical Writer — a narrow role: creating documentation, reference docs, tutorials. Less outreach. Marketing (B2B SaaS) — focused on lead generation and conversion, not on developer relationships. Metrics: MQL, CAC, conversion rate. Engineering — focused on product code, not on communication with users. By pay: Senior DevRel ≈ Senior Engineer > Senior Technical Writer > Senior B2B Marketer. DevRel combines engineering credibility with content/community skills. Product Marketing Manager (PMM) at developer-tool companies is sometimes close to DevRel (especially at startup stage when one role covers both functions).
Where to start to become a Developer Advocate in 2026?
DevRel is NOT an accessible entry role. You need 3-5 years of engineering experience + a notable community presence. The optimal path: 1) Become a Senior Backend/Frontend/DevOps. 2) Start a blog (dev.to, Medium, Habr) — 10-20 serious posts over 12-18 months. 3) Build a Twitter/X with 2K-5K technical followers. 4) Speak at 3-5 meetups locally, then apply to international conferences (Sessionize opens CFPs). 5) Open-source contributions to the target company's product or a crowd favourite (React, Vue, Next.js). 6) Apply for Junior/Middle Developer Advocate with a ready portfolio (blog + talks + GitHub). Books: "Developer Marketing Does Not Exist" (the DevRel book), "The Business Value of Developer Relations" (Mary Thengvall), DevRel.Agency blog. English C1+ — must-have. Courses: DevRel Foundations on CodeSchool.
How many open jobs are in this sample?
The published sample contains 346 open jobs after merging reposts. This is the same count shown in the main indicator. The geography section describes the sample coverage; this is not an estimate of the entire market.
Where do DevRel earn more — in Russia or at international tool companies?
Cyprus — a growing hub for Russian-speaking DevRel relocants on international pay. The main driver — English C1+ + a strong community presence (Twitter followers, blog reach, conference talks).
What skills does a Senior Developer Advocate need?
Senior DA — the full DevRel-function stack + ownership of strategy. Engineering depth: Senior level in the company's product stack (without this DevRel = just marketing). Content production at scale: 1-2 blog posts per month + 1-2 YouTube videos + regular talks. Public speaking: 6-12 conference talks per year (KubeCon, JS Conf, GopherCon, regional meetups). Community management: running Discord/Slack with 1K+ members, GitHub Issues triage. Strategy: designing DevRel programmes (workshops, hackathons, beta programmes), metrics (DAA, community growth, content reach). Cross-functional: collaboration with PMM (product marketing) on launches, with Sales on enterprise outreach, with Engineering on product feedback from community. English C1+ for international content and talks. Mentoring junior advocates. Travel readiness: 4-8 trips per year to conferences.
Leave a request
Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.