01
Research & strategy
Interviews, diary studies, heuristic audits, and the occasional spreadsheet. I'd rather kill a feature in research than ship it and discover it's wrong.
I'm a digital product designer with an engineering background. I run the research, draw the pixels, and write enough React to keep the handoff honest. Lately: B2B SaaS, design systems, and anything that involves rescuing a sprawling admin panel.
✦ The short version
I came to design through engineering — which is a fancy way of saying I learned to ship before I learned to draw. That order shapes how I work.
Six years in, I've designed for agency clients, embedded with an enterprise platform team for two and a half years, and led capstone work on hyperlocal social products. The throughline is research that shows up in the pixels, design systems that survive contact with engineering, and a strong allergy to decoration.
Read the long version →✦ What I do
I'd rather go deep than wide. Most projects I take on touch all three of these — they're not separate offerings, they're how I work.
01
Interviews, diary studies, heuristic audits, and the occasional spreadsheet. I'd rather kill a feature in research than ship it and discover it's wrong.
02
Wireframes, prototypes, full UI, and the design system underneath. I work in Figma but think in React components.
03
I write enough HTML, CSS, and React to make handoff a conversation, not a throw. Tokens, Storybook, and the boring infrastructure that keeps a system honest.
✦ Selected work
The boring parts of an interface should be boring. Save the design budget for the parts that are uniquely yours.
✦ Aastha's first design rule
I'm currently exploring full-time product design roles and select advisory projects. If you've got a B2B product that's grown into a maze, I'd love to hear about it.