Engineering practices at Maersk
summary
Maersk turns data into operational levers: a single E‑class ship moves 18,000 containers and one journey can exceed 19th‑century transcontinental volumes, so telemetry feeds logistics and a whale‑protection project enforces slowing below 12 knots to save animals. The org grows from 1,900 to ~6,000 tech staff with about 3,000 data engineers producing Spark/Databricks code, and puts Unravel in dev to analyze every line, give micro‑suggestions, shift cost controls left and prevent runaway cloud bills.
AI-written summary · about
chapters (12)
- 0:00Introduction to Maersk
- 1:53Mark Seer's background
- 3:37Data transformation at Maersk
- 6:53Data challenges faced
- 8:38Team size and growth
- 10:01Data maturity curve
- 12:29Shifting timeframes and expectations
- 13:52Tooling and Unravel
- 17:22Biggest hurdles in data ops
- 21:14Cloud cost management
- 24:47FinOps and team ownership
- 26:57Predictions for data industry
related talks
29mHow we turn data teams into better engineers at Netflix
17mOptimizing Tech Throughput
30mShipping Through Chaos: Engineering Resilience Across Borders
26mScaling engineering organizations
16mEngineering the Future with the Reliable Delivery Management
34mAn Engineering Team Where Everyone is a Leader
33mAn Engineering Team Where Everyone is a Leader
48mStriving for engineering excellence: Data-informed organization