NVIDIA DevOps, QA and Infra Intern Interviews: 12 Experiences

Shared by janebeingjane ·
Company
NVIDIA
Reports
12 interview reports
Level
Internship
Stages
OA → Onsite

NVIDIA infrastructure-side intern loops (DevOps, QA tools, cloud, AI infrastructure) in 2024–2026 vary by team, from one system design round to DSA.

At a glance

  • Process: each team runs its own loop. QA tools and tools-development loops opened with a HackerRank test (03, 04, 05, 12); infrastructure loops went straight to interviews, from one 45-minute round (01) to three one-hour interviews in a day (06).
  • Asked recently: general DSA in 6 of 12 (arrays, strings, binary search, bit tricks, BSTs), infrastructure concepts such as Docker, Kubernetes, CI/CD, Linux and Git (02, 05), and one DevOps system design round (01).
  • Difficulty: candidate 07 had one much harder question than the other; 10 was out after two string questions in an hour; 11's 90-minute first round went deep on systems.
  • Practise first: Find the Missing Number from 1 to 100, Delete a Node from a Binary Search Tree and Implement memmove.

Coverage: Internship only. DevOps intern, QA tools / test automation intern, cloud software & infrastructure intern, AI / deep-learning / autonomous-vehicle infrastructure intern, and software tools development intern. California, New York, Tel Aviv, India and China, plus reports with no location. Interviews from late 2024 to November 2026.

Each team at NVIDIA runs its own loop, so this article keeps the roles apart. Every section below has its own topics, questions and candidate timelines.

Role Reports Newest report
DevOps intern 2 Nov 2026
QA tools and test automation intern 3 Nov 2026
Cloud software and infrastructure intern 2 Sep 2026
AI, deep-learning and AV infrastructure intern 4 Feb 2026
Software tools development intern 1 Dec 2024

DevOps intern

Coverage: 2 reports. DevOps Intern (location not given, Nov 2026) and DevOps Engineer Intern (Tel Aviv, spring 2026).

What came up

The two DevOps loops looked nothing alike. One was a system design round. The other mixed short LeetCode-style questions with a quick-fire quiz on DevOps tools.

Topic Reports Last seen
System design 1 of 2 Nov 2026 (report date)
Coding (array / math) 1 of 2 May 2026
Docker, Kubernetes, CI/CD, Terraform, cloud basics 1 of 2 May 2026

Questions we found

Algorithms / Data Structures

Question Reports Last seen
Find the Missing Number from 1 to 100 1: 02 May 2026

2 detailed candidate timelines

01: A 45-minute round that turned into system design

Report date: Nov 5, 2026 · Role: DevOps Intern · Result: Not shared yet

Interview (scheduled for 45 minutes)

  1. The candidate was asked a system design question, then a run of follow-ups on it. They didn't say what the system was.
  2. They had been told that the format depends on the hiring manager, so the next candidate might not see the same thing.

02: Quick LeetCode questions plus a DevOps quiz

Interview date: Spring 2026 · Role: DevOps Engineer Intern · Location: Tel Aviv · Result: No offer

The candidate applied in person, and the whole process took a little over a week.

Interview

  1. Two or three LeetCode-style questions. One of them: an array holds the numbers 1 to 100 with one value missing, so find the missing value (practice it here).
  2. Rapid-fire questions on DevOps tools: Docker, Kubernetes, CI/CD, Terraform, automation and cloud services.

QA tools and test automation intern

Coverage: 3 reports. QA test dev intern (India, fall 2026), Software QA Automation Intern (Tel Aviv, spring 2026), QA Tools / Automation Engineer Intern (India, late 2024).

What came up

All three started with an online assessment. After that came a technical round, and two of the three added a projects, HR or manager round at the end.

Topic Reports Last seen
Online assessment first 3 of 3 Nov 2026 (report date)
Resume and project discussion 2 of 3 Nov 2026 (report date)
OS, Linux and scripting basics 2 of 3 Spring 2026
AI concepts (RAG, vector databases) 1 of 3 Late 2024

The 2024 report is the only one that shared actual questions.

Questions we found

Concept questions

Question Reports Last seen
What is RAG? What is a vector database and how do you use it? 1: 05 Late 2024
What is classification? How does ChatGPT tell "apple" from "Apple"? 1: 05 Late 2024
Linux: how do you add a user, what is a Bash script, what does chmod do, how do you set permissions? 1: 05 Late 2024
What is Git and how have you used it? 1: 05 Late 2024

Online assessments (OA)

HackerRank first, every time

Reports: timelines 03, 04 and 05

  1. The Tel Aviv candidate's HackerRank test covered Python, logic and problem solving.
  2. The 2024 India candidate's test had about 40 questions across aptitude, operating systems, general AI, data structures, software testing, SQL and machine learning.
  3. The fall 2026 India candidate didn't describe the test, only that it came first.

3 detailed candidate timelines

03: Selected about a week after the last round

Report date: Nov 1, 2026 · Role: QA test dev intern · Location: India · Result: Selected

Online assessment — details not shared.

Technical round — details not shared.

Projects + HR round

  1. A walk through the candidate's projects, plus HR questions.

The selection news came about a week after the final round.


04: Python test, then a coding and OS round

Interview date: Spring 2026 · Role: Software QA Automation Intern · Location: Tel Aviv · Result: Accepted offer

The candidate applied online. The process took three weeks.

HackerRank assessment

  1. Python, logic and problem-solving questions.

Technical interview

  1. Coding, OS concepts and reasoning questions.
  2. A conversation about QA automation and development practices.

05: Linux, Git and a few AI questions

Interview date: Late 2024 · Role: QA Tools / Automation Engineer Intern · Location: India · Result: No offer

HackerRank assessment

  1. About 40 questions: aptitude, operating systems, general AI, data structures, software testing, SQL and machine learning.

Technical interview (Microsoft Teams)

  1. What project are you working on now?
  2. What is RAG? What is a vector database, and how would you use one?
  3. What is classification? How does ChatGPT tell "apple" the fruit from "Apple" the company?
  4. Which OS do you use, and have you worked with Linux?
  5. How do you add a user? What is a Bash script? What does chmod do, and how do you set user permissions?
  6. What is Git, and how have you used it in your projects?

Managerial interview

  1. Leadership, teamwork and fit with the team's goals.

Cloud software and infrastructure intern

Coverage: 2 reports. System Software Engineering Intern on a cloud software and infrastructure team (California, Summer 2027 cycle) and Cloud Software intern (New York, early 2025).

What came up

One loop was three hour-long interviews in a single day with no OA. The other was a single coding round with two short DSA problems.

Topic Reports Last seen
Several interviews with the team on one day 1 of 2 Sep 2026
Coding: binary search, bit manipulation 1 of 2 Feb 2025

2 detailed candidate timelines

06: Three one-hour interviews on the same day

Interview date: Sep 29, 2026 · Role: System Software Engineering Intern, Summer 2027 · Team: Cloud software and infrastructure · Location: California · Result: No decision three weeks later

  1. No OA. A recruiter reached out directly.
  2. Three one-hour interviews back to back on one day, all with the team, one of them with the hiring manager. The candidate noted this was more rounds than they had seen for other internships.
  3. Three weeks later there was still no decision. The recruiter said the team hadn't decided yet.

07: Two DSA questions, one much harder than the other

Interview date: Feb 2025 · Role: Cloud Software intern · Location: New York · Result: No offer

Coding interview

  1. A binary search problem. The candidate solved it.
  2. A bit-manipulation problem. This one was tough, and the candidate felt the interviewer wasn't very supportive.

AI, deep-learning and AV infrastructure intern

Coverage: 4 reports. AI Infrastructure Engineer Intern (Summer 2026), an internship on the AV (autonomous vehicle) Infrastructure team (fall 2025), Infrastructure Software Engineering Intern, Deep Learning (Jan 2025), and an AI infrastructure spring intern in China (Dec 2024).

What came up

Coding showed up in three of the four reports. The China loop went furthest into systems: OS internals, TCP and a hand-written memmove.

Topic Reports Last seen
Coding round 3 of 4 Feb 2026 (report date)
String problems 1 of 4 Jan 2025
Project deep dive 1 of 4 Dec 2024
OS and networking concepts 1 of 4 Dec 2024
Trees (BST) 1 of 4 Dec 2024
Memory copying (memmove) 1 of 4 Dec 2024

The AV Infrastructure report covers timing only.

Questions we found

Algorithms / Data Structures

Question Reports Last seen
String reversal with extra conditions (two questions, exact prompts withheld) 1: 10 Jan 2025
Delete a Node from a Binary Search Tree 1: 11 Dec 2024 (report date)
Implement memmove 1: 11 Dec 2024 (report date)

Concept questions

Question Reports Last seen
How do system calls work, and why does copy_from_user exist? 1: 11 Dec 2024 (report date)
TCP half-open connections; does a SYN use up a sequence number? 1: 11 Dec 2024 (report date)

4 detailed candidate timelines

08: Python on HackerRank

Report date: Feb 15, 2026 · Role: AI Infrastructure Engineer Intern (Summer 2026) · Result: Not shared

  1. The coding interview ran on HackerRank. The candidate used Python and said you could pick your own language.

09: AV Infrastructure, on to a second round

Interview date: Mid-November 2025 · Role: Internship, AV Infrastructure team · Result: Invited to schedule a likely second round

  1. One interview. The candidate didn't share its content.
  2. A few days later, an email asked for their availability for what looked like a second round. The recruiter said the number of rounds depends on the team.

10: Two string questions in an hour, out after round one

Interview date: Early January 2025 · Role: Infrastructure Software Engineering Intern, Deep Learning · Result: Rejected after round 1

Round 1 (60 minutes)

  1. Two DSA questions, one easy and one medium. Both were about reversing strings, with extra conditions added. The candidate chose not to share the exact prompts.
  2. The added conditions are what made the second question feel like a medium.
  3. No system design came up.

11: A 90-minute first round that went deep on systems

Report date: Dec 13, 2024 · Role: AI infrastructure spring intern · Location: China · Result: Not shared

The round was booked for about an hour and ran close to ninety minutes.

Round 1

  1. When could they start, and for how long?
  2. A short self-introduction, with no project details yet.
  3. Over 40 minutes on the candidate's internship project. The interviewer asked them to justify each design choice.
  4. How do system calls work? Why does copy_from_user exist? Which OS books have you read?
  5. TCP: what is a half-open connection, and does a SYN use up a sequence number?
  6. Coding: delete a node from a binary search tree. The candidate had forgotten the exact steps.
  7. While they coded, the interviewer asked about grades, competitions and other offers.
  8. Coding: implement memmove. The interviewer pushed on overlapping memory: when the source and destination overlap, which way do you copy, front to back or back to front? The candidate needed several hints.
  9. A last question about converting a five-point GPA to a percentage.

Software tools development intern

Coverage: 1 report. Software Tools Development Intern, late 2024.

One report: a three-stage loop with coding in every stage, plus web-stack and OS questions.

1 detailed candidate timeline

12: Coding in all three stages

Report date: Dec 2024 · Role: Software Tools Development Intern · Result: Offer; the candidate later did a tools and automation internship

Online assessment

  1. Multiple-choice questions on operating systems, databases and computer networks, plus aptitude.
  2. Two easy-to-medium coding problems.

Technical interview (virtual)

  1. Resume projects: how they were built, what went wrong, and how the candidate fixed it.
  2. React, Node.js and JavaScript, including performance tuning.
  3. OS: process management and memory allocation.
  4. Two easy-to-medium coding problems. The candidate talked through the reasoning while coding.

Managerial + HR round (virtual)

  1. How the projects would work in the real world, and the skills listed on the resume.
  2. General AI questions.
  3. Scenario questions about decisions, teamwork and communication.
  4. One more coding problem.

Patterns across the reports

  1. The QA and tools loops opened with an online assessment; the infrastructure loops didn't mention one. All three QA tools and automation reports (03, 04, 05) and the tools development report (12) started with an OA, on HackerRank where the platform was named (04, 05). None of the cloud, DevOps or AI infrastructure reports described an OA, and the cloud & infrastructure candidate (06) said there wasn't one.

  2. Coding rounds used general data-structure problems. Six reports had coding (02, 07, 08, 10, 11, 12). Where the topic was shared, it was an array, string, binary search, bit-manipulation or BST problem; 11 added a low-level memmove. Infrastructure knowledge came up as separate concept questions instead (02, 05, 11).

  3. Linux and tooling basics came up across roles. Reports 02 and 05 both asked about everyday infrastructure tools: Docker, Kubernetes, CI/CD and Terraform in one, and Linux users, chmod, Bash and Git in the other.

  4. The format depends on the team. Candidates in 01 and 09 were told outright that structure depends on the manager or team. Their loops ranged from one 45-minute system design round (01) to three hours in one day (06).

Common questions

Does the NVIDIA infrastructure intern interview have an online assessment?

The QA tools and tools-development loops did, on HackerRank where named (03, 04, 05, 12). None of the DevOps, cloud or AI-infrastructure reports mentioned one.

What does the NVIDIA DevOps intern interview ask?

It depends on the manager: one candidate had a single system design round (01), and the other a few LeetCode-style questions plus a quiz on Docker, Kubernetes, CI/CD and Terraform (02).

Keep practicing

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.

Comments

0

No comments yet — be the first to share what you know.