Ruby on Rails jobs are easy to search for and hard to count. Every figure on this page comes from a
named source with a date on it, and where no such source exists, this page says so rather than
filling the gap with a plausible number. Several of the most repeated claims about the Ruby on Rails
job market turn out to have no source at all, and they are named here too.
Two kinds of evidence exist, and mixing them is where most writing on this subject goes wrong.
Developer surveys tell you what a self-selected pool of respondents says about the work they already
do. Job advertisement trackers tell you what employers wrote in ads in one country over one window.
Neither is a census of employment, and neither becomes one by being multiplied by the other.
Why nobody can tell you how many Ruby on Rails jobs exist
A count of Rails roles, worldwide or in any single country, is not published by any source that can
be named and dated. The closest measurable thing is advertisements: IT Jobs Watch recorded 177 UK
permanent job ads citing Ruby on Rails in the six months to 11 September 2026, the figures on this
page having been read on that date. That is a count of ads collected by one aggregator in one
country, not a count of jobs, and an employer who advertises one role and hires three appears once.
The arithmetic that produces a worldwide figure is the part to distrust. Taking a survey's usage
share, such as the 5.9% of Stack Overflow's 2025 respondents who reported using Rails, and
multiplying it by an estimate of the world developer population yields a headcount that no source
stands behind, because the survey's respondents were never a random sample of developers. Any page
that opens with "there are N Rails jobs" is performing that multiplication or inventing the result
outright.
What can be described honestly is the shape of the work: what employers ask for, how Rails teams are
sized, how old the applications are, and how the pay data behaves when you read the footnotes.
That is what the rest of this page does.
How many developers report using Rails, according to Stack Overflow
Stack Overflow's 2025 Developer Survey puts Ruby on Rails at 5.9% of all respondents who answered
its web framework question, which is 1,395 people out of a base of 23,678, and at 6.2% of
professional developers, 1,208 out of 19,460. Rails ranks 20th of the 28 web frameworks and
technologies the chart lists, between NestJS at 6.7% and Astro at 4.5%. Ruby the language does
slightly better on its own question: 6.4% of all respondents, 2,046 out of a base of 31,771, and
18th of the 42 languages listed.
Those bases matter more than the ranks. Stack Overflow reports 49,009 responses used in its 2025
results, but the framework question was answered by fewer than half that number, so 5.9% is a share
of the people who answered that one question. A share of a self-selected survey pool is not a
population estimate, and it cannot be turned into one.
Sentiment is measured separately, and Rails does well there. The same survey's admired and desired
chart, which defines admired as the proportion of people who used a technology in the past year and
want to continue and desired as the proportion who want to use it, puts Rails at 52% admired and
5.5% desired. For scale, Phoenix is the most admired web framework in that chart at 79%.
Whether Rails demand is rising or falling
Four sources answer that question, and they do not agree, which is itself the finding. Stack
Overflow's usage share went up: Ruby on Rails moved from 4.7% to 5.9% of all respondents and from
5.2% to 6.2% of professional developers between the 2024 and 2025 surveys, and Ruby the language
moved from 5.2% to 6.4% and from 5.8% to 6.9%. The caveat travels with the number. Stack Overflow
reported 65,437 respondents in 2024 and 49,009 responses used in 2025, so the composition of who
answered changed, and a rising share of a shrinking pool is not evidence of rising absolute usage.
JetBrains argues the opposite and publishes nothing to support it. The only mention of Ruby anywhere
in the 2025 State of Developer Ecosystem's Tools and Trends page is one sentence: "PHP, Ruby, and
Objective-C are in long-term decline while Rust, Go, and Kotlin continue their slow, steady ascent."
No Ruby figure appears beside it, and JetBrains stopped breaking Ruby out after 2023: the 2023
report has a dedicated Ruby page, the same URL with 2024 in it returns a 404, and the 2025 report
has no per-language pages at all. Anyone citing "the JetBrains report" for a Ruby number after 2023
is citing something that does not exist.
Planet Argon's 2024 Ruby on Rails Community Survey carries the gloomiest signal, and the only
Rails-specific one. Asked whether their development team had grown or shrunk in the last two years,
961 respondents said grown (36%), 1,250 said about the same (46%) and 484 said shrunk (18%). In the
2022 edition the same question returned 54% grown and 9% shrunk. The survey's own comment is that
"teams are having to maintain their applications with less".
IT Jobs Watch's UK ad counts refuse to form a trend at all: 94 ads in the six months to September
2024, 42 in the same window of 2025, and 177 in 2026. A series that swings by a factor of four in
either direction is too volatile to read as a trend.
Where Ruby on Rails developer jobs are advertised
Advertisement data for the United Kingdom comes from IT Jobs Watch, whose Ruby on Rails page is the
most specific public data available for any single market. Over the six months to 11 September 2026,
Ruby on Rails ranked 633rd of all the IT skills it tracks, appeared in 177 permanent vacancies, and
accounted for 0.16% of all UK permanent IT jobs and 1.48% of its Libraries, Frameworks and Software
Standards category.
Job titles in those ads are broad rather than framework-specific. Developer appears in 62.71% of
them, Full-Stack Developer in 29.94%, Senior in 28.25%, Ruby Developer in 23.73% and Ruby on Rails
Developer in only 16.38%. Someone filtering a job board for the exact string "Ruby on Rails
Developer" is therefore looking at a minority of the ads that actually want Rails.
Locations concentrate outside London. England accounts for 113 of the ads at a median advertised
salary of £75,000, the UK excluding London for 103 at the same median, Work from Home for 79 at
£72,500, and London itself for only 46, also at £75,000.
No equivalent named, dated dataset breaking out Rails exists for the United States, so this page
makes no claim about US vacancy counts. The 2024 Ruby on Rails Community Survey charts 795
participants in the United States, the largest single country in its location chart, which is a fact
about who took that survey and not a measurement of demand anywhere.
What employers ask for alongside Rails
Co-occurring skills in those 177 UK ads are the clearest evidence of what a Rails role is expected
to include. IT Jobs Watch lists Ruby in 99.44% of them, AWS in 73.45%, Full-Stack Development and
React in 49.15% each, Agile in 38.42%, PostgreSQL in 37.29%, JavaScript in 34.46%, Node.js in
33.33%, Serverless in 32.77%, CI/CD in 30.51%, AWS Lambda in 29.94%, Microservices in 28.25%,
Docker in 23.73%, Scrum in 21.47%, and Terraform and Next.js in 15.25% each.
Three quarters of the ads asking for AWS and nearly half asking for React is the practical answer to
what a Rails employer wants: Rails plus cloud infrastructure plus front-end work, rather than Rails
alone. The presence of Microservices in 28.25% of the ads sits oddly against what Rails developers
report actually working on, which the next section covers.
An advertisement is a filter, not a job description, and it should be read as one. RSpec appears in
just 7 of the 177 ads, 3.95%, while 2,096 of the 2,709 respondents to the 2024 Ruby on Rails
Community Survey, 77%, said they test with RSpec. The gap does not mean employers do not use RSpec.
It means ads list what a recruiter screens on, so the absence of a tool from an ad is not evidence
the job does not involve it.
How a Rails role differs from a generic backend role
Monoliths are the defining difference, and they are not a minority position among Rails developers.
Asked what they primarily work on, 2,034 of the 2,654 respondents to Planet Argon's 2024 survey said
a monolith, 459 said hybrid and 161 said microservices. That is 77% monolith against 6%
microservices, in a market where a generic backend job description will often assume the reverse.
Team size is the second difference. The same survey's buckets put 432 respondents on a team of one,
816 on a team of 2 to 4 and 500 on a team of 5 to 8, which is 1,748 of 2,700 answers, 65%, on teams
of eight or fewer. Planet Argon's own comment on that chart is "perhaps there is something to this
one-person framework".
Breadth follows from both. Half of respondents, 1,361 of 2,699, said their team is responsible for
between two and five Rails applications, and 866 said one. A backend specialist on a large team owns
a service; a Rails developer on a team of four frequently owns several applications end to end,
which is the same reason the UK ads ask for full-stack and infrastructure skills next to the
framework.
Why much Rails work is maintenance rather than greenfield
Application age is the part of the picture that most job seekers do not expect. Asked how long their
Rails application had been in development, respondents to the 2024 Ruby on Rails Community Survey
put 1,434 of 2,694 applications, 53%, at seven years or older, and only 197, 7%, at under a year.
Inherited code is common too: 503 respondents said mostly legacy and 373 said all legacy, which is
876 of 2,667 answers, 33%.
Framework versions confirm it. Rails 7.1.x was in use by 1,900 respondents and 7.0.x by 1,104, but
selections for Rails 5.x and older still total 730, spread across 5.2.x, 5.1.x, 5.0.x, 4.2.x and a
long tail below that. A meaningful minority of Rails roles therefore involve an application several
major versions behind the releases the same survey shows most teams on, and upgrade work is part of
the job rather than an exception to it.
What that means for a candidate is concrete. Interview questions about legacy code, upgrade
strategy, test coverage on code you did not write and the behaviour of older Rails APIs are not
trick questions in this market, they are the work. A candidate who can only describe greenfield
development is describing the 7% case.
What the pay figures actually support
The most recent survey salary figure for Ruby is Stack Overflow's 2024 top-paying technologies
chart, where Ruby is fifth at a median yearly salary of $90,221, behind Erlang at $100,636, Elixir
at $96,000, Clojure at $95,541 and Nim at $94,924, and just ahead of Perl at $90,000. Two caveats
ship with it. The figure measures the language Ruby and not the Rails framework, and it is a global
mix of countries rather than any one market's salary.
Nothing newer exists from that source. Stack Overflow's 2025 survey publishes salary by developer
type rather than by language, and the phrase "top paying" appears nowhere on its 2025 technology
page, so anyone quoting a 2025 or 2026 Stack Overflow salary for Ruby is quoting something the
survey did not publish.
Advertised UK salaries are a different kind of number and the only current one. IT Jobs Watch puts
the median advertised annual salary for Ruby on Rails at £72,500 from 163 quoted salaries in the six
months to 11 September 2026, with a 10th percentile of £45,250 and a 90th of £100,000, against
£70,000 in the same window of 2025 and £65,000 in 2024. For comparison, the median across its whole
Libraries, Frameworks and Software Standards category is £67,500. An advertised salary is what an
employer published, not what anyone was paid.
A Rails premium or discount against generic backend work cannot be calculated from any of this.
Stack Overflow's $90,221 is measured by language, its developer-type salaries are measured by role,
and subtracting one from the other compares two different populations in two different charts. The
comparison is unavailable rather than unfavourable, and this page will not manufacture it.
Remote work in Rails roles
Remote work is the majority arrangement among Rails developers who answer the Rails survey. Planet
Argon's 2024 edition records 1,954 respondents working remotely (72%), 608 hybrid or sometimes (23%)
and 137 primarily on-site (5%). Across editions the same question returned 50% remote in 2020, 76%
in 2022 and 72% in 2024, so remote work peaked in 2022 and came down slightly. The survey's own
commentary describes "consistent growth in the percentage of remote workers" since 2020, which its
own chart does not show.
A comparison with developers at large has to be made carefully, because it crosses two surveys and
two populations. Stack Overflow's 2025 work environment question, answered by 33,686 people, records
32.4% fully remote, 19.9% hybrid leaning in-person, 17.9% in-person and 17.2% hybrid leaning
flexible. Rails developers who take a Rails agency's survey are not a random sample of developers,
so 72% against 32.4% is context rather than a measured gap.
UK advertisements land between the two. Work from Home appears in 79 of the 177 Ruby on Rails ads
IT Jobs Watch tracked in the six months to 11 September 2026, which is 45%, at a median advertised
salary of £72,500.
Getting a first Rails job, and what the data does not say
Experience skews long in the Rails survey, which is the strongest available clue about entry-level
hiring and still only a clue. Asked how many years of Rails experience they had, 1,903 of 2,707
respondents, 70%, said seven years or more, and 1,426, 53%, said ten or more. Under four years of
Rails experience accounts for 375 people, 14% of the survey. How they learned to code splits almost
evenly: 1,109 (41%) have a computer science degree and 1,042 (38%) are self taught, with 231 on the
job and 220 through a bootcamp.
Planet Argon pairs that chart with a named opinion rather than a measurement. Jeff Casimir,
Executive Director of the Turing School, writes that "the continued trend in hiring is that
experience is more important than credentials" and that "getting that first job is tough right now".
That is his view, attributed as such, and the survey publishes no figure behind it.
No source found for this page measures how many Rails roles are open to juniors, in any market. The
widely repeated claim that Rails has no junior roles has no dated, nameable source behind it, and
neither does its opposite. What the survey does record is that 87 of its 2,709 participants, 3%,
described themselves as currently looking for work, while 1,871 (69%) work at a product company,
386 (14%) are freelancers or contractors and 346 (13%) work at a consultancy.
How Rails developers rate Rails, and why that is not a market signal
Community sentiment towards Rails is overwhelmingly positive, and it is worth reading with the
selection bias stated up front. In the 2024 Ruby on Rails Community Survey, 2,456 of 2,594 answers
(95%) named Rails as the respondent's server-side framework of choice, 2,415 of 2,614 (92%) would
recommend new developers learn Rails, and 2,458 of 2,634 (93%) totally or mostly agreed that Rails
is still relevant.
Those are answers from Rails developers who chose to take a Rails agency's own Rails survey. They
measure the enthusiasm of the people who showed up, which is a real thing worth knowing before you
join the ecosystem, and they measure nothing at all about how many employers are hiring. Enthusiasm
and demand are separate questions, and survey sentiment can only answer the first.
The Rails survey also runs on a two-year cycle, published in 2009, 2012, 2014, 2016, 2018, 2020,
2022 and 2024. Planet Argon's survey index states that the 2026 edition is closed and its results
are not yet published, so every Rails-specific figure on this page is from the 2024 edition and
should be re-read against the 2026 one when it appears.
Preparing for a Rails interview
Interview preparation is where the job search gets concrete, and it is the one part of this subject
where a Rails-specific answer beats a generic backend one. The
Rails interview questions page in this cluster groups
questions by what each one tests rather than by a years-of-experience label, because no source
measures which questions are asked at which seniority, and two pages split by year count would be
near-duplicates of each other.
Runnable answers sit in the Ruby quiz, where each question is a small program with its
real output rather than a paragraph asserting what Ruby does. Reading the answer is worth less than
predicting it and being wrong, which is the same experience an interviewer is trying to create at a
whiteboard.
What no page can honestly give you is a frequency: how often a given topic comes up in Rails
interviews has not been measured by anyone whose work can be cited here, so this cluster describes
what a question tests and leaves the rest alone.
Ruby on Rails jobs are easy to search for and hard to count. Every figure on this page comes from a named source with a date on it, and where no such source exists, this page says so rather than filling the gap with a plausible number. Several of the most repeated claims about the Ruby on Rails job market turn out to have no source at all, and they are named here too.
Two kinds of evidence exist, and mixing them is where most writing on this subject goes wrong. Developer surveys tell you what a self-selected pool of respondents says about the work they already do. Job advertisement trackers tell you what employers wrote in ads in one country over one window. Neither is a census of employment, and neither becomes one by being multiplied by the other.
Why nobody can tell you how many Ruby on Rails jobs exist
A count of Rails roles, worldwide or in any single country, is not published by any source that can be named and dated. The closest measurable thing is advertisements: IT Jobs Watch recorded 177 UK permanent job ads citing Ruby on Rails in the six months to 11 September 2026, the figures on this page having been read on that date. That is a count of ads collected by one aggregator in one country, not a count of jobs, and an employer who advertises one role and hires three appears once.
The arithmetic that produces a worldwide figure is the part to distrust. Taking a survey's usage share, such as the 5.9% of Stack Overflow's 2025 respondents who reported using Rails, and multiplying it by an estimate of the world developer population yields a headcount that no source stands behind, because the survey's respondents were never a random sample of developers. Any page that opens with "there are N Rails jobs" is performing that multiplication or inventing the result outright.
What can be described honestly is the shape of the work: what employers ask for, how Rails teams are sized, how old the applications are, and how the pay data behaves when you read the footnotes. That is what the rest of this page does.
How many developers report using Rails, according to Stack Overflow
Stack Overflow's 2025 Developer Survey puts Ruby on Rails at 5.9% of all respondents who answered its web framework question, which is 1,395 people out of a base of 23,678, and at 6.2% of professional developers, 1,208 out of 19,460. Rails ranks 20th of the 28 web frameworks and technologies the chart lists, between NestJS at 6.7% and Astro at 4.5%. Ruby the language does slightly better on its own question: 6.4% of all respondents, 2,046 out of a base of 31,771, and 18th of the 42 languages listed.
Those bases matter more than the ranks. Stack Overflow reports 49,009 responses used in its 2025 results, but the framework question was answered by fewer than half that number, so 5.9% is a share of the people who answered that one question. A share of a self-selected survey pool is not a population estimate, and it cannot be turned into one.
Sentiment is measured separately, and Rails does well there. The same survey's admired and desired chart, which defines admired as the proportion of people who used a technology in the past year and want to continue and desired as the proportion who want to use it, puts Rails at 52% admired and 5.5% desired. For scale, Phoenix is the most admired web framework in that chart at 79%.
Whether Rails demand is rising or falling
Four sources answer that question, and they do not agree, which is itself the finding. Stack Overflow's usage share went up: Ruby on Rails moved from 4.7% to 5.9% of all respondents and from 5.2% to 6.2% of professional developers between the 2024 and 2025 surveys, and Ruby the language moved from 5.2% to 6.4% and from 5.8% to 6.9%. The caveat travels with the number. Stack Overflow reported 65,437 respondents in 2024 and 49,009 responses used in 2025, so the composition of who answered changed, and a rising share of a shrinking pool is not evidence of rising absolute usage.
JetBrains argues the opposite and publishes nothing to support it. The only mention of Ruby anywhere in the 2025 State of Developer Ecosystem's Tools and Trends page is one sentence: "PHP, Ruby, and Objective-C are in long-term decline while Rust, Go, and Kotlin continue their slow, steady ascent." No Ruby figure appears beside it, and JetBrains stopped breaking Ruby out after 2023: the 2023 report has a dedicated Ruby page, the same URL with 2024 in it returns a 404, and the 2025 report has no per-language pages at all. Anyone citing "the JetBrains report" for a Ruby number after 2023 is citing something that does not exist.
Planet Argon's 2024 Ruby on Rails Community Survey carries the gloomiest signal, and the only Rails-specific one. Asked whether their development team had grown or shrunk in the last two years, 961 respondents said grown (36%), 1,250 said about the same (46%) and 484 said shrunk (18%). In the 2022 edition the same question returned 54% grown and 9% shrunk. The survey's own comment is that "teams are having to maintain their applications with less".
IT Jobs Watch's UK ad counts refuse to form a trend at all: 94 ads in the six months to September 2024, 42 in the same window of 2025, and 177 in 2026. A series that swings by a factor of four in either direction is too volatile to read as a trend.
Where Ruby on Rails developer jobs are advertised
Advertisement data for the United Kingdom comes from IT Jobs Watch, whose Ruby on Rails page is the most specific public data available for any single market. Over the six months to 11 September 2026, Ruby on Rails ranked 633rd of all the IT skills it tracks, appeared in 177 permanent vacancies, and accounted for 0.16% of all UK permanent IT jobs and 1.48% of its Libraries, Frameworks and Software Standards category.
Job titles in those ads are broad rather than framework-specific. Developer appears in 62.71% of them, Full-Stack Developer in 29.94%, Senior in 28.25%, Ruby Developer in 23.73% and Ruby on Rails Developer in only 16.38%. Someone filtering a job board for the exact string "Ruby on Rails Developer" is therefore looking at a minority of the ads that actually want Rails.
Locations concentrate outside London. England accounts for 113 of the ads at a median advertised salary of £75,000, the UK excluding London for 103 at the same median, Work from Home for 79 at £72,500, and London itself for only 46, also at £75,000.
No equivalent named, dated dataset breaking out Rails exists for the United States, so this page makes no claim about US vacancy counts. The 2024 Ruby on Rails Community Survey charts 795 participants in the United States, the largest single country in its location chart, which is a fact about who took that survey and not a measurement of demand anywhere.
What employers ask for alongside Rails
Co-occurring skills in those 177 UK ads are the clearest evidence of what a Rails role is expected to include. IT Jobs Watch lists Ruby in 99.44% of them, AWS in 73.45%, Full-Stack Development and React in 49.15% each, Agile in 38.42%, PostgreSQL in 37.29%, JavaScript in 34.46%, Node.js in 33.33%, Serverless in 32.77%, CI/CD in 30.51%, AWS Lambda in 29.94%, Microservices in 28.25%, Docker in 23.73%, Scrum in 21.47%, and Terraform and Next.js in 15.25% each.
Three quarters of the ads asking for AWS and nearly half asking for React is the practical answer to what a Rails employer wants: Rails plus cloud infrastructure plus front-end work, rather than Rails alone. The presence of Microservices in 28.25% of the ads sits oddly against what Rails developers report actually working on, which the next section covers.
An advertisement is a filter, not a job description, and it should be read as one. RSpec appears in just 7 of the 177 ads, 3.95%, while 2,096 of the 2,709 respondents to the 2024 Ruby on Rails Community Survey, 77%, said they test with RSpec. The gap does not mean employers do not use RSpec. It means ads list what a recruiter screens on, so the absence of a tool from an ad is not evidence the job does not involve it.
How a Rails role differs from a generic backend role
Monoliths are the defining difference, and they are not a minority position among Rails developers. Asked what they primarily work on, 2,034 of the 2,654 respondents to Planet Argon's 2024 survey said a monolith, 459 said hybrid and 161 said microservices. That is 77% monolith against 6% microservices, in a market where a generic backend job description will often assume the reverse.
Team size is the second difference. The same survey's buckets put 432 respondents on a team of one, 816 on a team of 2 to 4 and 500 on a team of 5 to 8, which is 1,748 of 2,700 answers, 65%, on teams of eight or fewer. Planet Argon's own comment on that chart is "perhaps there is something to this one-person framework".
Breadth follows from both. Half of respondents, 1,361 of 2,699, said their team is responsible for between two and five Rails applications, and 866 said one. A backend specialist on a large team owns a service; a Rails developer on a team of four frequently owns several applications end to end, which is the same reason the UK ads ask for full-stack and infrastructure skills next to the framework.
Why much Rails work is maintenance rather than greenfield
Application age is the part of the picture that most job seekers do not expect. Asked how long their Rails application had been in development, respondents to the 2024 Ruby on Rails Community Survey put 1,434 of 2,694 applications, 53%, at seven years or older, and only 197, 7%, at under a year. Inherited code is common too: 503 respondents said mostly legacy and 373 said all legacy, which is 876 of 2,667 answers, 33%.
Framework versions confirm it. Rails 7.1.x was in use by 1,900 respondents and 7.0.x by 1,104, but selections for Rails 5.x and older still total 730, spread across 5.2.x, 5.1.x, 5.0.x, 4.2.x and a long tail below that. A meaningful minority of Rails roles therefore involve an application several major versions behind the releases the same survey shows most teams on, and upgrade work is part of the job rather than an exception to it.
What that means for a candidate is concrete. Interview questions about legacy code, upgrade strategy, test coverage on code you did not write and the behaviour of older Rails APIs are not trick questions in this market, they are the work. A candidate who can only describe greenfield development is describing the 7% case.
What the pay figures actually support
The most recent survey salary figure for Ruby is Stack Overflow's 2024 top-paying technologies chart, where Ruby is fifth at a median yearly salary of $90,221, behind Erlang at $100,636, Elixir at $96,000, Clojure at $95,541 and Nim at $94,924, and just ahead of Perl at $90,000. Two caveats ship with it. The figure measures the language Ruby and not the Rails framework, and it is a global mix of countries rather than any one market's salary.
Nothing newer exists from that source. Stack Overflow's 2025 survey publishes salary by developer type rather than by language, and the phrase "top paying" appears nowhere on its 2025 technology page, so anyone quoting a 2025 or 2026 Stack Overflow salary for Ruby is quoting something the survey did not publish.
Advertised UK salaries are a different kind of number and the only current one. IT Jobs Watch puts the median advertised annual salary for Ruby on Rails at £72,500 from 163 quoted salaries in the six months to 11 September 2026, with a 10th percentile of £45,250 and a 90th of £100,000, against £70,000 in the same window of 2025 and £65,000 in 2024. For comparison, the median across its whole Libraries, Frameworks and Software Standards category is £67,500. An advertised salary is what an employer published, not what anyone was paid.
A Rails premium or discount against generic backend work cannot be calculated from any of this. Stack Overflow's $90,221 is measured by language, its developer-type salaries are measured by role, and subtracting one from the other compares two different populations in two different charts. The comparison is unavailable rather than unfavourable, and this page will not manufacture it.
Remote work in Rails roles
Remote work is the majority arrangement among Rails developers who answer the Rails survey. Planet Argon's 2024 edition records 1,954 respondents working remotely (72%), 608 hybrid or sometimes (23%) and 137 primarily on-site (5%). Across editions the same question returned 50% remote in 2020, 76% in 2022 and 72% in 2024, so remote work peaked in 2022 and came down slightly. The survey's own commentary describes "consistent growth in the percentage of remote workers" since 2020, which its own chart does not show.
A comparison with developers at large has to be made carefully, because it crosses two surveys and two populations. Stack Overflow's 2025 work environment question, answered by 33,686 people, records 32.4% fully remote, 19.9% hybrid leaning in-person, 17.9% in-person and 17.2% hybrid leaning flexible. Rails developers who take a Rails agency's survey are not a random sample of developers, so 72% against 32.4% is context rather than a measured gap.
UK advertisements land between the two. Work from Home appears in 79 of the 177 Ruby on Rails ads IT Jobs Watch tracked in the six months to 11 September 2026, which is 45%, at a median advertised salary of £72,500.
Getting a first Rails job, and what the data does not say
Experience skews long in the Rails survey, which is the strongest available clue about entry-level hiring and still only a clue. Asked how many years of Rails experience they had, 1,903 of 2,707 respondents, 70%, said seven years or more, and 1,426, 53%, said ten or more. Under four years of Rails experience accounts for 375 people, 14% of the survey. How they learned to code splits almost evenly: 1,109 (41%) have a computer science degree and 1,042 (38%) are self taught, with 231 on the job and 220 through a bootcamp.
Planet Argon pairs that chart with a named opinion rather than a measurement. Jeff Casimir, Executive Director of the Turing School, writes that "the continued trend in hiring is that experience is more important than credentials" and that "getting that first job is tough right now". That is his view, attributed as such, and the survey publishes no figure behind it.
No source found for this page measures how many Rails roles are open to juniors, in any market. The widely repeated claim that Rails has no junior roles has no dated, nameable source behind it, and neither does its opposite. What the survey does record is that 87 of its 2,709 participants, 3%, described themselves as currently looking for work, while 1,871 (69%) work at a product company, 386 (14%) are freelancers or contractors and 346 (13%) work at a consultancy.
How Rails developers rate Rails, and why that is not a market signal
Community sentiment towards Rails is overwhelmingly positive, and it is worth reading with the selection bias stated up front. In the 2024 Ruby on Rails Community Survey, 2,456 of 2,594 answers (95%) named Rails as the respondent's server-side framework of choice, 2,415 of 2,614 (92%) would recommend new developers learn Rails, and 2,458 of 2,634 (93%) totally or mostly agreed that Rails is still relevant.
Those are answers from Rails developers who chose to take a Rails agency's own Rails survey. They measure the enthusiasm of the people who showed up, which is a real thing worth knowing before you join the ecosystem, and they measure nothing at all about how many employers are hiring. Enthusiasm and demand are separate questions, and survey sentiment can only answer the first.
The Rails survey also runs on a two-year cycle, published in 2009, 2012, 2014, 2016, 2018, 2020, 2022 and 2024. Planet Argon's survey index states that the 2026 edition is closed and its results are not yet published, so every Rails-specific figure on this page is from the 2024 edition and should be re-read against the 2026 one when it appears.
Preparing for a Rails interview
Interview preparation is where the job search gets concrete, and it is the one part of this subject where a Rails-specific answer beats a generic backend one. The Rails interview questions page in this cluster groups questions by what each one tests rather than by a years-of-experience label, because no source measures which questions are asked at which seniority, and two pages split by year count would be near-duplicates of each other.
Runnable answers sit in the Ruby quiz, where each question is a small program with its real output rather than a paragraph asserting what Ruby does. Reading the answer is worth less than predicting it and being wrong, which is the same experience an interviewer is trying to create at a whiteboard.
What no page can honestly give you is a frequency: how often a given topic comes up in Rails interviews has not been measured by anyone whose work can be cited here, so this cluster describes what a question tests and leaves the rest alone.