This is a deeply technical role. Youll spend most of your time partnering with engineering – architects, engineers, and the other PMs in the team – on how the infrastructure is designed and how it scales. Your two main areas of focus are architecture and design partnership (shaping how the infra is built) and the non-functional posture of the system (performance, scale, reliability, cost). The internal product roadmap and the APIs other teams consume are a by-product of getting these two right.
The infra is primarily consumed by other product teams inside the company, but parts of it are exposed externally – APIs, feeds, and capabilities that customers depend on – so youll need to think about both internal developer experience and external contract stability.
Were hiring for technical depth and architectural judgment over maritime domain knowledge. If youve built shared platforms used by other product teams and youre at home in deep system-design conversations, we want to hear from you.
What youll do
Own the product vision, roadmap, and backlog for the Activities and Risk infrastructure layer – covering data and streaming pipelines, ML model lifecycle, and the core services that the behavior products build on.
Drive the ML pipeline product: make it fast and frictionless for the team to take a new detection or risk model from research into production, with strong evaluation, observability, and rollout primitives.
Partner deeply with architects and engineering leads on system design – drive trade-offs on architecture, technology choices, scaling strategy, and where to invest engineering effort.
Own the non-functional posture of the infrastructure – latency, throughput, reliability, cost, and observability – and define the metrics and SLAs the team is held to.
Work hand-in-hand with other PMs (Activities, Risk, Maritime intelligence) to understand what they need from the infrastructure and turn those needs into a coherent platform roadmap.
Shape the API and event contracts the infrastructure exposes – both to other internal teams and to external customer surfaces – so theyre versioned, stable, and easy to build on.
Communicate roadmap, technical trade-offs, and progress clearly to engineering, product, and company leadership.
8+ years in product management, with significant time owning technical / platform / infrastructure products.
B.Sc. in software engineering or similar, and hands-on experience as a developer
Deep experience with data and streaming pipeline architecture – real-time event processing, streaming systems (Kafka or similar), and hybrid batch/streaming designs.
Experience with ML or detection infrastructure – model lifecycle, feature stores, evaluation pipelines, and productionization workflows for ML models.
Strong architectural judgment – comfortable in deep system-design discussions with senior engineers and architects, and able to drive technical trade-offs that hold up over time.
Track record building platforms whose primary consumers are other product teams (with external surfaces as a secondary concern).
Strong understanding of non-functional concerns – performance, scale, reliability, cost, observability.
Strong written and verbal communication, especially with technical audiences.
