OpenAPI Experts in Germany

Working Environment

• Insurance / Claims Management (Property, Liability, Automotive)
• REST-based ClaimAPI with Guidewire ClaimCenter

Scope

• Further development of the internal REST-based ClaimAPI with Guidewire ClaimCenter as the backend and various portals/front-end offices as clients, and with the following objectives: + increased AI-supported claims processing outside of Guidewire ClaimCenter + and support for all lines (property, liability, automotive).
• Further development of automated claims processing

Activities

• Interfacing IT & Business
• Design activities with documentation in Confluence, Jira: + Requirements engineering (functional and non-functional) + Design of REST endpoints and coordination with interface partners (esp. AI-colleagues) + Identification, design and evaluation of alternative solutions (moving away from a monolithic approach toward fine-grained endpoints, with code reuse across all lines if possible) + Creation / refinement of product backlog items in Jira, i.e. epics, user stories and tasks, incl. alignment with developers & POs during (pre-)refinement sessions + Using AXA Secure GPT when creating / refining user stories (description, acceptance criteria) and designing REST endpoints + Estimation and prioritization of user stories and tasks during Sprint Planning sessions + Coordination and support during the implementation of Product Backlog items + Driving decision making with preparation and presentation of decision-making documents
• Quality assurance: + Test management, including test case creation using Xray in Jira + Test execution using Bruno as REST client and in Guidewire ClaimCenter + Submission of test artifacts for PO approval + Analysis of production bugs

Methods Big Room Planning (aka PI-Planning in SAFe), Scrum, BPMN, EPK, UML, ERM, DDD

Tools / Tech Stack Teams, Confluence, Jira with Xray, OpenAPI/Swagger, REST, JSON, XML, MS Office, Bruno, GitHub repository (reading), Guidewire ClaimCenter, AXA Secure GPT (AXA's in-house GenAI solution based on Azure OpenAI)

Product:

• Built a production-ready AI platform for generating brand-aware marketing images and videos from product data, user requirements, and uploaded media.
• Own the platform architecture, technical roadmap, API design, security, deployment workflow, operational reliability, and model-provider strategy.
• Developed the core platform in .NET and built supporting AI and workflow prototypes in Python, applying language-independent API contracts and structured interfaces between services and model providers.
• Implemented reliable background processing with RabbitMQ, persisted workflow state, idempotent handling, retries, failure recovery, logging, secure storage, authorization, and credit accounting.
• Made pragmatic build-versus-buy and model-routing decisions based on reliability, latency, cost, and maintainability rather than novelty.

Agent Orchestration & RAG Systems

• Built and compared agent workflows using Microsoft Agent Framework, LangGraph, and LangChain, including tool use, conditional routing, clarification steps, state management, and hand-offs between agents.
• Implemented reusable .NET components for agents, prompts, tools, model providers, structured responses, and retrieval with pyvector, making it easier to change AI providers without rewriting the core workflow.

• Built a scalable nearshore IT developer hub (Croatia, Czech Republic, Poland) as an independent company through a BOT model (Build – Operate – Transfer)
• Identified, selected, and managed full-service agencies; introduced management and control mechanisms, including KPIs, SLAs, and regular service reviews
• Prepared and reviewed data processing agreements and framework contracts in coordination with Legal & Compliance; integrated regulatory requirements (including KRITIS) into process design
• Advised on cloud vs. on-premise strategies, data storage, and authorization concepts; supported Procurement with tendering and service provider evaluations
• Managed change and process harmonization between internal teams and nearshore partners; reported to executive management, CFO, and CIO

Result: Scalable IT developer hub with an audit-ready governance model, reduced operating costs, and accelerated product development.

Maturing their API practices on both a business and technology level. My role covers strategy, architecture, developer advocacy as well as hands-on software engineering, enabling both technical teams and business leadership to adopt and act on API-centric principles effectively. Coincidentally, we also establish GitOps, DX and platform best practices with this project.

Highlights:

• Aligning executives with the initiative by clarifying strategy, replacing misconceptions and myths with facts, clarifying the value of existing assets and enabling informed decision-making
• Formulating a way forward for API Lifecycle Management at OTTO
• Driving platform progress and fostering developer engagement by hands-on engineering work towards strategic goals

API Lifecycle Management, Team Topologies, Organizational Evolution, Regulatory, Platform Advocate, Developer Platform, Communities of Practice, Terraform, Kotlin, Kafka, Kong, WSO2, Apigee, Gravitee, Backstage, AsyncAPI, OpenAPI, API Design, AWS, React, Node.js, TypeScript, Redocly, reactive programming, CDC, Golang, Gin, GitOps, DX (developer experience), stakeholder management, roadmaps, workshops, discovery.

• Focus: System architecture, cloud-native platforms, microservices, API design
• Product: Pflege-Pfad is a digital placement platform that directly connects relatives of people in need of care with verified care services and caregivers – without an agency and without ongoing fees.
• Business analysis & process design:
• Analysis of the German care market and identification of the key pain points of both target groups.
• Modeling of core business processes: registration, verification, care request, application, placement, and rating.
• Definition of the business model as a freemium/premium model with optional contact unlocking.
• Creation of user stories and requirements documentation for relatives, care services, and administrators.
• Design of trust and quality assurance mechanisms with document upload, admin review process, and rating system.
• Coordination with stakeholders and validation of product decisions with potential users.
• Technical implementation:
• Design and implementation of the entire platform architecture as the sole developer.
• Design and implementation of a REST API with Spring Boot and Kotlin, including JWT-based authentication.
• Development of the frontend as a single-page application with Angular 17.
• Implementation of the AWS infrastructure with EC2, RDS PostgreSQL, S3, CloudFront, and IAM.
• Document upload with AWS S3 using presigned URLs to verify care services.
• Email notifications via Resend API.
• AI-supported care service search via OpenAI API.
• Implementation of complete user flows such as registration, login, password reset, and the placement process.
• Development of an admin panel for user and care service management as well as analytics.
• CI/CD with GitHub Actions and containerized deployments with Docker.
• End-to-end tests with Playwright.

Technologies: Kotlin, Spring Boot 3, Spring Security, JWT, JPA/Hibernate, PostgreSQL, Angular 17, TypeScript, RxJS, AWS (EC2, ECS, S3, CloudFront CDN, RDS PostgreSQL, IAM), nginx, GitHub Actions, Playwright, Maven, Git, OpenAI API, Resend API, Docker, Scrum, i18n (DE/EN/TR), Kiro, feature flag architecture.

• Implementation of a full-stack application with Angular as frontend framework and Java as backend language
• Use of the Swagger OpenAPI specification for REST communication between frontend and backend applications
• Control of a card printer via the Nexus Card SDK framework
• Design and implementation of card management software with web interface and JavaFX module for printer monitoring
• Use of Cucumber tests for test automation and creation of test artifacts for testing outside the development environment
• Use of Wireshark for network investigations to analyze the API of a third-party product and to check the REST API of the self-developed software

Project: Introduction of statutory-compliant electronic invoicing (outbound, Germany) in SAP for an international technology group.

• Project management: Planning, steering and reporting of the E-Invoicing outbound rollout across all affected business areas, including budget and resource coordination.
• UAT: Structured user acceptance test with key users per business area, test cases per invoice scenario, and consolidated test results for decision making.
• Defect management: Handover and tracking of defects in Jira, including validation of the generated invoices against the statutory schemas.
• Cutover, go-live and hypercare: Readiness checks and cutover planning aligned with the statutory deadlines, coordination of go-live and stabilization during hypercare.
• Stakeholder management and reporting: Alignment with Finance, Tax, business departments and IT, preparation of status reports and decision papers, and consistent follow-up of open items.
• Change management and documentation: Communicated process changes to the business departments, enabled key users, and created process and compliance documentation to ensure traceability and audit readiness.

• Designed and implemented modular AI assistants for sales and business processes within the Microsoft ecosystem (Agentic AI, Copilot extensions)
• Frontend architecture and development with React + TypeScript for embedded chat and assistant surfaces (streaming UI, Hooks, React Query, OpenAPI clients)
• Enterprise-level agent development: reusable skill/agent library, MCP servers, review and compliance gates
• LLM integration into the user experience: Anthropic (Claude), OpenAI, tool use, RAG pipelines, prompt engineering, guardrails
• Architecture and code review consulting, and mentoring within the AI development team
• Integration with Microsoft Graph, Power Platform, and Azure services
• Technologies: React, TypeScript, Anthropic Claude, OpenAI, MCP, RAG, Microsoft Graph, Power Platform, Azure

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

• Designed a migration strategy for WLS applications to BKA Cloud and Stack IT

• Created a hybrid cloud for internal testing and development with Kubernetes

• Transformed the IT landscape from an outdated monolithic architecture to a cloud-based architecture

• Integrated new CI/CD processes using Azure Pipelines

• Quadrupled the processing throughput for personnel security checks

• Migrated personnel security screening applications to Docker-based applications

• Implemented CI/deployment pipelines using Azure DevOps

• Environment: Java Springboot, Kubernetes, Oracle Weblogic, OpenID, Camunda, JUnit, TOGAF

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.

Participation in the EU-funded MORANE-2 project to validate the Future Railway Mobile Communication System (FRMCS) in real-world use cases: preparation of the requirements specifications for TOBA and the associated test specifications.

Technologies: 5GS (Radio & Core), FRMCS, MCx (MCPTT, MCData, MCVideo), MC Gateway UE, MCx Priority/Security/QoS Management, ETCS, SIP, IMS

• Recurring problem in my own AI-assisted projects: requirements analysis, use cases, and architecture decisions can be created quickly with AI support, but remain difficult to follow and scattered across Markdown files – knowledge is lost as soon as it is no longer in the context window. arknet turns requirements engineering and architecture knowledge into structured, verifiable data instead of plain text: requirements, use cases, and architecture decisions form a consistently linked knowledge graph, traceable from requirement to architecture decision – queryable by both people and AI agents. Technically based on RDF/OWL and a custom MCP server.

• Result: Working MCP daemon, Docker image published automatically to GHCR, nine hexagonal modules, eleven ADRs (including an Open-Core licensing model). Requirements engineering and Ubiquitous Language hexagons are active. Public as a Community Edition under Apache-2.0 since 07/2026 (github.com/kogn-io/arknet), together with the Claude Code plugin and GHCR image; Open-Core model.

• Label: Java, Maven, RDF, RDF4J, OWL, SPARQL, Model Context Protocol, Spring AI, Docker, GitHub, Git, Claude Code, Obsidian, DDD, Hexagonal Architecture, ArchUnit, JUnit, AssertJ, Interface Development, Software Architecture, Continuous Integration, Knowledge Management

Development and further development of an internal platform for managing and providing technical resources, virtual machines, and infrastructure services. The platform supports self-service processes and covers functions that are conceptually comparable to cloud management solutions like Azure or AWS.

• Responsible involvement in the design, development, and implementation of new backend and frontend features
• Hands-on development with Java, Spring Boot, Python, and Angular
• Implementation of REST interfaces, business logic, validations, and integrations into existing system landscapes
• Further development of modern web interfaces with Angular, including connection to backend services
• Participation in architecture and design decisions within the team, especially with regard to scalability, maintainability, and clean interfaces
• Containerization and deployment of applications with Docker, Kubernetes, and Helm
• Support with CI/CD processes and deployment to Kubernetes-based environments
• Work in the environment of vSphere, Broadcom, GitLab CI/CD, ArgoCD, Maven, npm, and NuGet
• Close collaboration with developers, business teams, DevOps, and other technical stakeholders
• Analysis of technical requirements, deriving suitable solutions, and independent implementation in an agile team
• Use of GitHub Copilot to support code generation, refactoring, test case creation, and technical documentation

Methods/ tools/ technologies: Languages & frameworks: Java (21), Spring Boot (4.x), Python, Angular, Robot Framework, Kubernetes, Helm Persistence: PostgreSQL, MongoDB, Hibernate, Liquibase Architecture & communication: REST, gRPC, GraphQL, Apache Kafka, OpenAPI, Microservices, Event Driven, Domain Driven Design Cloud & infrastructure: Terraform, Docker, Rancher, Helm, Ansible Security: OAuth2, MS (Entra ID), web security, Keycloak (extensions for detailed group rights) DevOps: GitLab CI/CD, Ansible, Maven, Gradle, Grafana, Prometheus, Git, GitHub Copilot Testing & QM: JUnit, Robot Framework, automated component and integration tests, E2E tests with Playwright, Testcontainers, EasyMock Methodology & approach: Kanban, JIRA, Confluence, Clean Code