Engineers for infrastructure as code, with Terraform

Hire engineers
who fit your team

Tell us what you need, and within 48 hours we’ll introduce engineers who work with Terraform, 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 infrastructure, how changes reach it today, and who you need. The first call is free.

  2. We introduce.

    Meet engineers matched to it

    Within 48 hours, we introduce engineers 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

Code, plans, state and the upgrades around them.

New infrastructure in code

Written from the start, with a plan in every pull request.

What was set up by hand

Imported a part at a time, each plan read until it shows no changes.

Modules

Shared modules with versions, pinned where each team uses them.

State

Kept remote, locked while each change runs, with its access kept to the pipeline.

Renames and moves

Recorded in the code, so nothing running is replaced.

Drift

Plans run on a schedule, and each change found outside the code settled.

Upgrades

Terraform and its providers moved up on purpose, each step tried on a copy first.

Planning a new platform, or a bigger move? Infrastructure as code

Ways to hire

One engineer

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

A small team

Engineers who look after your infrastructure code together, from the modules and the plan in each pull request to the state and the upgrades.

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 engineers?

{{ eDevs }}

When should they start?

{{ eStart }}

{{ eHName }}

{{ eHMail }}

{{ eHSend }}

{{ hireThanks }}

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

Questions worth asking

How soon can an engineer start?

We introduce engineers 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 engineer 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

Some of our infrastructure was never in code. Can they bring it in?

Yes. They bring in each part with an import block, write its code until the plan shows no changes, and only then apply it.

Can they reorganize our code without replacing anything?

Yes. They record each rename and move in the code, and check the plan shows moves, not replacements, before anything is applied.

Can they move our state somewhere safer?

Yes. They move it to a remote backend with locking, keep its access to the pipeline, and check the next plan shows no changes.

Can you take on the whole project instead?

Yes. That starts with a written review of your code, where its state lives and how changes reach it, and a proposal for a first step, such as state moved to a remote backend with locking.

Infrastructure as code

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

Let’s build it better

Tell us about your infrastructure code, where its state lives and the changes ahead, and we’ll introduce engineers who can start there.

Thanks, we’ll be in touch soon.

{{ ctaStatus }}