I work best in pre-seed to Series A environments where requirements are unclear, speed matters, and the product still needs to earn user trust. I focus on structuring problems before polishing screens.
I worked on product design across core user flows, internal tools, and early system decisions. The work involved operating with incomplete requirements, collaborating closely with engineering, and designing foundations that could scale as complexity increased.
I’ve learned design by shipping real products and prototypes, not just academic exercises. Building helps me understand constraints, edge cases, and what actually breaks once users interact with a product.
Early-stage work rarely comes with clean briefs. I’m comfortable asking the right questions, narrowing scope, and making decisions with imperfect information.
I think in flows, components, and states so designs translate cleanly into code and continue to work as the product evolves.
I prioritize flows, structure, and edge cases before visual polish so the product holds up as complexity grows.
I value speed, but not at the cost of clarity. Shipping fast only matters if users understand what they’re doing and trust the product.
I treat trust as something that must be designed deliberately. Every interaction either builds confidence or introduces doubt.
I’m naturally curious and tend to go deep on problems I care about. I enjoy building small things, experimenting, and learning through hands-on work. I’ve learned that stepping away when clarity drops often leads to better decisions than pushing harder.