I have been working in software development for more than 19 years, and by now it has become clear to me: successful products and teams don't become strong because of the number of lines of code, but because of good decisions, transparent processes, and above all, consistent execution.
This is when I first came into contact with the industry — seeing engineers work as a team in the office, coordinating with manufacturing.
As an intern at FCI, I built a database-driven product catalog system. At Balluff, I implemented and documented software protocols for RFID devices. Early in my career at Sense/Net, I mastered the dynamics of enterprise CMS portal development and fast-paced delivery.
Read the stories:
➜ My first paid job: FCI Connectors
➜ From student to engineer – Balluff
The automotive industry instilled structured planning into my blood: without the strict unity of requirements, design, implementation, and testing, there is no reliable software.
As an embedded systems developer and later as a software project manager (ITC), I worked on critical safety systems. I didn't just code — I also coordinated software and hardware design, prepared cost estimates, and accompanied products all the way to production launch. This is where I mastered systems-level thinking.
I deliberately moved away from the automotive domain to learn less specialized (= more broadly applicable) software development tools and methods.
In the cybersecurity domain, I also started as a software engineer, and for some time now I have been supporting my team as a team lead. Today I am responsible for the professional growth of my team members, process optimization, and setting technical direction in a global environment.
I founded my own business to share the methodologies I have learned and refined over the decades in the simplest and most understandable form.
As a software development consultant and mentor, I help my partners increase their efficiency. A solid understanding of established methodologies is highly valuable in — now — AI-supported development workflows.
I introduce theoretical methodologies that have already been proven in practice, offering solutions that can be applied immediately in daily work.
I work together with team members to develop solutions so that everyone feels a sense of ownership over the new processes.
Beyond one-time consultations, there is an opportunity to maintain a long-term partnership with your team. This allows for immediate correction of initial deviations.