Hi, I'm Rudhra.
A product designer who makes sense and cents.
The version your hiring manager meets — a research-driven product designer who turns messy problems into calm, shipped interfaces across healthtech, edtech, SaaS & AI. Flip the switch to meet the one after six.
A designer with a research habit.
I'm Rudhra. I blend psychology, research and visual craft to design products that feel obvious in hindsight, shipped across healthcare, education, SaaS and early-stage startups.
My day moves between end-to-end research (interviews, field work, usability testing, journey mapping) and the fine craft of interaction design, prototyping and design systems. I care about decisions that are data-informed, not data-decorated.
What I’m shipping
A short tour of the work I keep returning to — and what each one taught me.
- SolvirIT · AI agents & web
- Superstars · real-time product UX
- Compass Health · mobile + system
- SimplUI · capstone system
Tools that earn their keep
Not the longest list — the most used one.
- Figma & FigJam
- Miro · Hotjar · Maze
- Framer & Webflow
- HTML · CSS · JavaScript
- Claude Design · Stitch · Claude Code
Education, two degrees, one habit
The computer-science half is the reason I read tickets like a developer, and why the hand-off usually lands.
The working kit
Five quiet movements, one loud outcome.
The rhythm holds; the shape bends per project. It is a loop rather than a line: I go back a step whenever the evidence says to.
-
i.
Listen
Stakeholder kick-offs, user interviews, field observation, support tickets. I hunt the gap between what people say they need and what their behaviour is asking for. Nothing survives if I get this wrong.
-
ii.
Frame
Synthesise the patterns into a problem the team actually agrees on — journeys, jobs to be done, an opinionated “we will / we won't” list.
+ AI · stress-tests the framing against opposing lenses before committing -
iii.
Draw
Quantity before quality — sketches, lo-fi flows, divergent options. Rough things hit the wall on day three, not week three. Then wireframe to prototype to hi-fi, on a system.
+ AI · three hand sketches become clickable in an afternoon -
iv.
Validate
Prototypes in front of people who have never seen them, inside the week. Findings triaged by severity, not by preference — five sessions, three big ones, one that changes the brief.
+ AI · patches drafted between sessions, not after the round -
v.
Ship & revisit
Annotated specs, assets, and engineers I sit with rather than hand to. Fixes land before hand-off, not as a bug list after. Design isn't done at ship — it's just visible.
I close the laptop and open something deeper.
Most evenings split between long-form documentaries and a controller in hand. Both feed the same thing: I like watching a system reveal itself, whether it's a city, an algorithm, or a fictional world. Documentaries show me how one was built; games let me feel how it behaves when somebody is inside it.
Now playing: Minecraft, redstone era
Logic gates, item sorters, the occasional working calculator. The rest are old saves I keep coming back to.
Watching: long-form, slow-burn, a little nerdy
Subjects I keep returning to after dark.
- Attenborough's Light on Earth
- PC builds & tech deep-dives
- Veritasium · Kurzgesagt · Huberman
- Real Engineering · Mark Rober
Learning to cook, with an AI in the passenger seat
Thai, currently. The AI knows what galangal is, which chillies to soak, and why my coconut milk split. It has never once tasted the pot.
That is the whole job, really. It reads everything and decides nothing. I still have to stand there, taste it, and admit it needs more fish sauce.