Developers for Go codebases

Hire developers
who fit your team

Tell us what you need, and within 48 hours we’ll introduce developers who work on Go 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 services, the Go release they’re on, how they’re 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, upgrades, work done at once and the checks around them.

New services and tools

Back-end services, APIs and command-line tools in Go, with their tests from the start.

Upgrades to a supported release

The go line raised one release at a time, with the removed settings checked first.

Leaks, races and time limits

The race detector in your tests, the leak profile on Go 1.27, and a time limit on every call.

Performance, measured first

Profiles before any change, and each change measured before and after.

APIs and integrations

REST and gRPC services, with data checked where it enters.

Checks in CI

Tests, the race detector, fuzzing and govulncheck on every change.

Builds and containers

One file per service, built for the systems you run, in your images and pipelines.

Planning a move to a supported Go release? Software development, in Go

Ways to hire

One developer

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

A small team

Developers who split the work on your services between them, from the upgrade and the time limits to the tools 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 keep us on a supported Go release from now on?

Yes. They raise the go line one release at a time on a branch, check the settings each release removes, and run your tests and the race detector before each step merges, so each new release is the next small step.

Can they find goroutine leaks and data races in our services?

Yes. They run the race detector in your tests and, on Go 1.27, the goroutine leak profile, then fix each cause where they find it.

Can they build the command-line tools our team uses?

Yes. They build each tool as one file for the systems your team uses, with its own tests.

Can you take on the whole project instead?

Yes. That starts with a written review of your services, their go.mod files, their builds and the way they run, and a proposal for a first step, such as one service moved up to a supported release.

Software development, in Go

Go is a trademark of Google. Webair is independent of Google, and isn’t sponsored by, endorsed by or affiliated with it.

Let’s build it better

Tell us which Go release your services run on and how they’re built, and we’ll introduce developers who can start there.

Thanks, we’ll be in touch soon.

{{ ctaStatus }}