Senior Engineering Manager, Data Platform

Job description

Job responsibilities

• Build the team and platform that become Hadrian's data backbone. Lead the engineers responsible for the path from machines and operational systems to the trusted datasets, streams, and interfaces that scheduling,…
• Own the Data Platform roadmap and delivery. Turn ambiguous needs across Software, Infrastructure, Analytics, Data Science, Operations Research, ML, and Manufacturing into clear priorities, interfaces, owners, and…
• Raise the operational bar for the platform: reliability, data-quality SLAs, observability, incident response, backfills and recovery, cost, security, schema evolution, provenance, and clear ownership when something…
• Partner with senior engineers and technical leads on architecture across CDC and streaming, Snowflake and Iceberg, orchestration, data contracts, schema governance, and the interfaces between the data platform and its…
• Turn repeated one-off work into paved roads. Build standards, contracts, tooling, documentation, and migration paths that let other engineering and data teams move faster without creating a collection of bespoke…
• Hire and grow an exceptional team. Set a clear technical and performance bar, give direct feedback, develop engineers into broader technical leaders, delegate real ownership, and build a team whose capability grows…

Job requirements

• A track record leading engineers responsible for production data infrastructure, distributed systems, developer platforms, infrastructure, or similarly critical technical systems.
• Strong technical judgment in modern data and platform systems: event streaming and CDC, warehouses and lakehouses, orchestration, schema evolution, data modeling, distributed-system failure modes, and the tradeoffs…
• Experience building for environments with real constraints. You understand that the architecture changes when data comes from hardware, machines, devices, files, telemetry, regulated systems, edge environments, or…
• A real platform mindset. You think in shared abstractions, contracts, ownership, operating guarantees, adoption, migration, deprecation, and paved roads — not just a set of infrastructure components owned by one team.
• An operator's mindset. You know what your systems promise, how you know they are healthy, what happens when those promises fail, and how an incident becomes a permanent improvement rather than a recurring story.
• Strong people leadership and high agency across organizational boundaries. Your engineers know what is expected of them, where they stand, and how they can grow;