← Back to Directory

NVIDIA interview notes, page 17 of 17

FAANG / Big Tech

Most of these NVIDIA write-ups come from Software Engineers (137), then Product Managers (15) and Data Scientists (10). The most reported rounds are the technical phone screen (106), the system design round (28), the hiring manager screen (13) and the product sense round (13).

166 interview notes · updated Aug 2026

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·Data Scientist·Onsite - Behavioral / Leadership

Jul 2026
Behavioral round at NVIDIA for a Data Scientist role. Two heavy questions, both requiring pretty detailed storytelling with numbers and postmortems. Felt more like a leadership interview than a data science one, which threw me off a bit.
  • Tell me about a professional conflict you had with a cross-functional partner. What was the exact disagreement, how did you de-escalate it, what framework guided your decision, and what was the measurable outcome?
  • Describe a project you owned that failed. What early warning signs did you miss, how did you run the postmortem, what guardrails did you put in place afterward, and how would you catch a similar failure sooner next time?

“The part that tripped me up was 'precise point of disagreement.' I had a story ready but it was fuzzy on the actual crux, more like a general tension than a specific call.”

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 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·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·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