Back to experience
D

Building DeepOcean Live

Tech Lead / Lead Software Engineer

Sep 2025 - Present

Next.jsNestJSAzureTerraform

I joined DeepOcean in September 2025 as the founding engineer for a new enterprise web platform project. Nine months later, we had our first enterprise customer. That project became DeepOcean Live, a shared web platform bringing together subsea operational tools built by engineering teams across DeepOcean. My role covered the core platform’s engineering, roadmap, and UX, alongside growing the engineering team from one person to four.

Platform launch

Building the core platform

I built the core platform capabilities that applications would share: user management, access controls, single sign-on through SAML and OIDC, audit logs, and project workflows. These gave DeepOcean Live a common foundation across its tools.

For example, I built a flexible role-based access control (RBAC) system with permissions as its smallest building block. Permissions combined into roles, assigned to users or user groups through role assignments, supporting the complex organizational structures and access requirements of large enterprises.

Enabling other teams to build on it

Different engineering teams at DeepOcean needed to add their applications to DeepOcean Live and use its shared platform capabilities. I designed the extensibility framework that made this possible.

Each team owned its application code, managed its own deployments, and chose its frontend and backend frameworks. This independence was possible with a bridge layer connecting their applications to the DeepOcean Live host app.

For the MVP, the framework brought together applications from four independent engineering teams.

Building tools across teams

Some of my work served engineering teams beyond the core platform. I built a shared UI library based on shadcn/ui, incorporating DeepOcean’s branding guidelines. On top of that, I added industry-specific components for maps, video playback, and telemetry that teams could reuse in their applications.

I also built an offshore data server covering vessel and remotely operated vehicle (ROV) telemetry, Norwegian shelf data, and other offshore datasets. This provided shared access to operational and geographic data alongside the UI building blocks teams could use in their applications.

Connecting the platform to offshore operations

Alongside the platform foundation, I built three of its core applications: live video, documents, and map. This gave me responsibility for both the shared capabilities other teams would use and the applications end users would interact with directly.

The live video work connected the web platform to activity offshore. I engineered real-time video streaming, automated stream routing, and vessel telemetry supporting 22 vessels and numerous remotely operated vehicles. These capabilities brought live operational information into the platform, alongside the applications and workflows teams were developing.

The work spanned the user interface, backend services, and cloud infrastructure, using Next.js, NestJS, Azure, and Terraform.

Growing the team alongside the product

As the platform developed, I contributed to hiring as the engineering team grew from one person to four, and took on tech lead and team lead responsibilities.

I established engineering standards, decision records, and release practices alongside the product work. Building the platform and establishing how we worked happened together: we needed to deliver the first customer release while making it possible for a growing team to contribute.

My responsibilities continued to span implementation, technical direction, roadmap, and UX as that team took shape.

Preparing for the first customer

Preparing for our first enterprise customer meant making sure the platform was ready for external scrutiny. User management, access controls, SSO, and audit logs were core parts of the product, and we needed an independent assessment of the security work behind them.

We partnered with PwC for a security review and SITS for penetration testing. The review and testing provided complementary perspectives: examining the platform’s security approach and testing it for vulnerabilities. Both assessments received above-average ratings.

For me, this was part of taking the product from an MVP to its first enterprise release. Alongside building features and establishing release practices, we had to be ready to explain our technical decisions and have the platform assessed by external specialists.

Continuing beyond the first launch

Within nine months, DeepOcean Live had gone from inception to its first enterprise customer. By its public announcement, it was running in production.

The work has continued since then. We have improved the UI and UX, improved performance and reliability, and added an admin portal for DeepOcean’s internal operational tools, alongside other improvements and new capabilities.

I continue to help develop the platform as it grows, building on the core capabilities, applications, and shared tooling we established for the first release.