Ruby on Rails: market
Data as of November 19, 2026: 188 open Ruby on Rails jobs, 64% remote among jobs that state a work format; median advertised salary $6,467/mo (from 18 postings that state a salary). Source: Zorky, updated daily.
Ruby on Rails — backend development in the Ruby language with the Ruby on Rails framework: product web development with emphasis on product speed (developer happiness, convention over configuration). A mature segment with a steady «second youth» 2024–2026 — the so-called Rails renaissance: Rails 7 / 8, Hotwire (interactive UI almost without writing JavaScript), the course toward «majestic monolith» (a powerful monolith instead of microservices by default), the Solid Queue / Solid Cache / Solid Cable stack (removes mandatory Redis dependency), deploy via Kamal, «No Build» asset approach. Role family: Ruby on Rails Developer (general — full-cycle product development), Ruby Backend Engineer (APIs and services), Senior / Staff Rails Engineer (architecture of a large monolith, performance), Rails + Hotwire fullstack (see also /research/fullstack/rails-fullstack). Stack 2026: Ruby 3.x (must — 3.3 / 3.4, YJIT JIT compiler), Rails 7 / 8, Hotwire (Turbo + Stimulus — UI dominator 2024–2026), PostgreSQL, Sidekiq or Solid Queue (background jobs), Redis, RSpec / Minitest (tests), Puma (server), Devise (authentication), ViewComponent, Sidekiq, Sorbet / RBS (static typing — growing), graphql-ruby or REST API, Kamal (deploy), Docker + Kubernetes. Top stack: ruby, rails, ci/cd, postgresql, docker. Among jobs with a stated work format, 64% are remote. Ruby — a niche segment in CIS with a small pool of developers, but Ruby engineers are paid well due to the shortage, and the international remote market is wide and premium.
Data as of:
Key numbers for the Ruby on Rails market: open jobs, median salary, observed talent pool and remote share.
The Ruby on Rails market currently has 188 open roles, 156 of them freshly observed. Median salary $6,467/mo.
Among jobs with a stated work format, 64% are remote. Ruby — one of the most remote-friendly stacks (legacy of 37signals — pioneers of «remote by default»).
⚠ salary known for 18 of 188 jobs; remote share from 154 with a stated format; 156 counted as fresh observations; trend and hiring difficulty are not shown
Timeline: postings and sources
How many Ruby on Rails 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
| Period | New postings per week |
|---|---|
| 2026-06-01 | 4 |
| 2026-06-08 | 7 |
| 2026-06-15 | 7 |
| 2026-06-22 | 18 |
| 2026-06-29 | 36 |
| 2026-07-06 | 27 |
| 2026-07-13 | 34 |
| 2026-07-20 | 37 |
| 2026-07-27 | 15 |
| 2026-08-03 | 19 |
| 2026-08-10 | 40 |
| 2026-08-17 | 21 |
| 2026-08-24 | 17 |
| 2026-08-31 | 14 |
| 2026-09-07 | 13 |
| 2026-09-14 | 18 |
| 2026-09-21 | 39 |
| 2026-09-28 | 25 |
| 2026-10-05 | 23 |
| 2026-10-12 | 126 |
| 2026-10-19 | 47 |
| 2026-10-26 | 43 |
| 2026-11-02 | 30 |
| 2026-11-09 | 25 |
Active sources per week
Sources over the period: 106. ▲ — a week with a large batch of new sources.
Chart data
| Period | Active sources |
|---|---|
| 2026-06-01 | 3 |
| 2026-06-08 | 5 |
| 2026-06-15 | 5 |
| 2026-06-22 | 8 |
| 2026-06-29 | 18 |
| 2026-07-06 | 12 |
| 2026-07-13 | 20 |
| 2026-07-20 | 20 |
| 2026-07-27 | 11 |
| 2026-08-03 | 11 |
| 2026-08-10 | 15 |
| 2026-08-17 | 12 |
| 2026-08-24 | 11 |
| 2026-08-31 | 10 |
| 2026-09-07 | 10 |
| 2026-09-14 | 10 |
| 2026-09-21 | 17 |
| 2026-09-28 | 17 |
| 2026-10-05 | 15 |
| 2026-10-12 | 18 |
| 2026-10-19 | 22 |
| 2026-10-26 | 17 |
| 2026-11-02 | 18 |
| 2026-11-09 | 19 |
New sources connected: Jun 29 +13 · Jul 20 +9 · all weeks (23) in the table
| Week | New sources | New postings |
|---|---|---|
| Jun 8 | +3 | 7 |
| Jun 15 | +4 | 7 |
| Jun 22 | +6 | 18 |
| Jun 29 | +13 | 36 |
| Jul 6 | +7 | 27 |
| Jul 13 | +7 | 34 |
| Jul 20 | +9 | 37 |
| Jul 27 | +2 | 15 |
| Aug 3 | +4 | 19 |
| Aug 10 | +2 | 40 |
| Aug 17 | +4 | 21 |
| Aug 24 | +3 | 17 |
| Aug 31 | +2 | 14 |
| Sep 7 | +3 | 13 |
| Sep 14 | +2 | 18 |
| Sep 21 | +4 | 39 |
| Sep 28 | +2 | 25 |
| Oct 5 | +3 | 23 |
| Oct 12 | +5 | 126 |
| Oct 19 | +5 | 47 |
| Oct 26 | +2 | 43 |
| Nov 2 | +5 | 30 |
| Nov 9 | +6 | 25 |
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
| Week | New postings per week | Active sources |
|---|---|---|
| 2026-06-01 | 4 | 3 |
| 2026-06-08 | 7 | 5 |
| 2026-06-15 | 7 | 5 |
| 2026-06-22 | 18 | 8 |
| 2026-06-29 | 36 | 18 |
| 2026-07-06 | 27 | 12 |
| 2026-07-13 | 34 | 20 |
| 2026-07-20 | 37 | 20 |
| 2026-07-27 | 15 | 11 |
| 2026-08-03 | 19 | 11 |
| 2026-08-10 | 40 | 15 |
| 2026-08-17 | 21 | 12 |
| 2026-08-24 | 17 | 11 |
| 2026-08-31 | 14 | 10 |
| 2026-09-07 | 13 | 10 |
| 2026-09-14 | 18 | 10 |
| 2026-09-21 | 39 | 17 |
| 2026-09-28 | 25 | 17 |
| 2026-10-05 | 23 | 15 |
| 2026-10-12 | 126 | 18 |
| 2026-10-19 | 47 | 22 |
| 2026-10-26 | 43 | 17 |
| 2026-11-02 | 30 | 18 |
| 2026-11-09 | 25 | 19 |
Remote work over time
Share of Ruby on Rails postings offering fully remote work, per week.
Remote postings, %
Chart data
| Period | Remote |
|---|---|
| 2026-06-22 | 66.7 |
| 2026-06-29 | 54.8 |
| 2026-07-06 | 65.2 |
| 2026-07-13 | 76.9 |
| 2026-07-20 | 65.5 |
| 2026-07-27 | 84.6 |
| 2026-08-03 | 82.4 |
| 2026-08-10 | 81.1 |
| 2026-08-17 | 50 |
| 2026-08-24 | 53.3 |
| 2026-08-31 | 66.7 |
| 2026-09-07 | 50 |
| 2026-09-14 | 56.2 |
| 2026-09-21 | 70.4 |
| 2026-09-28 | 73.9 |
| 2026-10-05 | 81 |
| 2026-10-12 | 59 |
| 2026-10-19 | 54.8 |
| 2026-10-26 | 76.9 |
| 2026-11-02 | 56 |
| 2026-11-09 | 61.9 |
The series starts on Jun 22: 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 | 66.7 |
| 2026-06-29 | 54.8 |
| 2026-07-06 | 65.2 |
| 2026-07-13 | 76.9 |
| 2026-07-20 | 65.5 |
| 2026-07-27 | 84.6 |
| 2026-08-03 | 82.4 |
| 2026-08-10 | 81.1 |
| 2026-08-17 | 50 |
| 2026-08-24 | 53.3 |
| 2026-08-31 | 66.7 |
| 2026-09-07 | 50 |
| 2026-09-14 | 56.2 |
| 2026-09-21 | 70.4 |
| 2026-09-28 | 73.9 |
| 2026-10-05 | 81 |
| 2026-10-12 | 59 |
| 2026-10-19 | 54.8 |
| 2026-10-26 | 76.9 |
| 2026-11-02 | 56 |
| 2026-11-09 | 61.9 |
Technologies over time
How the share of Ruby on Rails postings mentioning each of the top technologies changed.
Postings mentioning the technology, %
Chart data
| Period | ruby | Rails | cloud |
|---|---|---|---|
| 2026-08-10 | 95 | 75 | 2.5 |
| 2026-08-17 | 95.2 | 71.4 | 9.5 |
| 2026-08-24 | — | — | — |
| 2026-08-31 | — | — | — |
| 2026-09-07 | — | — | — |
| 2026-09-14 | — | — | — |
| 2026-09-21 | 89.5 | 78.9 | 18.4 |
| 2026-09-28 | 84 | 68 | 28 |
| 2026-10-05 | 100 | 81.8 | 27.3 |
| 2026-10-12 | 91.1 | 82.3 | 7.3 |
| 2026-10-19 | 95.5 | 72.7 | 9.1 |
| 2026-10-26 | 82.9 | 58.5 | 26.8 |
| 2026-11-02 | 84.6 | 65.4 | 23.1 |
| 2026-11-09 | 82.6 | 60.9 | 8.7 |
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 | ruby | Rails | PostgreSQL | JavaScript | cloud |
|---|---|---|---|---|---|
| 2026-08-10 | 95 | 75 | 2.5 | 2.5 | 2.5 |
| 2026-08-17 | 95.2 | 71.4 | 0 | 0 | 9.5 |
| 2026-08-24 | — | — | — | — | — |
| 2026-08-31 | — | — | — | — | — |
| 2026-09-07 | — | — | — | — | — |
| 2026-09-14 | — | — | — | — | — |
| 2026-09-21 | 89.5 | 78.9 | 7.9 | 10.5 | 18.4 |
| 2026-09-28 | 84 | 68 | 12 | 12 | 28 |
| 2026-10-05 | 100 | 81.8 | 4.5 | 36.4 | 27.3 |
| 2026-10-12 | 91.1 | 82.3 | 22.6 | 20.2 | 7.3 |
| 2026-10-19 | 95.5 | 72.7 | 11.4 | 25 | 9.1 |
| 2026-10-26 | 82.9 | 58.5 | 24.4 | 9.8 | 26.8 |
| 2026-11-02 | 84.6 | 65.4 | 7.7 | 19.2 | 23.1 |
| 2026-11-09 | 82.6 | 60.9 | 0 | 8.7 | 8.7 |
Countries over time
How the share of Ruby on Rails postings in each of the top countries changed, per week.
Postings in the country, %
Chart data
| Period | USA | Poland | Russia |
|---|---|---|---|
| 2026-06-29 | 8 | 32 | 20 |
| 2026-07-06 | 15 | 30 | 10 |
| 2026-07-13 | 21.7 | 34.8 | 17.4 |
| 2026-07-20 | 6.2 | 43.8 | 12.5 |
| 2026-07-27 | — | — | — |
| 2026-08-03 | — | — | — |
| 2026-08-10 | 30.8 | 7.7 | 34.6 |
| 2026-08-17 | — | — | — |
| 2026-08-24 | — | — | — |
| 2026-08-31 | — | — | — |
| 2026-09-07 | — | — | — |
| 2026-09-14 | — | — | — |
| 2026-09-21 | 42.9 | 19 | 0 |
| 2026-09-28 | — | — | — |
| 2026-10-05 | — | — | — |
| 2026-10-12 | 23.6 | 8.3 | 1.4 |
| 2026-10-19 | 25.7 | 20 | 11.4 |
| 2026-10-26 | 17.2 | 3.4 | 0 |
| 2026-11-02 | 0 | 9.5 | 4.8 |
| 2026-11-09 | — | — | — |
The series starts on Jun 29: 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 | Poland | Russia | UK | Germany |
|---|---|---|---|---|---|
| 2026-06-01 | — | — | — | — | — |
| 2026-06-08 | — | — | — | — | — |
| 2026-06-15 | — | — | — | — | — |
| 2026-06-22 | — | — | — | — | — |
| 2026-06-29 | 8 | 32 | 20 | 16 | 8 |
| 2026-07-06 | 15 | 30 | 10 | 0 | 5 |
| 2026-07-13 | 21.7 | 34.8 | 17.4 | 8.7 | 0 |
| 2026-07-20 | 6.2 | 43.8 | 12.5 | 9.4 | 0 |
| 2026-07-27 | — | — | — | — | — |
| 2026-08-03 | — | — | — | — | — |
| 2026-08-10 | 30.8 | 7.7 | 34.6 | 7.7 | 0 |
| 2026-08-17 | — | — | — | — | — |
| 2026-08-24 | — | — | — | — | — |
| 2026-08-31 | — | — | — | — | — |
| 2026-09-07 | — | — | — | — | — |
| 2026-09-14 | — | — | — | — | — |
| 2026-09-21 | 42.9 | 19 | 0 | 9.5 | 0 |
| 2026-09-28 | — | — | — | — | — |
| 2026-10-05 | — | — | — | — | — |
| 2026-10-12 | 23.6 | 8.3 | 1.4 | 9.7 | 11.1 |
| 2026-10-19 | 25.7 | 20 | 11.4 | 8.6 | 0 |
| 2026-10-26 | 17.2 | 3.4 | 0 | 6.9 | 3.4 |
| 2026-11-02 | 0 | 9.5 | 4.8 | 0 | 9.5 |
| 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 Ruby on Rails.
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 Ruby on Rails jobs there are and how many matching specialists Zorky observes.
Demand and observed supply
Chart data
| Metric | Value |
|---|---|
| Open demand | 188 |
| Open demand | 188 |
| Observed supply | — not published |
Ruby — a niche but stable backend segment experiencing a «second youth» (Rails renaissance 2024–2026): Rails 7 / 8, Hotwire, Solid stack, Kamal. Drivers: Rails remains the fastest way to bring a product to prod — the choice of product startups. Demand is pointed: few vacancies, but staff shortage keeps salaries high. The main growth — international full-remote.
⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown
How salaries in Ruby on Rails jobs are distributed, in US dollars per month.
Salary distribution
Chart data
| Metric | Value |
|---|---|
| <$1k | 0 |
| $1–2k | 0 |
| $2–3k | 2 |
| $3–4k | 2 |
| $4–5k | 2 |
| $5–6k | 0 |
| $6–7k | 3 |
| $7–8k | 0 |
| $8–9k | 2 |
| $9–10k | 1 |
| $10–12k | 2 |
| $12–15k | 1 |
| $15–20k | 3 |
| $20k+ | 0 |
- usable for the calculation: 18 (9.6%)
- stated but not converted to USD/month: 21 (11.2%)
- not stated: 149 (79.3%)
One in ten postings offers under $2,175, one in ten over $16,391. Half of the postings offer between $4,374 and $11,333. Sample: 18.
Due to the developer shortage, the segment is paid above the backend average at the same grade.
⚠ percentiles from 18 salaries out of 188 jobs — a guide on a small sample
Chart data
| Metric | Lower bound | Upper bound | Count |
|---|---|---|---|
| <$1k | 0 | 1,000 | 0 |
| $1–2k | 1,000 | 2,000 | 0 |
| $2–3k | 2,000 | 3,000 | 2 |
| $3–4k | 3,000 | 4,000 | 2 |
| $4–5k | 4,000 | 5,000 | 2 |
| $5–6k | 5,000 | 6,000 | 0 |
| $6–7k | 6,000 | 7,000 | 3 |
| $7–8k | 7,000 | 8,000 | 0 |
| $8–9k | 8,000 | 9,000 | 2 |
| $9–10k | 9,000 | 10,000 | 1 |
| $10–12k | 10,000 | 12,000 | 2 |
| $12–15k | 12,000 | 15,000 | 1 |
| $15–20k | 15,000 | 20,000 | 3 |
| $20k+ | 20,000 | — | 0 |
Which countries have the most open Ruby on Rails jobs.
Demand geography
| country | jobs | share |
|---|---|---|
| United States | 39 | 30.7% |
| Poland | 14 | 11% |
| United Kingdom | 9 | 7.1% |
| Russia | 6 | 4.7% |
| India | 5 | 3.9% |
| Germany | 5 | 3.9% |
| Bulgaria | 4 | 3.1% |
| Canada | 4 | 3.1% |
| Ukraine | 4 | 3.1% |
| Brazil | 4 | 3.1% |
| Other countries | 33 | 26% |
Leader by Ruby job count — the US (39 positions). In CIS Ruby is niche (product companies, e-commerce, individual fintech / SaaS). Germany — Ruby-friendly EU (many Rails startups in Berlin). The main volume for a Russian-speaking Rails engineer — international full-remote (Rails community historically remote-first).
⚠ job counts only: salary by country is not published
Chart data
| Country | Jobs |
|---|---|
| US | 39 |
| PL | 14 |
| GB | 9 |
| RU | 6 |
| IN | 5 |
| DE | 5 |
| BG | 4 |
| CA | 4 |
| UA | 4 |
| BR | 4 |
Which technologies are most often required in the same job as Ruby on Rails.
Used together with
Share — how many of the 188 jobs in the Ruby on Rails 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 Ruby stack 2026: Ruby 3.x (must — YJIT), Rails 7 / 8, Hotwire (Turbo + Stimulus — UI dominator), PostgreSQL, Sidekiq or Solid Queue (background jobs), Redis, RSpec / Minitest (tests), Puma, Devise, ViewComponent, Sorbet / RBS (typing — growing), graphql-ruby or REST, Kamal (deploy), Docker + Kubernetes.
Common pairs: Ruby + Rails, Rails + Hotwire (Turbo + Stimulus), Rails + PostgreSQL + Sidekiq, Rails + RSpec, Rails + Kamal + Docker. Learning roadmap: Ruby as a language → Rails Guides + The Odin Project → ActiveRecord and fighting N+1 → RSpec → Hotwire → background jobs → service objects → pet project on Rails 8 with deploy via Kamal.
Chart data
| Name | Count |
|---|---|
| ruby | 156 |
| rails | 134 |
| postgresql | 34 |
| javascript | 34 |
| cloud | 34 |
| aws | 33 |
| react | 33 |
| docker | 32 |
| redis | 19 |
| sql | 19 |
| mysql | 16 |
| kubernetes | 12 |
How many Ruby on Rails jobs there are at each level, from junior to principal.
Demand by grade
| grade | jobs |
|---|---|
| senior | 71 |
| middle | 16 |
| principal | 15 |
| lead | 6 |
| junior | 2 |
Junior vacancies almost don't exist — the market expects Middle+. Career flow: backend developer from another language → Ruby Middle in 3-6 months → Senior → Staff / Tech Lead, or Rails + Hotwire fullstack, or architecture. The staff shortage lifts salaries above the backend average at the same grade.
⚠ demand side only: the grade of the observed pool is unknown for most of it
Chart data
| Level | Count |
|---|---|
| senior | 71 |
| middle | 16 |
| principal | 15 |
| lead | 6 |
| junior | 2 |
Who hires the most for Ruby on Rails and how concentrated demand is among the largest companies.
Employers
Demand is spread across 126 employers. The largest accounts for 3.7%, the top ten for 18.9%; the remaining 81.1% is long tail.
| share | value |
|---|---|
| top-1 | 3.7% |
| top-3 | 9.2% |
| top-10 | 18.9% |
| long tail | 81.1% |
⚠ 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 Ruby on Rails jobs from.
Where Zorky sees this market
Observed across 48 sources; the largest accounts for 11.7% — this market does not rest on a single channel.
Ruby vacancies: hh.ru, Habr Career, getmatch, Djinni, LinkedIn (large international Ruby segment), Telegram, Ruby Weekly newsletter, GoRails Jobs, We Work Remotely (Ruby section — many remote), Y Combinator Work at a Startup. The real market for a Russian-speaking Rails engineer is wider than local thanks to international remote.
Chart data
| Class | Name | English name | Count | Share |
|---|---|---|---|---|
| ats | ATS и карьерные сайты | ATS & career sites | 116 | 0.617 |
| board | джоб-борды и агрегаторы | job boards & aggregators | 51 | 0.2713 |
| telegram | Telegram | Telegram | 20 | 0.1064 |
| community | сообщества и публичные профили | community & public profiles | 1 | 0.0053 |
The newest Ruby on Rails jobs from company career sites.
Recent openings
- 🔥 Горячая неделя: свежие уязвимости в Ruby, nginx, PHP и Java · RU
- Senior Software Engineer (Ruby on Rails) · US · $15,000
- Ruby‑разработчик (Москва) в «Пангео‑Горизонт» · RU
- Senior Ruby/Rails Back-End Developer · BG
- Backend Engineer (Ruby), AI Engineering: AI Catalog
- Fullstack Engineer, Source Code: Repository Services (Ruby) · CA
- Full Stack Rails Engineer · $8,333
- Full Stack Rails Engineer · US · $9,167
Latest open Ruby on Rails jobs — most recent 10 positions with adequate description quality. Full list — in our CRM or via the «see all» link below.
Adjacent markets
Ruby — a niche backend segment: few vacancies by count, but staff shortage keeps salaries above average. Close directions — Rails + Hotwire fullstack, Python / Django (neighboring «batteries included» framework), Elixir / Erlang (neighboring BEAM segment, syntactically related to Ruby). Comparison — in the SiblingSubnichesChart above.
⚠ 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.
Direction: Backend
Related specializations
Inside Ruby on Rails: Ruby on Rails Developer (general — full-cycle product development), Ruby Backend Engineer (APIs and services), Senior / Staff Rails Engineer (architecture of large monolith, performance), Rails + Hotwire fullstack (cross-link to /research/fullstack/rails-fullstack), Erlang / Elixir — neighboring BEAM segment for comparison. Comparison — in the bar below.
Frequently asked questions
The most common questions about Ruby on Rails: pay, grades (Junior almost none), is Rails dying or not (Rails renaissance), Ruby vs Python vs Node, what Hotwire is, remote (one of the most remote-friendly stacks), companies, how to start (3-6 months for an experienced backend), Senior skills. Answers recompute automatically.
What stack is most often required from a Ruby on Rails developer?
Top 5: ruby, rails, ci/cd, postgresql, docker. Ruby 3.x (must — 3.3 / 3.4, YJIT compiler gives a noticeable speed boost). Rails 7 / 8. Hotwire (Turbo + Stimulus) — the dominant UI approach 2024–2026: interactive interfaces almost without writing JavaScript. PostgreSQL. Background jobs — Sidekiq (classic, on Redis) or the new Solid Queue (on the DB itself, no Redis). Redis (cache, queues). Tests — RSpec (dominates) or Minitest (native for Rails). Puma (web server). Devise (authentication). ViewComponent (component approach to views). Sorbet or RBS — Ruby static typing (a growing trend in large codebases). API — graphql-ruby or REST. Deploy — Kamal (from 37signals) or Capistrano (legacy), Docker + Kubernetes. Understanding ActiveRecord and fighting N+1 queries, Rails conventions, service objects and business logic organization — a Senior must. Profiling — rack-mini-profiler, Bullet (N+1 detector).
Is Rails dying? Should you learn Ruby in 2026?
No, «Rails is dying» — a persistent myth that's been around for more than 15 years. Reality 2024–2026 — on the contrary, Rails renaissance: Rails 7 and 8 shipped, Hotwire brought back productive UI development without a heavy JS frontend, the Solid Queue / Solid Cache / Solid Cable stack removed the mandatory Redis dependency, simple deploy via Kamal appeared. Rails remains one of the fastest ways to bring a product from idea to prod — which is why startups love it. What's true: Ruby — a niche language, its market share is less than Python / JS / Java, and it's not growing explosively; there are few new Junior vacancies. What this means for a career: learning Ruby «from scratch as a first language for fast employment» — questionable (few entry positions). But for an already working backend developer, Ruby is an excellent second language: shortage of staff → high salaries, strong international remote market, pleasant language. Conclusion: Rails is alive and healthy as a niche premium segment — not as a mass «entry to IT».
Ruby on Rails vs Python/Django vs Node.js — what to choose?
Ruby on Rails wins: maximum product creation speed (convention over configuration, everything «out of the box»), mature framework with a coherent philosophy, Hotwire for interactive UI without SPA, the favorite stack of product startups. Cons: niche, few Junior vacancies, runtime performance lower than compiled languages. Python / Django: larger market and more vacancies, indispensable if ML / data / AI are nearby, also «batteries included». Node.js: one language for front and back, best niche — real-time and I/O-bound services, huge market. Strategy for CIS: for entering the profession, Python or Node is more practical (market capacity, has Junior vacancies); Ruby — a strong choice as a second language for an experienced backend developer who wants to work at product companies and on international remote with a shortage premium. The transition to Rails itself is fast — the language and framework are mastered in 3-6 months.
What is Hotwire and why does a Rails developer need it?
Hotwire (HTML Over The Wire) — an approach to building interactive web interfaces promoted by Rails creators (37signals / DHH), the UI dominator in the Rails world 2024–2026. The idea: instead of a heavy SPA frontend (React / Vue with a separate API), the server sends ready-made HTML, and interactivity is achieved with a small amount of JavaScript. Consists of: Turbo — Turbo Drive (speeds up page transitions), Turbo Frames (updating chunks of the page), Turbo Streams (precise real-time updates via WebSocket / SSE); Stimulus — a lightweight JS framework for «adding behavior» to HTML; Strada — bridge for hybrid mobile applications. Why this matters for a developer: Hotwire allows a full-stack Rails engineer to do a modern interactive UI without going into full SPA frontend development — less code, less logic duplication, faster. Knowledge of Hotwire in 2026 — practically a mandatory requirement for Rails vacancies. Suitable for most product applications; for interfaces of the complexity of a sophisticated dashboard / editor, SPA may still be chosen. Hotwire — a key element of the «Rails renaissance».
What share of jobs are remote?
Among jobs with a stated work format, 64% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.
How to start in Ruby on Rails in 2026?
Assumes a basic programming background (Ruby — an excellent second language). Roadmap: 1) Ruby as a language — «The Well-Grounded Rubyist» (David A. Black), official documentation, ruby-koans for practice; understand blocks, methods, metaprogramming. 2) Rails — official Rails Guides (excellent documentation), «Agile Web Development with Rails», The Odin Project course (Ruby on Rails path — free, quality). 3) ActiveRecord deeply — associations, migrations, and most importantly — fighting N+1 queries (gem Bullet). 4) Testing — RSpec (or Minitest), TDD practice. 5) Hotwire — Turbo + Stimulus (mandatory for 2026 — official Hotwire handbook). 6) Background jobs — Sidekiq / Solid Queue. 7) Business logic organization — service objects, «fat model / thin controller» patterns, when to extract to services. 8) End-to-end pet project: Rails 8 app with Hotwire UI + PostgreSQL + Devise (auth) + Sidekiq + RSpec tests + deploy via Kamal. 9) Book «Sustainable Web Development with Ruby on Rails» (David Bryant Copeland) — about a healthy large codebase. Resources: The Odin Project, GoRails (video screencasts — the best practical resource), Drifting Ruby, podcast / newsletters Ruby Weekly. A backend developer from another language masters productive Rails in 3-6 months.
How many open jobs are in this sample?
The published sample contains 188 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.
What skills does a Senior Ruby on Rails need?
Senior Ruby on Rails owns the full product development cycle and the architecture of a large monolith. Ruby: deep understanding of the language — blocks and procs / lambdas, metaprogramming (and when NOT to apply it), modules and mixins, memory / GC specifics. Rails: ActiveRecord at expert level (associations, scopes, fighting N+1, proper migrations, indexes), Rails conventions and conscious deviations from them, caching (fragment / russian-doll caching, Solid Cache), Action Cable / Turbo Streams for real-time. Architecture: designing the domain model, business logic organization (service objects, form objects, query objects — «fat model» versus smeared logic), maintaining a healthy large codebase, conscious choice «monolith versus services». Hotwire: Turbo + Stimulus at production level. Performance: profiling (rack-mini-profiler, memory profilers), SQL optimization, tuning Puma and connection pool, background jobs (Sidekiq / Solid Queue). PostgreSQL: advanced SQL, indexes, query plan explanation. Testing: mature strategy (RSpec, factories, what and how to test, run speed). Typing: Sorbet or RBS in large projects. DevOps: Docker, Kamal / CI-CD, basic Kubernetes. Soft: code review, mentoring, communication with product. English for Senior+ — practically mandatory: the main premium market for Ruby is international remote.
Leave a request
Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.