Quality becomes infrastructure.
I turn quality from a late-stage concern into a repeatable engineering capability: tooling, standards, visibility and feedback loops that scale across projects.
QUALITY / TOOLCHAINMUNICH · GERMANY / TECHNOLOGY · ENGINEERING · LEADERSHIP
I lead where engineering, operating models and transformation meet — connecting technical depth with strategy, governance, economics and execution.


“Stay close enough to the technology to understand the problem. Step back far enough to improve the system around it.”

I am a computer engineer operating at the intersection of engineering execution and enterprise leadership. My career has moved from building solutions to owning the systems, mechanisms and decisions around them. My focus is not simply to deliver a technical answer, but to make the environment around it work better: clearer ownership, stronger governance, better developer experience and decisions that remain sound as complexity grows.
Today I lead software quality and toolchain evolution in an automotive environment across 12 projects and a broad stakeholder landscape, with responsibility spanning technology, governance, planning and economics. My scope spans technical direction, governance, planning, budget, supplier management, reporting, migrations and cost optimization.
I am most effective where technology has to create leverage at scale: aligning people, architecture, governance and economics so change survives beyond the project and improves the operating system around it.
I turn quality from a late-stage concern into a repeatable engineering capability: tooling, standards, visibility and feedback loops that scale across projects.
QUALITY / TOOLCHAINI connect technical detail with governance, planning and stakeholder alignment so trade-offs become visible, owned and actionable.
GOVERNANCE / LEADERSHIPI treat migrations, supplier choices and cost optimization as operating-model decisions — balancing value, continuity, adoption and maintainability.
TRANSFORMATION / COSTLess about titles. More about the systems, decisions and operating mechanisms that become better because I own them.
Creating a shared quality and toolchain operating model across a 12-project environment.
Turning technical tooling into an intentional platform capability with standards, roadmap and adoption.
Bringing budget, suppliers, migration choices and cost optimization into the engineering decision frame.
Making good engineering repeatable through governance, visibility, explicit ownership and reusable practices.
I operate at the intersection of technical credibility and enterprise leadership — translating engineering realities into strategy, operating models, investment choices and transformation.
I lead software quality and toolchain evolution across 12 projects, creating common governance, visibility and mechanisms instead of solving the same problem twelve times.
My scope reaches beyond engineering execution into planning, budget, supplier management, stakeholder alignment and reporting — the parts that make technical change sustainable.
I drive migrations and toolchain evolution with continuity, adoption, maintainability and measurable value in the decision frame — not as afterthoughts.
I favor standards, reusable tooling, explicit governance and clear ownership models that improve engineering quality and decision speed at scale.
The strongest technology leaders can zoom in and out without losing the thread. They can discuss a toolchain detail, a supplier decision and an organizational trade-off — and still make the whole system coherent.
That is the leadership space I am deliberately moving toward: technical depth with a wider field of ownership — across people, economics, operating models and long-term technology direction.
Make ownership and decisions visible.
Build repeatable ways of working.
Use technical depth where it creates leverage.
Across software, hardware, product and engineering environments, the common thread has been increasing scope: hands-on engineering → systems thinking → cross-functional leadership → enterprise ownership.
BMW Group · Munich
Leading the evolution of quality and toolchain capabilities across 12 projects. Scope includes governance, technical direction, planning, budget, suppliers, reporting, migrations and cost optimization.
Industrial & technology environments
Built and led software and hardware solutions across backend systems, industrial applications, connected products and custom engineering programs — moving between hands-on delivery and project ownership.
University of Catania
Computer Engineering education followed by a career shaped by systems thinking, software, hardware and continuous learning.
A few representative themes that show how I think about engineering, transformation and ownership — without turning the site into a list of technologies.

Designing quality into the delivery system so it scales across teams instead of depending on individual effort.

Reusable capabilities, standards and ownership models that improve engineering flow, consistency and decision speed.

Migrations, supplier decisions and cost optimization treated as engineering and operating-model decisions.

Hands-on engineering experience still shapes how I evaluate architecture, quality, delivery and risk today.

That is the standard I use for engineering, leadership and every decision in between.
Continue on LinkedIn ↗Technology is the profession. Curiosity is the habit. I am most energized by hard problems, strong teams, steep learning curves and the moment a complicated situation becomes clear enough to act on.
