Available
Designing AI products
people actually use
7 years in product design. 4 in AI. I was the founding designer at Instaheadshots & Magic Studio, where I built the system and shipped the product from zero to 20 million users.
Designing experiences
that solve real problems.
Four years of that were spent building AI consumer products. Most of it as the founding designer at Magic Studio & Instaheadshots, where I took a single tool to a nine-product platform used by 20 million people. I owned end-to-end: the design system, the product strategy, the decisions that didn't have a clear owner yet.
Before design, I studied literature & psychology. I think it's why I care so much about what a product communicates, not just how it functions. Good interfaces have a point of view. They make you feel capable.
I'm at my best on hard, undefined problems, with people who sweat the details. Curious by default.
Experience, Tools & Evolving Craft
Tech Stack
Product & Interaction Design, Website & App Designs
Figma
Adobe
Adobe
Motion Design
Framer
Jitter
Rive
Adobe
Generative Stack
Claude
ChatGPT
ChatGPT
01
What kind of role are you looking for?
I want to work on teams that ship often and care about the details, because I'm someone who's already proven I can do that. At InstaHeadshots, I was the only designer taking the product from nothing to 20M+ users and 150M+ images processed, and I built the design system from scratch because there wasn't one. I like 0-to-1 work: messy problems, no roadmap yet, figuring out what we're even building. Based in Mumbai, open to remote, hybrid, or relocating.
02
How do you actually approach a design problem?
I start by trying to understand why something matters before figuring out what to build. That usually means a lot of conversation with users, with PMs, with engineers before I open Figma. I'd rather show three rough directions than one over-finished concept. Sometimes elimination of extra steps is better than adding in design.
03
What kind of work energizes you most?
Where I get to spend time figuring out what's actually broken before designing the fix. I also love working closely with engineers; some of my best decisions have come from a casual "wait, why does it need to do that?" conversation.
04
How do you handle being the only designer on a project?
Being the only designer meant no one to blame when I got it wrong, so I learned to trust my gut fast and fix it faster when the gut was wrong too. The con is real: you're making calls alone and hoping they hold up. The upside is I still booked critiques every couple weeks and pulled engineers and PMs in early, because trusting yourself isn't the same thing as trusting yourself blindly.








