Web apps
Customer-facing apps and internal tools built the Rails way, with a clear structure the next developer can follow.
Home / Technology / Hire developers / Ruby on Rails developers
Ruby on Rails developers · Apps, APIs and upgrades · USA and Canada
PromotEdge International lets businesses in the USA, Canada and other markets hire Ruby on Rails developers from our team. They build and maintain Rails web apps and APIs, move old apps to newer Rails versions, and fix slow or fragile code. By the hour, part-time or full-time, in your repository and under your lead. Our delivery team is in India.
Rails work that is readable, tested and easy for your team to carry on.
In short
PromotEdge International lets you hire a Ruby on Rails developer for a new app, a feature backlog or a version upgrade. Take one by the hour in blocks of 40 hours, part-time at 80 hours a month, or full-time at about 160. You interview and approve the person first.
On an existing app or a new one.
Customer-facing apps and internal tools built the Rails way, with a clear structure the next developer can follow.
JSON APIs for your mobile app or a partner, with versioning, authentication and tests.
A steady list of tickets cleared on branches, with pull requests your lead reviews.
An older Rails app moved to a newer version one step at a time, with tests at each step.
Slow pages and database queries found, measured and fixed.
Scheduled work, emails and links to payment, CRM and other services.
Versions and tools we work with: Ruby with Rails, a database such as PostgreSQL or MySQL, and the test tools your app already uses.
Brands we have worked with
















Work done for these clients' business in India by the PromotEdge group.
See all clientsWe use these details only to reply to you.
Rather talk now?
Examples of the Rails work people hand over first. You set the order.
The queries behind a slow page found with a profiler, then fixed with indexes or changed code, and checked again.
Tests for the part of the app that breaks most often, so later changes are safer.
A list of what blocks the next Rails version, with the order of steps and the tests to run at each one.
Stand-up in your overlap hours; the board and any failing tests reviewed.
Tickets built on branches, each with tests and a pull request.
Pull requests reviewed with your lead, and slow queries checked.
Merged work checked on staging, and next week's tickets agreed.
Each person is tested on the skills the role needs; the cards below are examples of what that can include, and the mix follows your app. Our hire page lists the four checks every developer passes.
Past Rails code, read for clear models, small controllers and tests a new teammate could run.
For example, a feature added to a sample Rails app with tests, then reviewed by a senior colleague.
Questions on slow queries, migrations that lock tables, and moving a Rails app to a newer version safely.
Your lead asks about your own code and tickets, and you say yes before the developer starts.
Pick by how much Rails work you have. The terms for each choice are on our hire page.
| Question | Hourly | Part-time | Full-time |
|---|---|---|---|
| Fits when | A bug, a slow page or a one-off task | A steady backlog of Rails tickets | A product that is built in Rails every day |
| Typical Rails work | Fixing a failing job or a slow report | Features and fixes each month | New features, upgrades and support across the app |
| Who sets the tasks | You, job by job | Your lead, week by week | Your lead, through the day |
Rails apps are often years old, and many teams need a developer who can read other people's code before writing their own. A hired Rails developer works in your repository, follows your conventions and takes tickets from your lead, so you keep control of the product.
Pick hourly for a fix or a review, and part-time for a steady backlog. Our hourly developers page covers how hours are agreed and logged. If your app also has a Python or Java service, you can hire Python developers or Java developers on the same terms.
Want the app built for you instead? See our web application development page or software maintenance for an older app.
A Rails developer's rate depends on the work, so we quote it after we hear what the app needs.
A written rate comes to you before any Rails work begins. The NDA, the paid trial week and your ownership of the code are covered by our hire terms.
Yes. Rails hours are sold in blocks of 40 and spent on jobs you approve, such as a bug, a slow page or a code review. Each hour is logged on a weekly timesheet that you approve before we bill. Our hourly developers page has the detail.
Yes. Taking over an app starts with reading it: the models, the tests, the deploy steps and the gems it depends on. The developer then lists what is risky, agrees a first set of tickets with your lead and works from your repository.
Yes. An upgrade starts with a check of which gems and code block the next version. The developer then moves one version at a time on a branch, fixes the warnings, and runs the tests at each step. Your team reviews each pull request, and production changes only after staging is clean.
Yes. Our Rails developers write tests for new code and add them around the parts of an older app that break most often. Where there are no tests yet, they begin with the code that runs most often.
That is the aim for every developer we place. They write readable code and a short note on how to run it and its tests. If you end a staff augmentation engagement, the 30 days' notice includes a handover.
Our hire page sets out one set of terms for every role, Rails included. Three are worth knowing first: the first week is a paid trial on a real task, the hours go on a weekly timesheet you approve, and the code belongs to you once it is paid for.
A real person reads every message and replies.