NVIDIA Software Engineer interview questions

137 Software Engineers have shared notes from their NVIDIA interviews, with the questions they were asked in each round. That is 83% of the 166 NVIDIA interview notes on Screna AI.

137 Software Engineer interview notes

NVIDIA·Software Engineer·Hiring Manager Screen

Jul 2026
Applied for an embedded firmware role at Nvidia and got a surprise email from a hiring manager asking for a quick call. The call lasted maybe a minute, two questions, then he said good luck and hung up. Still not sure what to make of it.
  • What are you looking for in your next role?
  • Are you comfortable commuting to the office three times a week?

“Said embedded firmware, which felt obvious given what I applied for.”

View Post

NVIDIA·Software Engineer·Technical Phone Screen

Jul 2026
NVIDIA graphics/compute engineering interview that went deep into the math behind rendering pipelines. The question was essentially a written proof with a numeric example tacked on, which I was not fully expecting from a software engineering screen.
  • Walk through the full model-view-projection pipeline using homogeneous coordinates. Derive how a 3D world-space point ends up in normalized device coordinates and then screen space, and explain why normals require the inverse-transpose of the model matrix rather than the model matrix itself. Include a concrete numeric example.

“This wrecked me a little.”

View Post

NVIDIA·Software Engineer·Technical Phone Screen

Jul 2026
NVIDIA software engineer interview with a NumPy coding problem that looked straightforward on the surface but had a specific constraint that tripped me up a bit.
  • Implement a 2D convolution on a 4x4 input with a 3x3 filter at stride 1 using NumPy, but without writing any explicit Python loops. Return the resulting 2x2 output.

“The no-loops constraint is what makes this non-trivial.”

View Post

NVIDIA·Software Engineer·Hiring Manager Screen

Jul 2026
NVIDIA software engineer interview that focused heavily on self-presentation: walking through your current role, a resume project, and wrapping up with questions for them. Felt more like a structured conversation than a technical grilling, which I wasn't fully expecting.
  • What do you do outside of work to support your professional growth?
  • Walk me through your current role and one project from your resume in depth: the goals, your specific contributions, key technical decisions, impact metrics, and what you would have done differently.
  • Close the interview by asking two thoughtful questions about the product and team that show genuine interest.

“Fumbled this a bit.”

View Post

NVIDIA·Software Engineer·Technical Phone Screen

Jul 2026
NVIDIA technical screen for a software engineering role focused almost entirely on Python test infrastructure for graphics validation. Dense interview, lots of ground covered, felt more like a system design session than a coding round.
  • How would you design a Python test harness for graphics validation? Walk through your approach to fixtures, parametrization, and dependency injection.
  • Compare unittest and pytest for a large-scale graphics testing project. What are the real tradeoffs?
  • How would you implement logging, retries, and resource cleanup in a test harness running across multiple GPUs?
  • How would you use generators and context managers in a test orchestration system?
  • How would you use asyncio or multiprocessing to run tests across multiple GPUs while avoiding GIL bottlenecks?
  • Where would you apply type hints in a test harness codebase and what value do they actually provide?

“This was the core question and it ate up most of the interview.”

View Post

NVIDIA·Software Engineer·Onsite - Product Sense / Strategy

Jul 2026
NVIDIA software engineer interview that revolved around a single product strategy question about competitive benchmarking. Pretty niche topic but it makes sense given how much NVIDIA cares about its public image versus AMD.
  • Should the company publicly benchmark its software against a competitor's in blog posts, and if so, what conditions would need to be in place before doing that, and how do you handle the ethical side of presenting those results?

“This one had more layers than I expected.”

View Post

NVIDIA·Software Engineer·Technical Phone Screen

Jul 2026
Technical screen for a Research Engineer role at NVIDIA. One meaty ML fundamentals question that sounds straightforward until you're actually on the spot trying to remember the exact decomposition formula.
  • Explain the bias-variance trade-off precisely, including how bias and variance each factor into the expected prediction error decomposition, and how model complexity, training set size, and regularization each shift the balance.

“I knew the general story but fumbled the exact decomposition.”

View Post

NVIDIA·Software Engineer·Technical Phone Screen

Jul 2026
NVIDIA software engineer interview with a algorithms-focused coding round. The problem was straightforward on the surface but pushed you to think about efficiency at scale, which is pretty typical for NVIDIA from what I've heard.
  • Given an integer n, return the n-th prime number. Your solution should be efficient enough to handle moderately large inputs (think up to around 100,000).

“My first instinct was trial division and I started coding it up before they even finished explaining.”

View Post

NVIDIA·Software Engineer·Onsite - Multi Round

Jul 2026
NVIDIA software engineer loop that throws everything at you in one sitting: resume walkthrough, behavioral stuff, system design, a domain deep dive, and a coding problem. The context switching is real and the time pressure makes it hard to go deep on any single piece.
  • Walk me through your resume and the projects you've worked on.
  • Tell me about a time you had to navigate a difficult situation on a team or project.
  • Design a distributed system for a large-scale use case relevant to NVIDIA's infrastructure.
  • Deep dive into a domain-specific technical area related to the role, such as GPU architecture, parallel computing, or hardware-software interaction.
  • Solve a coding problem on the spot, likely involving algorithms or data structures.

“I rambled a bit on the first project and ate up too much time before they steered me elsewhere.”

View Post

NVIDIA·Software Engineer·Technical Phone Screen

Jul 2026
NVIDIA software engineer round focused on a practical API integration task. Nothing algorithmic, just real-world HTTP client work with error handling and clean code. Felt more like a take-home than a live coding session in terms of what they were actually testing.
  • Write code to make an HTTP GET request to a public API endpoint, parse the JSON response, and perform some post-processing on the result like filtering or aggregating the data.
  • How would you handle errors in this HTTP client code, specifically network failures, non-2xx responses, and malformed JSON?
  • How would you structure this code so the result-processing logic is easy to test independently of the HTTP request?

“The post-processing part is where I think I lost points.”

View Post