Le processus a pris 2 semaines. J'ai passé un entretien chez NVIDIA (San Jose, CA) en sept. 2009
Entretien
I was contacted by Nvidia's recruiter. They first scheduled a one-on-one interview, followed by two phone interviews [second gentlemen was calling out of Germany ]. The phone interviews were straightforward with one or two "trick" questions. The one-on-one interview was also straightforward but the gentelmen who I was talking with appeared to be very cocky and somewhat rude. At the end of the interview he went on to comment on my coding skills, which he described as OK for someone with my experience. This is considering that I solved his problem correctly and was invited to do two more phone interviews.
Questions d'entretien [2]
Question 1
Write and aligned malloc() that gets memory size needed and an alignment mask as its arguements. Write a free() function to go with the aligned malloc that takes only the pointer to the allocated chunk of memory.
Write a macro to which you can pass a name of a structure and a name of one of its fields and get a relative offset of this field within the structure.
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.
Meilleures entreprises pour « Rémunération et avantages » près de chez vous
