OpenTelemetry Experts in Germany

The Base Services of DB InfraGO form a central data hub between the company’s IT systems. Common Data Services are developed that distribute data from source systems to a variety of downstream systems (via JMS) and make them available (via REST API). The existing service landscape based on TIBCO is being migrated to DB InfraGO’s cloud-native platform.

• Architecture design and implementation for performance-optimized bulk data processing of several million datasets at specific times during the day
• Technical specification and documentation of business requirements
• Integration of various subsystems (including SAP and Salesforce) through the reimplementation of more than 40 microservices based on Spring Boot
• Migration of TIBCO Based microservices from the Enterprise Integration Platform to the Cloud Native Platform using Spring-Boot
• Establishment of a deployment pipeline using GitLab CI/CD, Artifactory, and automated deployment to a Kubernetes environment with the help of ArgoCD
• Definition and implementation of automated unit, integration, and regression tests

Team Size: 9

Technologies/Tools: Java, Spring Boot, ActiveMQ(JMS), JUnit, Tibco Business Works, Gitlab (CI/CD), Kubernetes (Amazon AWS), ArgoCD, postgreSQL, Oracle, Postman, Hoppscotch, openAPI, Sonarqube

• Fully on-premises LLM document-examination platform for a compliance-critical banking domain: agentic LangGraph pipeline with deterministic verification, every AI judgment structured and source-anchored; ~960 automated tests, zero data egress
• GPU throughput engineering (quantized serving, speculative decoding, prefix caching): 9.5x extraction speed-up, 500+ multi-document case files per day on a single A100
• AI-native EDI/EDIFACT integration platform (~116k LOC Java 25 / Spring Boot 4, 1,900+ tests): LLM-drafted partner mappings machine-verified before go-live (DFDL conformance, field-coverage checks, dry runs), ~99.5% byte match on real customer files — replacing weeks of manual mapping per partner

Multi-Agent Document-Generation Platform

Problem:

Turn a single prompt into a well-researched, structured and cited document, while keeping the user in control: every stage can be reviewed, corrected or revisited before the system moves on.

Architecture:

A multi-agent system orchestrated by a central controller. More than 20 specialised pydantic-ai subagents (understanding, structuring, planning, research, writing, assembly, cross-reference check, glossary, citation, reference table and more) pass results forward through a shared plan persisted in Postgres (asyncpg); a runner layer dispatches each task by name to its agent, and mechanical steps such as formatting, table of contents and list of figures are deterministic code instead of LLM calls. Provider (Anthropic or OpenAI) is a configuration setting, and responses stream over Server-Sent Events.

Hosting & Infrastructure:

Stateless container run as a Scaleway Serverless Container on a private network with managed PostgreSQL, object storage for finished documents and assets, and centralized log shipping (Loki / Scaleway Cockpit), provisioned with OpenTofu modules and deployed through GitLab CI; usage is metered per API key.

My Contribution & Key Decisions:

• Central decision controller: a satisfaction classifier turns the user's free-text feedback into a verdict (keep working, advance, cancel or revise an earlier task), and a middleware applies it to the plan. Plan progression supports jumping back to earlier tasks and re-running the stages after them.
• Research and writing fan-out: planning produces a plan from which a research-design agent generates individual research tasks and a writing-design agent generates individual writing tasks, each linked to the research it needs. Every task runs in its own dedicated agent with its own conversation history.
• Self-review and human-in-the-loop: after each step a critical-thinking agent reviews the output; the user can accept, refine, or ask questions about a critique before the plan advances.
• MCP integrations: two remote MCP servers, web search and internal document search, connected through pydantic-ai with retries and long-running tool-call timeouts. Classifier agents decide per task whether web search is needed, and a small model condenses raw search results into structured findings before they reach the writing agents.

Usage Metering:

Clients authenticate with an API key validated against a key-management service; consumption is charged in credits calculated from token usage per model plus a markup, and exhausted quota is answered with HTTP 429.

• Client: Prime Force Group GmbH

Technologies used: Java 25, Spring Boot 4, MapStruct, JSpecify, PostgreSQL, Redis, Liquibase, REST/OpenAPI, Apache Kafka, Apache Solr, OpenID Connect via IronGate/Keycloak, SAP Customer Data Cloud, JUnit, Testcontainers, Karate, Playwright, GitLab monorepo with CI/CD, Jenkins, JFrog Artifactory, FluxCD, Docker, Kubernetes on Azure, OpenTelemetry, arc42, Jira, Confluence

The Team Management Center is the new central platform of the DFB for planning, managing, and carrying out team activities for the national teams - from squad selection and training camps to communication with players, clubs, and legal guardians. The platform is designed for multi-tenancy for the DFB and regional associations; player, club, and master data are intentionally not copied, but connected at runtime via the DFBnet APIs.

I have been involved in the project continuously since the architecture and concept phase (Sprint 0) and work in a distributed Scrum team in two-week sprints. In addition to implementation, my focus is on architecture alignment, connecting the DFBnet interfaces, as well as code reviews and test automation as quality assurance in the team.

Focus areas:

• Development and implementation of the multi-tenancy concept (tenant model for the DFB and regional associations), including data model, access layer, and Liquibase migrations.
• Design of the person service and the search concept based on Apache Solr.
• Integration of the DFBnet APIs (player, person, and club search, club data), including authentication and synchronous master data synchronization.
• Hardening the integration through resilience patterns: separate read timeouts for each search path, correction of circuit breaker counting, limiting parallel requests, and a club cache to reduce load on the external system.
• Development of self-service endpoints for players (own activities, activity details, games), including an access concept for participants, as well as person documents and file uploads.
• Standardization of API design: OpenAPI annotations, nullability model via a custom ModelConverter, JSpecify migration of the DTOs, and documented API guidelines.
• Build and maintenance of Karate-based API and integration tests, integration tests with Testcontainers, test guidelines, and bug triage from the integration and reference environments.
• Code reviews via merge requests, architecture documentation according to arc42, and architecture decisions (ADRs) in Confluence.
• Automated deployment to the integration and reference environments, analysis of login and OIDC issues in combination with IronGate.

Status: ongoing - as of 08/2026 in Sprint 17, around 940 person hours worked; testable delivery to the integration environment every two weeks.

• Led end-to-end delivery of ML/AI applications for the QuantistryLab simulation platform, from requirements definition and solution design to development, testing, deployment, and production support, coordinating efforts across back-end, DevOps, and ML teams
• Designed and implemented a compound search system with an open-weights LLM, the Pydantic AI agent framework, and the Model Context Protocol (MCP), exposing it through FastAPI endpoints
• Deployed and configured vLLM-based LLM serving on Kubernetes
• Built CI/CD pipelines and Helm charts to automate deployments across staging and production environments
• Instrumented the search system with OpenTelemetry spans and traces, integrating with the Honeycomb observability platform to monitor component-level latency and functional errors
• Developed a custom evaluation dataset and implemented evaluations for retrieval relevance, answer correctness, tool-call accuracy, and end-to-end task success
• Reduced infrared spectrum prediction time by 83% (from 60 to 10 minutes) by replacing a quantum-mechanical model with a pretrained graph neural network; fine-tuned the model using PyTorch, built and containerized the inference pipeline with Docker, and integrated it into the platform
• Implemented an MLflow model registry with MinIO-backed artifact storage
• Advised sales and science teams on ML/AI applications for prospective client projects, providing technical expertise to shape proposed solutions and prototypes

Technologies: AWS, Hetzner, Kubernetes, Helm, Docker, vLLM, Pydantic AI, MCP, Qwen, Llama 3, MLflow, MinIO, GitHub Actions, Python, FastAPI, OpenTelemetry, Honeycomb, PyTorch, Polars, pytest

• Led migration to GCP using Terraform, GKE, and GitOps, improving deployment consistency and scalability
• Implemented Datadog observability stack via Terraform and datadog-operator
• Established automated end-to-end tests and on-call processes, improving incident response and service reliability
• Migrated from NGINX Ingress Controller to Kubernetes Gateway API (NGINX Gateway Fabric)
• Migrated stateful services (PostgreSQL and Redis) to GCP, improving scalability and operational reliability

AI Platform Backend – Senior Developer

Hired to design and build an AI platform backend from the ground up, including multi-provider LLM orchestration and real-time infrastructure for AI influencer personas at scale.

Tasks and Responsibilities

• Architected and implemented a multi-LLM orchestration layer with Semantic Kernel to integrate GPT-4 and other providers for core platform logic and AI influencer personas, reducing model-switching overhead by abstracting provider APIs behind a unified interface.
• Designed and developed a backend from the ground up in C# / .NET 10, including domain modeling with DDD, a versioned RESTful API layer, and cloud infrastructure on Azure.
• Built real-time chat infrastructure with Server-Sent Events (SSE), message persistence, and delivery guarantees for running AI influencer personas live at scale.
• Developed a media management service with cloud object storage integration for uploading and retrieving influencer-generated content.
• Created an integration and unit test suite with data seeding for reliable regression testing across all core platform flows, significantly reducing the production error rate.

Tools and Technologies: C#, .NET, ASP.NET Core, Python, TypeScript, MySQL, Semantic Kernel, EF Core, Minimal APIs, LLM Orchestration, Prompt Engineering, Agentic AI, Generative AI, AI-Assisted Engineering, Claude Code, GitHub Copilot, Google Gemini, OpenAI API, Ollama, Redis, Azure, Azure Container Apps, Azure Database for MySQL, Docker, GitHub Actions, Clean Architecture, Vertical Slice Architecture, CQRS, Domain-Driven Design, REST API, xUnit, Integration Testing, Unit Testing, Jira, Confluence, Scrum

Transmission system operator – network provisioning platform (team lead)

• Designed the saga orchestrator in Python that provisions network fabrics with rollback.
• Split IP, identity, and resource allocation into bounded contexts with their own databases and typed clients.
• Implemented data access using DDD repositories and units of work, with no SQL in the domain code.
• Required integration tests using real PostgreSQL and RabbitMQ containers, and API fuzzing for every service.
• Introduced an agent workflow where a spec starts each change and a human approves every merge.
• Rolled out OpenTelemetry auto-instrumentation through GitOps across eighteen Kubernetes clusters.
• Led incident response for stuck provisioning and recorded every outage as a post-mortem.

Languages and software used: Python, FastAPI, Pydantic v2, SQLAlchemy async, PostgreSQL, RabbitMQ, Celery, pytest, testcontainers, schemathesis, Helm, Flux CD, GitLab CI, OpenTelemetry, pi coding agent.

Software product company – datacenter simulation SaaS (backend development)

• Built the asynchronous simulation pipeline as the second-largest contributor among more than twenty team members.
• Tagged every image by commit SHA and semver in the GitHub Actions deployment workflows.
• Diagnosed the RabbitMQ memory alarm that froze every simulation and fixed the limits in the Helm chart.
• Converted the test suite to function-style pytest, with coverage reported in every pipeline.

Languages and software used: Python, FastAPI, SQLAlchemy, Alembic, Celery, RabbitMQ, Redis, PostgreSQL, S3, EKS, Helm, Keycloak, GitHub Actions, pytest, mypy, ruff, SonarQube.

Internal AI platform – model serving and telemetry

• Built the FastAPI service that deploys open-weight models on GPU tiers as OpenAI-compatible endpoints.
• Upgraded production EKS by two Kubernetes minor versions and fixed zone-bound storage faults.
• Traced every model call, including its token count, cost, and latency, through the OpenTelemetry operator.

Languages and software used: Python, FastAPI, vLLM, LangGraph, pydantic-ai, OpenAI and Anthropic APIs, EKS, Helm, Flux CD, Terraform, GitLab CI, OpenTelemetry, Grafana.

• Development and introduction of operations processes
• Preparation of complete documentation packages (including incident management and operations support) to meet compliance requirements
• Introduction of a workshop on IaC (Infrastructure as Code)
• Technical consulting for the project security concept (ISMS)
• Installation and operation of Kubernetes clusters on AWS, on-prem, and Azure
• Hybrid cloud architecture design (on-prem, Hetzner, AWS)
• Analysis and troubleshooting of incidents and system outages
• Network adjustments for firewall rules, gateways, OpenVPN settings, and IPsec tunnels (pfSense)
• Technical consulting on Bitbucket, Jenkins, and GitLab CI/CD pipelines
• Consulting on Ansible deployments and infrastructure automation
• Consulting on building a scalable system in the cloud (AWS / Azure)
• Technologies / Tools: Ansible, Terraform, AWS, Azure, VPN, pfSense, Jenkins, Bitbucket, Kubernetes, GitLab Runner, ISMS, Golang, Prometheus, Grafana, S3, Lambda, RDS, ECS, Cognito, OIDC, Harbor, MinIO, Postgres, Redis, Keycloak, Ceph, Proxmox, CloudFormation, PostgreSQL, Flux CD, Hetzner, IONOS, Sonatype Nexus Repository, Entra ID, Dex IdP, Pulumi

Independent engineering practice focused on custom AI systems, production delivery, and fractional technical leadership.

Selected client engagement: Scalutions

• Role: Serve as fractional CTO and hands-on technical lead, responsible for the architecture and agentic infrastructure behind its managed B2B outbound operation.

• Product: Designed and built OutboundLoop, an agentic SDR operating system for research, qualification, personalized outreach, campaign management, human approvals, measurement, and continuous improvement.

• Scope: Own the full system lifecycle—from business processes and agent behavior to context design, model routing, integrations, evaluation, telemetry, reliability, cost control, and production operations.

• Delivered MVP-focused full-stack architecture for a health-sector client: Vite/React frontend, backend services on Google Cloud Run, and Supabase for database plus IAM/authentication.
• Supported product requirements engineering and prioritized cost-aware workload placement, implementing browser-side/edge computation where feasible before moving logic to backend services.

• Acted as technical consultant to optimize multi-layer ensemble models combining ResNet, CNN-BiGRU-Attention, and XGBoost.
• Guided implementation of a Logistic Regression meta-learner to solve class imbalance problems, achieving 92.86% accuracy and 0.9644 AUC on PTB-XL and Chapman-Shaoxing datasets.

Built and operated the entire infrastructure and observability platform for an AI agent evaluation platform on AWS/Kubernetes. Led the evolution of an AI-first cloud-native platform by building end-to-end observability, automating infrastructure and CI/CD, improving reliability and scalability, optimizing performance through data-driven engineering, and operating in an AI-native development workflow centered on rapid iteration, code review, and automation. Tech stack included Terraform, AWS, Kubernetes, Grafana, Github Actions, Python, and Cursor.

• Manage multiple Kubernetes clusters in Production with Ceph as storage layer.
• Implemented CICD pipelines for automating deployments with Gitlab CI
• Terraform for Infrastructure provisioning.
• Claude code
• Helm charts for deploying via ArgoCD
• Implemented automated incident notification pipelines in Kubernetes to align with NIS2 mandatory 24-hour early warning disclosure rules
• Configured Azure Policy and Logging guardrails aligned with BSI IT-Grundschutz (SYS.1.3 / OPS.1.1), ensuring continuous baseline compliance across 50+ cloud workloads

Environment: Gitlab CI, IONOS Cloud, Ceph, ArgoCD, terraform, Elastic cluster, Grafana, Alert Manager & Prometheus