Engineers for Kubernetes® clusters

Hire engineers
who fit your team

Tell us what you need, and within 48 hours we’ll introduce engineers for Kubernetes clusters, 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 clusters, how changes reach them 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

Clusters, the changes that reach them, and the upgrades they need.

Clusters and their setup

Clusters laid out for what runs on them, on a cloud’s managed service or your own machines, and defined in code.

Changes, one way in

The cluster’s files kept in the repository, reviewed, and applied only from CI.

Rollouts

New versions rolled out a few copies at a time, each copy ready before it counts.

Limits and access

Requests, limits, network policies and the Pod Security Standards set for each workload.

Upgrades

Each minor release in turn, with removed APIs found first and the add-ons kept current.

Monitoring

Logs, metrics and alerts that show what restarted and why.

Room and costs

Requests set from measured use, and machines sized to fit.

Planning a new platform, or a bigger move? Engineering

Ways to hire

One engineer

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

A small team

Engineers who look after your clusters together, from the files in the repository and the checks in CI to the upgrades and the alerts.

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

Can they replace our Ingress NGINX controller?

Yes. They map what each route does today, try Gateway API or another Ingress controller on a copy of the cluster, and move the traffic over one route at a time.

Can they bring our cluster back into support?

Yes, one minor release at a time, each tried on a copy of the cluster first, with the files checked for removed APIs before each step.

Can they put what was changed by hand back into the repository?

Yes. They compare what’s running with what’s written down, write what’s missing into the repository, and from then on apply changes only from there.

Can you take on the whole project instead?

Yes. That starts with a written review of your clusters, how changes reach them and what runs against what’s written down, and a proposal for a first step, such as one service’s files moved into the repository.

Engineering

Kubernetes is a registered trademark of LF Projects, LLC in the United States and/or other countries. Webair is independent of LF Projects, LLC, The Linux Foundation and the Kubernetes project, and isn’t sponsored by, endorsed by or affiliated with any of them.

Let’s build it better

Tell us about your clusters, how changes reach them and the upgrades ahead, and we’ll introduce engineers who can start there.

Thanks, we’ll be in touch soon.

{{ ctaStatus }}