About
How I grew from deep technical foundations into a product-oriented, startup-minded builder.
Close to the user
I started by working close to the user: building interfaces with React, thoughtful component architecture, and a focus on performance and accessibility. I care about performance budgets, semantic structure, and design systems that scale, as well as real-time experiences that feel fast and responsive. For me, the interface is where product intent becomes real, and where small details shape how people experience a system.
Building the systems behind it
Over time, I moved deeper into the systems that power those experiences—distributed services, APIs, cloud infrastructure, and the reliability and scalability that sit behind every good product. I think in terms of failure modes, observability, and long-term maintainability, not just shipping features.
Owning the product, not just the code
I've learned to take ownership of outcomes, not just tasks. That means building end-to-end, measuring impact, learning from user feedback, and connecting technical decisions to real product and business goals. Shipping is the start of the learning loop, not the finish line.
Looking toward building from zero to one
I'm especially drawn to early-stage and 0→1 work: discovering the right problems, moving quickly with tight feedback loops, and building with small, driven teams where each person's judgment and craft matter. I want to be in environments where technical depth, product thinking, and ambition come together to create something new, not just maintain what already exists.