HashiCorp Vault Experts in Munich

• Partner directly with C-level leadership (CEO, CAIO, CTO) on architecture, OKR strategy, and cross-team roadmap prioritization, translating strategic goals into structured engineering requirements.
• Surfaced and mapped technical debt across the entire organization with C-level leadership and co-defined a prioritized remediation strategy, balancing debt paydown against feature delivery.
• Led code reviews and technical standards across the team, fostering a mentor-first environment with two-way feedback dialogue — pairing on complex pipeline work and unblocking junior engineers on async architecture patterns.
• Re-architected the AI companion's core processing pipeline from synchronous to asynchronous with a queue-based worker architecture, enabling horizontal scalability and cutting upload processing time ~4x (from ~22s to 5–10s) while improving response accuracy.
• Designed an AI-driven document intelligence workflow with automatic multi-document classification, per-document summarization, and relevance guardrails for the patient care journey.
• Built a unified patient memory system (short- and long-term context) bridging the document vault and chatbot into a single bidirectional, context-aware platform.

• Adjusting, optimizing, configuring, and administering a multi-stage GitLab instance with over 250 users
• Building, adjusting, expanding, and optimizing infrastructure, configuration, and monitoring
• Providing services and handing them over to production
• System environment: DependencyTrack, GitLab, Grafana, Hedgedoc, Kubernetes, OAuth2 Proxy, Openstack, Prometheus, Syseleven

• Maintained a SaaS billing platform on AWS as part of the Site Reliability Engineering (SRE) team.
• Played a key role in an AWS cloud migration project, implementing Terraform (IaC), creating CI/CD processes and pipelines, hardening images, upgrading tool versions, and developing scripts.
• Wrote documentation.

AWS Cloud migration:

• Design and implement CI/CD for deploying AWS resources using GitLab CI, Terraform, and GitOps.
• Create and configure DevOps toolchain including Jenkins, Harbor, and Vault.
• Deploy billing application, microservices, and supporting infrastructure services to Nomad clusters.
• Re-designed TLS/mTLS certificate management using Vault and Lambda.

Security (Infrastructure Hardening & Patch Management & Vulnerability Scanning):

• Managed multiple AWS accounts for Consul/Nomad/Traefik clusters (10–20 EC2 instances/account, ASG) and DevOps toolchain accounts (Harbor, Jenkins, Vault).
• Created hardened AMIs via Packer based on CIS benchmarks for Nomad, Jenkins, Harbor, and Vault; deployed using Terraform.
• Integrated Trivy via Harbor plugin for container image scanning.
• Implemented strict AWS VPC security group rules.
• Developed and maintained patching process across environments using Qualys and Wiz.
• Deployed Qualys Cloud Agent to all EC2 instances, tracked CVEs and tested patches in lower environments before rollout.
• Automated patch deployment across all AWS accounts using Terraform and GitLab CI and verified patch compliance via Qualys/Wiz dashboards.

• Topics: Business Analysis, Data Privacy, Data Management, Stakeholder Management, Conceptualization
• This project focuses on developing and implementing a strategic approach for data deletion in SAP systems. The goal is to identify the relevant data and structures during system migration to ensure both data privacy and IT system efficiency. At the same time, downtime should be minimized and regulatory requirements met.
• Development of a comprehensive approach for data deletion in SAP systems, considering data privacy and business requirements.
• Ensuring efficient and structured data transfer to the new system.
• Optimizing system efficiency and reducing downtimes during migration.
• Creating functional and technical concepts to ensure compliant and sustainable data management.
• Topic preparation: Detailed study of the "data deletion" area to lay the foundation for a structured data migration.
• Definition of project structure: Setting roles, interfaces and the project's organizational structure.
• Regulatory requirements: Analysis of data privacy regulations and business requirements to define deletion criteria.
• Approach: Developing possible scenarios and methods for data cleansing and deletion.
• Deletion concepts: Creating functional and technical deletion concepts that structure the implementation and provide clear guidelines.
• Setting deletion criteria: Defining which data and structures to delete or transfer.
• Responsibilities: Clarifying responsibilities within the project team and among stakeholders.
• Analysis of ongoing activities: Identifying and collecting existing activities in the "data deletion" area.
• Effort, cost and timeline planning: Creating estimates for resources, effort and budget.
• Implementation initiatives: Developing and executing concrete measures to apply the defined deletion strategies.
• IT system efficiency: Analyzing the existing IT infrastructure to identify optimization potential for data deletion and transfer.
• Technology trends: Evaluating new technologies and tools that can support the data cleansing process.
• Cost-benefit analysis: Assessing the financial impact of data cleansing and the introduction of new solution approaches.
• Risk management: Identifying potential risks during implementation and developing appropriate mitigation measures.
• This project lays the foundation for a sustainable and compliant data transfer to a new SAP system. With a clear approach to data deletion, it meets data privacy requirements, reduces downtimes and increases the efficiency of the new system. The results and recommendations will help companies develop a future-proof data strategy that meets legal and business needs.