My path into software engineering is a bit unconventional. Before writing production code, I spent nearly two decades as the owner of Strokers, a motorcycle service business in Merced, CA — and before that I was a clinical engineer maintaining medical equipment at Stanford University Hospital and Walter Reed Army Medical Center.
I came back to school in my 40s, finished a B.S. in Software Engineering at ASU with a 3.83 GPA, and I'm now working through an M.S. in CS with an AI concentration. The business and engineering background informs how I approach software: I think about what actually needs to work, for whom, and what breaks first under real load.
My current focus is AI and full-stack development. I've shipped two production SaaS products, built an open-source agent framework, competed in an AI hackathon, and done coursework covering everything from binary exploitation to distributed systems to deep learning.
Stanford Medicine / Lucile Packard Children's Hospital
Clinical Engineering — PiNO System
Before software, I spent years as a clinical engineer maintaining critical medical equipment. At Stanford I worked on a portable inhaled nitric oxide delivery system (PiNO) for neonates — a project that went through FDA evaluation and a multicenter trial whose results were published in the New England Journal of Medicine. It's an unusual background for a software engineer, and it shapes how I think about reliability.
