Skip to content

Hire a Databricks engineer

Databricks specialists employed by Data Science Lab who help build in your own workspace to your standards, as they do for GVB.

At GVB, we set up an MLOps workflow in Databricks with reusable templates

The travel behaviour segmentation model needed to run reliably and meet GVB’s data architecture standards. We therefore set up a consistent MLOps lifecycle in Databricks with Azure DevOps, so the model can remain in production and be maintained.

Read the case study

Who takes over the Databricks work while our team migrates?

The overnight job runs on a manually created cluster, the tables are still in the Hive metastore, and the colleague who set it up has left. One of our Databricks engineers takes it on in your workspace and records everything in Git.

Book a call
Teamleider staat aan het hoofd van een tafel en bespreekt de planning met vier collega's achter hun laptops.

Every Databricks role we provide is grounded in our own project experience

Discuss your project

Data engineer

Builds pipelines with Lakeflow and Spark in Python and SQL, as in Fokker Services Group’s data platform, which uses medallion architecture.

Data platform engineer

Configures workspaces, Unity Catalog, permissions and CI/CD as code, as we did for Vivara with Terraform and DevOps on Azure Databricks.

Analytics engineer

Creates tested data models with dbt on Delta tables, as in the data platform with Unity Catalog for Koninklijk Concertgebouworkest.

MLOps engineer

Deploys models to production reproducibly with MLflow and jobs, as in the MLOps lifecycle we set up for GVB in Databricks.

Get to know each other before choosing a Databricks specialist

  1. Workspace and assignment

    We discuss your cloud environment, workspace, the status of Unity Catalog and the backlog, then suggest suitable colleagues.

  2. Meet and choose

    You can speak to the candidate with no obligation and decide for yourself. If they’re not the right fit, we’ll suggest someone else.

  3. Access and getting started

    We arrange access permissions through a group in Unity Catalog beforehand. Code and design decisions go into your repository.

How does hiring a Databricks specialist work in practice?

Talk it through with us

Support that fits the assignment

There is no fixed minimum or maximum engagement period. We agree on the hours per week, duration and whether the work is on site or remote based on what the assignment requires.

What determines the rate

The expertise required, the specialist’s experience and the length of the engagement. We have plenty of experience with different procurement processes.

Employees, not freelancers

Our Databricks engineers are employed by Data Science Lab. Selection, onboarding and follow-up are handled through a single point of contact. Check your own hiring policy with HR, procurement or an adviser.

Not the right fit if

You want an entirely new platform delivered, the work is ongoing, or the sticking point lies in definitions and ownership. In those cases, a project, a permanent employee or data governance is a better fit.

Secondment through us, a freelancer or a project?

Secondment through us

Choose this if your team retains ownership of the platform but lacks Databricks capacity or expertise during a migration, a workload peak or a period of leave. We recommend it when the knowledge needs to stay with your team.

A Databricks freelancer

Choose this if you can assess and support candidates yourself, and can take responsibility as the client for arrangements concerning independent contractor status and the Dutch DBA Act.

The work as a project

Choose this if you want a completed platform, with one party responsible for its design and delivery, such as a Databricks implementation.

Our Databricks engineers have a whole team behind them

Data Science Lab is a Databricks Partner with certified consultants. Our engineers can draw on their colleagues, our in-house lab and the Techdays, where we share knowledge. We’ve worked with data and AI since 2016.

Book an introductory meeting

Your workspace and backlog are central to our first conversation

Stef Stoelwinder

Stef Stoelwinder

Business Development

Stef is your first point of contact. In our first conversation, we’ll discuss your Databricks environment, the project and your team, and what kind of profile would be the right fit.

What Databricks knowledge is our team missing right now?

Tell us about the project and the environment. We’ll reply by email or arrange an initial conversation.

Enter a valid email address.

Let us know how we can help you.

Frequently asked questions

Whatever your team needs on Databricks: loading data from sources with Lakeflow Connect or Spark, building pipelines with Lakeflow, scheduling tasks in Lakeflow Jobs, managing permissions and lineage in Unity Catalog, or defining jobs and pipelines as code.

The engineer works as part of your team, on your backlog. You can read how selection and placement work on our staffing page. Our partner page explains how we work with Databricks.

A Databricks engineer knows the platform’s components: Delta Lake, where all tables on Databricks are stored by default, Unity Catalog, Lakeflow, serverless compute and SQL warehouses. That matters if you already use Databricks or are migrating to it.

If the work is mainly about making data sources accessible and building data models, regardless of platform, a data engineer with broader experience is a better fit.

Yes, provided the engineer has account admin permissions or works with your admin. Workspaces created after 8 November 2023 have Unity Catalog automatically. For older workspaces, you set up identities at account level, connect the workspace to a metastore, migrate tables, and update queries and jobs.

For larger migrations, Databricks Labs provides the UCX tools. Afterwards, you disable the old features so no one can bypass the new permissions.

By running each workload on the cheapest suitable compute. Scheduled pipelines run on job compute, which Databricks says costs considerably less than all-purpose compute. SQL workloads belong on a SQL warehouse.

The engineer also tags workspaces and clusters by team or project from the outset, because tags cannot be applied retroactively. You can then see usage by tag in the system.billing.usage system table.

Our Databricks engineers are employed by Data Science Lab, which places them with clients. You have one point of contact for selection, onboarding and follow-up, and the engineer can draw on colleagues with other specialisms.

With a freelancer, you assess the quality yourself. Since 1 January 2025, the Dutch Tax Administration has resumed enforcement against false self-employment. As the client, you must therefore assess whether the assignment is suitable for a self-employed professional.

An account in your identity system, such as Microsoft Entra ID, that is provisioned at account level in Databricks. Grant permissions through a group in Unity Catalog, limited to the catalogues and schemas needed for the work, so you can revoke them easily at the end.

Also arrange access to the repository and development environment, and document who the client is and which standards apply.

By defining jobs and pipelines as code rather than creating them manually in the workspace. With Declarative Automation Bundles, formerly Databricks Asset Bundles, jobs, pipelines and their settings sit alongside the code in your repository, with review and CI/CD.

Where it makes sense, the engineer works on the same tasks as an internal colleague. Knowledge transfer happens when you want it, not just at the end of the assignment.

If the work is ongoing, you may be better off hiring someone directly. If you want a completed platform rather than additional capacity, a project is a better fit. If the issue is how data is defined or who owns it, more engineering will do little; start with data governance instead.

Want to compare providers first? See our overview of Databricks partners in the Netherlands.