2025Idealaya
Product Designer
Enterprise web software, high-fidelity product design and design-system work aimed at clearer implementation.
About Nischhal Raj Subba
I design by staying close to the product and close to the build.
I’m a product designer based in Kathmandu, Nepal. My work spans UX architecture, interface design, design systems, technical websites and implementation handoff.
I started in agency and client work, which taught me to move between industries and explain design decisions to people with very different priorities. Product roles pushed the work deeper: more states, longer-lived systems, permissions, data, engineering constraints and the consequences of decisions that cannot be solved by a nicer component.
That is the part of design I enjoy most. I like products where the brief is incomplete and the interface has to make a complicated system easier to reason about. I care about hierarchy, state language, recovery, responsive behavior and the quiet rules that make a product feel predictable.
I also stay close to implementation. I do not need to own the front end on every project, but understanding browser behavior, component constraints and UI QA makes my design work more practical and my handoff less theatrical.
A career that moved from broad client work into deeper product systems.
The short version for hiring teams. The resume carries the full chronology.
2024–25Mokshya Protocol
Product Designer
Web3 product and website design, including wallet-native behavior, prototypes and technical product storytelling.
2023Tegzy
Lead User Experience Designer
Design-system consistency, reusable product patterns and stronger design-to-development handoff.
2021–23ESR Tech
Senior UI/UX Designer
Dashboard and internal-tool UX alongside broader product and website work.
2021ThemeGrill
Senior UI/UX Designer
Reusable UI components and prototypes inside a WordPress product environment.
2019–21Gurzu
UI/UX Designer
Client-facing product design, prototyping and interface improvement across early-stage and existing products.
Three habits I bring into almost every product.
Start with what the user needs to decide.
It keeps flows, content and visual hierarchy tied to a job instead of a collection of screens.
Design what happens when the happy path stops.
Waiting, errors, permissions, empty states and recovery are product behavior, not cleanup copy.
Make the handoff explicit.
Responsive rules, component behavior and QA should survive without a designer narrating every frame.