Performance Agent
A .NET performance regression tool built on BenchmarkDotNet with deterministic PASS / FAIL / INCONCLUSIVE verdicts, explicit budgets, evidence history and optional AI analysis.
Technical Lead · Software Architecture · Senior .NET Engineering
I design, modernize and operate business-critical distributed systems, combining hands-on .NET engineering with software architecture, cloud-native platforms, production reliability and practical AI engineering.
Selected work
I work where architecture meets production: system boundaries, reliability, observability, performance and the engineering practices that keep complex platforms understandable.
A .NET performance regression tool built on BenchmarkDotNet with deterministic PASS / FAIL / INCONCLUSIVE verdicts, explicit budgets, evidence history and optional AI analysis.
A public collection of small agents, reusable skills and evaluation experiments built around explicit constraints, evidence and failure cases.
Services
Architecture, hands-on engineering and technical assessment across .NET, distributed systems, platforms, observability and applied AI.
Architecture reviews, modernization planning, integration design and practical technical decisions for complex software systems.
Hands-on engineering for .NET backends and cloud-native platforms, with emphasis on reliability, performance, operability and maintainability.
Adding useful AI capabilities to real products and workflows, including tool calling, evaluation, RAG and production observability.
Focused investigation of architecture, performance, reliability and production problems, followed by evidence-based recommendations.
Selected writing
Performance Engineeringarticle
An evidence-first approach to investigating memory growth in a production .NET service without jumping straight to the memory-leak conclusion.
AI Engineeringarticle
A practical boundary for AI-assisted engineering: code evaluates the evidence, while AI explains changes and proposes what to investigate.
Engineering Reliable AI Systems, part 1
Distributed Systemsarticle
A production-minded way to investigate .NET timeout errors by following latency, resource saturation and dependency evidence before changing timeout values.
Let's talk
Based in Vienna. Interested in Technical Lead and Software Architect roles, as well as selected consulting conversations, with remote collaboration across Europe, the United States and Canada.