Senior Data Engineer

About this role

As a Senior Data Engineer you will own the layer everything else depends on. Operational data arrives from a different historian on every fleet, with different channel names, different units, different resolutions, and gaps nobody documented, and the models are only as honest as the structure that data is resolved into.

This is not a pipeline that moves rows from one place to another. Deciding that a flat-lined sensor is faulty rather than becalmed, that a timestamp series crossed a daylight-saving boundary, or that a period was curtailed rather than underperforming are all decisions made here, and each one changes what a customer is told about their turbines.

What you'll do

• Own ingestion and normalization of SCADA history across manufacturers, historians, and export formats.
• Build the validation layer that reports channel coverage, timestamp integrity, and sensor faults before any modeling runs.
• Resolve units, channel naming, and turbine metadata into one structure the modeling team can rely on.
• Make the pipeline reproducible, so a finding produced six months ago can be reconstructed exactly.
• Operate the platform in production: scheduled transfers, failure recovery, and data quality regressions caught before a customer sees them.
• Work directly with the modeling team, whose input assumptions are your output contract.

What we're looking for

• 5+ years building and operating data-intensive systems in production, with genuine ownership of pipelines other people depended on.
• Strong Python and SQL, and fluency with a modern data stack (Spark, Arrow, Airflow, or equivalents).
• Experience with time-series data at scale, including the failure modes that do not raise errors.
• Comfortable with the production stack: containers, CI/CD, and a major cloud provider.
• A working instinct for data quality: the ability to look at a series and tell that the instrument, not the world, changed.
• Comfortable owning open-ended production problems on a small team with broad technical scope.

Nice to have

• Experience with industrial or operational technology data - SCADA, historians, or condition monitoring systems.
• Background in energy, utilities, or another asset-heavy sector.
• Familiarity with the IEC 61400 series, or with how availability and performance are contracted in wind.

This role is for you if you are

• Treats a silent data quality failure as a defect with an owner rather than an oddity to note.
• Can reason across ingestion, storage, modeling inputs, and delivery instead of treating each boundary as another team's problem.
• Works effectively on a small team where technical judgment, direct collaboration, and production ownership matter.