You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
STARK

Data Platform Engineer – Data Operations (all genders)

  • Office
  • English (B2)

Salary

Not stated

Similar roles pay €55K - 110K a year · our estimate

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The company builds autonomous defence platforms and AI-driven software for NATO Allies and partners, and it is growing its Data Operations team.

The team handles the full data lifecycle for the company's AI stack: collecting, acquiring, generating, curating and managing data. It runs its own data-collection campaigns across Europe, evaluates new sensors and platforms, and builds the internal data platform that turns raw recordings into datasets ready for use. Everything it produces feeds the perception and autonomy systems on the company's platforms.

The role centres on the software behind the data platform: metadata systems, ETL pipelines, data contracts, catalogs, databases and internal tools. The aim is for engineers to find, check, and reuse terabytes of multi-sensor field data in minutes rather than days. Data context is treated as a product, meaning it is structured, searchable, version-aware, documented and traceable from the raw recording through to the ML workflow that uses it.

You will act as the link between field data collection, external annotation vendors and the ML engineers who train models, and you will automate the workflows that connect these groups.

Responsibilities

  • Design, write and maintain typed Python software and ETL pipelines that ingest and merge field recordings (flight data, rosbags, video) and vendor deliveries into the company's GCP cloud storage.
  • Build tools that sub-sample video, extract useful frames, package datasets and give people self-serve data access.
  • Design, implement and maintain metadata databases and data catalogs that track datasets, recordings, sensors, labels and lineage, using SQL and sound schema design.
  • Own the technical workflows for data curation and labeling: build the operational tooling, coordinate external labeling subcontractors, track progress and run automated QA.
  • Develop backend APIs, self-service dashboards and data-access tools so the wider AI and engineering organisation can search, filter and understand terabytes of multi-sensor data.
  • Set and enforce engineering standards in a young codebase, covering testing, typing, documentation, logging and CI/CD.
  • Take on open-ended problems, migrate legacy data, manage access, and automate manual support tasks so they are not repeated.

Requirements

  • Strong Python skills, with clean, typed, tested code and a software engineering approach to data problems.
  • Proven experience building and running robust ETL and data ingestion pipelines.
  • Solid SQL, ideally PostgreSQL, with good schema design, data modelling and metadata system experience.
  • Hands-on work with object storage (GCP/GCS or S3), plus basic Docker and CI/CD.
  • Comfort with Unix/Linux, shell scripting and standard command-line tools.
  • Ability to weigh a quick fix against a long-term architecture, and to adapt when startup priorities shift.
  • Able to coordinate with external vendors and non-technical stakeholders on labeling and curation work.
  • Willingness to handle support tasks, combined with the skill to automate them.
  • Nice to have: experience with synthetic data generation or GenAI-assisted workflows, such as auto-labeling, data augmentation or foundation-model-based curation.
  • Nice to have: familiarity with data versioning tools (DVC, LakeFS, FiftyOne), computer vision annotation formats such as COCO, or large-scale curation workflows.
  • Nice to have: experience with GCP services beyond storage, such as BigQuery, Cloud Run and IAM.
  • Nice to have: exposure to robotics data formats (ROS bags, MCAP, PX4 logs) or heavy multi-modal streams such as video and lidar.
  • Send your CV in English.
  • Candidates must be eligible to obtain and keep the security clearance this role requires. Details follow during recruitment.

Conditions

Work in a defence-sector environment where candidates must be able to obtain and maintain the required security clearance.

Equal opportunity applies to all candidates.

Benefits

  • The work protects personnel and supports European and national sovereignty.
  • You will work alongside leading specialists in autonomous systems, advanced propulsion and secure cyber platforms.
  • The environment is fast-paced and collaborative, with strong R&D support for new ideas.

Where you’d work

From the office

About the company

STARK

Office in Munich, Germany

Also hiring in United Kingdom, Berlin, Germany, Stockholm, Sweden and 2 more places

4 of their 46 open roles are remote

Your chances

Worth a look before you spend an evening tailoring a CV for it.

  • 19 checks run
  • 3 red flags

Still hiring?

13 checks

2 red flags

How crowded?

6 checks

1 red flag

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details9 facts · Role, Location, Compensation, Requirements
Tech stack
  • Python
  • SQL
  • PostgreSQL
  • Docker
  • BigQuery
  • LLMs
  • Computer vision
Specialty
Data Engineering
Region
Europe
Pay period
Annual
Show 5 more factsShow less

Role

Category
Data & Analytics
Specialty
Data Engineering
Tech stack
  • Python
  • SQL
  • PostgreSQL
  • Docker
  • BigQuery
  • LLMs
  • Computer vision

Location

Work model
Office
Region
Europe
Office
  • Munich, Germany

Compensation

Salary
Salary by agreement
Pay period
Annual

Requirements

Languages
  • English (B2)

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason