Bring-up / an analog designer at the bench.
On D0, an analog designer used Claude and the prepared tools to investigate I²C communication, submit a firmware change and program the device.
Chips in production cars. Firmware on real silicon. A print-ready toy from my daughter’s drawing. I work across the whole hardware chain — and run an AI engineering team that turns ideas into real hardware.
I’ve designed chip architectures, analog circuits, digital logic and the systems around them. That breadth lets me connect the right knowledge, tools and engineering checks—so AI can do useful work across UltraSense.
Your spec, sketch or brief becomes precise instructions and acceptance checks.
Specialist agents develop electronics, mechanics, FPGA and firmware in parallel, on shared product knowledge.
Hardware, code and test records — plus a product digital twin your own team and agents can query.
Sensors, analog circuits, digital logic and firmware running inside the chip—then the board, mechanics and experiments around it. I understand the work on both sides of each interface.

At Berkeley, I developed ultrasonic transducers, interface circuits and imaging systems. At TDK-InvenSense and UltraSense, I worked across ASICs, electronics, firmware and mechanical integration.
Architecture, analog circuits, digital logic, on-chip MCU + firmware and top-level integration. I understand the design decisions inside each block—and the interfaces between them.

I can follow a design from the analog signal path through RTL and firmware to the full-chip interfaces.
Explore my circuits and chip portfolio
D0 = the day the first chip arrived.

My research · UC Berkeley
Research & original figure
Prior team work · UltraSense
Hardware portfolio
Ponchi AI · EchoMind design
Design files & context
AI workflow · UltraSense, first bring-up weeks
Experiments & resultsI bring electronics, firmware and mechanical constraints into the same engineering conversation. Today, I use that experience to direct AI development across PCB design, enclosure CAD and bench testing.





Because I’ve worked inside the chip and across the bench, I know how to turn an engineering goal into the right context, tool connections, agent tasks and acceptance checks. That is the foundation of the AI environment I deployed at UltraSense.

Sensor simulation & design connects my PMUT and piezo transducer work with a parallel agent for multiphysics studies and hand-calculation checks.
At UltraSense, I built the shared knowledge base, agent workflows and tool connections that put AI into everyday engineering. Engineers and specialist agents work across design, firmware, chip bring-up, calibration and physical tests—with common context and results the team can inspect.

I connect chip knowledge, design records and test methods so engineers and agents can work from the same sources.
I build the paths from a question to code changes, debugging, firmware programming and equipment-driven experiments.
Colleagues use and adapt the environment for their own work. I direct parallel development and review the engineering results.
On D0, an analog designer used Claude and the prepared tools to investigate I²C communication, submit a firmware change and program the device.
Another engineer used his own Claude environment to make small firmware and GUI changes for tactile testing, then kept the setup for future work.
Read the adaptation record“Introducing AI lowered the difficulty of these workflows enough for us to contribute.”
I set the questions and review the tradeoffs. AI develops candidates and runs supported test loops across independent setups.

Develop firmware and press-detection candidates, run supported press tests and compare the measured response.
Compare filtering and signal-analysis candidates, then carry selected changes into firmware and measurement.
Results return to me for comparison and the next decision. Agents develop and test on independent hardware loops.


Original figures, complete cases and the career behind the work.
Email Ponchi AI directly