Profile
I support work where technical systems need to be planned, improved, or operated reliably.
I connect architecture, platform engineering, DevOps, observability, and technical implementation with clear communication - remotely and around Augsburg.
- Architecture, infrastructure, operations
- Direct collaboration
- Implementation with technical depth
MY PATH
From software to operations
I do not only come from an infrastructure perspective. My starting point was software: development, APIs, technical implementation, and the question of how an idea becomes a working system.
Over time, the next question became more important to me: how can this software be operated reliably, observed, automated, and evolved?
That is where my current focus on platform engineering, DevOps, observability, and architecture comes from.
- 01
Understand software
Development, APIs, backend work, and product implementation shaped how I think about requirements, users, and technical feasibility.
- 02
Consider operations
Deployments, infrastructure, and monitoring made one thing clear: good software does not end with code; it needs to run reliably.
- 03
Shape systems holistically
Today I connect architecture, platforms, automation, and observability into solutions that remain understandable and operable.
PERSONAL
What drives me
Why technology is more than implementation to me.
Approach
How I work
Understand first, then decide and implement.
-
Understanding before implementation
At the start, I clarify how application, infrastructure, processes, and operations fit together.
-
Make decisions visible
You do not only get what is implemented, but also why.
-
Name risks early
Open points, technical limits, and dependencies are assessed early.
-
Think implementation and operations together
Architecture, automation, documentation, and handover are planned so the solution remains operable in daily work.
Principles
Why good technical work matters to me.
Good technical work is not only about whether a system works today. It also shows in whether decisions are understood, responsibilities are clear, and operations remain traceable later.
- Good systems reduce uncertainty.
- Communication is part of technical work.
- Solutions need to remain operable in daily work.
Questions
Questions about working together
How do you start a new project?
First we clarify the system, goal, risks, and constraints. From there we define priorities and the first practical steps.
How do you work with existing teams?
I work directly with the people involved and make decisions traceable. What matters is that knowledge stays with the team and operations are considered early.
How do you handle unclear requirements?
I make open points visible, document assumptions, and prioritize together with the team. This keeps uncertainty explicit before it creates problems in implementation or operations.
When is it probably not a fit?
It is less fitting for pure ticket execution without a target state, quick-and-dirty work without maintainability, or situations with no room for technical decisions.
Contact
Does my way of working fit your project?
Briefly describe your project, current situation, or technical challenge. In a conversation, we can clarify whether and how I can support you meaningfully.