JUnit Experts in Germany

• Development of cloud native applications to provide a multi-vendor marketplace for different digital assets (e.g. NFTs)
• Design and operation of a microservice architecture using Nest.js, MySQL, Redis, Hasura, Algolia, Docker and Serverless
• Design and operation of a streaming data architecture using Kafka (with JSON Schemas)
• Creation of CI/CD pipelines with GitHub Actions for automated deployment of applications
• Testing and evaluating new technologies for more stable, faster, safer and more sustainable application development
• Building the full infrastructure with Terraform in AWS
• Integration of Stripe to handle international payments
• Use of Algolia for real-time search of digital assets on the platform
• Presenting results to stakeholders and running internal meetups
• Federation of services with GraphQL and Hasura
• Discussions about architecture decisions in the IT landscape and their impact
• Use of message queues for app-internal communication and component encapsulation
• Advising internal staff on the implementation of business and technical requirements
• Test Driven Development: unit, integration and E2E testing using JUnit
• Use of Next.js/React with SASS/SCSS for frontend applications
• Use of Vue.js with SASS/SCSS for frontend applications
• Integration of security-related mechanisms (JWT tokens with Auth0, OAuth, OIDC, IP guards, BOLA, secret vaults)
• Creation of microfrontends using Retool for fast prototyping and testing of functionality
• Use of nx monorepo with nrwl

• A recurring problem in my own AI-supported projects: requirements analysis, use cases, and architecture decisions can be created quickly with AI support, but they remain hard to trace 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 as a continuously linked knowledge graph, traceable from the requirement to the architecture decision – queryable for both people and AI agents alike. Technically based on RDF/OWL and its own MCP server.

• Result: MCP daemon running, Docker image automatically published on GHCR, nine hexagonal modules, eleven ADRs (including an open-core licensing model). Requirements engineering and ubiquitous language hexagon active. Publicly available since 07/2026 as a Community Edition under Apache-2.0 (github.com/kogn-io/arknet), together with the Claude Code plugin and the 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

• 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

• Further development of the existing e-commerce platform based on SAP Commerce (Hybris) to meet the growing demands of digital commerce.
• Ensuring the scalability and performance of the backend, so the platform remained stable and efficient even under heavy user load.
• Development and integration of new OCC REST APIs and services for modular extensions and flexible adjustments, to implement new features quickly.
• Optimization of data flows and interfaces, which significantly improved platform efficiency and system performance.
• Ensuring a maintainable and scalable code base by using Clean Code principles, proven design patterns, and a future-proof architecture.
• Reduction of errors through extensive testing with JUnit, Mockito, and load tests with Gatling, supported by the introduction of automated test processes.
• Improved system performance through targeted refactoring measures and efficient database queries, especially to handle peak loads.
• Use of modern cloud and monitoring tools such as Kubernetes, Google Cloud Platform (GCP), and Grafana to ensure a stable and monitored infrastructure.
• Clear improvement in efficiency, scalability, and reliability of the platform, which now meets the demands of a dynamic and growing e-commerce market.

• Building a data integration platform for high, medium, and low voltage assets for contextual analysis of time series with master data from the SCADA control system (IEC 60870 104), INIS, and SAP.
• Responsibility for the architecture and implementation of the solution, as well as sparring partner for the Product Owner.
• Use of Kotlin, Spring Boot, Maven, TimescaleDB, PostgreSQL, liquibase, Elements IoT, Docker, Kubernetes, Grafana, Python, jupyter, and various API gateways.

• Ride-sharing and bus platform, live and working. Backend Spring Boot 4.1 on Java 21, PostgreSQL with Flyway, Testcontainers integration tests. Running 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 throughout AI-assisted with Claude Code, including my own skills and project-specific memory. Spring Boot · Java 21 · PostgreSQL · Flyway · Docker · AWS ECS/ALB/ECR · CI/CD · GitHub Actions · Claude Code

• Architected the Yatta Integration Layer – a config-driven integration platform on Java 25, Spring Boot 4 (WebFlux), Temporal, gRPC and Kafka, enabling new third-party integrations (e.g. AVS fulfillment) via declarative JSON configs with zero code changes.
• Designed and implemented Tink integration with 0Auth IBAN verification to enhance fraud prevention and account validation workflows with Adyen payByBank.
• Architected and implemented an OpenFGA-based authorization model for centralized management of users, groups, and fine-grained access control in the vendor portal.
• Architected and led delivery of the Yatta API Gateway platform using GraphQL Federation, providing a unified enterprise API layer across distributed microservices with centralized authentication, authorization and request orchestration.
• Replaced NGINX + NLB with Istio service mesh and AWS ALB; rolled out WAF, OAuth (Cognito), IP whitelisting and RBAC across environments.
• Migrated CDC from Confluent Cloud connectors to a self-hosted Kafka Connect + Debezium stack, reducing operational cost by ~80% across multiple environments.
• Implemented the Transactional Outbox pattern with Debezium for reliable, exactly-once event publishing to Kafka with Avro and Schema Registry.
• Migrated dunning/payment-recovery workflows from Airflow to Temporal, achieving 99.9% reliability for settlement handling.
• Optimised Apache Airflow with deferrable sensors to handle 1000+ concurrent DAG runs without scaling the worker pool.
• Refactored a monolithic Terraform codebase into 3 modular projects, cutting deployment time by ~45%.
• Stood up full observability with OpenTelemetry, Tempo, Prometheus and Loki; automated dev/staging/prod with ArgoCD, Image Updater and Helm.
• Collaborated with product, operations and engineering stakeholders to define scalable platform architecture and integration standards aligned with long-term business and operational goals.

• Training the AI models, evaluating images and texts for UI/UX, turning the provided data into insights via OpenAI Feather as part of the machine learning workflow

Technologies: OpenAI Feather

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

Temporary employment

• System black-box integration tests (BBIT, IVVQ): Execution of regression, release, acceptance, and compliance tests for safety-critical brake control units in the rail industry
• Software test application & integration: Runtime configuration of software components and libraries, validation of interfaces, configuration dependencies, and component interactions
• Test automation (FEAT framework): Co-development and further development of an automated test framework for test execution, reporting, and result analysis
• Functional safety (SiL4, FuSi): Ensuring compliance with safety requirements, traceability and coverage, as well as standards compliance according to EN50126/28/29
• Test automation for communication components: Configuration and validation of fieldbus (CAN) and Ethernet-based TCMS data communication interfaces (TRDP and CIP)
• Requirements analysis & shift-left (PTC Windchill ALM): Analysis of software and system artifacts to identify gaps, ambiguities, and redundancies early in the SDLC
• Test design & test case development: Derivation of test conditions, coverage strategies, and implementation of data-driven test cases (DDT), including reusable test data fixtures
• CI/CD & automation (Python, PowerShell, Jenkins, SVN): Automation of build, test, and HIL deployment processes as well as integration into CI/CD pipelines
• Test data & configuration management (XML): Maintenance and adaptation of XML test vectors and system configurations with automated integration into test environments
• Non-functional testing: Execution of performance and load tests to assess stability and system behavior
• Agile development & defect management (JIRA, Confluence): Participation in Scrum teams, test coordination, review of test artifacts, as well as defect tracking and root-cause analysis
• Error analysis & debugging (CANoe, CANalyzer): Analysis of errors and message flows across multiple system layers (application to bus)
• Model-based analysis (UML, Enterprise Architect): Specification of SUT/SOW and support for systematic test control
• Process & test documentation: Creation of integration and test documentation according to internal quality and certification requirements

maturing their API Practices on both, a Business and Technology level. My role encompasses 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, nodejs, typescript, redocly, reactive programming, CDC, golang, gingonic, GitOps, DX (developer experience), stakeholder management, roadmaps, workshops, discovery.

• 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

• Developed backend features for Modern RIS, a web-based Radiology Information System integrated with the existing Classic RIS via WebView.
• Worked on a modular Spring Boot backend covering clinical workflows such as appointments, examinations, patients, orders, reporting, billing, and inventory.
• Contributed to event-driven architecture using domain events to decouple workflows across backend modules.
• Implemented REST/OpenAPI endpoints, service-layer business logic, DTO mapping, validation, and integration points for the React frontend.
• Worked with PostgreSQL-backed domain models, Liquibase database changes, read/write model separation, and legacy RIS database structures.
• Integrated authentication and authorization flows using Keycloak and OAuth2.
• Added and maintained unit/integration tests using JUnit, Rest Assured, Testcontainers, and project-specific test utilities.
• Supported CI/CD and local development workflows using Maven, Docker Compose, Jenkins, and generated OpenAPI clients.

Tech stack: Java 21, Spring Boot 3.5, Maven, PostgreSQL, Liquibase, Keycloak, OAuth2, REST, OpenAPI/Springdoc, MapStruct, Lombok, Docker, Testcontainers, Jenkins.

Development of an iOS app for virtual try-on and outfit suggestions

The goal of the project is to develop a mobile application for personalized, photorealistic outfit suggestions. Users should be able to upload their own photos, try on clothes virtually, and find products that can be bought directly in the generated suggestions.

• Planning and implementation of the onboarding and photo upload in the iOS app
• Development of the mobile application with Expo and React Native
• Implementation of a Hono/Node.js backend for user, product, and generation processes
• Building an asynchronous processing pipeline with BullMQ and Redis
• Connection of PostgreSQL/pgvector and S3 for product, image, and generation data
• Integration of Gemini and OpenAI for outfit generation and image processing
• Implementation of a credit system and integration of RevenueCat
• Integration of Stripe Connect and affiliate product feeds for products that can be bought directly

Label: TypeScript, React Native, Expo, Hono, Node.js, PostgreSQL/pgvector, BullMQ, Redis, S3, Gemini, OpenAI, RevenueCat, Stripe Connect, Docker