Software engineer,architect,problem solver.
I’ve spent 20+ years building and evolving web software — from hands-on development to architecture, cloud infrastructure and seven years as a CTO.
Today, I work independently with teams that need experienced technical thinking, practical engineering and someone willing to get close to the actual problem.
I started as a developerand never really stopped being one.
Over the years, my work gradually moved from writing individual features to understanding the systems around them — architecture, infrastructure, deployment, performance, integrations and eventually the business decisions behind technology.
I spent seven years as a CTO, where I had to make those decisions for real: moving legacy systems to the cloud, introducing modern delivery practices, evolving monoliths, dealing with infrastructure costs and helping teams navigate technology choices that often looked very different on a whiteboard than they did in production.
I still like writing code. I still like getting into the details. And I still think the best architectural decisions usually come from understanding the actual problem first.
20+ years ofbuilding software.
Hands-on web development, software engineering and building platforms across different frameworks and technologies.
Engineering leadership, SaaS platforms, cloud infrastructure, CI/CD, architecture, modernization and technology strategy.
Complex e-commerce systems, Shopware, integrations, migrations, performance and hands-on engineering across large web platforms.
Focused technical consulting, architecture, Google Cloud, AI integration and targeted engineering for complex software problems.
What I knowand where I’m useful.
Architecture & Engineering
Cloud & Infrastructure
Products & Platforms
AI
Technology should solveproblems, not create new ones.
I’m skeptical of architecture for architecture’s sake.
Microservices are not automatically better than a modular monolith. Kubernetes is not automatically better than a VM. And adding AI to a product doesn’t make it smarter unless it actually solves something.
I like technology, probably more than is healthy — but I like useful technology even more.
I care about the trade-offs: complexity, cost, maintainability, performance and the people who eventually have to live with the system.
Tools I’ve worked with.
- PHP
- Symfony
- Shopware
- Node.js
- JavaScript
- TypeScript
- Vue.js
- GraphQL
- REST APIs
- Google Cloud
- Kubernetes
- Docker
- Terraform
- Helm
- MySQL
- Redis
- OpenSearch
- Jenkins
- Git
- Prometheus
- Grafana
- Sentry
- Claude Code
Not all equally deep. My strongest ground is web software, architecture and complex systems — especially PHP/Symfony, e-commerce, Google Cloud and infrastructure.
Curiosity is probablythe constant.
Outside of software, I’m usually trying to solve some completely unnecessary problem just because I became curious about how it works.
I like understanding things deeply — whether that means software architecture, a new technology or something completely unrelated.
That curiosity is probably the one thing that has stayed constant throughout my career.
Have a difficult
problem?
You don’t need to have the solution figured out before we talk. That’s often the reason to talk in the first place.