NVIDIA · Primly Community

NVIDIA product designer / UX interview and portfolio review: what they actually care about

brand_ben · 4 replies

went through the NVIDIA product designer loop this spring. ended up declining the offer for personal reasons but the process was genuinely interesting and I don't see much about it online. sharing for anyone preparing.

NVIDIA hires designers mostly for internal tools (developer platforms, NGC, CUDA toolkits UI, DRIVE visualization interfaces). it's not consumer product design. if you want to work on everyday apps, this is not that. if you find highly technical users and complex domain problems exciting, it's actually a really interesting design space.

the process:

portfolio review (45 min): led by a design manager. they want depth on 1-2 projects, not a parade of screenshots. they will ask: who were the users, what did they actually need, how did you find that out, what did you explore that you didn't ship, what did you measure after launch. if your portfolio leans visual without UX reasoning underneath, this is where it surfaces.

for NVIDIA specifically: they responded much more to projects where the users were technical (developers, researchers, engineers) than to consumer-facing work. not that consumer work is bad, but they want to see you understand technical users, not just 'users'.

design exercise: they gave me a prompt 24 hours in advance. mine was: design a dashboard that lets a developer monitor and debug a distributed model training job. I had 30 min to present. they weren't evaluating visual polish. they were evaluating: did I understand what a developer actually needs during a training run? did I prioritize the right information? did I handle error states? did I consider performance at scale (virtualized lists, lazy loading, etc.)?

behavioral: 3 rounds of STAR. they cared about collaboration with engineering, managing stakeholder disagreement, and working on something technically beyond your initial expertise. all real situations for a designer embedded with GPU software teams.

cross-functional round: a senior engineer on the team. they were checking: can you have a technical conversation? do you make engineers' lives harder or easier? they didn't quiz me on CUDA, but they did want to see that I could engage with implementation constraints without dismissing them.

comp for senior product designer: base was around $185k in Santa Clara. RSUs bring total comp to a different place. smaller than the engineering bands but not out of line with what senior designers make at hyperscalers.

4 replies

ux_uma

the 'technical users not just users' thing is so important and so often ignored in design prep. I've interviewed at a bunch of infra-adjacent companies and the designers who bomb the loop are almost always the ones who treated a developer as just another user persona with a different job title.

returner_ren

how did you handle the 24-hour design exercise in terms of how much you polished it vs. depth of thinking? I always struggle with that tradeoff.

brand_ben

I spent about 3 hours on it total. one hour on actual thinking and sketching (paper). one hour building a rough Figma mockup. one hour on a short narrative doc explaining my decisions. the doc was the most important artifact. they wanted to see reasoning, not a finished design. the Figma was just to anchor the conversation.

alex_design

this is one of the better write-ups on a big tech design loop I've seen. the point about them caring more about technical user empathy than visual polish is exactly right and it doesn't get said enough.