And a willingness to stay with the problem.
Usually asking “why?”Hi again, I’m Prajwal
Product Designer and Design Engineer focused on design systems, complex workflows, and AI-assisted product development. Experience spans a live Google product through Smollan and independent web and Android products, from research and prototyping through implementation.
Since May 2025, my work through Smollan has included design systems, content and design automation, CMS workflows, and enterprise product research. Alongside that, I design and build FixTheResume and ScoreKeeper.
My Bachelor of Computer Applications at BVP IMED, Pune grounds that practice in HCI, web development, and software engineering. Based in Pune, India, I stay close to both the design and the build.
Say helloUX/UI Designer
Built a token-based design system with Figma Make and Claude Code to improve product consistency and reduce repetitive design work.
Built a full-stack internal tool that automates content and design workflows for the teams producing them.
Simplified complex CMS workflows by connecting business rules, AI-assisted improvements, and clearer interfaces.
Not a process checklist. These are the convictions that shape every decision - how I read a problem, what I refuse to skip, and where the work has to land to feel finished.
I do not start with screens. I start with the gap between what a product promises and what it actually delivers. Interfaces that skip this step look polished and fix nothing. The friction is almost always upstream of the UI.
The interesting design happens in the states no one shows in the pitch: loading, failure, empty, edge. A flow that only works in the ideal case is not a flow - it is an illustration. The system has to hold when things go wrong.
I use AI to close the gap between a decision and a working version of it. The product judgment, the quality bar, and the structural thinking remain manual. Speed without judgment produces volume. That is not what I am optimising for.
A design that loses its intent between the file and the build was never really finished. I stay close to implementation - not to control, but because that is where the gaps between intent and behaviour actually surface.
The interface is the last mile of a much bigger decision.
See that thinking in the work
