To hire Ruby on Rails developers well, decide first which of two hires you mean. One keeps a Rails 5, 6 or 7 monolith alive and knows its every quirk. The other builds new products on Rails 8. The version named in your job ad decides which person applies, and an ad that doesn't name one attracts the wrong half of the pool.
This guide sits in our series Hire developers by tech stack: rates, vetting and interview guides.
Which Rails and Ruby version should the hire know in 2026?
The Rails team's maintenance policy gives each minor series bug fixes for one year after its first release and security fixes for two years. After a series falls out of support, no new versions ship, and you either fix problems yourself or upgrade. Here's the table for the series that are supported, as of 2 October 2026 (check the page, because it changes).
| Rails series | Bug fixes until | Security fixes until |
|---|---|---|
| 8.1.x | 10 October 2026 | 10 October 2027 |
| 8.0.x | 7 May 2026 (ended) | 7 November 2026 |
Rails 8.1 loses bug-fix support eight days after this snapshot, so a hire for a new project should expect to be on 8.1 or its successor. Rails 7.2 isn't on the maintenance page's supported list, so a 7.x codebase has no supported series to point at.
Ruby has its own clock. The Ruby branches page lists 4.0 and 3.4 in normal maintenance, 3.3 in security maintenance, and 3.2 as end of life since 1 April 2026. Meanwhile the Rails upgrade guide says Rails 8.0 and 8.1 require Ruby 3.2.0 or newer. The oldest Ruby Rails 8 accepts is therefore one that's no longer supported.
For the job ad, that means naming both versions. "Rails 8 on Ruby 3.4" is a real requirement. A candidate who has only run Ruby 3.2 isn't disqualified, but ask them how they'd move off it.
Which Rails hire do you need?
There are three profiles, and they're three different jobs.
The legacy maintainer works on Rails 4 to 7 apps. No Rails series older than 8.0 is on the maintenance page's supported list, and the Ruby underneath is often past support too. The work is reading unfamiliar code, adding tests where none exist, and planning an upgrade path one step at a time. Patience matters more than novelty here.
The current-Rails builder works with what Rails 8 ships by default. The Rails 8.0 announcement lists Kamal 2, Thruster, Solid Cable, Solid Cache, Solid Queue, Propshaft and an authentication generator. Someone fluent in those has built on the current framework, not just maintained an old one.
The API-mode specialist builds a Rails backend behind a separate React or mobile client. Views and Hotwire matter less. Serialisation, versioning and auth matter more.
Write two job descriptions if you have two problems. The same split exists elsewhere, and how the same legacy-versus-modern divide plays out for Java reads almost the same. If you're still choosing the framework, the Django version of this guide covers the closest peer on the Python side.
What separates a senior Rails developer from someone who lists Rails
Rails makes it easy to ship something that works without understanding why. Plenty of CVs carry five years of rails generate. The general markers of seniority in backend work are in what separates senior backend developers from mid-level ones, so this section stays on what's specific to Rails.
Start with ActiveRecord. The classic Rails performance problem is the N+1 query: load a list, touch an association on each record, and you've issued a query per row. A senior developer spots it in review and knows the options for loading associations up front, including how includes, preload and eager_load differ.
Callbacks are convenient and turn into hidden control flow. A senior developer knows when a model has grown too fat and what to pull out of it.
Background jobs are the next check. Sidekiq is a common choice, while Rails 8 ships Solid Queue, and the same announcement says it replaces the need for Redis and a separate job framework "for most people". A good candidate has an opinion on which they'd pick and why.
For testing, the choice of RSpec or Minitest, fixtures or factories matters less than whether they test behaviour or just chase coverage. On security, strong parameters and mass assignment are the entry-level check. If they can't explain why Rails makes you permit attributes explicitly, keep looking.
Where your app uses Hotwire, ask what they've built with Turbo and Stimulus. Where it doesn't, skip it.
How to hire a Ruby on Rails developer
The sequence below is our own editorial guidance, not a sourced standard.
1. Write the job spec with Rails and Ruby versions
Name the Rails series and the Ruby version your app runs, and the one you plan to move to. Say whether the work is maintenance, new features or an upgrade. Candidates self-select far better when the ad reads like your actual codebase.
2. Pick the engagement model
Bounded work such as a Rails upgrade or a performance audit suits a contractor. Open-ended product work suits a direct hire or an augmented engineer who stays for months. That's editorial opinion, and we say more in the last section.
3. Source where Rails developers are
Look at who has contributed to the gems you already depend on, and at the people answering questions about them. We haven't sourced a list of Rails-specific job boards, so we're not naming any.
4. Screen on a real codebase
Send a short Rails controller and model with three planted problems: an N+1 query, a callback chain with a side effect, and an unpermitted attribute. Ask for written review comments. Strong candidates explain the runtime effect, not only the rule.
5. Run a short pairing session or take-home in actual Rails
Skip algorithm puzzles. Give them a small feature in a real Rails app (a paginated list with an association, say) and watch how they handle migrations, tests and queries. If you pair live, running the live coding stage without theatre covers how to keep it useful.
6. Check references on upgrades and production ownership
Ask a former colleague whether the candidate ever led a Rails or Ruby upgrade, and who got paged when something broke in production. Both answers are hard to fake.
Rails interview questions that show depth
These are our suggestions, not a standard. The notes describe what we'd listen for.
- How would you find and fix an N+1 query? A strong answer starts with logs, then picks between
includes,preloadandeager_loadand explains the difference. - What does a long callback chain cost you? Listen for hidden side effects, hard-to-test models, and where they'd move the logic instead.
- Solid Queue or Sidekiq for a new app? Good answers weigh operational simplicity against throughput and existing infrastructure instead of declaring a winner.
- How would you upgrade a Rails 6 app? The upgrade guide advises moving "one minor version at a time" to make use of deprecation warnings, with good test coverage first and Ruby and Rails upgraded separately. A candidate who proposes jumping straight to 8 has probably never done it.
- What's mass assignment, and how does Rails protect against it? Look for strong parameters and an example of what goes wrong without them.
- When would you leave the monolith? Strong answers are specific about a pain (team size, deploy independence, scaling one workload), not fashion.
- How do you read an unfamiliar Rails codebase? Listen for routes, schema and tests as starting points, and for running the app.
Is Rails still worth hiring for in 2026?
Yes, on the evidence available. The framework is actively released: Rails 8.0 shipped on 7 November 2024, and the Rails 8.1 release post is dated 22 October 2025. In the Stack Overflow 2025 developer survey, 5.9% of the 23,678 respondents to the web-frameworks question used Rails, and 6.4% named Ruby in the language question. The denominators differ, so don't compare the two figures.
That's a smaller pool than for the largest frameworks, and it's a real one. We're skipping popularity-index and usage-count claims because we couldn't verify them at the source.
What drives Ruby on Rails developer cost
We aren't quoting Rails rates. We didn't find a dated primary source, and the figures that rank for this topic are undated, second-hand or published by vendors selling the hire. A made-up range is worse than none.
What moves a quote is predictable. Seniority comes first. Legacy work can price differently from greenfield. Location matters, as does the engagement model. The last driver is how margin is applied: some vendors quote one blended number, others show what the engineer earns and what they add. Ask any vendor to separate the two before you compare quotes.
Freelance, in-house or staff augmentation for Rails
This is our opinion, not a sourced finding. A Rails upgrade, a performance audit or a security review has a finish line, and a freelancer suits that. A product that will outlive the project needs people who accumulate its history, which favours in-house or an augmented engineer embedded for months.
If your app is a ten-year-old monolith, expect the expensive problems to be about context. A contractor who leaves after six weeks takes it with them.
FAQ
What Rails and Ruby version should I hire for?
Rails 8.1 on Ruby 3.4 or 4.0 for new work, as of 2 October 2026. Rails 8.0 and 8.1 both need Ruby 3.2.0 or newer, but Ruby 3.2 reached end of life on 1 April 2026. If your app is older, hire for that profile separately and say so in the ad.
How do I test a Rails developer's ActiveRecord knowledge?
Give them a short model and controller with an N+1 query and ask for a written code review. Then ask how includes, preload and eager_load differ and when they'd use each. Someone who has debugged a slow page in production can answer from experience. Someone who has only followed tutorials usually can't.
Should I hire a freelancer or staff augmentation for a Rails upgrade?
A bounded upgrade suits a freelancer, provided your test coverage is decent. The Rails upgrade guide recommends one minor version at a time, so plan for several passes, not one. If the work will continue after the upgrade, an augmented engineer keeps the context.
Is Rails still maintained?
Yes. As of 2 October 2026, Rails 8.1.x receives bug fixes until 10 October 2026 and security fixes until 10 October 2027, and Rails 8.0.x receives security fixes until 7 November 2026. Check the maintenance page for the current dates.
Can I hire a Ruby or Rails developer part-time?
Yes, as a contract engagement, and it's a common fit for upgrades and audits. Agree the scope, the hours per week and who owns production issues before you start. We don't quote figures for part-time Rails work.