Time since we first saw it
Day 91
Up longer than most. Similar jobs usually come down between day 6 and day 56.
From 14,767 similar postings that came down. Coming down is not always a hire.
Nice, France
Open 3 months, first seen by us 91 days agoWork setup in the employer’s posting: RemoteFrom the employer’s posting
Employment type in the employer’s posting: Emp. Full-Time (CDI) - EOS FranceFrom the employer’s posting
Design ingestion for offline recording nodes, including buffering and reconciling late data on reconnection
Define which data is prioritised during short, bandwidth-limited connection windows
Handle sensor time-series data and clock drift across nodes
Own orchestration workflow definitions, including retry, idempotency and backfill behaviour
Design ingestion for distributed recording nodes that are offline most of the time, including local buffering, resumable transfer, and reconciliation of late-arriving or out-of-order data on reconnection.
Define, together with the ML team, which data is prioritised during short and bandwidth-limited connection windows.
Work with sensor-generated data, including sequential data where timestamps and the order of observations are important, and handle clock drift across nodes to ensure timing remains trustworthy downstream.
Own the workflow definitions in our orchestration layer: what runs, in what order, and with what retry, idempotency and backfill behaviour.
Demonstrated experience designing and implementing data pipelines from zero (not cloud-based), including architectural and technical decisions.
Experience building pipelines involving at least some of the following: images, video, sensor data, time-series or other sequential data.
Experience with systems that must tolerate unreliable or absent network connectivity and recover gracefully, offline-first, store-and-forward, edge collection or similar architectures.
Experience running data infrastructure on bare metal or self-managed servers, rather than exclusively on managed cloud services.
Good understanding of data ingestion, transformation, storage, validation and data-quality principles.
Experience working with large or complex datasets.
Open 3 monthsWe first saw this posting 91 days ago and it is still up. Roles open this long are often slow to fill or kept open to collect applications.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 91
Up longer than most. Similar jobs usually come down between day 6 and day 56.
From 14,767 similar postings that came down. Coming down is not always a hire.
2 open jobs
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.
- Work with sensor-generated data, including sequential data where timestamps and the order of observations are important, and handle clock drift across nodes to ensure timing remains trustworthy downstream. - Develop robust and scalable data processing solutions using Python and SQL. - Design appropriate data models and storage approaches according to the nature and use of the data, including capacity planning and retention for large volumes of image and video data on self-managed storage.
- Demonstrated experience designing and implementing data pipelines from zero (not cloud-based), including architectural and technical decisions. - Good programming skills in Python & SQL - Professional experience working with several different types of data
We are looking for someone with strong professional experience who has already designed and built data pipelines from the ground up, rather than only maintaining or using existing pipelines. This platform runs entirely on our own infrastructure, no AWS, GCP or Azure, and no managed services to fall back on. Deployed systems are genuinely air-gapped: they operate offline for extended periods and connect only briefly, on request, with limited bandwidth. Deciding what data is worth those windows, and designing pipelines that behave correctly when nodes reconnect with large backlogs, is central to the role. Your assumptions about cloud-native workflows will be tested regularly. Our data environment is complex and varied. We work not only with traditional structured/tabular data, but also with images, video and temporal/time-series data, including data generated by sensors and tracking systems where the sequence and timing of information are critical.
Complete your application on marss.bamboohr.com. The employer’s form will show what is required.
Already applied? Track this application
Job Title: Data Engineer – Complex Data Pipelines (On-Premise)
Reports to: VP AI
Location: France - Nice
Type: Full-time
The Role
We are looking for an experienced Data Engineer to join our AI team and play a key role in building our in-house data platform and pipelines.
We are looking for someone with strong professional experience who has already designed and built data pipelines from the ground up, rather than only maintaining or using existing pipelines.
This platform runs entirely on our own infrastructure, no AWS, GCP or Azure, and no managed services to fall back on. Deployed systems are genuinely air-gapped: they operate offline for extended periods and connect only briefly, on request, with limited bandwidth. Deciding what data is worth those windows, and designing pipelines that behave correctly when nodes reconnect with large backlogs, is central to the role. Your assumptions about cloud-native workflows will be tested regularly.
Our data environment is complex and varied. We work not only with traditional structured/tabular data, but also with images, video and temporal/time-series data, including data generated by sensors and tracking systems where the sequence and timing of information are critical.
You will design the architecture required to ingest, process, transform, store and make these different data sources available to our AI and software teams.
This role works alongside an MLOps Data Engineer who owns the infrastructure, environments and deployment layer. You own the data itself: architecture, models, pipelines, quality, and prioritisation. Both roles report directly to the VP AI.
Main Responsibilities
Requirements
New Data Engineer postings at the employers we follow are up 13% over the last 6 weeks compared with the 6 before.
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.
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.
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.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Nice, France
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.