Design
Philosophy

“In enterprise products — whether it is a security console, an HRMS, or a CDP — the real competition is the user's cognitive load. If they have to think twice, you have already lost them. I design to make complex workflows feel obvious.”

“My career so far has been embedded inside product companies, where design work is tied to shipped outcomes. That means sitting with PMs and engineers in sprint planning, pushing back on feature creep, and measuring success in user and business impact — not only handoff decks.”

“Contributing to the Cylance design system while working on Aurora Unified Portal taught me that a design system succeeds when engineers stop asking 'which variant?' and PMs stop asking 'does this exist?'. The value is not in Figma — it is in the alignment it creates across every team that ships product.”

“At Employee Experts, I was the sole designer for an entire HRMS — recruitment, payroll, leave, LMS, a native desktop app. No one to delegate to, no process to inherit. You learn to prioritise ruthlessly, ship confidently, and be accountable for every pixel that reaches a user.”

“Most designers switch domains every two years. I went deeper — from PCI compliance at SISA, to endpoint security at BlackBerry, to MDR/XDR at Arctic Wolf. Each layer made me faster, sharper, and harder to replace. Deep domain knowledge is the moat that generalist design cannot cross.”

“The gap between design and engineering is widest in Indian product companies — not because of talent, but because of translation loss. I write HTML, CSS, and basic React. I understand component states, API constraints, and sprint trade-offs. That fluency makes me a partner, not a gatekeeper.”