Engineers for Databricks workspaces

Hire engineers
who fit your team

Tell us what you need, and within 48 hours we’ll introduce engineers for Databricks workspaces, 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 workspaces, the jobs that run there, 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

Pipelines, jobs, the catalog, and the runtimes they run on.

Pipelines

Data loaded on a schedule or as it arrives, with checks on each record.

Jobs from notebooks

The notebooks that matter moved into a repository, reviewed and scheduled.

Catalog upgrades

Tables moved off the legacy metastore, and file mounts replaced.

Grants

Access set for groups, at the level each team’s work fits.

Runtimes

Each job moved to a supported long-term support runtime, tested first.

Compute and costs

Compute that stops when it’s idle, policies, and tags by team.

Monitoring

Job alerts, and what the system tables show.

Planning a new data platform, or a bigger move? Data 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 workspaces together, from the pipelines and the jobs to the catalog, its grants and the runtimes underneath.

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 move our tables off the legacy metastore?

Yes. They upgrade the tables a schema at a time, point each job at the new names, and keep the old tables readable until every job has moved.

Can they get our jobs onto a supported runtime?

Yes. They list each job’s runtime and its end-of-support date, try each job on a newer long-term support runtime first, and move it ahead of that date.

Can they turn our notebooks into jobs we can review?

Yes. They move the notebooks that matter into a repository, add tests that run on every change, and deploy them as scheduled jobs.

Can you take on the whole project instead?

Yes. That starts with a written review of your workspaces, the jobs that run there and the tables they read, and a proposal for a first step, such as the jobs on the oldest runtime moved to a supported one.

Data engineering

Databricks is a trademark of Databricks, Inc., and Unity Catalog and Databricks Runtime are its products. Apache Spark, Spark, Apache and the Spark logo are either registered trademarks or trademarks of The Apache Software Foundation in the United States and other countries. Webair is independent of Databricks, Inc. and The Apache Software Foundation, and isn’t sponsored by, endorsed by or affiliated with either.

Let’s build it better

Tell us about your workspaces, the jobs that run there and the work ahead, and we’ll introduce engineers who can start there.

Thanks, we’ll be in touch soon.

{{ ctaStatus }}