Back to jobs

Data Engineer (Autonomous Systems)

Oxford, England, United Kingdom

Actively hiring, first seen by us 3 days ago
Pay
Pay not listed
Work setting
On-site — work setting source
Work setup in the employer’s posting: On-site
From the employer’s posting
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
  • Build low-latency ingestion for live video, sensor telemetry, robot state and instrument signals

  • Work across the edge-to-cloud stack, from MQTT brokers to Kafka topics, storage and APIs

  • Turn robot, instrument and video streams into structured database records

  • Build a knowledge graph linking inputs to results and traceable to source video and sensor data

  • Make outputs model-ready with the formats, labelling and provenance training needs

From the employer’s posting
Build high-throughput, low-latency ingestion for live video, sensor telemetry, robot joint state and instrument control signals
Work across the edge-to-cloud stack, from edge devices and MQTT brokers through to Kafka topics, cloud storage, and the APIs that serve scientists and ML pipelines
Turn streams of robot state, instrument output and video into structured database transactions
Build the knowledge graph on top of that, linking inputs to results, so that a fact can always be traced back to the video segment and sensor readings behind it
Make the output model-ready: the formats, sampling, labelling and provenance that training and evaluation need

Before you apply

Work authorization
Must already have the right to work in the UKYou must have the right to work permanently in the UK with a willingness to travel as necessary

What you’ll bring

All qualifications

Core experience

  • Experience with real-time data streaming - Kafka or Pub/Sub (or equivalent), and the challenges that come with high-frequency, low-latency data capture.
  • Knowledge, entity, search or feed systems where correctness under continuous update was the hard part.
  • Experience working close to model development, such as curating training or evaluation data, or building the data systems that feed models.
Qualification wording
Experience with real-time data streaming - Kafka or Pub/Sub (or equivalent), and the challenges that come with high-frequency, low-latency data capture.
Knowledge, entity, search or feed systems where correctness under continuous update was the hard part.
Experience working close to model development, such as curating training or evaluation data, or building the data systems that feed models. You don’t need to be a machine learning engineer, but you should know what makes a dataset good.

Posting record

Report an error

Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 18, 20263 days ago
Recorded sightings
5
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 3

Early. 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.

Ellison Institute of Technology is hiring

6 open jobs

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

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
  • Kafka
  • FastAPI
Where the posting names them
Nobody checks every box - if you’re not sure if you’re qualified, we still encourage you to apply. - You have strong programming experience in Python, and value code quality, reliability, and performance while adapting to an evolving industry. - You think in systems and own them end-to-end - from device output to APIs - and embrace long-term engineering rather than one-off scripts.
Your Role: At EIT we are seeking an experienced Data Engineer to join our Scientific Compute and Data team. Our Data Engineers in Autonomous Systems work within a wider project, AutoLabs. This is where EIT automates the scientific discovery loop: experimental design, execution, analysis, and the learning that feeds back into the next experiment and the lab itself. The AutoLabs data platform captures, stores and serves high-frequency multimodal data. It spans an edge-to-cloud telemetry stack (MQTT, Kafka, media streams such as HLS), streaming APIs, and a growing set of hardware integrations across multiple sites including robotic systems, sensor rigs and lab instruments. Our labs produce raw data for a fast-growing set of models: vision-language-action models, orchestration and monitoring models, and world models that learn the dynamics of a laboratory to simulate experiments before they are run.
- Build high-throughput, low-latency ingestion for live video, sensor telemetry, robot joint state and instrument control signals, integrating validation at the edge before data reaches the cloud. - Work across the edge-to-cloud stack, from edge devices and MQTT brokers through to Kafka topics, cloud storage, and the APIs that serve scientists and ML pipelines. - Turn streams of robot state, instrument output and video into structured database transactions: which arm did what to which sample, when, and what came out.
- You think in systems and own them end-to-end - from device output to APIs - and embrace long-term engineering rather than one-off scripts. - Experience with real-time data streaming - Kafka or Pub/Sub (or equivalent), and the challenges that come with high-frequency, low-latency data capture. - You treat reproducibility, version control, schema design and lineage as the things that make good science possible.
- Knowledge, entity, search or feed systems where correctness under continuous update was the hard part. - Stateful stream processing (Flink, Kafka Streams, Beam or similar): event time, watermarks, exactly-once. - APIs for data ingestion and consumption with FastAPI, gRPC or GraphQL.
- Stateful stream processing (Flink, Kafka Streams, Beam or similar): event time, watermarks, exactly-once. - APIs for data ingestion and consumption with FastAPI, gRPC or GraphQL. - Graph stores and entity resolution or curation at scale, where the interesting decisions are about what to keep, merge or drop.

Your next step

Complete your application on apply.workable.com. The employer’s form will show what is required.

Applying through Workable

  • No account needed. You can import your resume to fill in the form, or skip that and fill it in yourself.

Already applied? Track this application

Job description

View original posting ↗

Join us at EIT:

At the Ellison Institute of Technology (EIT), we’re on a mission to translate scientific discovery into real world impact. We bring together visionary scientists, technologists, engineers, researchers, educators and innovators to tackle humanity’s greatest challenges in four transformative areas:

  • Health, Medical Science & Generative Biology
  • Food Security & Sustainable Agriculture
  • Climate Change & Managing CO₂
  • Artificial Intelligence & Robotics

This is ambitious work - work that demands curiosity, courage, and a relentless drive to make a difference. At EIT, you’ll join a community built on excellence, innovation, tenacity, trust, and collaboration, where bold ideas become real-world breakthroughs. Together, we push boundaries, embrace complexity, and create solutions to scale ideas from lab to society. Explore more at www.eit.org.

The Scientific Compute and Data Team

The Scientific Compute and Data team builds the compute, data and tooling foundation behind EIT's science. We run the cloud and GPU infrastructure that the models train on, the data infrastructure that instruments, robots and researchers use, and the data products and shared data models that let one team's results be built on by the next. We provide hands-on expertise in platform engineering, data engineering, and data management, and create common tooling for every lab to accelerate their experiments across gene editing, battery chemistry, plant biology and more. 

Your Role:

At EIT we are seeking an experienced Data Engineer to join our Scientific Compute and Data team. Our Data Engineers in Autonomous Systems work within a wider project, AutoLabs. This is where EIT automates the scientific discovery loop: experimental design, execution, analysis, and the learning that feeds back into the next experiment and the lab itself. The AutoLabs data platform captures, stores and serves high-frequency multimodal data. It spans an edge-to-cloud telemetry stack (MQTT, Kafka, media streams such as HLS), streaming APIs, and a growing set of hardware integrations across multiple sites including robotic systems, sensor rigs and lab instruments. 

Our labs produce raw data for a fast-growing set of models: vision-language-action models, orchestration and monitoring models, and world models that learn the dynamics of a laboratory to simulate experiments before they are run.  

As a Data Engineer, you’ll work directly alongside AI researchers, software engineers, robotics engineers, and domain scientists to build the data layer that makes our autonomous operations possible. You will contribute to an engineering culture that values robust system design, testing, and deep collaboration, but allows flexibility for rapid prototyping and responsiveness to changing landscapes. 

  

Day-to-Day, You Might: 

  • Build high-throughput, low-latency ingestion for live video, sensor telemetry, robot joint state and instrument control signals, integrating validation at the edge before data reaches the cloud. 
  • Work across the edge-to-cloud stack, from edge devices and MQTT brokers through to Kafka topics, cloud storage, and the APIs that serve scientists and ML pipelines. 
  • Turn streams of robot state, instrument output and video into structured database transactions: which arm did what to which sample, when, and what came out. 
  • Build the knowledge graph on top of that, linking inputs to results, so that a fact can always be traced back to the video segment and sensor readings behind it. 
  • Make the output model-ready: the formats, sampling, labelling and provenance that training and evaluation need, working directly with the researchers who consume it. 

Requirements

What Makes You a Great Fit 

Nobody checks every box - if you’re not sure if you’re qualified, we still encourage you to apply.  

  • You have strong programming experience in Python, and value code quality, reliability, and performance while adapting to an evolving industry.  
  • You think in systems and own them end-to-end - from device output to APIs - and embrace long-term engineering rather than one-off scripts. 
  • Experience with real-time data streaming - Kafka or Pub/Sub (or equivalent), and the challenges that come with high-frequency, low-latency data capture. 
  • You treat reproducibility, version control, schema design and lineage as the things that make good science possible. 
  • A clear, respectful communicator who can collaborate with scientists, roboticists and researchers. 

  

It would be great if you also have: 

  • Automated lab or life sciences environments - instrument APIs, lab protocols, and what scientists expect of data quality. 
  • Data pipelines for physical systems: robotics (e.g. MQTT), autonomous vehicles, lab or clinical instruments, industrial control, or similar environments. 
  • Knowledge, entity, search or feed systems where correctness under continuous update was the hard part. 
  • Stateful stream processing (Flink, Kafka Streams, Beam or similar): event time, watermarks, exactly-once. 
  • APIs for data ingestion and consumption with FastAPI, gRPC or GraphQL. 
  • Graph stores and entity resolution or curation at scale, where the interesting decisions are about what to keep, merge or drop. 
  • Experience working close to model development, such as curating training or evaluation data, or building the data systems that feed models. You don’t need to be a machine learning engineer, but you should know what makes a dataset good. 

Benefits

We offer the following benefits:

  • Salary dependent on experience + travel allowance + bonus 
  • Enhanced holiday. Our annual leave allowance is 25 days plus 8 bank holidays and an additional 3 days between Christmas and New Year. You will also have the opportunity to purchase an additional 5 days annual leave in January and July.
  • Pension - Employer contribution 7.5%, minimum employee contribution 5%
  • Life Assurance.
  • Income Protection
  • Private Medical Insurance as standard for you, your partner and any dependents. Including hospital Cash Plan
  • Employee discounts
  • Electric car scheme
  • Nursery Salary Sacrifice scheme
  • Cycle to Work Scheme
  • Family Planning
  • Neurodiversity support including advise and assessments
  • Coaching & Therapy services

 

Working Together – What It Involves:

  • 2 days per week in Oxford office, 1 day per week in employee’s choice of Oxford or London office, 2 days per week work from any UK location. 
  • You must have the right to work permanently in the UK with a willingness to travel as necessary. In certain cases, we can consider sponsorship, and this will be assessed on a case-by-case basis.

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

Oxford, England, United Kingdom

Working pattern and location restrictions need checking in the full posting.

Work authorization
- 2 days per week in Oxford office, 1 day per week in employee’s choice of Oxford or London office, 2 days per week work from any UK location. - You must have the right to work permanently in the UK with a willingness to travel as necessary. In certain cases, we can consider sponsorship, and this will be assessed on a case-by-case basis.

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.