Developers who build on AWS

Hire developers
who fit your team

Tell us what you need, and within 48 hours we’ll introduce developers who build on AWS, 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 systems, how your accounts and access are set up, 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, accounts, access and the code that defines them.

New services and functions

Services, functions and background jobs added to what you run, with tests from the start.

Infrastructure as code

Your resources described in AWS CloudFormation or the AWS Cloud Development Kit, each change reviewed before CI deploys it.

Accounts and access

Accounts by environment, each person and service holding only the permissions it uses.

Containers

Services on Amazon ECS or Amazon EKS, their images rebuilt and kept up to date.

Data

Amazon RDS, Amazon Aurora and Amazon DynamoDB, with copies of the data restored in tests.

Versions within support

Runtimes, clusters and database engines moved forward before their standard support ends.

Costs and tags

Tags on every resource for its team and product, with budgets and alerts set.

Planning a new system on AWS, or a bigger move? Software development

Ways to hire

One developer

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

A small team

Developers who look after your systems together, from the accounts and the access to the code that defines them 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 work inside our accounts and access rules?

Yes. They sign in as themselves, with the access you give them, and the changes they make are recorded by AWS CloudTrail in your accounts.

Can they move what we built by hand into code?

Yes. They describe what’s running in code, one part at a time, and check it matches before anything changes.

Can they bring our versions back inside standard support?

Yes. They list each version against its end of standard support, and move each one forward on a branch, tested, before its date.

Can you take on the whole project instead?

Yes. That starts with a written review of your accounts, who can reach what, how much of what runs is in code and how it’s deployed, and a proposal for a first step, such as one role narrowed to the permissions it uses.

Software development

Amazon Web Services, AWS and the names of AWS services are trademarks of Amazon.com, Inc. or its affiliates. Webair isn’t affiliated with, sponsored by or endorsed by AWS.

Let’s build it better

Tell us about your systems on AWS, the accounts they run in and the changes ahead, and we’ll introduce developers who can start there.

Thanks, we’ll be in touch soon.

{{ ctaStatus }}