How AI Changed the Ruby on Rails Developer Job Description

A Ruby on Rails developer job description usually reads like a stack checklist. Strong Ruby and Rails, knows Active Record, comfortable with PostgreSQL and RSpec, writes clean, idiomatic code. That list describes someone who can produce Rails code. Producing Rails code, with all its conventions and generators, is exactly the kind of thing AI does well, so the list now screens for the wrong thing.

Rails was built on convention over configuration, which made it fast for humans and makes it even faster for AI. Ask a model for a standard Rails controller, model, and migration and it produces something idiomatic in seconds. That’s useful, and it’s also why “can you build Rails features” no longer separates a strong hire from a weak one. The scarce part is the judgment Rails conventions can’t give you: what to build, how the app should be structured as it grows, and whether the generated code is actually right.

I run Full Scale, where we staff Rails teams for US companies. Here’s what changed about the role, what to require instead, and a template you can copy.

Stop hiring Rails engineers. Start hiring Rails developers.

This reads like a word game, but I mean it literally, and I’m using the words backward from how most people do.

For most of my career, a “Rails engineer” was the person who writes the Ruby. You handed them a spec, they built it, you shipped it. That’s the role most Rails job descriptions still hire for: a pair of hands that knows the framework.

That job is shrinking. When AI writes a large share of the code, paying someone mainly to generate controllers and models is a poor use of the budget. Microsoft says AI already writes as much as 30% of its new code, and Google’s CEO put their number at 75%. The mechanical Rails got cheap.

So the role I hire for now is broader. A developer, in the sense that matters, owns the whole arc: spotting the problem, writing the requirements, building the feature, testing it, shipping it, and confirming the customer actually got what they needed. The code is one slice of that, and it’s the slice AI helps with most. The rest of the arc still sits squarely on the developer.

The job description has to hire for the expanded role, not the shrinking one.

That’s the shift, and it’s why a list of gems tells you almost nothing about whether someone can do the work.

What a Rails developer actually does now

A current Ruby on Rails developer job description should describe an owner. Here’s the real shape of the role.

• Turns a fuzzy problem into a clear requirement. Most of the cost of bad software is building the wrong thing well. Rails is fast to build in, which makes it easy to build the wrong thing quickly. A developer who can work out what the business actually needs is worth more than one who waits for a perfect ticket.
• Designs the app, not just the model. As a Rails app grows, the conventions stop making your decisions for you. Service objects, background jobs, data modeling, and where the logic lives are real architecture choices. AI is good at the generated scaffold. It is far weaker at the structure underneath.
• Writes and directs the code. They still write Ruby. But increasingly they’re steering an AI tool through it, which takes a different skill: knowing what to ask for, and knowing when the generated code is quietly wrong.
• Reviews everything, especially the AI’s work. This is the new core skill. Veracode found that 45% of AI-generated code carried a known security flaw, and the bigger, newer models were no safer. Rails makes some things easy and some footguns easy too, so review matters: in the 2025 Stack Overflow developer survey, 66% of developers said their top frustration with AI is code that’s “almost right, but not quite.”
• Owns testing and the deployment. The job isn’t finished at the merge. It’s finished when the feature is live and working for the customer.

Notice what’s missing: memorizing Rails trivia. A developer who can recite the Active Record callback order from memory but can’t tell when the AI generated an N+1 query that will melt under load is the wrong hire now. What you want instead is someone who reasons well and reviews carefully, even if they look up the API along the way.

The skills and requirements that still matter

You still need a requirements section. Just aim it at the right things.

Technical foundation (table stakes, not the whole story):

• Strong Ruby and Rails, with Active Record and a real grasp of the framework’s conventions
• Solid PostgreSQL or MySQL, background jobs, REST or GraphQL APIs, and testing (RSpec or Minitest)
• Version control, CI/CD, and cloud or managed-hosting familiarity
• Comfortable using AI coding tools, and honest about where they fall short

The skills that actually separate candidates:

• Judgment about code quality. Can they read a diff, AI-generated or not, and tell you what’s wrong with it, including the query that won’t scale?
• Product thinking. Do they ask why a feature exists and who it serves, or just build what they’re handed? When AI does the mechanical work, this becomes the durable skill, and the person who is only a coder is the most exposed.
• Communication. They have to write a clear requirement, explain a tradeoff, and push back when the plan is wrong.
• Architecture sense as the app grows. Rails conventions carry you early and stop carrying you later, which is where this matters most.

The technical list gets you a candidate who can function. The second list is what tells you whether they’re worth keeping.

Senior versus junior: the gap is wider now

A senior Rails developer job description and a junior one should look more different than they used to, because AI widened the distance between them.

A junior used to be slow because they were still learning Ruby and the conventions. AI mostly erased that penalty. What it didn’t erase is judgment, and judgment is the entire senior job. A senior Rails developer knows when the AI’s code hides an N+1 query, when a convention is the wrong fit as the app scales, and when to tell a stakeholder no. I have watched the failure mode up close: a junior ships the AI’s idiomatic-looking code because the tests passed, and the senior is the one who catches what happens when the table has a million rows.

So weight a senior description toward architecture, scaling judgment, mentoring, and owning ambiguous problems end to end. For a junior role, screen for reasoning and curiosity over how many gems they can name. The junior who asks good questions and checks the AI’s output is the one worth betting on.

How we screen for this at Full Scale

Writing the job description is the easy half. The hard half is telling, from a stack of candidates, who can actually do the expanded job, because anyone can put “product thinking” on a résumé.

We screen for it directly. Less than 3% of applicants make it through our process, and the bar isn’t trivia. We look at how someone reasons through an open problem, how they review code they didn’t write, and how they work with AI without leaning on it for the parts where judgment matters. If you want the actual questions, I wrote them up in our guide to Ruby on Rails developer interview questions, and the same philosophy runs through how we run offshore Ruby on Rails development for clients.

A trained team also beats a fresh job posting on speed. Our engineers go through an internal AI upskilling program, the Spartan Training Academy, so they aren’t guessing at how to use these tools. Rails always rewarded developers who could move fast without making a mess. AI raised the speed for everyone, which makes the “without making a mess” part the whole job.

A Ruby on Rails developer job description template you can use

Here’s a copy-paste template built for the role as it exists now. It leads with ownership and judgment on purpose, and keeps the technical stack at the bottom where it belongs. Edit the bracketed parts and cut what doesn’t apply.

Job title: Ruby on Rails Developer (or Senior Rails Developer)

About the role:

We’re looking for a Rails developer who owns problems end to end. You’ll work with [team/product] to figure out what to build, design how the app holds together as it grows, build it with Ruby on Rails, review your own and others’ code (including what AI tools generate), and make sure it actually ships and works for our customers.

What you’ll do:

• Turn business problems into clear technical requirements
• Design the app and own the architecture decisions as it scales
• Use AI coding tools effectively, and review their output critically
• Build and maintain features with Ruby on Rails
• Own quality through reviews and testing, and see your work through to deployment

What we’re looking for:

• Good judgment about code quality, including AI-generated code
• Product thinking: you ask why, not just how
• Clear communication and the confidence to push back
• Architecture sense as a Rails app grows past its conventions
• A solid technical floor: strong Ruby and Rails ([N]+ years), Active Record, a relational database, and testing

Nice to have:

• [Domain experience, e.g. fintech, marketplaces]
• Background jobs and high-traffic experience
• Front-end experience (Hotwire, React) for full-stack work

Use it as a starting point. The bullets that decide your hire are the judgment and product-thinking ones at the top, so keep them there.

Write the description for the job you actually have

The job changed, so the job description has to change with it.

If yours still leads with a list of gems and finishes with “writes clean, idiomatic code,” it measures the commodity part of the role while the part that actually decides whether the hire works out goes unmentioned. Lead with ownership, judgment, and product thinking. Treat the Rails stack as the floor, not the ceiling.

And if you’d rather skip the part where you screen a hundred candidates to find the one who can actually do the expanded job, that’s what we do. Talk to us about building your Rails team, and we’ll put pre-vetted developers in front of you who already work this way.