Developers for Ruby on Rails applications

Hire developers
who fit your team

Tell us what you need, and within 48 hours we’ll introduce developers who work on Ruby on Rails applications, matched to your work, so you choose who joins your team.

Thanks, we’ll be in touch soon.

{{ heroStatus }}

You’re in good company

A few of the companies we’ve worked with.

How hiring works

From the first call to their first day, you decide each step.

  1. You tell us.

    Tell us about the work

    A short call about your app, the Rails and Ruby versions it runs on, how it’s deployed, and who you need. The first call is free.

  2. We introduce.

    Meet developers matched to it

    Within 48 hours, we introduce developers whose experience fits, with the work each has done.

  3. You choose.

    Choose who joins

    You talk to each one and decide who starts.

  4. They start.

    Start on a date you agree

    They join your team in your tools, and work in your time zone.

What they work on

Features, upgrades, background jobs and the checks around them.

Features in your app

New features in your codebase, with tests added around what they touch.

Upgrades to supported versions

Rails one minor release at a time and Ruby on its own step, with the warnings fixed first.

Background jobs

Jobs on the queue you run, with retries, and long jobs that can pick up after a restart.

Pages that update in place

Hotwire’s Turbo and Stimulus, or an API for your front end.

Faster pages and queries

Slow and repeated queries found and fixed, measured before and after.

APIs and integrations

JSON APIs and the services your app talks to, with incoming data checked before it’s used.

Checks in CI

Your tests, the code scanner, the gem audit and the style checks on every change.

Planning a move to a supported Rails version? Development for Ruby on Rails applications

Ways to hire

One developer

Full time, by the month, working as part of your team.

A small team

Developers who divide the work on your app between them, from the upgrade and the new defaults to the features and the background jobs.

How each is paid for: PricingWhen each way of working fits: Engagement Models

Working in your team

They work the way your team already does.

  • Your tools. Your own chat, tickets and code repository, so you see the work as it happens.
  • Your hours. They work in your time zone, on hours you agree before anyone starts.
  • Your access. You decide what they can reach, and remove it when they leave.

Tell us who you need

A few details are enough to start. We’ll reply by email to arrange a short call.

What should they work on?

{{ eWork }}

How many developers?

{{ eDevs }}

When should they start?

{{ eStart }}

{{ eHName }}

{{ eHMail }}

{{ eHSend }}

{{ hireThanks }}

We’ll be in touch by email, and introduce developers matched to your request within 48 hours.

Questions worth asking

How soon can a developer start?

We introduce developers matched to your work within 48 hours. Once you’ve chosen, they start on a date you agree.

Can we interview them first?

Yes. You talk to each developer and choose who joins.

Will they work in our time zone?

Yes. They work in your time zone, on hours you agree before anyone starts.

What does it cost?

It depends on the experience you need and how long you need them. Your proposal sets out the monthly fee and how you pay before anyone starts.

Pricing

Can they move us off a Rails version that no longer gets security fixes?

Yes. They fix the deprecation warnings first, move up one minor release at a time on a branch, and run your tests before each step merges.

Can they upgrade Ruby at the same time?

They move one at a time, so a failure has one cause: the newest Ruby you can move to first, then Rails, as Rails’ upgrade guide suggests.

Can they work on our background jobs?

Yes. They work on the queue you run, add retries where a job can fail, and split long jobs so they can pick up after a restart.

Can you take on the whole project instead?

Yes. That starts with a written review of your app, its Gemfile, its tests and the way it’s deployed, and a proposal for a first step, such as the deprecation warnings fixed on a branch.

Development for Ruby on Rails applications

Rails and Ruby on Rails are registered trademarks of David Heinemeier Hansson, exclusively licensed to The Rails Foundation. Webair is independent of Rails, its trademark owner and The Rails Foundation, and isn’t sponsored by, endorsed by or affiliated with any of them.

Let’s build it better

Tell us what your app does and which Rails version it’s on, and we’ll introduce developers who can start there.

Thanks, we’ll be in touch soon.

{{ ctaStatus }}