Back to jobs

Senior ML Engineer

Reads like a Data Engineer role: pipelines and data infrastructure.

Pay
Pay not listed
Work setting
Not stated
Employment
Full-time — employment source
Employment type in the employer’s posting: Full-time
From the employer’s posting

What you’ll work on

Full posting
  • Design and maintain production data and feature pipelines for ML systems

  • Package, deploy and monitor models, with versioning and automated retraining

  • Build batch and ELT pipelines using Python, PySpark and cloud data services

  • Own and improve CI/CD for data and ML workflows

  • Mentor junior and mid-level data engineers through code review and knowledge sharing

From the employer’s posting
Take ownership of designing, building, and maintaining the production data and feature pipelines that machine learning systems depend on
Take models from prototype to production and keep them there: packaging and deployment alongside data science colleagues, model versioning, automated retraining, and the monitoring that catches drift and degradation before a client does
Build and maintain the batch and ELT pipelines the ML work sits on, using Python, PySpark, and cloud data services
Own and continuously improve CI/CD for data and ML workflows
Mentor and support junior and mid-level data engineers, reviewing code and sharing knowledge
Apply at CreateFuture

Posting record

Report an error
Status in our records
Live
First seen by us
Oct 16, 202636 days ago
Recorded sightings
42
Last seen by us
Nov 22, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 36

Similar jobs usually come down between day 6 and day 56.

From 14,766 similar postings that came down. Coming down is not always a hire.

CreateFuture is hiring

7 open jobs

Open jobs by the week we first saw them, last 12 weeks.

  • Hiring has slowed
  • Takes jobs down at a usual pace
Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • Python
  • SQL
  • AWS
  • Databricks
  • MLflow
  • Redshift
  • S3
  • SageMaker
  • Snowflake
  • PySpark
  • PyTorch
  • scikit-learn
  • TensorFlow
Where the posting names them
About the role and team: We are looking for a Senior Data Engineer with a machine learning focus to join our data team, taking ownership of the data and feature pipelines that production ML systems depend on, training data preparation, feature engineering, and the path from a model that works in a notebook to one that runs, and keeps running, in production. You’ll work with a high degree of autonomy on the more complex and ambiguous problems across client engagements, partnering closely with data scientists and ML engineers, while mentoring junior engineers and helping to raise the bar on engineering practice. The foundations still matter: this is a data engineering role at heart, built on Python, PySpark, and platforms like Databricks, Snowflake, or AWS. What you'll be doing:
- Take models from prototype to production and keep them there: packaging and deployment alongside data science colleagues, model versioning, automated retraining, and the monitoring that catches drift and degradation before a client does - Build and maintain the batch and ELT pipelines the ML work sits on, using Python, PySpark, and cloud data services (e.g., AWS Glue, EMR, S3, Redshift, Athena, or the Databricks / Snowflake equivalents), making sound decisions on architecture, data modelling, and tooling and weighing up trade-offs in performance, cost, and maintainability - Own and continuously improve CI/CD for data and ML workflows, ensuring reliable, repeatable deployments of pipelines and models alike
- Have deep SQL skills and hands-on experience with data modelling (e.g., Kimball, medallion/lakehouse patterns, or domain-driven modelling), this is the load-bearing, provider-agnostic skill underneath almost all of our pipeline work - Have strong Python and PySpark for batch processing, with production-grade, well-tested code. The bulk of this work is batch and ELT, but you’ll need to have experienced event-driven or micro-batch pipelines and know where the design assumptions stop holding - Have owned orchestration in production, dependency design, retries, SLAs, and the observability that tells you a pipeline failed before the client does
- Have designed and operated production data pipelines on a modern cloud data platform, AWS (Glue, EMR, Redshift, S3/Lake Formation), Databricks, Snowflake or comparable, and can talk about which of those decisions would travel to a different one, and which wouldn’t - Have deep SQL skills and hands-on experience with data modelling (e.g., Kimball, medallion/lakehouse patterns, or domain-driven modelling), this is the load-bearing, provider-agnostic skill underneath almost all of our pipeline work - Have strong Python and PySpark for batch processing, with production-grade, well-tested code. The bulk of this work is batch and ELT, but you’ll need to have experienced event-driven or micro-batch pipelines and know where the design assumptions stop holding
- Are comfortable with ML frameworks such as scikit-learn, PySpark MLlib, or PyTorch / TensorFlow, enough to productionise a data scientist’s work, reason about what a model needs from the data, and spot where a training pipeline and a serving pipeline have quietly diverged. You don’t need to be the person designing the model - Have designed and operated production data pipelines on a modern cloud data platform, AWS (Glue, EMR, Redshift, S3/Lake Formation), Databricks, Snowflake or comparable, and can talk about which of those decisions would travel to a different one, and which wouldn’t - Have deep SQL skills and hands-on experience with data modelling (e.g., Kimball, medallion/lakehouse patterns, or domain-driven modelling), this is the load-bearing, provider-agnostic skill underneath almost all of our pipeline work
- Have hands-on experience building the data and feature pipelines behind production machine learning, training data preparation, feature engineering, and feature stores, and understand why reproducibility and point-in-time correctness matter more than they first appear - Have worked with MLOps in practice rather than in principle: model versioning and registries, experiment tracking, automated retraining, and monitoring for drift and model degradation (MLflow, SageMaker, Databricks ML, Vertex AI or comparable) - Are comfortable with ML frameworks such as scikit-learn, PySpark MLlib, or PyTorch / TensorFlow, enough to productionise a data scientist’s work, reason about what a model needs from the data, and spot where a training pipeline and a serving pipeline have quietly diverged. You don’t need to be the person designing the model
- Have worked with MLOps in practice rather than in principle: model versioning and registries, experiment tracking, automated retraining, and monitoring for drift and model degradation (MLflow, SageMaker, Databricks ML, Vertex AI or comparable) - Are comfortable with ML frameworks such as scikit-learn, PySpark MLlib, or PyTorch / TensorFlow, enough to productionise a data scientist’s work, reason about what a model needs from the data, and spot where a training pipeline and a serving pipeline have quietly diverged. You don’t need to be the person designing the model - Have designed and operated production data pipelines on a modern cloud data platform, AWS (Glue, EMR, Redshift, S3/Lake Formation), Databricks, Snowflake or comparable, and can talk about which of those decisions would travel to a different one, and which wouldn’t

Your next step

Complete your application on job-boards.eu.greenhouse.io. The employer’s form will show what is required.

Applying through Greenhouse

  • No account needed: the form is one page, with an “Autofill my application” option that reads your resume.
  • Greenhouse doesn’t read resumes over 2.5 MB, or details placed in a header, footer, text box, table or second column. The file still attaches, but a recruiter has to type you in by hand.

Already applied? Track this application

Job description

View original posting ↗

Working at CreateFuture

CreateFuture is an AI-native consulting partner where people do work that matters and are supported to do it well. We work alongside organisations such as PayPal, adidas, NatWest, FanDuel and Money Saving Expert, building digital products and services that make a difference  while always putting people first.

We’re a team of creators. We write code, shape delivery, build go-to-market strategies, develop AI solutions and create the practices that support our people. We work side by side with our clients, challenging what’s not working and helping them to build the future. Our commitment to craft, quality, and culture has helped us scale to over 600 people in just a few years.

CreateFuture is a Great Place to Work-Certified™ company and has won Best Workplaces UK multiple years in a row.

Join us on our journey. Let’s create tomorrow, together, today.

 

About the role and team:

We are looking for a Senior Data Engineer with a machine learning focus to join our data team, taking ownership of the data and feature pipelines that production ML systems depend on, training data preparation, feature engineering, and the path from a model that works in a notebook to one that runs, and keeps running, in production. You’ll work with a high degree of autonomy on the more complex and ambiguous problems across client engagements, partnering closely with data scientists and ML engineers, while mentoring junior engineers and helping to raise the bar on engineering practice. The foundations still matter: this is a data engineering role at heart, built on Python, PySpark, and platforms like Databricks, Snowflake, or AWS.

What you'll be doing:

  • Take ownership of designing, building, and maintaining the production data and feature pipelines that machine learning systems depend on, training data preparation, feature engineering, and reproducible, point-in-time-correct datasets, with minimal supervision
  • Take models from prototype to production and keep them there: packaging and deployment alongside data science colleagues, model versioning, automated retraining, and the monitoring that catches drift and degradation before a client does
  • Build and maintain the batch and ELT pipelines the ML work sits on, using Python, PySpark, and cloud data services (e.g., AWS Glue, EMR, S3, Redshift, Athena, or the Databricks / Snowflake equivalents), making sound decisions on architecture, data modelling, and tooling and weighing up trade-offs in performance, cost, and maintainability
  • Own and continuously improve CI/CD for data and ML workflows, ensuring reliable, repeatable deployments of pipelines and models alike
  • Mentor and support junior and mid-level data engineers, reviewing code and sharing knowledge to raise the standard of delivery across the team
  • Troubleshoot and resolve complex issues in live data pipelines and deployed models, acting as a point of escalation for the wider team
  • Partner with data scientists, cross-functional teams, and client stakeholders to understand data and ML requirements and shape them into technical solutions

We'd love to talk to you if you:

  • Have hands-on experience building the data and feature pipelines behind production machine learning, training data preparation, feature engineering, and feature stores, and understand why reproducibility and point-in-time correctness matter more than they first appear
  • Have worked with MLOps in practice rather than in principle: model versioning and registries, experiment tracking, automated retraining, and monitoring for drift and model degradation (MLflow, SageMaker, Databricks ML, Vertex AI or comparable)
  • Are comfortable with ML frameworks such as scikit-learn, PySpark MLlib, or PyTorch / TensorFlow, enough to productionise a data scientist’s work, reason about what a model needs from the data, and spot where a training pipeline and a serving pipeline have quietly diverged. You don’t need to be the person designing the model
  • Have designed and operated production data pipelines on a modern cloud data platform, AWS (Glue, EMR, Redshift, S3/Lake Formation), Databricks, Snowflake or comparable, and can talk about which of those decisions would travel to a different one, and which wouldn’t
  • Have deep SQL skills and hands-on experience with data modelling (e.g., Kimball, medallion/lakehouse patterns, or domain-driven modelling), this is the load-bearing, provider-agnostic skill underneath almost all of our pipeline work
  • Have strong Python and PySpark for batch processing, with production-grade, well-tested code. The bulk of this work is batch and ELT, but you’ll need to have experienced event-driven or micro-batch pipelines and know where the design assumptions stop holding
  • Have owned orchestration in production, dependency design, retries, SLAs, and the observability that tells you a pipeline failed before the client does
  • Have experience owning the delivery of data engineering work with limited oversight, including CI/CD management and support
  • Have experience mentoring or supporting the development of less experienced engineers
  • Are comfortable working directly with stakeholders to shape technical solutions from ambiguous requirements, presenting your work, estimation and discussing tradeoffs and risks.

What we’ll offer you:

We trust people to do their best work. That means flexibility over rigid rules, impact over activity, and real investment in your growth both professionally and personally. You’ll be part of a supportive, and friendly culture, surrounded by smart, curious people who care deeply about what they do.

We offer flexible working, including hybrid and remote options. Our office hubs are located in Edinburgh, Leeds, Manchester, London and Bulgaria, with occasional travel to client sites or CreateFuture offices when needed.

We trust you to manage your time balancing collaboration with client time and focused work. What matters is the impact you have, not how busy you look.

Our hiring process

We try to keep our hiring process clear, fair and respectful of your time. We aim to get back to everyone who applies and we will be upfront about where you are in the process.

It usually looks like this:

  • Call with our Talent Acquisition Team 
  • Role specific capability interview 

Depending on the role, we might also ask you to do a short presentation, a practical or technical task or have a values focused conversation. We will explain what is involved before anything happens.

Inclusion at CreateFuture 

We believe diverse teams build better workplaces and better products. We want CreateFuture to be a place where people feel able to be themselves and do their best work.

If you need any adjustments or support during the application process, just. We will do what we can to help.

We look forward to your application!

Demand for Data Engineer roles

New Data Engineer postings at the employers we follow are up 13% over the last 6 weeks compared with the 6 before.

Weekly new Data Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 845, the most 1,344, and the latest week had 1,007.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under Data Engineer, by the work the posting describes.

Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.

Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.

An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.

US government figures for database architects

Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs

The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

United Kingdom

We trust people to do their best work. That means flexibility over rigid rules, impact over activity, and real investment in your growth both professionally and personally. You’ll be part of a supportive, and friendly culture, surrounded by smart, curious people who care deeply about what they do. We offer flexible working, including hybrid and remote options. Our office hubs are located in Edinburgh, Leeds, Manchester, London and Bulgaria, with occasional travel to client sites or CreateFuture offices when needed. We trust you to manage your time balancing collaboration with client time and focused work. What matters is the impact you have, not how busy you look.
Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.