Drive business growth through technical excellence

That’s the belief I’ve built 16 years of engineering leadership on, across startups, scale-ups, and multinational corporations, in recruiting, social networking, audio streaming, and UX tooling. I’ve sat in every seat in the room: developer, team lead, engineering manager, head of engineering, CTO. I’ve led the technical side of 4 products that went on to generate over €25 million in annual revenue, and every one of them taught me the same lesson from a different angle.

---

Architecture serves the product, not the other way around

The best technical decision is the one nobody notices, because it just works for the user.

I don’t believe in architecture for its own sake. Every scaling decision, every technology choice, every hour spent on technical debt exists to serve what the product needs to do next, not to satisfy an engineering ideal. I’ve watched teams build systems that were technically impressive and strategically useless, because nobody asked what the user actually needed first. I ask that question before I ask any technical one.

Good process is invisible. Bad process is everywhere.

A team that needs a framework to function doesn’t have a process problem, it has a trust problem.

Every architecture decision is really a bet on how the business will change. Technology stack, data model, scaling approach, security posture, I’ve made these calls at companies going from ten users to millions, and the ones that aged well weren’t the most elegant. They were the ones that left room to be wrong later.

AI is a tool. It hasn’t changed what good judgment looks like.

The interesting question was never whether AI can write code. It’s whether the person using it still understands what they shipped.

I’ve spent my career staying close to new technology, and AI is the biggest shift I’ve seen. But I don’t think it’s changed the fundamentals of what makes an engineer, a product, or a business decision good. It’s changed how fast you can get to a wrong answer. Knowing the difference between speed and progress is more important now, not less.

---

Want to work together?

• CTO-Led Technical & Leadership Interviews, a live session for the senior engineering and leadership hires where getting it wrong is expensive.
• How I can help your team, for a broader look at advisory and fractional engagements.

---