RepostedNVIDIA logo

NVIDIA · OA

In process

NVIDIA Ignite SWE Intern OA Questions: 6 Experiences

Software engineer · InternshipOct 2025
Shared byjanebeingjane

NVIDIA Ignite SWE intern OA reports from fall 2025 describe two LeetCode-style coding questions and an operating-systems multiple-choice section to finish.

At a glance

  • Process: resume screen, then one online assessment. One candidate timed it at 90 minutes (03); two described two coding questions next to a multiple-choice section (01, 02).
  • Asked recently: operating systems in 5 of 6 reports, coding in 4 of 6. Specific topics named once each: process synchronization (03) and an anagram-themed coding task (01).
  • Difficulty: the coding read as LeetCode easy to medium (03) or "average" (01). The OS part was where three candidates lost points (02, 05, 06); one found it manageable after studying (04).

Coverage: NVIDIA Ignite software engineering internship, online assessment only. Six reports posted between October 25 and November 28, 2025. Two candidates said they were freshmen; one was in Gettysburg, Pennsylvania, and the rest gave no location.

What came up

Operating systems is the thread that runs through these reports. Even candidates who felt fine about the coding wrote mostly about the OS questions.

Topic Reports Last seen
Operating systems (multiple choice) 5 of 6 Nov 2025 (report date)
Coding questions 4 of 6 Nov 2025 (report date)
Process synchronization 1 of 6 Oct 2025
Anagram-themed coding 1 of 6 Nov 2025 (report date)

A candidate can appear in more than one row. No report named a specific coding problem, so there is no question table here.

6 candidate reports

01: Two average coding questions and an OS quiz

Report date: November 4, 2025 · Role: Software Engineer, Ignite · Result: No offer

  1. The process opened with a resume screen and then the online assessment.
  2. The OA had two coding questions, which the candidate called average in difficulty, plus multiple choice on basic operating systems.
  3. Their notes mentioned anagrams as a coding theme but did not say what the program had to compute.

02: A freshman who struggled on both halves

Report date: November 3, 2025, with a follow-up on November 4 · Level: Freshman · Result: Rejected

  1. After the rejection, the candidate said the multiple-choice section had gone badly.
  2. Asked about the two LeetCode-style coding questions, they said those had not gone well either.
  3. They did not name the coding tasks or the subjects of the multiple-choice questions.

03: A 90-minute OA with process synchronization

Interview date: October 2025 (day not given) · Report date: November 28, 2025 · Location: Gettysburg, Pennsylvania · Result: No offer

  1. The candidate applied online. The whole process took about two weeks.
  2. The OA ran 90 minutes. They put the programming questions at LeetCode easy to medium.
  3. They singled out operating systems, especially process synchronization: keeping processes that share a resource from stepping on each other.
  4. Their question list also mentioned behavioral questions, without saying which stage they came from.

04: OS felt manageable after focused study

Report date: October 27, 2025

  1. Before the test, this candidate watched videos and worked through practice questions on operating systems.
  2. They said the OS questions felt manageable as a result. They did not describe individual questions.

05: Coding went fine, a few OS answers did not

Report date: October 26, 2025

  1. This candidate said the coding part went well.
  2. They knew they had answered some OS questions wrong, so confidence on one half did not carry over to the other. No outcome was reported.

06: A freshman who prepared and still found OS hard

Report date: October 25, 2025 · Level: Freshman

  1. The candidate had prepared before taking the SWE OA but still found the OS questions difficult.
  2. They asked others how much that section might weigh on moving forward. They did not describe their coding or share a result.

Patterns across the reports

  1. The OS section decides how candidates feel. Three said it was the weak spot (02, 05, 06) and one said it was fine after study (04). Nobody described the coding as the main problem except 02, who struggled with both.
  2. Two coding questions. Both reports that counted the coding tasks said two (01, 02), and 03 described "questions" in the plural at LeetCode easy to medium.

Common questions

How long is the NVIDIA Ignite OA?

One report gave a length: 90 minutes (03). The others did not say.

What is on the NVIDIA Ignite SWE intern OA?

Two coding questions and a multiple-choice section on operating systems (01, 02). Process synchronization was the one OS topic named (03).

How hard is the NVIDIA Ignite OA coding?

Candidates called it LeetCode easy to medium (03) or average (01). The OS multiple choice caused more trouble than the coding for 02, 05 and 06.

What happens after the NVIDIA Ignite OA?

Three of the six reported a result, and all three were rejections (01, 02, 03). For 03, the whole process took about two weeks.

Keep practicing

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

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