Companies

Ruby on Rails board

Full-stack Ruby on Rails jobs

Rails was built for one person to carry a feature from the migration to the button, and full-stack listings here are the ones that still expect that. The filter is a plain one: these are the Rails roles on the board that are not marked backend-only, so the work reaches the browser as well as the database.

Open roles
53
Companies hiring
45
Countries
15
Fully remote
12
Pay published by the employer
26 of 53

See all 53 on the Ruby on Rails board →

What full-stack means on a Rails team today

Usually one of two shapes. Either the frontend is server-rendered with Hotwire and the boundary barely exists, or there is a React or Vue application talking to a JSON API and the boundary is the interesting part of the job. Those are different roles with the same title, and the tags on each listing will tell you which one you are looking at faster than the prose will.

The advantage is the seam

The reason teams pay for this is that most awkward bugs live where the layers meet: a serializer that quietly changed shape, a form that posts something the controller was not expecting, an N+1 that only appears once the page renders a list. Candidates who can talk about a bug they found by following it across the seam interview much better than candidates who present two separate skill sets.