From Engine Room to Innovation Room: My Journey from Sea to Software

For years, I sailed the oceans, rising through the ranks to become a Second Engineer. Life at sea was intense, challenging, and immensely rewarding. It shaped my character — forged in the heat of real-time crises, long watches, and hard-earned victories. The persistence, discipline, and never-give-up attitude I carry today were built inside the steel walls of an engine room.

Like many marine engineers, I thought the only path forward was linear: climb to Chief Engineer, then move ashore into a technical superintendent’s role. That was the script. But deep inside, something in me questioned that script. I always felt there had to be more — another way to contribute beyond the conventional shore-based roles.

And that’s when maritime digitalisation or more profoundly Product management found me.

 

The first glimpse into the world of maritime technology was like a spark — one that lit a fire I couldn’t ignore. It wasn’t just about coding or tools; it was about possibility — the ability to build, to solve, and to reshape the very industry I had lived and breathed for years.

But let’s be clear: this path was anything but easy.

I had no formal software education, no fancy degrees in computer science, and no background in product development. All I had was curiosity, hunger to learn, and belief in myself. I knew I had to start from scratch — and I did.

I spent nights and weekends learning software development, diving into product management principles, and understanding digital workflows in maritime. I reverse-engineered my own syllabus, teaching myself step-by-step what it meant to build digital products from scratch.

Bit by bit, I immersed myself in how software products are built. I had to learn not just the tools, but the thinking behind them — how to break down problems, design workflows, prioritise features, and translate user feedback into real improvements.

I slowly built my understanding of product development — not through a single course or degree, but through consistent, self-driven learning, guided by real-world problems I had faced at sea. I taught myself what it meant to not just build something, but to build something useful.

This wasn’t just about technology. It was about shifting my mindset — from operating machinery to creating solutions, from managing operations to delivering value.

And slowly… I started to build.

Today, I’m proud to say I’ve design and build maritime software tools that are used by fleets, superintendents, and technical teams – from dry dock project management to defect tracking to inspections and many more — tools that I wish I had access to when I was at sea.

This journey from sea to software has been a transformation — not just of skillset, but of mindset. It’s taught me that your past doesn’t define your future — your effort, curiosity, and courage do.

If you’re a mariner like I was — wondering if there’s more to your journey than the traditional path — know this: there is. The tools to transition are within reach. You just have to be bold enough to grab them.