
OH-SO Digital GmbH
Engineering Director, Agentic AI at OH-SO Digital
Engineering Director, Agentic AI
Relevance
What my role is about
My mandate connects client value, technical responsibility, and developing shared capability.
Mandate
My goal is not to collect as many technical decisions as possible. I want to help build good systems and leave clients and colleagues able to do more themselves.
Focus on agentic AI
I work AI-native across the product path: organize signals, reduce uncertainty, prepare decisions, build, verify, and learn from operations. AI accelerates the work. Human judgment sets direction; verification protects value.
Areas of responsibility
In the client project
Connect the client problem with technical direction
Work with clients, strategy, and design to decide what is worth doing, which risks matter, and which technical path holds up.
On the system
Build hands-on and stand behind the quality
Share responsibility for architecture, security, maintainability, and operations through direct work on the system.
Beyond the project
Make experience useful to others
Make recurring lessons reusable through tools and working practices, and help others grow through pairing, mentoring, and clear development paths.
Case context
Overview
Since September 1, 2026, I have been employed full-time at OH-SO Digital as Engineering Director, Agentic AI. I carry technical responsibility across client projects and still work directly on the systems.
The role brings together the pattern running through my career: understand client problems, build products and systems, shape technical direction, and help people take more ownership. Agentic AI is the current field in which I apply that pattern.
Responsibility
Activities
- Work with clients, strategy, and design to identify the problem worth solving and a technical direction that holds up.
- Own architecture and technical quality across client projects while continuing to build at the difficult parts of the system.
- Use agentic AI in products and software development where it creates demonstrable value and ownership remains clear.
- Consider scope, technical risk, and commercial viability together, then turn recurring lessons into better tools, practices, and services.
- Help people take more technical responsibility through pairing, mentoring, hiring, and clear development paths.
Operating mode
Methodology
AI is only one part of the fit. OH-SO aims to leave clients more capable rather than dependent. Its published values emphasize initiative, ownership, depth, and openly shared learning. That is remarkably close to my own view of good software development.
My work therefore starts with a signal, not a finished ticket. I clarify the problem, value, risks, and assumptions before we settle on a solution. Then we find the smallest credible path through development and operations that can teach us something real. AI supports that entire path: discovery and prototyping, code, tests, reviews, and evaluating the result.
"Mastery + Multiplication" sums up how I work: stay deep enough in the system to judge, build, and debug; then turn recurring lessons into tools, practices, and better judgment that others can use.
A good outcome is therefore not "Ask Lenny, he knows." It is the team or client making this kind of decision well on their own the next time.
Technical context
Technology stack
The tools are not the point by themselves. What matters is which system layers had to work together.
Practices
6DevOps
2Next step
If you need similar responsibility, we can identify the next useful leverage point directly.
Send the situation, goal, and decision in front of you. I will respond personally with a clear view of the value I could add.