Hire developers
Rails still runs a lot of revenue, so the demand is real, but the pool has thinned as newer grads chase JavaScript and Go. That works in your favor and against you: the people who stayed tend to be senior and pragmatic, but juniors are scarce and salaries at the top end are not cheap. The bigger risk is inheriting a large Rails app that has drifted into fat models, callback spaghetti, and a test suite nobody trusts, and hiring someone who only knows how to add more of the same.
Look for someone who treats Rails conventions as a starting point, not gospel: they can say when a service object or a plain Ruby class beats stuffing more into a model, and they know where ActiveRecord generates the N+1 queries that quietly kill a page. Ask them to walk through a slow endpoint they profiled and fixed, and listen for real tools (the query log, bullet, a flamegraph) rather than guessing. A good tell is how they talk about background jobs and migrations on a live database, since that is where Rails apps actually break in production. Test discipline matters too: ask what they mock, what they don't, and why their suite is or isn't fast enough to run before every push.
Describe the role in one chat and it goes live after a quick review. Ruby on Rails developers apply straight to your inbox.
Post a roleLooking for work? See Ruby on Rails developer jobs.