I am an embedded systems engineer who designs complete electronic products: the circuit, the PCB and the firmware that runs on it. Most of my work is on connected sensors, industrial control units and small battery-powered devices that have to run reliably for years without attention.

My background is in electronics engineering, and I have spent my career close to hardware: starting with board bring-up and test, then schematic and layout work, and firmware in C on STM32, ESP32 and Nordic parts. That path means I debug across the whole stack, whether the problem turns out to be a marginal power rail or a race condition in an interrupt handler.

I design hardware and firmware together rather than in sequence. Pin assignments, power domains and connector choices are made with the firmware architecture on the table, which avoids most of the painful late-stage surprises. Everything I hand over is documented: schematics that can be reviewed, commit histories that can be followed, and bring-up notes the next engineer can actually use.

Away from client work I keep a bench full of half-finished experiments, usually an excuse to try a new sensor, a new RTOS feature or a PCB technique I have not used before.