OpenAPI Experts in Germany

• 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.

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

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.

• 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

Participation in the EU-funded MORANE-2 project to validate the Future Railway Mobile Communication System (FRMCS) in real-life use cases: creation of the requirement specifications for TOBA as well as the associated test specifications.

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

• Optimizing and accelera­tion of our Gitlab CI pipeline

• Conceptual work for the PoC of the Zero Trust system

• Extension of the policy-engine backend in Go

• Extension of the policy-testing mechanism in Python

• Architectural design of the PEP component of Zero Trust

• Documentation of the product

• Technologies: Zero Trust, Go, Python, Gitlab CI, Docker, JWT, Domain-Driven Design

• Ride-sharing and bus platform, live and fully functional. Backend with Spring Boot 4.1 on Java 21, PostgreSQL with Flyway, and Testcontainers integration tests. Hosted in my own AWS account (ECS Fargate, ALB, ECR, IAM Least-Privilege) with CI/CD via GitHub Actions and OIDC federation without static credentials. Development fully AI-supported with Claude Code, including custom skills and project-specific memory. Spring Boot · Java 21 · PostgreSQL · Flyway · Docker · AWS ECS/ALB/ECR · CI/CD · GitHub Actions · Claude Code

• 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.

• Development and optimization of the RTL+ frontend application for SmartTV and set-top box platforms with React and Next.js.
• Key role in the technical coordination of developers within the team and in coordinating implementation.
• Central interface to adjacent teams to simplify development processes and improve cross-team alignment.
• Improved frontend performance, stability, and rendering behavior on low-powered devices in a restricted runtime environment.
• Implemented a frontend testing strategy with Jest, React Testing Library, and Playwright.
• Implemented accessibility improvements according to WCAG 2.2 and WAI-ARIA.
• Integrated Didomi Consent Management as a contribution to increasing ad monetization on streaming platforms.
• Used AI-supported engineering workflows with Cursor for structured implementation, refactoring, and faster problem solving.

Technologies used: React, Next.js, TypeScript, JavaScript, GraphQL, Apollo Gateway, Zustand, Tailwind CSS, Styled Components, React Testing Library, Playwright, Jest, HTML5, CSS3, AWS Lambda, EC2, CloudFront, S3, GitLab CI/CD, NX, Cursor

IT consulting, analysis, architecture design, new and further development, code review, test automation, continuous integration, continuous delivery in backend and frontend areas for Automotive Project Instavalo.

Frontend:

• Implementation of UI components according to specifications, especially style guides and responsive design eith React and Typescript
• Component testing
• Code documentation
• CI/CD with Gitlab Pipeline

Backend / IoT:

• Analysis and architectural design with AWS Greengrass IoT on Edge Devices
• Setting up Microservices containers with Docker Compose on Edge device with AWS Greengrass and AWS IoT IAM, Token Exchange Service, Ansible
• CI/CD with Gitlab Pipeline, Terraform, AWS ECR
• Logging with Fluentbit Lua Language for AWS Cloudwatch
• Python Lambda for AWS Greengrass Recipe deployment on Edge Devices
• Implementation of test-driven development with JUnit, Mockito, and code Coverage
• Jacoco
• Definition of REST interfaces with OpenAPI / Swagger
• Development and enhancement of software based on Java Quarkus, Typescript NestJs NodeJs and Python
• Authentication and authorization in Aws IAM
• Development of REST and gRPC interfaces for the frontend and backend
• Implementation of Maven dependencies with DevSecOps OWASP
• Spring AI, Jetbrains AI Assistant, Junie, Github Copilot, Claude Code, Agents, Skills, Command, Hooks, Subagents

• Focus: system architecture, cloud-native platforms, microservices, API design
• Product: Pflege-Pfad is a digital matchmaking platform that connects relatives of people in need of care directly 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 the 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 a solo 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 via presigned URLs for verification of 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 placement process.
• Building 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.

• SPA for automated communication of medical findings with role-based access (Sanctum)
• Server-side LLM integration (OpenRouter) with structured processing
• Automated sending via SMS/voice call (Twilio, ElevenLabs) with queue + status retry
• Full test coverage with 80+ documented test cases

Technologies: PHP, Laravel, LLM API (OpenRouter), Twilio, ElevenLabs, Laravel Sanctum, PHPUnit, Playwright, Docker, REST

Independent, part-time open-source engineering focused on build-time tooling for Next.js, React, MDX, and JavaScript/TypeScript compiler pipelines.

• Built next-slug-splitter to optimize content-driven Next.js applications. It analyzes MDX content at build time, resolves component usage, and generates route-specific handlers so pages avoid sharing the full catch-all component bundle.

• Created supporting plugins and utilities for scoped MDX transformations, nested component dependency resolution, compile-time refinement, safe ESTree evaluation, and object-graph diffing.

• Own architecture, API design, implementation, automated testing, npm publishing, documentation, demos, and performance benchmarking.

Building blocks:

• remark-scoped-mdx: Context-aware AST transformations with nested scope isolation, typed component registries, and prop inference.

• recma-component-resolver: Dependency-graph analysis and selective component forwarding across nested MDX includes.

• recma-static-refiner: Build-time prop extraction, schema validation, derivation, and pruning.

• estree-util-to-static-value and object-graph-delta: Safe static evaluation and deterministic, cycle-safe structural diffing.

Tech Stack:

• Frameworks: TypeScript · Next.js · React · MDX

• Compiler tooling: Unified · Remark · Recma · MDAST · ESTree · ts-morph · esbuild

• Competencies: Static analysis · AST traversal and transformation · dependency graphs · code generation · schema validation · route and bundle splitting

• Tooling: Vitest · tsup · npm · performance benchmarking