Developers for Rust codebases

Hire developers
who fit your team

Tell us what you need, and within 48 hours we’ll introduce developers who work on Rust codebases, 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 code, what it sits beside, how it’s built and run, 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

Services, code beside C and C++, unsafe code and the checks around them.

Services and tools

New back-end services and the command-line tools your team uses, written in Rust with their tests.

Code beside C and C++

A C or C++ component replaced one at a time, its callers left as they are.

Unsafe code, reviewed

Each block kept small, with a safety note, tests under Miri where Miri can run them, and a safe interface around it.

Modules for your other code

Rust libraries packaged for your Python or Node.js code, or built as WebAssembly for the browser.

The latest stable release

The toolchain moved with the releases, with each dependency’s minimum Rust version checked.

Performance, measured first

The hot paths profiled first, then each change benchmarked against the code it replaces.

Checks in CI

Tests, Clippy, rustfmt and the advisory check on every change.

Planning to bring Rust into a C or C++ codebase? Software development, in Rust

Ways to hire

One developer

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

A small team

Developers who share the work on your codebase between them, from the unsafe review and the C boundary to the services and the checks in CI.

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 bring Rust into our C or C++ code one part at a time?

Yes. They move one component behind the interface it already has, run the same tests against both versions, and keep the unsafe code at the boundary small and reviewed.

Can they review the unsafe code we already have?

Yes. They find each unsafe block, write down what it relies on, add tests and run them under Miri where Miri can run them, and put a safe interface around what they can.

Can they build Rust modules our Python or Node.js code calls?

Yes. They build the module with its own tests, keep the boundary between the two languages small, and package it for the way you deploy.

Can you take on the whole project instead?

Yes. That starts with a written review of your crates, their unsafe parts, their tests and the way they’re built, and a proposal for a first step, such as one unsafe block documented and tested on a branch.

Software development, in Rust

Rust and Cargo are trademarks of the Rust Foundation. Webair is independent of the Rust Project and the Rust Foundation, and isn’t sponsored by, endorsed by or affiliated with either.

Let’s build it better

Tell us what your Rust code does and what it works with, and we’ll introduce developers who can start there.

Thanks, we’ll be in touch soon.

{{ ctaStatus }}