I’m Anil, a senior product and UX designer with 8+ years in enterprise AI, payments, education and consumer apps. I design in Figma, then build the risky parts in React and Next.js, so teams test real behaviour, not just pictures.
Worked with CloudGen Systems, N3XGEN.io, Genie Connections, TILLI Software, BYJU’S, Krify Software across enterprise AI, payments, EdTech and consumer apps.
Both are enterprise products where AI agents touch real systems, real data and real money. The hard part was never the AI. It was making people trust it.
An integration platform where AI agents do the heavy lifting, and people stay in charge.
One calm place to build, test, govern and run AI agent workflows.
Ten of the 79 hi-fi screens I designed this year. Swipe, and tap any screen to see it full size.
For eight years I’ve worked on products where a confusing screen has a real cost. AI agents that touch live systems. Payment flows that move money across borders. Lessons a ten-year-old should understand without help. My job is to make that complexity feel calm.
Senior Product Designer · Senior UX Designer
I start with people and the work they actually do, not the feature list. I like messy problems: twelve tools stitched together, approvals that live in email, logs nobody can read at 2 AM. I map them, give things plain names, and design the few moments where a person really has to decide.
Most of my recent work is enterprise AI. At CloudGen Systems I led UX for N3xgen Agentic OS, designing how IT admins, architects, analysts and compliance teams build, test, approve and audit AI agent workflows. The thread through all of it is trust. Show what the system did, why it did it, and how to undo it.
Before that I worked on payments at TILLI, where my redesign of payment setup lifted task completion by more than 40% in testing; on K–12 learning at BYJU’S; on a social discovery app as a freelancer; and on many web and mobile products at Krify, where I learned the craft.
I also write code. I prototype in React and Next.js with AI coding tools, so engineers get something they can click, break and question early. This site is one of those builds.
Four rules I keep coming back to. Each one has saved a project at least once.
People trust what they can see. I would rather put the full flow on one screen than hide it behind a five-step wizard.
Testing should be the default. Going live should be a clear, reviewed choice, never a toggle buried in a form.
A red dot is not a design. Say what broke, what it affects and the safest thing to do next.
If a new teammate cannot guess what a label means on their first day, the label is wrong, not the teammate.
A Double Diamond with gates, plus one step most designers skip: building it. Every phase ends with something people can sign off, so fast projects do not turn into fast mistakes.
Stakeholder talks, an honest audit of what exists, desk research and competitor reviews. I end this phase with two lists: what we know and what we are only guessing.
Proto-personas, journeys, problem statements and an object model simple enough to learn in ten minutes. Then I agree on the success metrics before drawing a single screen.
Three directions, scored openly. Then wireframes, a token-based design system and hi-fi screens where every state is designed: empty, loading, error, waiting for approval.
I build the risky parts in React and Next.js with AI coding tools. Engineers can click it, break it and question it early, and we argue about behaviour instead of pictures.
Dev Mode specs, edge cases, acceptance criteria and design QA every sprint. I stay close until it ships, because that is where the details get lost.
Vibe coding, done with care. I use AI coding tools to turn designs into working React and Next.js prototypes in hours, not weeks. Engineers get something real to click and question, and I get honest feedback before anything is final.
Real states, real data shapes and real edge cases, so usability tests feel like the product.
Clean React and Tailwind, with tokens that match the Figma variables one to one.
Feasibility questions get answered in a day, and design QA happens in the same language as the build.
Led UX for N3xgen Agentic OS, an enterprise AI platform that IT admins, process architects, analysts and compliance teams use to run and watch automated workflows.
Finding the real problem and shaping the flow around it.
Systems that scale, and handoff that engineers actually like.
AI-assisted prototypes in real code, so we test behaviour, not pictures.
I’m looking for a senior product or UX design role where AI, data or money makes the work hard. Recruiters and hiring managers, I usually reply within a day.