Companies

Ruby on Rails board

Senior Ruby on Rails jobs

Senior on a Rails team is mostly measured by what you can change safely. Almost every codebase behind these listings is old enough to have opinions in it, and the person they are hiring is the one who can add a feature to that without the test suite getting slower or the on-call rota getting worse.

Open roles
186
Companies hiring
118
Countries
19
Fully remote
45
Pay published by the employer
109 of 186

See all 186 on the Ruby on Rails board →

The interview is about a migration

Sooner or later a senior Rails interview arrives at a table too big to lock, a backfill that has to run while the site is up, or a model that has quietly become two models. Having one of those to talk through — what you did, what went wrong, what you would do differently — is worth more than any amount of framework knowledge. The second most common question is how you found the cause of something slow, and the expected answer starts with a measurement.

Level names are not standard

Senior, staff and principal mean different things at different companies, and some employers still use one label for a ten-year span of experience. This collection filters on the level the listing itself states, so it inherits whatever the employer meant — we do not infer seniority from a title. Where a listing says nothing about level it will not appear here, which is the honest behaviour even though it hides some real matches.