Maximilian Fischer, AI Engineer

Ride the wave of demand.

Nalu is Hawaiian for wave.

I take data projects from assessment to daily operation.

Since July 2025 I have been building and running, as the sole developer, the internal forecasting and planning platform of a mid-sized meat industry group with three sites. The data platform behind it, the replacement of the integration platform and the leadership of the AI team being set up are mine as well.

What I claim, I back with measurement. Including where the result is uncomfortable.

Maximilian Fischer

Four numbers with evidence

Each number has a project behind it, with measurement and source.

legacy systems and manual processes replaced
21
How measured

Count of documented replacements, as of October 2026: 13 up to July 2026, since then the daily list of open items and seven Excel reports from livestock settlement. An entry counts only once the new path is in use.

forecast error at the decision level, instead of 28.2 % for carry-forward
20.6 %
How measured

Weighted mean absolute percentage error (WMAPE) at the animals-per-week level, walk-forward over 159 weeks out of sample, against the previous-week carry-forward at 28.2 %.

lines of code, built and owned as the sole developer
110,000
How measured

Line count of the platform’s source code, rounded, as of July 2026.

rows from four source systems, operated alone
155 m
How measured

Sum of rows from the four source systems in the data platform, ten years of history, rounded.

Projects

Five projects, each with the same structure: starting point, decision, implementation, result with measurement, and what I would do differently.

How I work

Method instead of a tool list. Three of eight points:

The whole method

Nalu AI

Decision platform for demand forecasting, configurable per customer, every instance at the customer. The entry point is a list of decisions that are due, not a wall of metrics.

In the making, not an offering. Drafts with sample data, no numbers until they are measured.

More about Nalu AI

Today: The entry point is not a wall of metrics but the list of decisions that are due. Each names reason, drivers, recommendation and how good the model was here recently.

What I work with

Tools from the projects, without rating bars. How I used each of them is described with the respective project.

Leadership and steering
  • Team building
  • Roadmaps
  • Decision papers for management
  • Prioritisation
  • Release ownership
  • Training programmes
  • Scrum
  • Kanban
ML and AI
  • LightGBM
  • scikit-learn
  • Temporal Fusion Transformer
  • Time series forecasting
  • Backtesting
  • Calibration
  • Anomaly detection
  • Customer segmentation
  • Churn detection
  • MLflow
  • RAG
  • Embeddings
  • Local language models (Ollama, LM Studio)
  • LLM tool use
  • Microsoft 365 Copilot
  • AI-assisted development (Claude Code)
Data engineering
  • ETL/ELT
  • Dagster
  • SAP R/3 (RFC)
  • Microsoft Graph API
  • PyODBC
  • PyArrow
  • Polars
  • Pandas
  • NumPy
  • Data quality checks
Infrastructure and operations
  • Linux
  • WSL
  • Docker
  • Nginx
  • Git
  • GitHub Actions
  • Azure DevOps
  • Prometheus
  • Grafana
  • OAuth2 (SSO)
  • Windows Server

Skills in the CV