The Rebelist
Engineering Leadership & Product Munich, Germany
No. 01 · Manifesto

Most teams are built to follow.
I build them to think.

Not think as in debate, think as in decide, own the outcome, and ship without waiting for permission. I build engineering teams where the people closest to the work hold the call and carry the result.
12+ years, backend and leadership, based in Munich.

Read the writing See the code
12+

Years shipping production software

4

Roles climbed, from engineer to manager

6

Markets shipped across Europe

3

Companies: Stepstone, Westwing, Jochen Schweizer mydays

Tools of the trade
  • Python
  • Pydantic
  • Vector Databases
  • AI Agents
  • LLMs
  • RAG
  • PHP
  • Symfony
  • Microservices
  • Apache Kafka
  • RabbitMQ
  • Kubernetes
  • Docker
  • AWS
  • CI/CD
  • Observability
  • Elasticsearch
  • PostgreSQL
  • Redis
  • MongoDB
No. 02

Selected Writing

No. 03

What I Build

Small, personal projects I build on the side, to learn, to scratch an itch, and to keep my hands in the code.

Pythonengineering metrics streamline An open platform for collecting, visualizing and analyzing engineering metrics, so teams improve from data, not gut feeling. View on GitHub PythonCLI tooling hack A command-line tool that automates the boring, repetitive work and standardizes how a team ships. View on GitHub PythonLLM · RAG revelations A Retrieval-Augmented Generation prototype that indexes Confluence spaces so answers are one query away. View on GitHub Pythonforecasting momentum Monte Carlo simulations over historical market data to model the range of where a stock might go next. View on GitHub
No. 04

What Guides Me

Autonomy over control

Teams with ownership, clear goals and trust outperform teams that are managed. My job is to remove obstacles, not to add myself as one.

Product-minded engineering

Engineers should own the "why." I push teams to validate ideas with prototypes and discovery before committing to a full build.

Loosely coupled, independently deployable

Kafka and clean domain boundaries aren't the goal, they're how a team ships on Tuesday without waiting on three others. I architect for independence first, because that's what lets people move fast safely.

Still building, still learning

A manager who can't build loses the plot. I came up through PHP and architecture, and I'm deliberately rebuilding that toolkit around AI and Python now, shipping small projects in the open, so my technical opinions stay earned, not remembered.