J'ai postulé via la recommandation d'un employé. J'ai passé un entretien chez NVIDIA en août 2012
Entretien
My resume was submitted to HR by a former colleague who works there. I was contacted the next week about several opportunities in several different groups. Initially I was set up to have a phone interview but that was changed to an in-person interview at the Santa Clara site. The interview was with an engineering group manager and we spent close to an hour going over details in my resume. Overall, it was a very pleasant experience. There was a follow-up phone interview with a different engineering manager. This one was pretty similar to the first one (mostly focusing on details in my resume and my past experience). I was contacted after this interview to schedule an on-site technical interview, which was supposed to last approximately 45 minutes. I ended up not going in for the last interview... because I accepted an offer at a different company.
Questions d'entretien [1]
Question 1
There weren't any questions that were difficult or unexpected... Mainly the questions focused on my previous experience and points listed on my resume.
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.