01
Product-ready electronics design
Schematic capture, PCB layout, component selection, BOM cleanup, connector strategy, panelization support, and design choices made with assembly, sourcing, test access, and field reliability in mind.
Electrical Design Engineer · Embedded Systems · PCB Design · Production Debug
I turn uncertain product ideas into electronics that can be built, tested, and trusted.
I am the engineer you bring in when the problem spans the whole product: schematic decisions, PCB layout, firmware behavior, BLE/device interfaces, production test, and the messy bench evidence that determines whether hardware is actually ready.
Concept → productionRequirements, design, bring-up, validation, and manufacturing support.
Hardware + firmwarePCB-level decisions tied directly to embedded behavior.
Evidence-first debugMeasurements and controlled changes before assumptions.
What I do
Practical electrical engineering for companies that need a product-minded engineer, not just a drawing package.
02
Firmware that respects the circuit
ESP32, AVR/ATmega, BLE products, low-power sleep behavior, RTC-based timing, peripheral drivers, production diagnostics, and firmware structured around how the hardware actually behaves.
03
System-level troubleshooting
Requirements decomposition, signal-path tracing, failure-mode thinking, dependency mapping, measured troubleshooting, and closed-loop validation before parts or code get blamed.
Why it works
I close the gaps between design intent and product reality.
Most product problems do not stay politely inside one discipline. A firmware symptom may be a power issue. A production failure may be a fixture assumption. A PCB change may be a field-support decision. I keep those connections visible.
Design for the bench and the factoryTest points, connector breakouts, diagnostics, fixture strategy, and acceptance criteria are part of the design, not an afterthought.
Debug across boundariesI move between schematic, scope, firmware logs, BLE behavior, CAD/BOM data, and user-visible product behavior without losing the thread.
Leave a trail others can trustResults are measured, repeatable, and documented well enough to defend the decision later.
Where I create value
Real product areas where hardware judgment, firmware fluency, and production awareness matter.
Battery-powered inspection products
Annual inspection indicators and similar embedded devices where the success criteria are long service life, predictable wake/sleep behavior, RTC scheduling, GPIO state retention, and battery budgets that survive real-world use.
ESP32RTCLow powerField behavior
Production test and board bring-up
Bench workflows, LED/test fixtures, firmware diagnostics, signal verification, acceptance criteria, and the practical checks that turn “it worked once” into a repeatable production result.
DFTFixturesDebugManufacturing
BLE-connected embedded controls
Connected device behavior, BLE service design, shell/debug commands, callback-driven hardware control, and reliability expectations that continue after the first connection succeeds.
BLEMCU callbacksDiagnosticsReliability
Engineering automation and CAD/BOM cleanup
BOM cleanup, CAD/CAM handoff support, panelization workflows, firmware tooling, and scripts that turn repetitive engineering work into controlled, auditable processes.
C/C++PythonMQL5BOM/CAD workflows
Available for select consulting, prototyping, and design-review work
If the risk crosses hardware, firmware, and production, I can help reduce it.
Good fit: embedded hardware and firmware reviews, prototype planning, PCB/BOM sanity checks, board bring-up strategy, production test criteria, and cross-discipline debugging where the expensive mistake is assuming the problem belongs to someone else.