Data Engineer (m/f/d) — sample posting

Platform · Konstanz, hybrid Posted on

The task

The data we work with is almost always there already — only in a controller from 2004, in an OPC UA server nobody has touched since commissioning, and in a CSV folder on a network drive. You build the route in between: connection, modelling, quality assurance, until a number that holds in operation also holds in the platform.

This is not work on a reference data set. When we take on a plant, you come along — because the question of what a signal means is answered in the hall and not in the data sheet. And what you build afterwards, you also operate: there is no team here that takes your pipelines off you once they run.

You come into a platform that exists and routes that are running. In the first weeks you take over an existing connection, then the next plant from the first measurement on.

Key facts

Location
Am Seerhein 6, 78467 Konstanz. Two days a week on site, the rest is yours to arrange.
Contract
Permanent employment, open-ended
Hours
Full or part time, from 30 hrs/week
Start
immediately
Pay
€58,000–72,000 gross per year, depending on experience. The negotiation is about where you sit on the scale, not about the number.
Closing date
. We fill the role as soon as we have found someone — earlier, if that is when it happens.
Questions beforehand
info@control-f.io

Your work and what it takes

What you do

  • Connecting plant: OPC UA, Modbus, MQTT, and the rest that arrives as a file. One decision per connection about what actually has to be read from the machine.
  • Building data models that describe a plant and not a table: signals, aggregates, states — versioned, so that an analysis from last year still means the same thing next year.
  • Making quality measurable. A missing reading, a frozen sensor and a changed scaling factor look the same in the database and are three different incidents.
  • Operating the routes: orchestration, alerting, catch-up after an outage. What breaks at night has to be complete in the morning without anyone touching it.
  • Working on the same model as the colleagues in analytics — they are the first to notice when a definition has shifted.

What is required

  • Three years or more of data routes in operation, not only in projects.
  • Python at a level where you tidy up other people's code; SQL at a level where you read a query plan.
  • Experience with time series and with what makes them difficult: time zones, sampling rates, late arrivals, gaps.
  • German for the hall, English for the documentation.

What helps and is not a condition

  • Industrial experience — PLC, control system, fieldbus. Anyone without it picks it up on the first plant.
  • Kubernetes, Terraform, everything around running the platform itself.
  • A degree. We have both in the team and the work does not differ by it.

Apply

A CV and three sentences on why this position in particular. No cover letter, no photo, no date of birth. We answer receipt within a week, and from receipt to decision it is usually three weeks — the procedure, with all four steps, is set out on the careers page, together with what happens to your documents afterwards.

The reference CF-MUSTER-01 goes in the subject line, so that your application lands in the right procedure. It also appears in the posting itself and is the only number we keep for it.

Other open positions

  • Analytics

    Machine Learning Engineer (m/w/d)

    Models for condition monitoring and predictive maintenance — from the first hypothesis into operation, including the question of how you later tell that they still hold.

    Location
    Konstanz, hybrid
    Contract
    Permanent employment
    Hours
    Full time
    Start
    from September 2026
  • Projects

    DevOps Engineer (m/w/d)

    You build and run our Azure data platform: CI/CD in Azure DevOps, infrastructure as code with Terraform, reliable operation of Azure Databricks.

    Location
    Remote
    Contract
    Permanent employment
    Hours
    Full time
    Start
    immediately
  • Product

    Working Student Frontend (m/f/d)

    You help build the surface on which operators read their plants. HTML, CSS and as much JavaScript as necessary — in our experience that is not much.

    Location
    Konstanz
    Contract
    Working student
    Hours
    16–20 hrs/week
    Start
    immediately

All four positions, with the full terms, are on the careers page.