I build engineering teams that can operate without every decision depending on me.
I’m an engineering leader and CTO/co-founder with 5+ years building software teams, delivery systems and digital products. At Nomu Labs, I helped grow the technology organisation to around 20 people, developed engineers into technical leadership roles, participated in 100+ interviews and ~30 hires, and built the operating model used to deliver multiple products in parallel.
I remain close to the technology, working across architecture, technical discovery, APIs, cloud infrastructure and complex implementation when needed.
PEOPLE · PRODUCT · TECHNOLOGYOWNERSHIP · DELIVERY · DIRECTION
~20 peopleTechnology organisation at peak
5 Squad LeadsDistributed technical leadership
20+ engineersCoached across their development
100+ interviewsAcross engineering and business
~30 hiresContributed to across the company
Selected work with FIBA · Samsung · Hyundai · NBN23
EXPERIENCE
People, delivery, product and technical leadership.
01
People & leadership
I’ve spent a significant part of my role hiring, coaching and developing engineers.
Most developers who joined Nomu were early in their careers. My focus was helping them improve not only technically, but also in ownership, product thinking, communication and decision-making.
As the organisation grew, several engineers took on broader responsibilities and we developed five Squad Leads capable of owning delivery across multiple products.
I designed and evolved the way our engineering organisation worked across technical discovery, estimation, capacity planning, delivery cadence, CI/CD, QA, risk management, documentation and escalations.
As the team grew, my role changed from making most technical decisions myself to building the systems and leaders that allowed decisions to happen closer to the work.
I worked closely with product, clients and operations to translate ambiguous business problems into executable technical plans.
That included scope, architecture, staffing, prioritisation, project economics and delivery risk.
One of the most important lessons from building Nomu was that engineering decisions cannot be separated from the economics and constraints of the product or business.
My work has included architecture, technical discovery, prototyping, code review, APIs, data models, integrations, cloud infrastructure and incident resolution.
A product that evolved with the organisation around it.
20+ countries · 3,000+ schools · 68k+ students · 12+ engineering contributors over time · €3M+ in funds distributed
I helped lead the product and technical evolution of Hoops for Schools over several years.
The platform started as a rapid white-label validation exercise and progressively evolved toward separated applications, React and Node.js, TypeScript and an AWS/serverless direction.
More than 12 engineers contributed to the platform over time, so the technical system also had to become easier for a growing team to understand and evolve.
Over the last three years, the platform has also helped distribute more than €3 million in funds to European basketball federations.
PRODUCT
White-label pilot→
European programme→
Global rollout→
Ongoing product
ARCHITECTURE
Legacy / white-label→
React + Node.js→
TypeScript→
AWS / serverless direction
ENGINEERING
Small team→
12+ contributors→
Stronger conventions→
Clearer ownership
Architecture should evolve with the maturity of the product.
The early technical debt helped us validate quickly. The mistake would have been treating an architecture designed for validation as permanent.
NOMU LABS · ENGINEERING ORGANISATION
From founder-led execution to distributed technical ownership.
As Nomu grew, I progressively moved from being directly involved in most technical and delivery decisions to building clearer ownership through squads and technical leadership.
My responsibility increasingly became context, coaching, architecture, capacity, risk and organisational improvement rather than being the route through which every answer had to pass.
The goal was not to remove myself from technical decisions. It was to stop being the bottleneck for them.
SWISHVERSE · NBN23
The project where team scale became a management problem.
€200k+ project revenue · 10+ people working on the product at peak
SwishVerse was one of Nomu Labs’ first large software engagements and an important step in my transition from individual technical execution toward engineering management.
As the team grew, we had to learn how to coordinate more people, delegate responsibility and create clearer ownership instead of solving every new problem by adding more developers.
SELECTED WORK
Over the last few years I’ve worked on product and technical initiatives for organisations including:
My role has typically sat between product, engineering and business: turning unclear problems into scopes, architectures and delivery plans that teams can actually execute.
TECHNICAL BACKGROUND
Before managing engineers, I spent three years turning research into software.
I worked as a Research Assistant / Software Engineer at the Ontology Engineering Group, focused on semantic web, data integration and virtual knowledge graphs.
My main implementation project was Morph-CSV, an open-source system for building virtual knowledge graphs from structured CSV data.
I also contributed to research including Mapeathor and Drugs4Covid, and co-authored four academic publications.
3 years at OEG · Open source · Morph-CSV · 4 publications
From building software to building engineering teams.
I started programming at 14, initially because I wanted to modify Minecraft servers.
I also became interested in hackathons and formed a team to compete in them.
That curiosity eventually took me through software engineering, university research, open source, startups and finally engineering leadership.
In 2021 I co-founded Nomu Labs.
Since then, the biggest change in my work has been moving from building software myself to building teams and systems capable of building software without depending on me for every decision.
EDUCATION & EXPERTISE
Software Engineering Studies
Universidad Complutense de Madrid / Universidad Politécnica de Madrid
I’m interested in engineering organisations, product evolution, technical decision-making and the point where software problems become organisational ones.
