Senior Product Designer & Design Leader — AI-First Practice — Pune, India
I lead the teams that decide where AI earns its keep.
Eight-plus years leading design — teams, stakeholders, and the roadmap decisions in between — through ambiguous, high-stakes problems: fintech trust, AI-guided forecasting, design operations at scale, AI-first logistics tooling. I've run a design team end to end, led discovery as the person stakeholders waited on, and owned the call on where AI should sit in a product — not just the screens that followed from it.
About
I'm a Senior Product Designer at GlobalLogic (now Hitachi Digital) — and for most of the last four years, the actual job has been leading: a design team, a room of stakeholders, a discovery effort, or the call on where AI should own a decision and where a person still has to. Design is the craft underneath all of it, not the whole job.
I've led design — not just contributed to it — across fintech (Mewt), AI-guided revenue forecasting (AVISO), design-ops tooling (Cubyts), and, over the last three years, a confidential logistics platform for truck leasing and rental. That's run a small design team through a ten-month engagement, led a two-month, sprint-based discovery that kept a business's stakeholders inside the process, set direction on an AI-guided forecasting experience, and owned the incremental call on how much of a workflow AI gets to run. Four very different domains that reward the same instinct: get the right people aligned on the real problem before anyone opens Figma.
That instinct came from consulting. I started as an Innovation Consultant, then moved through UX consulting at F1 Studios before taking on product ownership — and eventually team ownership — at Cubyts and GlobalLogic (now Hitachi Digital). Each step traded a little more distance for a little more accountability: for a roadmap, for a team's output, for a stakeholder relationship that had to survive disagreement. Leadership, to me, isn't the time I'm not designing. It's deciding what's worth designing, and getting the room to agree before we build it.
Where I've Led
For most of my career, the hardest part of the job hasn't been the screen — it's been getting a team, a stakeholder group, or an organization to agree on what's worth building. Four moments show that most clearly:
Ran a design team, not just a design task
Led a 2–3 person design team for roughly ten months — sprint planning, design reviews, day-to-day direction — while personally owning a module and carrying roughly 40% of stakeholder communication myself.
Read the Cubyts case studyLed the discovery the business waited on
Led a two-month, sprint-based discovery engagement — stakeholder interviews, competitive analysis, user research — keeping the business inside the process and turning findings into a backlog the in-house team could execute immediately.
Read the Mewt case studySet direction, not just delivered screens
Set design direction for an AI-guided forecasting experience at enterprise scale — running stakeholder alignment and pairing with engineering and ML teams from concept to delivery.
Read the AVISO case studyLed the call on where AI should quietly inform, not decide
Led the three-year call on how much utilization and maintenance forecasting should run as background AI feeding the reports and dashboards the counter team already trusted, versus route out to the people built to act on it — partnering with engineering and data teams to earn that scope incrementally, not claim it on day one.
Read the FleetOps case studyHow I Think
"The best use of a tool — AI included — is not to replace human judgment. It's to free humans to use it more."
Systemic thinking, to me, just means refusing to solve the visible problem until I understand the system producing it. In practice that shows up as four working beliefs — the same ones I apply to how I use AI in my own process:
Humans start it
Intent, context, and empathy are not things a system can supply on its own. Every process I run — human or AI-assisted — begins with a person deciding what actually matters here.
Dialogue, not dictation
The best collaborators, human or otherwise, push back. I design processes as a loop — question assumptions, surface gaps, propose, revise — rather than a one-way handoff of instructions.
Boundaries by design
Speed without guardrails just produces confident mistakes faster. I build explicit checkpoints into workflows so nothing exceeds its scope without a human saying so.
Speed and rigor together
Removing routine work should never mean removing judgment. Every efficiency I introduce is measured against whether it protects — or quietly erodes — the quality of the decision at the end.
Move faster on what matters. Stay careful about what ships.
Selected Work
Skills
Leading
- Team Leadership
- Stakeholder Management
- Discovery Leadership
- Cross-functional Partnership
- Design Ops at Scale
Design craft
- UI / UX Design
- Design Systems
- User Research
- Prototyping
- Figma / Sketch
AI-augmented workflow
- Claude
- ChatGPT
- NotebookLM
- Perplexity
- Figma Make
- Copilot Agents
Experience
-
Jun 2023 — Present
Senior Product Designer — GlobalLogic (now Hitachi Digital)
Design lead on a confidential client's Fleet & Unit Management Platform — a counter-team operations system for tracking and utilizing a truck and unit fleet. Took the product from a manual, spreadsheet-driven status tool to one where AI quietly informs utilization and maintenance forecasting in the background, feeding the same reports and dashboards the team already trusted rather than bolting on a separate AI feature.
Own the call, together with engineering and data teams, on how much of a decision AI should inform versus route to a person directly — expanding what AI touches only once the previous step had earned the team's trust. Three years in, still an active engagement, and the governance pattern set here is one I bring to how AI gets introduced elsewhere in the product.
-
Aug 2022 — May 2023
Product Designer — Cubyts Technologies Pvt. Ltd.
Senior design contributor at a design-ops product company, leading a 2–3 person design team for roughly ten months — sprint planning, design reviews, day-to-day direction — while personally owning a module end to end and carrying roughly 40% of stakeholder communication myself. Ran an incremental research method (five initial interviews, then eleven users over ten days) that redirected the product mid-build from a standalone-app idea into an AI-bridged dashboard built on Jira as the real source of truth.
That research shaped four core surfaces — a workspace statistics dashboard, a main dashboard, a timeline view, and cross-functional collaboration tools — used by design leaders to track team capacity, delivery velocity, and team health. Treated AI as a bridge into data the team already had rather than a feature to bolt on, and kept leading the team's day-to-day work without stepping back from my own delivery.
-
Aug 2021 — Aug 2022
User Experience Designer — F1 Studios
UX consultant across a diverse client roster spanning Mumbai and remote engagements. Set design direction on AVISO's AI-guided sales-forecasting workspace — an enterprise redesign of a deals table and deal-details experience — running design in the same sprint cadence as engineering and working directly with the data-science team on how a forecasting model's reasoning should be represented on screen, rather than skinning a number.
Separately led a two-month, sprint-based discovery and ideation engagement for the Mewt payments app, reframing the client's brief from "retention" to "trust" through structured stakeholder interviews and a four-competitor benchmark, and handing the business a prioritized design backlog its own product owners and in-house team could execute against immediately.
-
Jan 2018 — Jul 2021
Innovation Consultant — InstillMotion Consulting Pvt. Ltd.
Started my career in innovation and design consulting, working across tangible product design (including ChargePool) and innovation engagements for FMCG clients such as Cycle Agarbatti (NRR Group), alongside systems and service design work — a notably different discipline mix from the screen-based digital product design that followed.
That range is where the instinct that still drives my work today took shape: treat every brief as a systems problem before treating it as a design problem, and get a room of stakeholders aligned on what's actually worth building before shaping a single thing — whether that thing was physical, a service, or, later, a screen.
Contact
Have a hard, ambiguous problem that needs someone to lead it — not just execute it? I like those best. Reach out — I'm always open to a good conversation about design, leadership, or where AI actually helps.