.NET Core Experts in Munich

• AI Integration (LLM & RAG): Designed and built an internal intelligent RAG system (Retrieval-Augmented Generation) based on LLMs, n8n, and vector data to automatically analyze technical documents and error logs.
• Design & Implementation: Designed a robust RS-232/UART communication interface for an SBC-based embedded device used to control medical shaker systems.
• Architecture & Protocol Design: Built a highly maintainable software structure (OOP, SOLID) and defined resilient, hardware-level communication protocols, including multithreading and advanced error handling.
• Quality Assurance & DevOps: Automated testing with xUnit, ran integration tests directly on the hardware target, and maintained technical documentation to strict medical technology standards via Azure DevOps.

Label: C#, .NET, LLMs, RAG, n8n, RS-232, UART, Multithreading, async/await, xUnit, gRPC/protobuf, Blazor, MudBlazor, EF Core, Visual Studio 2026, Azure DevOps

Unified ITSM framework

• Definition of a company-wide ITSM target picture
• Introduction of a uniform service structure across all business units

SLA and OLA management

• Building a standardized SLA framework
• Definition of service classes (Business Critical, Standard, Low Priority)
• Introduction of OLAs between internal teams
• Building meaningful SLA reporting
• Definition of KPI and service dashboards for business units

Service portfolio management

• Definition of service descriptions
• If needed, preparing possible cost and service billing

Ticketing & processes

• Incident management
• Uniform ticket categories
• Standardized prioritization
• Escalation matrix
• Automations
• Self-service optimization

Request fulfillment

• Service catalog across all business units
• Approval workflows

Problem management

• Introduction of root cause analysis
• Known error database
• Problem review process

Complete asset management concept

• Hardware lifecycle management
• Software lifecycle management
• Leasing lifecycle
• Mobile device lifecycle
• Monitor lifecycle
• Phone lifecycle

Processes

• Procurement
• Goods receipt
• Inventory
• Assignment
• Return
• Disposal
• Leasing return Goal: single source of truth for all assets

CMDB design

• Definition of all configuration items:
• Workplace
• Notebooks
• Monitors
• Mobile phones
• Printers

Infrastructure

• Servers
• Firewalls
• Switches
• WLAN
• Storage
• Backup systems

Cloud

• Azure resources
• Microsoft 365
• SaaS services

Relationships

• User ↔ Asset
• Asset ↔ Service
• Service ↔ Infrastructure
• Location ↔ Asset
• Goal: make all service dependencies visible

Software asset & license management

• License management concept
• License balancing
• Compliance reporting
• Microsoft license management
• Adobe license management
• SaaS management
• Contract management
• Renewal management

Interfaces & automation Existing systems

• Workday
• Joiner
• Mover
• Leaver

TESMA

• Leasing data
• Contract data

Matrix42

• Asset synchronization
• User synchronization

Active Directory / Entra ID

• User management

Microsoft 365

• License assignment
• Group management

Dormakaba

• Access processes

• Lifecycle services

Monitoring platforms

• PRTG
• Palo Alto
• Cisco

Reporting & KPI framework

• Definition of a management dashboard
• KPIs
• Ticket volume
• SLA fulfillment
• MTTR
• First resolution rate
• Asset accuracy
• License compliance
• Change success rate
• Service availability
• Degree of automation

Network redesign support

• Governance
• Support of the network redesign from an ITSM point of view
• Definition of affected services
• Change management structure
• Communication concept

CMDB integration

• Recording of all network components
• Service mapping
• Dependency analysis

Validation of documentation and knowledge base articles

• Network documentation
• Operations documentation
• Standard changes

Monitoring & event management

• Target picture
• Central monitoring concept
• Event management process
• Alerting strategy
• Escalation model

Systems

• Cisco

• Palo Alto

• Fortinet

• Rubrik

• Veeam

• Matrix42

• Azure

• Microsoft 365 Automation

• Ticket creation from monitoring

• Escalations

• Standard actions

Audit, compliance & information security

• ISO 27001 consulting
• TISAX consulting
• NIS2 preparation - consulting
• Audit-ready processes
• Documentation structure
• Evidence tracking in Matrix42

Roadmap

• 12-month roadmap
• Prioritization of all measures
• Quick wins
• Medium-term projects
• Long-term target picture
• Documentation

• Designing the audit logging framework
• Implementing APIs for developers to integrate in their codebase
• Implementing ingestion pipeline, database query layer and UI for browsing the audit events
• Improving stability and reliability of the backend system

• Build and operate an end-to-end MLOps platform on Azure ML and Kubernetes (Kubeflow) for the automated deployment, monitoring, and scaling of forecasting models (including Temporal Fusion Transformer, Informer, Autoformer).
• Implement CI/CD pipelines in Azure DevOps for the full ML lifecycle – from resource provisioning (Terraform), data transformation (Hugging Face Datasets, Pandas, PyTorch, CUDA cluster) through training and evaluation to model registry and endpoint deployment.
• Integrate MLflow for experiment tracking, model versioning, performance monitoring, and automated registration in the Azure Model Registry.
• Develop and containerize PyTorch training jobs (Azure Notebook, Jupyter Notebooks) for price and time series forecasting (PFC models) with automatic rollout via Azure ML Endpoints and REST/gRPC interfaces, Docker containerization, secured with OAuth 2.0.
• Set up monitoring and alerting mechanisms (Prometheus, MLflow Metrics), log centralization, and cost monitoring.
• Automate infrastructure provisioning and model deployment using Terraform, Helm, and Azure CLI; connect to existing market data systems and event pipelines.
• Migrate existing workloads and databases (IONOS → Azure, MongoDB) with integration into central MLOps workflows and internal networks.
• Extend the platform with LLM-based tools (LangChain, LangServe) to integrate GPT-based analysis modules into existing Spring Boot services for market anomaly detection and automated reports.
• Analyze and architect a software solution to process large volumes of data efficiently (>3000 messages/sec.) (market data store).
• Spring Boot / Java 21 container development with RabbitMQ for distributing stock market data via MongoDB (Kubernetes) with fast storage of data in Redis RMaps, deduplication, forwarding messages to Read Model queues, and building Read Models for UI display in MongoDB.
• Integration of RESTHeart to create a REST API for MongoDB.
• Build an Angular frontend to simplify data queries and master data maintenance.
• Agentic coding with remote and local LLMs (Claude Sonnet, Ollama Qwen) and MCP servers.
• Develop Python scripts for transforming and cleaning incoming stock market data (Pandas, scikit-learn).

• Operations and extensions of Azure DevOps pipelines

• Operations and extensions of AWS services

• Citrix (Windows 10, Bitwarden)

• AWS: ECR, EKS, CloudFront CDN, Route 53, VPC peering and CNI upgrade, Atlas MongoDB, S3 buckets, static website hosting

• Azure: build and deploy with DevOps pipelines

Conducted an independent technical assessment of an AI-enabled software platform, combining AI risk auditing, cybersecurity analysis and software architecture review. Reviewed application components, APIs, data flows, LLM integrations, retrieval-augmented generation, multi-agent orchestration, authentication, tenant isolation, dependency vulnerabilities, AI governance and model lifecycle controls. Authored a technical audit report with a structured risk register, source-code evidence, regulatory references, corrective actions, AI system inventory, risk classification, remediation roadmap and Key Risk Indicators.

Technologies: TypeScript, JavaScript, React, Next.js, Node.js, REST APIs, MongoDB, Redis, AWS serverless services, OAuth 2.0 / OpenID Connect, LLM APIs, RAG, vector search, multi-agent orchestration, Model Context Protocol, C4 architecture modelling, threat modelling, NIST AI RMF, ISO/IEC 42001, ISO/IEC 23894, OWASP guidance, MITRE ATLAS

• Design and implementation of a Laravel backend API for provider-based geo search, feature details, boundary geometries and neighborhood detection.
• The API serves as a server-side proxy, cache and enrichment layer, protecting credentials for external geo services and persisting features, localizations, geometries, hierarchies and neighborhood relationships in MariaDB.
• Key areas included normalization of autocomplete and feature data, caching strategies for expensive boundary/polygon requests, spatial processing of GeoJSON and MultiPolygon geometries, as well as neighborhood detection using hierarchies, bounding box filters and topology checks.
• Additionally, separate production and diagnostic endpoints were created, along with status and error catalogs, discovery logging, a Docker development stack, API documentation, and unit and feature tests.
• Technologies: PHP 8.3, Laravel, REST API, geo data API, GeoJSON, MariaDB Spatial, Eloquent, Laravel Queues, PHPUnit, Mockery, Docker, Docker Compose, API design, geocoding, boundary data, spatial queries.

• Further development of the internal "ECockpit" platform with an Angular 17 frontend and .NET (C#) backend
• Maintenance and further development of Azure DevOps pipelines
• Introduction of technical improvements in build & release processes
• Collaboration on a modular architecture approach (Clean Architecture & DDD)
• Focus on scalability and secure data processing
• Tech stack: Angular 17, .NET / C#, Azure, Azure DevOps, Git, CI/CD, Clean Architecture, Domain Driven Design

• Implementing microservices in C# using dapr and Docker for a system to exchange analysis requests and results between laboratory systems
• Implementing a test automation framework with C# and SpecFlow for this system
• Build and release management with GitLab
• Evaluating laboratory systems for extensibility (using Python) and integration

• Architecture, design and further development of a hybrid solution consisting of a Java backend with REST API and C# / WPF frontend
• Development of secure, distributed functions for classified message processing, categorization and encryption
• Integration of backend services with document management systems (DMS) for structured file storage
• Planning, setup and continuous optimization of Azure DevOps pipelines for automated deployment and quality assurance of distributed applications in a security-critical environment
• Technical coordination with Bundeswehr project managers and third-party providers of relevant software and interfaces, and documentation of the developed solutions

• Further development of Excel templates for the electrical industry
• Design and development of new analysis functions
• Extension of Excel templates for data analysis
• Use of Excel and VBA

As part of an in-house development project, a pipeline for automated lead generation was created as the second stage of a preceding system for project monitoring. Based on a list of freelance project URLs (freelancermap), qualified lead records are generated, including company, contact person, official and personal email address, and the appropriate form of address (informal/formal). The technologies used were Python (openpyxl, requests) as well as an LLM agent workflow in VS Code (GitHub Copilot Chat) with a custom slash command and extensive rule set; search APIs (Serper.dev) are connected for research. My tasks included the full concept and development. The core is a rule set of around 480 lines that guides the LLM agent deterministically through extraction, website and email lookup, duplicate matching (against existing provider lists), and the creation of a structured JSON output. Deterministic steps (Excel matching, web/email search, pattern derivation) were moved into Python helper scripts. Other requirements included validating the results through versioned blind runs against a reference, iterative refinement of the rule set, and a swappable search provider layer for cost and stability reasons.