ABOUT
I came into design through industrial design — and never quite left.
I studied Industrial and Product Design at IIT Delhi, and what stayed with me from those two years wasn't styling or sketching — it was systems. How a backpack's strap interacts with a manufacturing tolerance. How a product line scales across SKUs without losing its idea. How a designer who can hold the whole system in their head, end to end, makes calmer decisions than one who can't.
A decade later, I do the same work on enterprise software. The materials have changed; the discipline hasn't.
01 — THE BRIDGE
From soft goods at company scale, to digital systems at enterprise scale.
After IIT Delhi I joined Roadgods — one of India's emerging travel-gear brands — where I shipped my first products and held a patent on the Gods Wolf camera bag. Then three and a half years at Wildcraft, where I owned the entire soft-goods design range and helped open two new business categories for the brand. Across those years I designed and shipped seventy products that contributed roughly ₹700 crore in revenue.
That experience anchored everything I do now. When you've designed something that has to survive a manufacturing line, a retail shelf, a monsoon, and a customer who paid for it — you stop thinking of design as decoration. You start thinking of it as a system that has to hold together under real conditions. Pixels are easier than stitching, but the discipline is the same.
Wildcraft — Product Designer (2018–2021) · 70 products shipped · ~₹700 Cr revenue across three years · led expansion into watches and trail-running shoes · proposed the Virtual Mask Size Finder during COVID-19, bridging physical product design with digital experience
02 — LEARNING TO LEAD
Three years at f1Studioz taught me what design leadership actually means.
I joined f1Studioz in 2021 as a Senior UX Designer and stepped into the Lead role a year later. Across three years I led parallel client engagements across B2B SaaS, BFSI, e-commerce, and telematics — usually leading teams of two to three designers, often working with three or four stakeholder groups whose priorities didn't agree.
Some of the work I'm most proud of came from there. On Capillary Tech, I led the IA restructuring of a global loyalty platform — and pushed the Hook Model as the data-architecture framework, holding the line when stakeholders wanted to apply it to the whole product. On Dinamani, I led the digital transformation strategy for one of Tamil Nadu's oldest newspapers and secured CEO, CMO, and MD buy-in — and then watched the same framework get commissioned for two more publications in different languages. On OneBill, I led a team of two through a focused two-month redesign of the pricing module, making explicit design bets about consolidation that the platform now ships.
I also mentored across all three editions of Sarva — f1Studioz's design mentorship program (2021, 2022, 2024) — guiding early-career designers through portfolio reviews and project critiques. It clarified for me that the kind of leader I want to be is one who teaches the thinking, not just the deliverables.
f1Studioz — Senior UX Designer to Lead UX Designer (2021–2024) · led teams across Capillary Tech, Dinamani, OneBill, OneInsure, Kotak Life, VeroModa, Energy Exemplar · authored f1Studioz' internal Design System and UX Analytics handbooks · mentored across three Sarva cohorts
03 — WHERE AM I NOW
At Nutanix, I design AI-driven workflows for the people who keep enterprise infrastructure running.
My current work sits at the intersection of three things I'd been moving toward for years: enterprise scale, complex data, and AI as a design material rather than a feature. I lead end-to-end design for AI-powered diagnostic tools used by Site Reliability Engineers, Sales, and Support teams — translating telemetry data and model outputs into decision-oriented interfaces that simplify high-volume triage.
What I've learned designing AI experiences for high-stakes ops users is that the AI isn't the design problem — it's the material. The design problem is how a tired engineer at 2am reads what the model is telling them, decides whether to trust it, and acts. Most AI-design work I've seen treats the model as a feature to surface. The work I care about treats AI confidence, uncertainty, and fallback states as first-class design materials — because that's what makes the difference between an engineer who trusts the tool and one who quietly ignores it.
Nutanix — UX Designer (2024–2026) · AI-driven diagnostic tools for SRE, Sales, and Support pods · interaction patterns for conversational and agent-based modules · contributing reusable patterns to the platform's AI experience library
03 — WHERE AM I NOW
Good enterprise design is invisible labour.
The work I value most rarely makes a screenshot look impressive. It's the IA decision that absorbed two new languages without rebuilding. The AI uncertainty state that prevented a junior SRE from acting on a false positive. The data architecture choice that let a marketing manager configure something she'd previously needed an engineer for.
Enterprise tools are where people spend their working lives. A small daily friction repeated across thousands of users is a real cost — and removing it is the most leveraged thing design can do. I think about scale not as a vanity number but as the conditions under which the design has to keep being true. Will this still work in a third language? Under a different AI capability? With a feature the product team hasn't conceived yet? If the answer is no, I haven't designed a system. I've designed a snapshot.