Nikhil K.
Senior UX/UI Designer | Figma, AI Products, SaaS
I've worked on products with 200 screens that needed 40, and MVPs with 3 screens that were missing the right ones. Seven years of product design comes down to knowing the difference. The job has never once been"๐ฆ๐๐ค๐ ๐ข๐ญ ๐ฉ๐ซ๐๐ญ๐ญ๐ฒ." It's always "๐ฎ๐ฌ๐๐ซ๐ฌ ๐๐๐ง'๐ญ ๐๐ข๐ ๐ฎ๐ซ๐ ๐ญ๐ก๐ข๐ฌ ๐จ๐ฎ๐ญ" or "๐ฐ๐'๐ซ๐ ๐๐ฎ๐ข๐ฅ๐๐ข๐ง๐ ๐ฌ๐จ๐ฆ๐๐ญ๐ก๐ข๐ง๐ ๐ง๐๐ฐ ๐๐ง๐ ๐ง๐๐๐ ๐ฌ๐จ๐ฆ๐๐จ๐ง๐ ๐ฐ๐ก๐จ ๐ ๐๐ญ๐ฌ ๐ญ๐ก๐ ๐๐ฑ๐ฉ๐๐ซ๐ข๐๐ง๐๐ ๐ซ๐ข๐ ๐ก๐ญ ๐๐๐๐จ๐ซ๐ ๐๐๐ฏ ๐ฌ๐ญ๐๐ซ๐ญ๐ฌ." That's what I do on daily basis across SaaS, custom web and mobile applications for different domains. ๐ ๐ฌ๐ญ๐๐ซ๐ญ ๐ฐ๐ข๐ญ๐ก ๐๐ฅ๐จ๐ฐ๐ฌ, ๐ง๐จ๐ญ ๐ฌ๐๐ซ๐๐๐ง๐ฌ. ๐๐ก๐๐ญ ๐ข๐ฌ ๐ญ๐ก๐ ๐ฎ๐ฌ๐๐ซ ๐ญ๐ซ๐ฒ๐ข๐ง๐ ๐ญ๐จ ๐๐จ, ๐ฐ๐ก๐๐ซ๐ ๐๐จ ๐ญ๐ก๐๐ฒ ๐ ๐๐ญ ๐ฌ๐ญ๐ฎ๐๐ค, ๐๐ง๐ ๐ฐ๐ก๐๐ญ'๐ฌ ๐ญ๐ก๐ ๐ฌ๐ก๐จ๐ซ๐ญ๐๐ฌ๐ญ ๐ฉ๐๐ญ๐ก ๐ญ๐จ ๐ ๐๐ญ ๐ญ๐ก๐๐ฆ ๐ญ๐ก๐๐ซ๐. By the time I open Figma, every screen has a reason to exist. When I'm done, you get organized components, documented interaction states, responsive specs, and handoff files clean enough that your dev team builds what I actually designed not their interpretation of it. Most of my clients are founders or product leads at companies where the designer isn't just decorating, they're making product decisions. I'm comfortable in that seat. I'll push back when a feature adds complexity without adding value, and I'll tell you when three screens can do the job of ten. ๐ญ๐ฌ๐ฌ% ๐๐ผ๐ฏ ๐ฆ๐๐ฐ๐ฐ๐ฒ๐๐ ๐ผ๐ป ๐จ๐ฝ๐๐ผ๐ฟ๐ธ. ๐๐ณ ๐ฎ๐ป๐ ๐ผ๐ณ ๐๐ต๐ถ๐ ๐๐ผ๐๐ป๐ฑ๐ ๐น๐ถ๐ธ๐ฒ ๐๐ผ๐๐ฟ ๐๐ถ๐๐๐ฎ๐๐ถ๐ผ๐ป, ๐บ๐ฒ๐๐๐ฎ๐ด๐ฒ ๐บ๐ฒ ๐๐ถ๐๐ต ๐๐ต๐ฒ ๐ฑ๐ฒ๐๐ฎ๐ถ๐น๐ ๐ฎ๐ป๐ฑ ๐'๐น๐น ๐ด๐ถ๐๐ฒ ๐๐ผ๐ ๐ฎ๐ป ๐ต๐ผ๐ป๐ฒ๐๐ ๐๐ฎ๐ธ๐ฒ ๐ผ๐ป ๐ต๐ผ๐ ๐'๐ฑ ๐ฎ๐ฝ๐ฝ๐ฟ๐ผ๐ฎ๐ฐ๐ต ๐ถ๐.