Backend-Focused .NET Engineer
Clean Architecture · Reliable Processing · Explicit Domain Logic
📍 Hamburg, Germany
I'm a backend-focused .NET engineer with a strong interest in structured application design, reliable data processing and explicit domain logic.
My background in game development shaped how I think about system behavior, state consistency and performance.
Today, I focus on backend systems that remain understandable and changeable over time — with clear boundaries, explicit error handling and testable business logic.
Two backend projects that highlight complementary engineering concerns:
Ingestor focuses on reliability, fault handling and operational resilience.
ServiceDeskLite focuses on architecture, domain boundaries and design clarity.
A reliable import system for processing delivery data from multiple suppliers. Built for a fictional furnishing logistics company (Fleetholm Logistics).
The goal is not domain complexity, but technical reliability — retry logic, dead-letter handling, idempotent processing and full audit trails.
-
Two-process architecture (API Host + Worker Host)
-
Database-backed job orchestration (Outbox pattern)
-
Configurable dispatcher abstraction (DB queue or RabbitMQ, config-switch)
-
Message-driven processing via RabbitMQ with dead-letter exchange
-
Automatic retries with exponential backoff
-
Dead-letter handling with manual requeue
-
Idempotent file ingestion (content hash + supplier)
-
Explicit status model with strict state transitions
-
Structured error classification (transient vs. permanent)
-
Batch import with chunk processing and partial success handling
-
Full audit trail for every job lifecycle event
-
OpenTelemetry tracing and structured logging
-
Integration tests with Testcontainers
-
Repository: https://github.com/goldbarth/Ingestor
A deliberately structured .NET 10 backend application demonstrating clean layering, explicit domain rules and consistent error handling in a realistic setup.
The goal is not feature breadth, but structural clarity, explicit boundaries, and reviewable design decisions.
-
Strict layered architecture (Domain / Application / Infrastructure / API / Web)
-
Explicit domain workflow rules
-
Result-based error handling (no exceptions crossing application boundaries)
-
RFC 9457 ProblemDetails strategy
-
Strongly-typed IDs
-
Deterministic paging & sorting (CreatedAt + Id tie-breaker)
-
Explicit UnitOfWork commit boundary
-
EF Core (PostgreSQL) + InMemory provider switch
-
End-to-end tests with provider matrix
-
Repository: https://github.com/goldbarth/ServiceDeskLite
-
Documentation: https://goldbarth.github.io/ServiceDeskLite
Beyond backend architecture, I have built system-oriented projects in C++ and Unreal Engine.
These projects shaped how I approach backend systems today:
explicit state handling, clear ownership and predictable behavior.
A physics-driven N-body simulation with fixed time-step integration.
- GameMode as composition root
- Explicit CelestialBody registry
- Separation between simulation logic and visualization
- Real mass–velocity–distance interaction
Repository: https://github.com/goldbarth/SolarSystem
A minimal rendering engine capable of loading and displaying OBJ models.
- Explicit resource and state handling
- Camera system (pan, rotate, zoom)
- Shader-based lighting
Repository: https://github.com/goldbarth/3DModelViewer
I value clarity, ownership and deliberate system design.
- Boundaries are intentional
- Domain logic is visible
- Trade-offs are discussed
- Quality is a shared responsibility
Open to backend-oriented engineering roles in Hamburg.