How I got here
I've worked with trucks since 2003. I began as a diagnostic engineer working with WABCO and Knorr-Bremse pneumatic systems, but that was only the starting point. Over the next fifteen years I gained broad, hands-on experience with heavy-duty vehicles, including diagnostics, repairs and workshop operations.
I worked at Iveco and Mercedes-Benz dealerships, served as a shift supervisor and a service advisor, and owned and operated my own service workshop. Those roles taught me different sides of the same business: finding difficult faults, managing workshop work, dealing directly with customers and taking responsibility for the result.
In 2018, BMW F-Series brought me into a different part of automotive engineering. I worked extensively with E-Sys and edited large numbers of vehicle coding and configuration files. To make that work more manageable, I started using Python for file processing, validation and automation. That was my entry point into programming and, eventually, embedded automotive software.
Today I focus on ECU firmware, reverse engineering, vehicle networks and diagnostic software. The years spent working on actual vehicles still shape how I investigate software: I want to understand what the system does, why it behaves that way and how to verify a result.
Heavy-duty vehicle engineering and workshop management
Truck diagnostics and repair; WABCO and Knorr-Bremse systems; Iveco and Mercedes-Benz dealerships; shift supervisor, service advisor and owner of an independent service workshop.
BMW F-Series, E-Sys and Python
Vehicle coding and configuration-file work led to programming, automation and custom software tools.
Firmware and embedded systems
ECU reverse engineering, firmware analysis, vehicle communication protocols and diagnostic software development.