Luca Faggion
Menu

Embedded software engineerScrum master

I build reliable systems where software meets hardware.

Embedded Linux, Yocto, Qt/QML and C++—from bootloader to interface.

Explore my work View experience
  • C++
  • Qt / QML
  • Yocto
  • Embedded Linux
Systems map
Application layerQt / QML UI01
Service layerC++ services02
System layerLinux / Yocto03

UART · I²C · SPI
CAN · ETH · GPIO

Portrait of Luca Faggion
>_ Parma area · ItalyScroll to inspect the system ↓

01 / About

A practical systems thinker.

I work best on problems that refuse to stay inside a single layer.

My work connects user interfaces, native services, embedded Linux platforms and physical devices. I move between them to understand the complete system, find the real failure mode and build a solution that is reliable in production.

Alongside hands-on engineering, I work as a Scrum Master—bringing the same clarity to priorities, risks and team coordination that I bring to technical investigation.

Correctness over appearancesEvidence over assumptionsMaintainability over needless refactoringPractical outcomes over theory alone

02 / Across the stack

One system. Four viewpoints.

The details change at every layer. The responsibility for the whole product does not.

01Application

Interfaces that feel simple

Qt/QML HMIs, reusable components, localization, workflows and visual feedback designed around real service operations.

  • Qt
  • QML
  • C++
  • HMI architecture
02Services

Logic that remains dependable

Native services, data models, networking, SQLite and integration code shaped for maintainability and constrained targets.

  • C++11/17
  • CMake
  • SQLite
  • Networking
03System

Platforms that boot and behave

Yocto images, Linux services, boot flows and system integration investigated as one complete product—not isolated layers.

  • Yocto
  • Embedded Linux
  • BusyBox
  • Bootloader
04Hardware

The physical edge

Device bring-up and diagnostics across serial links, Bluetooth, displays, touch controllers and board-level interfaces.

  • UART / RS-485
  • I²C / SPI
  • GPIO
  • Bluetooth

03 / Experience

Engineering ownership with delivery context.

CurrentAutomotive technology

MAHLE

Software Engineer & Scrum Master

Embedded HMI development for automotive service equipment, combining Qt/QML and C++ application work with Yocto Linux, hardware integration and cross-functional delivery.

  • Own features across QML interfaces, C++ services, databases and target deployment.
  • Diagnose platform issues spanning boot flow, Linux userspace, peripherals and application behavior.
  • Translate production constraints into maintainable technical decisions and clear team priorities.
  • Facilitate planning, risk visibility and coordination as Scrum Master.
EducationParma, Italy

Università di Parma

Degree in Computer, Electronic and Telecommunications Engineering

A multidisciplinary foundation in software, electronics, networking and the interfaces between them.

04 / Selected work

Problems solved across boundaries.

Representative work distilled around the engineering challenge and the system impact.

01

Offline VIN decoding engine

Ported layered decoding logic from a server-side database workflow to a C++ and SQLite library, including patterns, formulas, prioritization and error handling.

C++ · SQLite · QtComplex vehicle data available locally
02

Embedded HMI platform

Develop and maintain cross-layer functionality for automotive service equipment—from QML workflows and native services to Yocto integration and target deployment.

Qt/QML · C++ · YoctoOne mental model from UI to device
03

Intelligent manual navigation

Built tooling around PDF structure, table-of-contents recovery and text-position mapping to make technical manuals navigable inside a constrained Qt application.

Poppler · Qt · PythonFaster access to service information
04

Platform and device diagnostics

Investigate display, touch, serial, Bluetooth and networking issues across bootloader, kernel, userspace and application boundaries.

Linux · Bash · Hardware I/ORoot causes instead of workarounds

05 / Method

Troubleshooting is a design process.

Strong fixes begin with a precise model of what the system is actually doing.

  1. 01

    Observe

    Capture the exact symptom and the environment around it.

  2. 02

    Model

    Build competing explanations across every relevant layer.

  3. 03

    Test

    Use focused experiments to eliminate weak hypotheses.

  4. 04

    Integrate

    Deliver a practical fix that remains understandable.

06 / Contact

Let's make the whole system work.

Interested in embedded HMI, Linux platform integration or technical leadership? I'm always glad to compare notes on difficult, real-world engineering problems.

Based in the Parma area, ItalyEmbedded systems · Automotive HMI