ABOUT ME (THE NOT AT WORK VERSION)

Kayak Guide. Wilderness First Responder. Guitarist. Photographer. Painter. Bike Repairman.

Liverpool FC Supporter (YNWA).

Classic designer trope – I wear many hats and I’m always looking for more.

I moved from Chandigarh, India to the US at the age of 18 (in 2007) and have lived in Sioux Falls SD, Philadelphia PA, and most recently, Chebeague Island off the coast of Maine. I currently reside with in Saco, ME with my incredible wife, Lorren. 

Living in Saco allows me to be available in a hybrid fashion in Boston, NYC, and Philadelphia (my love) – but I’d love to stay remote as I have 14 years of experience of working remotely and delivering top quality results. 

For the past year since being laid-off at Comcast, I’ve been solving tech issues on a low capacity island – helping them with their local resources like the Town website, Rec Center, Island Council, Town Hall, and all the locals with literally any kind of tech issue beyond design. It’s been a key learning experience, embedding myself in a tight-knit community and making myself open to opportunities and giving it a 100% when given the chance. I took time to reflect on my career, learn some valuable AI methods, and reevaluate what I want out of my design career.  

My next few goals in life are to build something that will last, to advance my training as a medic, and to be in the water as much as possible.

ABOUT ME (THE AT WORK VERSION)

What excites me isn’t just good interface design, rather, it’s configuring the stuff behind it that makes things run smoothly. I’ve been gung-ho about design systems and atomic components and Figma and auto-layout… but, smart AI tools, component systems that actually scale, and delivering clean handoffs so teams can just build without hitting walls: that’s undeniably progressive – no more fidelity loss!

A huge part of my job is to act as a translator between designers, developers, stakeholders, project owners, and executives. I spend a lot of time bridging the gap between design decisions, business reality, and engineering constraints so everyone is moving in the same direction instead of working in silos. I like the messy, hard problems—heavy enterprise logic, edge cases, and turning chaotic requirements into simple, accessible software that makes sense.

Software should be reliable, accessible to everyone, and built to scale—but it should still feel human. And honestly? The process should be enjoyable.

Otherwise, what’s the point?