Product designer for early-stage startups turning messy ideas into usable products.

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.

Context

Pamir AIProduct LeadCurrent

I design by building. I talk to founders, they give me a bunch of ideas—my job is to make sense of them and see how they connect. Then I skip Figma and code prototypes directly. I brainstorm with Claude Code, tinker through the flows until they make sense, and document decisions for developers. By designing in code from day one, ideas move from uncertain to validated in days instead of months.

WompProduct Designer

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.

How I Work

Learning by building

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.

Clarity from incomplete information

Early-stage work rarely comes with clean briefs. I’m comfortable asking the right questions, narrowing scope, and making decisions with imperfect information.

Design that survives engineering

I think in flows, components, and states so designs translate cleanly into code and continue to work as the product evolves.

How I Approach Early-Stage Problems

Systems before screens

I prioritize flows, structure, and edge cases before visual polish so the product holds up as complexity grows.

Speed with intent

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.

Trust as a constraint

I treat trust as something that must be designed deliberately. Every interaction either builds confidence or introduces doubt.

What It’s Like to Work With Me

  • I ask uncomfortable questions early to avoid expensive mistakes later
  • I’m comfortable saying “we don’t know yet” and working toward clarity
  • I collaborate closely with engineers and respect technical constraints
  • I care about shipping, learning, and iterating quickly

Beyond Design

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.