Technical leadership with a business edge.
Software architecture and technical leadership for products that need to move fast.
How I help
“We are building fast, but I cannot tell if we are going in the right direction.”
The product is moving. You need someone to look at the technical side and tell you whether the foundation is solid or accumulating problems that will cost you later.
“We need to scale and I don’t know if the architecture will hold.”
The system works now. The question is whether it will work at 10x the load in the future. That is the architecture problem you need to solve before it becomes a crisis.
“I am non-technical and I need to make decisions about a team or a provider.”
Hiring, evaluating an agency, choosing a stack, deciding whether to rebuild or refactor. You need someone to assess the technical side without selling you anything.
“We need an independent technical opinion on what we are building.”
Internal teams, corporate ventures, strategic projects. You have the skills. You need someone outside the team who can look at the technical side independently.
“I don’t know if the product is accumulating tech debt.”
The team ships on schedule. But you cannot tell whether the codebase is holding together or getting harder to change. You need someone to look at it and tell you directly.
“Should we keep building on what we have or start over?”
A rewrite costs months. Building on a shaky foundation costs years. The answer depends on what is actually broken.
My recommendations come from over two decades of building systems and living with the consequences of those decisions. Technical and commercial considerations shape each other from the start. How I think →
Selected work
Retail, backend modernization
Replacing the backend without stopping 2,600+ stores and 9,500+ terminals. No downtime allowed. A wrong data migration would have been visible in every store the next morning. 141M+ documents, 1TB+ data. Throughput target exceeded by 79%, query time reduced 216x.
Luxury e-commerce
Three cities, three teams, one architecture. Distributed teams in Berlin, Geneva, and Shanghai building a luxury brand's e-commerce platform for China. Localization in Chinese and compliance with Chinese authority security requirements. Architectural decisions coordinated across three time zones.
Mobility & traffic management
Multiple national traffic sources, each with a different schema and update cycle. No single source of truth, and consumers relying on the output daily. 18 microservices on AWS, 10,000+ events/day, 99.9% uptime. Serving HERE, TomTom, Radio24. In production since 2017.
Public sector
400K+ entities, 9M+ API calls/hour at peak. Requirements still forming while the architecture needed to proceed. Optimizing Redis to relieve database pressure and building a roadmap from monolith toward modular architecture.
Enterprise content
Persistence and API layer for Crownpeak, deployed on Kubernetes to thousands of enterprise clients globally. One API contract, thousands of clients depending on it.
Open source platform
RESTHeart: 10+ years in production, 2M+ downloads. Architecture that evolved without rewrite across many major versions and breaking upstream changes. Adopted by Unisys, Northrop Grumman, and Crownpeak.
A 30-minute call to understand your situation, surface the key technical decisions, and determine if I can help.