NVIDIA Interview Questions — Page 9

NVIDIA·Software Engineer·Technical Phone Screen

May 2026

NVIDIA software engineer interview that went deep on GPU architecture, specifically how thread limits and occupancy work on modern hardware. More math-heavy than I expected for what I thought would be a conceptual discussion.

What is the maximum number of threads per block on an NVIDIA GPU, and why does that limit exist?
What are the different factors that limit the number of resident threads on a Streaming Multiprocessor simultaneously?
Given a kernel's per-thread register usage and per-block shared memory usage, how would you compute GPU occupancy?
How does occupancy influence how you choose your kernel launch configuration, and what are the performance tradeoffs involved?

“This part I actually knew cold.”

View Post

NVIDIA·Software Engineer·Onsite - System Design / Architecture

May 2026

NVIDIA software engineer interview that got into agent RAG system design, including how to optimize the retrieval and generation pipeline. Pretty technical conversation from what I remember.

How would you design an agent-based RAG (Retrieval-Augmented Generation) system, and what optimization strategies would you apply?

“This was the meat of the conversation.”

View Post

NVIDIA·Data Scientist·Technical Phone Screen

May 2026

Technical screen for a Data Scientist role at NVIDIA that went deep into linked list territory, way deeper than I expected for a DS position. The question had like four sub-parts and felt more like a systems/algorithms round than anything data-science-adjacent.

Reverse a singly linked list in place. Implement both an iterative solution using O(1) extra space and a recursive version, and explain how you'd prevent stack overflow for lists with up to a million nodes.
How do you handle edge cases for linked list reversal: an empty list, a single-node list, and an extremely long list?
What happens if the linked list has a cycle? Detect it using Floyd's algorithm, then decide whether to break the cycle or preserve it while reversing the linear segment, and justify your choice.
Walk through the time and space complexity of your solution, state the loop invariant you're relying on for correctness, and describe a minimal set of tests you'd write.

“The iterative part was fine, three pointers, done.”

View Post

NVIDIA·Software Engineer·Onsite - System Design / Architecture

May 2026

System design round at NVIDIA for a software engineering role. The whole thing was one big fraud detection problem and they wanted the full picture: architecture, ML serving, scaling, the works. Dense question, not a lot of room to wing it.

Design a real-time fraud detection system for a payments company that handles millions of transactions per day. The system needs to approve, flag, or block each transaction within 50ms, sustain over 10k requests per second with headroom for traffic spikes, and support ML model updates without any service downtime. Walk through the full architecture including data flow, model serving, scaling, and how you'd operate it in production.

“This is a lot to cover in one question.”

View Post

NVIDIA·Software Engineer·Onsite - Multi Round

May 2026

Went through a full NVIDIA senior SWE loop, two phone screens plus a five-round super day. The day was long and by round four I was running on fumes, which showed. Posting because I genuinely can't read how it went.

Solve a hard algorithmic problem, starting with brute force before optimizing.
Why do you want to join NVIDIA, and what specifically about this role appealed to you?
Why are you looking to leave your current company?
Solve two coding problems in sequence, including a partial puzzle problem.
Deep dive into a specific project from your background, with follow-up pressure questions.
Design a system and then answer a conceptual trade-off question about a key architectural choice.
Solve a straightforward coding problem as part of the system design round.

“They explicitly asked me to code brute force first, which was actually a relief.”

View Post

NVIDIA·Product Manager·Onsite - Product Sense / Strategy

May 2026

Nvidia PM interview, one question about walking through a product you scoped and built end to end. Pretty standard product sense round but the specificity they wanted caught me a bit off guard.

Walk me through a product you scoped and built from scratch. What was the goal and what was your specific role in it?

“I picked a project I knew cold but spent too long on the backstory and not enough on what I actually decided and why.”

View Post

NVIDIA·Software Engineer·Technical Phone Screen

May 2026

Interviewed at NVIDIA for a software engineer role and the technical screen went deep into GPU shader pipelines and graphics API internals. Not a casual conversation, they clearly wanted someone who had actually thought about this stuff from first principles.

Walk through the full shader compilation pipeline from HLSL or GLSL source code down to GPU-executable code, covering front-end parsing, intermediate representations, optimization passes, reflection metadata, and backend code generation.
Compare DirectX-style graphics APIs with Vulkan or OpenGL in terms of resource binding models, how commands get submitted to the GPU, and how pipeline state is managed.
How would you design a minimal shader compiler, specifically the front end and back end? What are the key components and decisions involved?

“This is where I spent the most time and also where I rambled the most.”

View Post

NVIDIA·Software Engineer·Onsite - System Design / Architecture

May 2026

NVIDIA system design interview for a software engineer role, focused almost entirely on CI/CD infrastructure for GPU workloads. One big sprawling question that kept branching into more sub-topics than I expected.

Design a Jenkins pipeline to build, deploy, and run GPU-dependent graphics tests across multiple hardware and driver configurations. Cover job orchestration, pipeline-as-code, parallelization, artifact management, test sharding, retry logic, flaky test quarantine, notifications, and promotion gates. Also explain how you'd handle driver updates and safe rollbacks.

“This was basically six questions bundled into one.”

View Post

NVIDIA·Software Engineer·Technical Phone Screen

Jun 2026

Interviewed for a solutions architect role at Nvidia and got hit with a graph/ordering problem that felt more like a backend engineering screen than anything SA-adjacent. Short interview, one meaty technical question, left feeling unsure if I'd framed my answer the right way.

Given a directed acyclic graph representing task dependencies, how would you determine the correct execution order?

“Topological sort, obviously, but I fumbled the explanation a bit.”

View Post

NVIDIA·Product Manager·Onsite - Product Sense / Strategy

Jun 2026

PM interview at Nvidia that was basically a single product sense question about ChatGPT. Pretty straightforward setup but the depth they expected caught me off guard a bit.

Why do you personally like ChatGPT, who are its users, what metrics would you use to measure its success, and how would you improve it?

“This is four questions stitched into one and I did not treat it that way at first.”

View Post