I'm Arshiya — a product designer with 3+ years across US and Indian fintech, from payments at Razorpay to investing at Groww to banking flows at OnePlusOne, now designing for global clients at Work & Co, New York. I treat every screen like a ledger entry: each decision traceable to research, each pixel accountable to an outcome.
At Razorpay I ran 50+ user interviews before touching the onboarding redesign. I don't design from taste alone — I design from transcripts, drop-off data, and support tickets, then let taste refine what evidence has already shaped.
When money moves, users read every word twice. I design for the moment of hesitation — confirmations that reassure, states that never surprise, language that says exactly what happens next.
I use AI tools to compress research synthesis and widen early exploration — more directions tested, faster. The judgment calls, the craft, and the accountability for the final experience stay mine.
Stakeholder interviews, analytics review, user interviews, and UX audits. I map where the product loses people before deciding what to build.
→ Problem framingJourney maps, affinity mapping, and prioritization with product and engineering — turning raw findings into a sharp, testable design brief.
→ Design briefRapid wireframes and user flows in Figma. Cheap to make, cheap to kill. I test structure and sequence before a single visual decision is made.
→ Validated flowsHigh-fidelity screens on a consistent design system, prototyped and pressure-tested with real stakeholder and usability feedback in iterative sprints.
→ Tested prototypeAnnotated handoff, close collaboration with engineering through build, and post-launch metrics review — because shipped is the start, not the end.
→ Measured outcomeTransfers took too many steps, transaction history buried the answers people came for, and unclear states made users double-check everything outside the app. A UX audit traced high bounce and weak retention to friction in the core transaction flow — the one journey every user takes.
I rebuilt the flow's skeleton first: surface balance and recent activity on one screen, cut the transfer journey from five steps to three, and give every transaction a state users can read at a glance. Wireframes were tested with quick hallway reviews before any visual design began.
The visual language is deliberately quiet — a dark, low-glare surface with one accent, generous type for amounts, and color reserved for meaning: green in, neutral out, amber pending. Every state was prototyped and refined against stakeholder and usability feedback across sprints.
Boost in user retention
Reduction in bounce rate
Active user growth in 2 months
Rapido's driver experience buried the two things drivers care about — the next ride and today's earnings — under cluttered navigation. Onboarding friction slowed new-driver activation, and mid-ride screens demanded too much attention at exactly the wrong moment.
The wireframes enforced one rule: anything a driver needs mid-shift lives in the bottom half of the screen, reachable by thumb. Ride requests became a single decisive card with the three facts that matter — fare, distance, pickup — and earnings got a permanent home instead of a buried menu item.
Hi-fi screens use oversized type, high-contrast surfaces, and one warm accent tuned for outdoor visibility. Within two months of launch, the redesigned interface lifted driver engagement by 30% and cut onboarding friction for new drivers.
Increase in driver engagement
Reduced onboarding friction
Target time to read a ride request
Annotated Figma files, documented states and edge cases, and consistent tokens — so development starts with clarity instead of a meeting. At Groww, tighter handoff helped cut sprint timelines by 30%.
I present research and rationale to product, engineering, and marketing stakeholders directly — the way I did at Razorpay — so alignment happens around evidence, not opinion.
Reusable patterns and design-system thinking on every project, keeping the experience coherent across features, sprints, and the designers who come after.
Retention, engagement, activation — I define success metrics with product before designing, then stay accountable to them after release. That's how 35% and 30% aren't guesses.
M.S. IT Management — St. Francis College, Brooklyn · Google UX Design Certificate