About me — Digital engineering from the Ruhr area

Enterprise engineering for the Mittelstand. Personal, predictable, pragmatic.

Enterprise engineering, without the corporate noise

Fabian Augenstein — digital engineer from Oberhausen

By day: digital engineering at a major enterprise, focus on backend for scalable online platforms. B.Sc. in computer science, IT specialist for systems integration, more than 10 years of experience in software architecture, solution design and backend engineering.

With Kumpel-IT I bring that enterprise experience to where it's often missing: the German Mittelstand. My specialty: backend engineering, APIs and fulfillment systems — exactly the stretch many shop agencies don't cover. Clean implementation instead of consulting decks. Clean APIs you actually own instead of vendor lock-in. Fixed prices with a clear scope instead of six-figure day rates. Personal, predictable, pragmatic — from Germany's Ruhr area.

Background

Information Technology Assistant (ITA)

Hans-Sachs-Berufskolleg, Oberhausen

2009-2012

IT Specialist — Systems Integration

Vocational training (Ausbildung)

2012-2015

B.Sc. Computer Science

FOM University of Applied Sciences

2022-2026

Digital engineering at a major enterprise

Focus on backend for scalable online platforms

2015-today

How I work

Pragmatic

Clean implementation instead of consulting decks. I talk with you about your order flow, your integrations, your pain — not digital transformation frameworks.

Predictable

Fixed price after a clear scope. 30-minute discovery call, a proposal in 5 business days, defined delivery dates. No day-rate surprises, no scope-creep upcharges.

Personal

One direct contact — no sales funnel, no account-manager layer. You speak with the person who later does the implementation.

Technical focus

Where my expertise sits deepest — and which problems I most enjoy solving.

APIs & integration engineering

Building clean integrations between grown system landscapes is the problem that has shaped my work for over 10 years. When ERP, shop, warehouse and third-party providers each speak their own APIs and data formats, the result is brittle mappings and manual intervention. My approach: a central integration layer with clear contracts, idempotent endpoints and traceable data flows.

  • REST
  • GraphQL
  • OpenAPI
  • Event-Driven Architecture
  • Kafka
  • RabbitMQ
  • Idempotency
  • Retry with backoff

Order processing & order management

When orders flow through complex routing rules from multiple channels — different warehouses, multiple carriers, edge cases like partial shipments, cancellations or returns — you need robust state machines and traceable error handling. Order-management backends are one of my core strengths.

  • State machines
  • Message queues
  • Carrier APIs (DHL, DPD, Hermes)
  • Idempotency

PIM & product data pipelines

Product data tends to come from multiple sources (supplier feeds, in-house editing, ERP master data) and has to take different shapes for different channels. I build central PIM backends with clean data modelling and channel-specific API endpoints — one source, many target formats.

  • Domain-Driven Design
  • REST APIs with projections
  • Data validation
  • Cache strategies
  • Optional AI enrichment

Digital engineering for mid-sized eCommerce.

Backend engineering, APIs and fulfillment systems for online shops and B2B platforms — from Germany's Ruhr area. Enterprise engineering quality, without the enterprise complexity.

Book a discovery call