Product engineer · Irvine, CA
I build products end to end: the insight, the interface, and the code underneath.
I'm a computer science student at UC Irvine who works the whole width of a product: figuring out who it's actually for, deciding what's worth building, then shipping it.
Most of what's below started as a problem I kept running into personally. I care about the part most engineering stops short of: whether anyone wants the thing, and whether they come back.
About me
I care about the whole lifecycle of a product: the problem worth solving, the person it's actually for, and whether the thing I shipped changed their behavior. The code is the part I enjoy most, but it's in service of that, not the point of it.
I'm part of Break Through Tech's AI Studio fellowship, on a small team building Chewy, a machine learning system for detecting AI-generated text. Outside of that, I'm deliberately building range across the full product stack: management, design, and engineering, plus the AI, agent, and infrastructure layers most products now run on.
Every case study on this site follows the same process: a real problem, a specific target user, a look at what already exists, the insight that made the solution different, how it got in front of people, and what changed after they used it.
- Based in
- Irvine, CA
- Studying
- Computer Science, UC Irvine
- Fellowship
- Break Through Tech AI Studio
- Currently learning
- Product managementProduct designProduct engineeringAIAgentsInfrastructure
Selected work
Open source
Shipping into code I don't own: someone else's review bar, someone else's users already depending on it.