Enterprise architecture, IT governance, and secure IT operations. I reduce complexity in architectures, responsibilities, and operations.
A decade of architecture and technology leadership across insurance, energy, and finance.
I am a technology leader focused on making complex IT environments steerable: through clear target states, working governance, and secure, reliable operations.
As Head of IT Infrastructure at a public-law body in the German healthcare system, I lead a department of 20 people at strategic and operational level, working through two team leads. My mandate covers infrastructure strategy, division-wide IT security in close collaboration with the information security office, Microsoft 365, service quality and governance, the orderly transition of new technologies into regular operations, and practical AI enablement in IT operations. The organization secures ambulatory medical care for 9.5 million people.
Before that, I led technical architecture for a major European insurance group within its shared group IT organization: heading an internationally distributed architecture team, co-establishing architecture standards across the insurance group and its reinsurance parent, operating architecture governance across portfolios, and steering modernization and simplification initiatives. Earlier roles at an international energy company and a consultancy focused on the financial industry centered on platform modernization and large-scale data and analytics architectures in regulated industries, including cloud and hybrid platforms.
I started out as a computational physicist (PhD, NTU Singapore, ten publications), which still shapes how I work: analytical, structured, careful about complexity and trade-offs. What interests me most is where strategy becomes execution: operating models, decision structures, and ownership teams can actually work with.
I lead by designing the system: clear ownership, decision paths that come with reasons, and target states people can navigate by. Decisions are made once, documented, and then relied on; commitments are kept or renegotiated early, never dropped silently. Change comes in staged, controlled moves, sized to what the organization can absorb. Structure is for systems; with people I adapt: delegation follows maturity, and conflicts get mediated rather than decreed. When the structure is right, reliability stops being a struggle and becomes a property of the system.
Before industry I spent a decade in physics: studies in Heidelberg, PhD in computational physics at NTU Singapore, a research stay at the University of Wuppertal, ten publications in lattice field theory and high-performance computing. Physics did not teach me technologies. It taught me how to take a complex system apart, model it honestly, and respect what the data says.
My foundation is technical: years of hands-on architecture and engineering work, and a working view of the stack from identity and networking to data platforms. A selection of side projects is on GitHub, including portfolioopt, a portfolio optimization library with over 300 stars.
I live in Düsseldorf and spent several years in Singapore during my PhD. Outside work I enjoy 3D printing, turning ideas into something you can hold.
Structures, roles, and decision paths that make an IT organization effective.
Target states, standards, and reference architectures that hold up in practice.
Governance as decision enablement: fewer gray areas, traceable decisions.
Reliability, Zero Trust, security-by-design, service quality.
Reducing landscape complexity and technical debt, orderly transitions into regular operations.
Practical enablement for automation, knowledge access, and operational relief.
Occasional notes on technology leadership: governance, operating models, infrastructure, and AI in IT operations. New notes appear here first.
Why good governance removes ambiguity instead of adding process, and how to build decision paths people actually use.
Why new technology needs an operating model before it needs a roadmap, and what a clean handover into regular operations looks like.
Integrating new platform services into an existing infrastructure organization: roles, responsibilities, and operating models without parallel structures.
Complexity as the real cost driver in IT, and how to make exceptions deliberate rather than accidental.
Automation, knowledge access, operational relief: what works today and what to leave alone.
A hands-on foundation, not a developer portfolio. A few projects I keep public:
Financial portfolio optimization in Python: Markowitz, minimum-variance and tangency portfolios. A compact example of programming, mathematics and practical problem solving meeting in one place.
View on GitHubA technical talk on cryptographic protocols and distributed trust: mathematically grounded computer science with a clear connection to real systems.
View the talkA frequency analysis of Chinese characters: the kind of small, well-defined side question I find hard to leave alone.
View on GitHubBefore industry I worked in computational physics: lattice field theory, large-scale numerical simulations, high-performance computing. Ten publications, including in Physical Review D; the full list is on arXiv and ORCID. That background is why I treat IT landscapes as systems: quantify, simplify, verify.
PhD thesis, Nanyang Technological University: lattice fermion formulations, numerical methods, and the theory behind them.
Read on arXivLattice fermions and chiral symmetry, studied in a controlled setting.
Read on arXivStochastic quantization and finite-density problems, checked against an exact solution.
Read on arXiv