Sea Sentinel AI · Munich · Full-Time

What we do

Sea Sentinel AI is a risk intelligence platform built specifically for the maritime container shipping industry. We monitor ports, vessels, and shipping routes worldwide, detecting disruptions before anyone else does.

When a vessel crashes, we detect it from a local newspaper hours or days before major media picks it up. When a typhoon is still days away from hitting a port, we warn customers before the chaos starts. This way, we enable our customers to be ahead of crises, rather than simply reacting to them last-minute.

We sell our intelligence via an API, which means our customers integrate directly into their own systems and workflows. No complex frontend to build or maintain — the data does the work.

We're a lean team of maritime experts and engineers that fully embraces the great opportunities of LLMs, and we punch well above our weight. Every line of code you ship has real consequences for real supply chains.

The role

We're looking for a backend engineer to join us as a full-time team member. This is a broad role with a clear center of gravity: keeping our data pipeline healthy and building the infrastructure for what comes next.

Concretely, that means:

• Owning our news and data pipeline (data upstream). At the core of what we do is a pipeline that ingests raw data from across the globe and transforms it into published maritime incidents at scale. The core infrastructure is built. Your job is to keep it healthy and make it more robust: scrapers break, proxies fail, crawlers get blocked, and somewhere in the chain a signal gets lost. You'll figure out where and fix it.
• Turning noise into signal (data downstream). Ingesting data is only half the job — most of it is noise. The harder problem is finding the genuine maritime incident buried in thousands of unrelated articles, deduplicating it, extracting what matters, and surfacing it before anyone else. You'll own the systems that separate signal from noise.
• Expanding into new data verticals. When we move into new areas, you'll help figure out how to approach them: researching the landscape, benchmarking data providers, assessing data quality, and making the case for what to integrate. You'll work with both structured and unstructured data and form your own views. This is where the role bleeds into product thinking — not in a process-heavy way, but in caring about whether what you're building actually solves the right problem.
• Working across the stack when needed. We have an internal frontend that's deliberately kept simple — it's a tool for our team, not a product. You'll own it, but we're not looking for a React expert or a designer. Common sense about what makes internal tooling actually useful is enough.

You won't have a backlog handed to you on Monday morning. You'll be expected to understand the system well enough to know what the most important problems are and go solve them.

What we're looking for

Must-haves:

• You've run something in production and dealt with it breaking — you know what silent failure looks like and how to find it, using sensible monitoring and alerting