About

Systems architect. Builder. Architecture-first by default.

The work focuses on designing and building scalable systems across trading, automation, infrastructure, and risk.

Rather than delivering isolated solutions, the focus is on building systems that operate reliably over time. The goal is not short-term optimization, but structural clarity and long-term stability.

Identity

I build systems that scale.

My work centers on architecture: defining boundaries, managing complexity, and designing systems that remain stable under changing conditions.

This includes trading infrastructure, automation systems, data pipelines, and operational architectures. The common thread is system design rather than packaged services or operational execution.

The orientation is technical, architecture-first, and intentionally light on operational overhead.

Working style

Deep work over noise.

The emphasis is on logic, interfaces, and structural clarity. Minimal meetings. Minimal process overhead. Focus on system design and technical architecture.

Work typically starts with identifying structural bottlenecks and system constraints. From there, the architecture is designed to reduce complexity and improve stability.

Philosophy

Most business problems are not people problems. They are system problems.

This perspective shapes both architecture work and personal systems. The focus is on identifying the structure producing a result, then redesigning the system.

The goal is not to optimize individual steps, but to improve the system as a whole.

Personal

I tend to follow projects rather than locations.

Over the past years, I have lived and worked across Switzerland, Denmark, Ukraine, Germany, and Poland. This shaped a pragmatic, project-driven working style and a preference for building systems that operate independently of location.

Outside of client work, I focus on trading systems, automation, and micro-SaaS ideas. I enjoy hiking, and I am currently working toward a private pilot license.