J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez NVIDIA (Santa Clara, CA) en janv. 2011
Entretien
Got a response within a week after applying online. Was then set up a phone interview, Phone interview was done by a very senior person (with 30+ years in industry), the guy was very cool. He asked mostly from my resume and a few C questions. After that got an onsite interview setup within a week. Had 4 1-1 interviews, 2 in the morning were easy was asked mainly simple c q's and about projects. afternoon interviews were tough , questions like traverse a binary tree without recursion and algorithms.
Questions d'entretien [2]
Question 1
questions related to RTOS, was asked to write a solution for producer-consumer problem.
bit manipulation questions like, write a macro to check if nth bit was set , write a function to count no of 1's in a variable and what was the complexity of the implementation etc .
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
Questions d'entretien [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.
Questions d'entretien [1]
Question 1
Asked me to explain about a project I did in university.
J'ai passé un entretien chez NVIDIA (San Jose, CA)
Entretien
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.