Jan Wagner · Software Engineering

Software for processes that have to hold.

I build durable digital systems for industrial and demanding business processes — with domain understanding, explicit architecture, and ownership of operations.

Selected work

Not features. Systems.

Each reference shows the same stance: understand the domain, make decisions explicit, run the system in real conditions.

Industrial software · product development

01

W-Make Batch

Batch management for container-glass production — from the batch ticket to the daily log.

Public product demo

Case study

Standalone · recipe engineering

02

Batchmaker Studio

A lean recipe studio for recipes, raw materials, batch tickets, and glass chemistry.

Independently operable product

Case study

How I work

Senior means owning the decision.

Technology is a means. What matters is whether a system models the right domain states and stays explainable.

  1. 01

    Domain first

    I start from the real process, not the framework. Rules become visible, testable, and traceable.

  2. 02

    Reliable states

    Bookings, migrations, and failure paths designed so the system stays intelligible under real conditions.

  3. 03

    Small, durable solutions

    No architecture for its own sake. The smallest design that lastingly improves the process.

Working together

Where I contribute most.

01

Process analysis

I analyse an existing digital process, make domain fractures visible, and turn the findings into a prioritised technical roadmap.

02

Product and backend development

I build or stabilise applications where the data model, domain logic, and operations matter more than a fast prototype.

03

Technical collaboration

I help teams with architecture decisions, difficult integrations, and turning accumulated code into a maintainable system.

Engineering notes

Decisions, not news.

From batch ticket to daily log

Two documents, one model. If they live apart, the fracture appears exactly where the shift hands over.

Read note

Why domain bookings must not simply be deleted

In a production model, delete is rarely the right correction. Usually you need a reversing entry.

Read note

Conversation

A process that deserves better software?

Let’s find the highest-leverage point — a new product, an existing system, or a technical decision.

Start a conversation