Electronic Hardware & Embedded Systems Engineer

I do not begin an engineering problem by immediately drawing a schematic or writing code. I first define what the system needs to do, including its interfaces, power requirements, performance targets, safety constraints, and operating conditions. I then divide the system into smaller blocks and test the most critical part as early as possible.

I followed this approach in the three-channel motor-driver project. Before designing the complete board, I built a single-motor prototype to validate the control loop and communication structure. For me, a good engineering solution is not only one that works in theory, but one whose verification process has been considered from the beginning.

The PoE Relay / IO Card is one of the projects I have owned most comprehensively. I worked across both the hardware and embedded-software layers of a system combining PoE power, Ethernet communication, an ESP32, an Ethernet PHY, four relay outputs, and isolated inputs. My responsibilities covered PCB layout, field-interface separation, relay transition logic, watchdog behavior, local configuration, and the update workflow.

I want to deepen my experience in embedded systems and control without moving away from hardware. I am particularly interested in motor control, real-time applications, sensor feedback, and avionics electronics. I also want to bring the analytical perspective I gained through EEG and signal-processing research into physical systems and embedded-control problems.

I value taking responsibility, explaining the reasoning behind technical decisions, and replacing assumptions with measurements, simulations, or focused tests. Rather than leaving a circuit at the schematic stage, I aim to develop it as a complete engineering system that includes the PCB, embedded software, control logic, protection mechanisms, and verification process.