Skip to content

Hire a machine learning engineer

Engineers employed by Data Science Lab bring your models into production as part of your own team, as they do in Waternet’s Datalab team.

As part of Waternet’s data lab team, we put models into production

Waternet’s data lab team works on projects that are put into practice. As part of the team, we set up and maintain the workflow, from the MLflow model registry and CI/CD templates to code and models in production, including a model to minimise nitrous oxide emissions at a wastewater treatment plant.

Read the case study

Why isn’t our model making it out of the notebook?

Your data scientist’s model performs well in the notebook, but no one turns it into a service with tests, versioning and monitoring. A machine learning engineer does that within your team and leaves a clear path to production.

Book a meeting
Twee collega's kijken samen naar een laptop aan een bureau, met papieren en notities ernaast.

Who you hire depends on where the model is stuck

Discuss your model

Machine learning engineer

Turns a notebook into tested code, a training pipeline and an endpoint or batch job, as at Waternet, where we put code and models into production.

MLOps engineer

Sets up a model registry, CI/CD and monitoring for multiple models at once, as at GVB, with a workflow and reusable templates in Databricks.

Data scientist

Explores what a model can do with new data, as in ProRail’s Datalab, using fibre-optic cables that measure sound waves along the railway.

AI engineer

Connects the model to an application so its output reaches people where they work, as at LUMC, in an easy-to-navigate application.

Talk to the engineer about your own model before you decide

  1. Model and environment

    We discuss which model needs to go into production, which platform it runs on and who will manage it.

  2. Profiles and introductions

    We introduce you to colleagues with experience on your platform. You can speak to them with no obligation and make your own decision.

  3. Working alongside your team and handing over

    The engineer works in your repository and backlog. What works is then captured in code, templates and documentation.

Is an ML engineer right for our team and our needs?

Find out in a conversation

A good fit if

You already have a model or a clear question backed by data, but your team lacks the expertise to put it into production and keep it running reliably.

Not a good fit if

You don’t yet have a question or the data to build a model, or you want a finished application rather than extra hands. In that case, a project is the better route.

Duration and rates

There is no fixed minimum or maximum engagement period. The cost depends on the expertise you need, the engineer’s experience and the length of the assignment.

Employed by us

You’re not hiring a freelancer: the engineer has an employment contract with Data Science Lab. HR, procurement or an adviser can check whether this fits your organisation’s policies.

Bring in an engineer, have the model built or hire someone in-house?

Bring in an engineer

Choose this if your data scientists will build and own the model, but need help getting it into production. It’s our recommendation when your first model needs to go live.

Have the model built

Choose this if you want a working application, with one provider handling both design and delivery. See commissioning machine learning development.

Hire someone in-house

Choose this if you’ll be developing models on an ongoing basis and need to keep the expertise in-house. Our engineer can establish the way of working and train your new colleague.

Behind every engineer is a team that keeps models running in production

Our engineers can draw on colleagues who have worked on models in production at Waternet, GVB and LUMC, as well as our internal lab and Techdays. Data Science Lab has been around since 2016.

Book an introductory meeting

Your model and platform are the focus of our first conversation

Stef Stoelwinder

Stef Stoelwinder

Business Development

Stef is your first point of contact. In our first conversation, we’ll discuss which model needs to go into production, which platform it runs on and what kind of specialist you need.

Which model should we put into production?

Tell us which model, platform and team are involved. We’ll reply by email or suggest an initial conversation.

Enter a valid email address.

Let us know how we can help you.

Frequently asked questions

A machine learning engineer makes sure a model works outside the notebook. They turn experimental code into tested Python code, build the pipeline that trains and deploys the model, put the model behind an endpoint or in a batch job, and set up monitoring.

Our staffing page lists this role as a machine learning specialist, alongside roles such as data scientist, AI engineer and MLOps engineer. The right colleague depends on your model and your platform.

A data scientist works out which model answers a question and whether it performs better than a simple baseline. A machine learning engineer puts that model into production and keeps it running. An MLOps engineer sets up the shared process that all models follow: model registry, CI/CD and monitoring.

In small teams, one person often covers two of these roles. If you want that process set up as a project, read about MLOps.

Training-serving skew is the difference between how well a model performs during training and in production. A common cause is that inputs are calculated slightly differently in production than in the notebook, for example because IT has rebuilt the calculation in another language.

Google recommends using the same code in the training and production pipelines as much as possible. That is exactly what an ML engineer does: create one tested preprocessing step that runs in both pipelines.

That depends on when you need the result. If an application needs an immediate answer for each request, you put the model behind an endpoint. If a result for all records every night or every hour is enough, a batch job is easier to manage.

In Databricks, you can do both with Model Serving for models registered in Unity Catalog. Azure Machine Learning has online and batch endpoints. With an online endpoint, you can split traffic between the old and new versions, allowing you to switch safely.

Since 1 January 2025, the Belastingdienst has resumed full enforcement of the rules on false self-employment. Whether someone works as an employee in practice depends on factors including supervision, integration into the organisation and whether they operate as a business.

An ML engineer placed with you by Data Science Lab has an employment contract with us. That is different from contracting a freelancer directly. Have HR, procurement or an adviser review your own hiring policy.

If the model processes personal data, the GDPR applies. According to the Autoriteit Persoonsgegevens, a DPIA is mandatory if you use algorithmic systems involving personal data, even for a pilot. The AI Act classifies software that sorts CVs, among other applications, as high-risk; according to the European Commission, those obligations will apply from 2 December 2027.

An ML engineer sets up logging, model versioning and monitoring so you can show how a model was developed. Your legal counsel or compliance department should assess whether the rules apply to your model. Read more about AI governance.

If you do not yet have a model or a clear question, an engineer has nothing to put into production. Start with data science or a maturity assessment instead. If the problem is missing or messy data, work on the data foundation first.

If you expect to keep adding models, hiring someone permanently makes more sense. If you need a finished application rather than extra hands, have the model built as a project.