Me postulé a través de una facultad o universidad. El proceso tomó 3 semanas. Acudí a una entrevista en NVIDIA
Entrevista
Took a quiz at college career fair, then had three phone interviews. There were some questions about operating systems I did not know how to answer, as I'm early on in undergraduate, but mainly data structures and sorting algorithms. Talked a lot about kernel debugging, which I had never done. Ultimately I think I simply was not far enough in classes to possess the knowledge and they seemed to need. Prepare very very well, no topic is off limits.
Preguntas de entrevista [4]
Pregunta 1
How to access the nth item in a linked list with less than 2m time worst case
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
Preguntas de entrevista [1]
Pregunta 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.
Preguntas de entrevista [1]
Pregunta 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.
Las mejores empresas en cuanto a "Remuneración y prestaciones" cerca de ti
