Marius NeumannIT ENTERPRISE INFRASTRUCTURE SPECIALISTAbout
Healthcare Tech Support taught me practical IT. AI is where I invest time now because it turns clear needs into calmer, more autonomous work.
From support to AI tooling
Worklife Progression
The path matters: direct user support first, then shared enterprise services, then infrastructure responsibility in a manufacturing environment.
Healthcare consulting
systema Deutschland GmbH
Worked across healthcare software rollouts, system integration, and hands-on technical support.
Software installation, customer support, troubleshooting, and direct user-facing delivery.
Enterprise IT services
Liebherr IT Services GmbH
Administered infrastructure services and enterprise systems with a focus on reliability, standardization, and repeatable operating routines.
Administration, standardization, repeatable operations, and shared infrastructure services.
Industrial IT
Liebherr Werk Biberach
Responsible for enterprise infrastructure, virtualization, SQL Server, backup, and platform reliability in a manufacturing environment.
Platform ownership, reliability, recovery, and infrastructure decisions with business impact.
Why Infrastructure
I am most useful where the environment is already real: mixed systems, long-lived services, production pressure, and decisions that have to survive more than one project phase.
Over time I moved toward the systems people notice only when they stop working: core services, database platforms, backup jobs, restore paths, storage, virtualization, and the scripts that keep routine work from becoming manual work.
Good infrastructure work is not loud. It shows up as fewer surprises, cleaner handovers, faster troubleshooting, and a team that knows where to look when something breaks.
How I Work
Working style
I prefer to slow the problem down: check the facts, narrow the cause, communicate clearly, and avoid changes that create a second incident.
Working style
I like to break problems down into facts, dependencies, and failure points before deciding where the real issue actually starts.
Working style
I am at my best when a system behaves unexpectedly and the task is to isolate the cause quickly without creating additional noise.
Working style
I care about whether the team can patch it, monitor it, restore it, and explain it after the original project is gone.
Working style
My style is straightforward: find the parts that cause repeat trouble, remove avoidable complexity, and make the next change easier.
Working style
I think beyond the immediate fix and look at what the team will need to operate, support, and defend the system over time.
Working style
I tend to connect infrastructure, databases, backup, monitoring, and operations instead of treating them as separate technical islands.
Working style
The best technical choices are the ones a team can still run well six months later.
Principles
Certifications
These areas match the systems I have worked with most: VMware, NetApp, SQL Server, and Veeam.
Virtualization
VSP, VTSP, and business-critical virtualization training
Storage
Administration and storage architecture trainings
Databases
Administration, operations and performance trainings
Backup
Veeam configuration, job handling, restore processes, and practical data protection for hybrid environments