Working style
Calm under pressure
I prefer structured diagnosis, clean communication, and decisions that reduce friction when systems are under load or recovery time matters.
About
I work best in environments that need to stay understandable, recoverable, and calm under pressure. The focus is not only what gets designed, but what still works well after rollout and in day-two operations.

I did not stay in infrastructure because it was fashionable. I stayed because I like systems that have to keep running when expectations, pressure, and complexity are all real at the same time.
I work on enterprise infrastructure that has to stay reliable in daily operations, not only in architecture diagrams. The focus is practical delivery across platform design, administration, and operational improvement.
My approach is direct and engineering-led: clear ownership, low-noise tooling, and technical decisions that still make sense after rollout, handover, and day-two operations.
Why Infrastructure
I am most useful in environments where operational quality matters more than presentation. That usually means long-lived systems, mixed estates, and teams that need decisions to stay defensible long after the project phase is finished.
Over the years I gravitated toward the parts of IT that tend to matter most when things get serious: core services, database platforms, backup design, recovery paths, and the operational details that decide whether an environment is actually dependable. That work taught me to value clarity over noise and control over architecture theatre.
What still keeps me in this field is the combination of responsibility and pragmatism. Good infrastructure work is rarely loud. It is the kind of work that makes systems easier to understand, easier to recover, and easier to trust after the initial rollout is over.
How I Work
The work I enjoy most sits somewhere between architecture, administration, and operational judgment. I tend to be most useful where a team needs someone who can simplify the environment without losing control.
Working style
I prefer structured diagnosis, clean communication, and decisions that reduce friction when systems are under load or recovery time matters.
Working style
I care about whether a design is still maintainable after handover, patch cycles, ownership changes, and the normal fatigue of production environments.
Working style
My style is straightforward: identify what matters, remove unnecessary complexity, and improve the parts that change operational confidence.
Working style
The best architecture choices are the ones teams can still run well six months later.
Principles
Experience
That mix matters to how I work today. It combines delivery, operational responsibility, and a practical understanding of what production environments ask from people over time.
Liebherr Werk Biberach
Ownership across enterprise infrastructure, virtualization, SQL Server operations, backup strategy, and security-oriented platform stability in a manufacturing environment.
Liebherr IT Services GmbH
Operational administration of infrastructure services and enterprise systems with a strong focus on reliability, standardization, and long-term maintainability.
systema Deutschland GmbH
Consulting work across enterprise customer environments with infrastructure ownership, systems integration, and broad operational responsibility.
Certifications
These areas support practical consulting work in production environments with long life cycles and clear operational requirements.
Virtualization
VSP, VTSP and business-critical virtualization training
Storage
Administration and storage architecture trainings
Databases
Administration, operations and performance trainings
Backup
Veeam configuration, job management, restore processes, and practical data protection for hybrid environments