I applied through college or university. I interviewed at NVIDIA
Interview
I got 2 technical interviews.
First phone interview, they asked some language specific questions with C++. I didn't do well on those questions since the last time I worked with C++ was like 3 years ago. After I told them I'm more familiar with C#, they tried to find the similarities between C# and C++ to make it easier for me.
Second phone interview with the team lead. Was told that they care more about my learning skills and my programming background than my knowledge on some specific programming language. I was asked some questions related to OS, computer architecture, and a few questions about bit manipulation. There were also questions about myself (why I applied for this job - since it does not really match my skillset.....), discuss my shortcomings etc.
Interviewers were nice and didn't make me feel too bad even if I couldn't answer half of the questions. The hiring team replied to my email promptly. Overall good experience.
Interview questions [3]
Question 1
C++ specific questions such as constructor, destructor, virtual functions, variable scope, global variables.
A non technical phone interview with hiring manager
One onsite technical interview with hiring manager which included 2 technical questions.
One online technical interview took 2 hours with hiring team lead which included 3 technical questions
Interview questions [1]
Question 1
One logical question and one leetcode style quesiton
Had a technical interview of 2 hours where they told me a little bit about the job, asked me to introduce myself, asked me about a project I did, and then there was a coding question.
Interview questions [1]
Question 1
Asked me to explain about a project I did in university.
A typical software engineering coding interview focuses on problem-solving under time pressure. Candidates are usually given one or more algorithmic problems similar to those found on LeetCode. The interviewer evaluates data structures, algorithm selection, code correctness, time and space complexity analysis, communication clarity, edge-case handling, and debugging ability. Interviews often begin with clarifying questions, followed by writing executable or near-executable code on a shared editor or whiteboard. Strong candidates explain trade-offs, optimize incrementally, test thoughtfully, and remain calm while reasoning through unfamiliar problems.
