I build things in 48-hour sprints, then obsessively polish the details after.
I build at the intersection of product, engineering, and execution, and I care a lot about making things feel clear. I like shipping fast, sharing what broke, and improving each version in public.
I'm studying CS at San José State and I'm usually thinking about workflows that waste people's time. The projects I keep coming back to are the ones that reduce friction, make decisions faster, and actually get used.
Fun fact: if I can't explain the product clearly in one sentence, I treat that as a bug.
Professional Development Committee
Technical Development Board Member
We built bottlr in 48 hours at SF Hacks because campus recycling handoffs were chaotic and hard to track. It became a real-time pickup network and won SFU Innovation & Entrepreneurship / Emerging Tech and Jobs for Future Ventures: Best Hack for the Future of Work.
I built Invara after missing too many important details buried in noisy group chats. It reads conversation context and surfaces what actually needs action.
I'm always down to chat about internships, projects, or just random ideas.
My post
