About

Safety-critical embedded systems, built so agents can work on them

I'm Stefano Falasca. I help industrial SMEs and deep-tech hardware startups build robust embedded systems, and I focus on the verification loop that lets AI coding agents build, test, and iterate on those systems without a human watching every cycle.

Who I work with

Two kinds of team keep running into the same wall. The first is industrial manufacturers and automation vendors: small-to-medium suppliers scaling up, often carrying years of legacy code, who need safety-critical software maturity as they take on larger enterprise programs. The second is deep-tech hardware startups building real hardware that needs software robust enough to ship.

Different entry points, one underlying problem: you know the codebase has an architectural or reliability issue, you have the budget to fix it properly, and you'd rather find the right person before you've spent tens of thousands of euros on an attempt that didn't hold. That's the work I take on.

The experience behind this

This practice is built on real production-grade embedded work, not theory. In automotive I built hardware-in-the-loop and software-in-the-loop test tooling for LiDAR systems at a Tier 1 supplier, worked on a telematics control-unit platform used in truck and commercial-vehicle programs, and contributed to an automobile OEM program. On industrial printers I covered diverse roles across the full product lifecycle, on 16- and 32-bit PIC microcontrollers: I wrote the bare-metal C and C++, but also did the formal systems engineering, owning the system architecture definition through to compliance and verification. That systems-engineering ownership recurs later, when I built the ESP32 firmware for a domestic water-pump product and, as its systems engineer, defined how the device, its cloud, and its app work together as one IoT system, over-the-air updates included. The common thread across automotive, industrial, and connected devices is safety-critical embedded software held to production standards, on systems where a defect that reaches the field is expensive and sometimes dangerous.

Alongside that, I build AI agent infrastructure: the tooling that lets coding agents work inside a codebase reliably. That is the same "agent-ready" verification this site is about, applied to the embedded systems I have spent my career on. I don't name past clients or employers here on purpose, the same reason there are no logos or testimonials on this site, but the kind of work is exactly what these pages describe.

Background

Fifteen years of C++ and safety-critical embedded systems work sits behind this practice. In day-to-day terms that means reproducible builds, compile-time testing in C++, breaking hardware dependencies out so logic is testable without a board, and the feedback-loop infrastructure that makes AI coding agents usable on embedded codebases at all.

If any of that maps to a problem you're carrying, the blog works through the technical detail, the services page describes how an engagement is structured, and the fastest route to a conversation is the contact page.

Elsewhere

If you'd rather see the work first, my code is on GitHub and my professional background is on LinkedIn.