Me postulé a través de una facultad o universidad. El proceso tomó 4 semanas. Acudí a una entrevista en NVIDIA (Santa Clara, CA)
Entrevista
3 Phone interviews, first 2 were technical interviews with various members of the team, third interview ended up being more HR oriented with minimal technical questions. The offer came in after the third interview.
Doing the interviews on the phone was a little akward, especially when I had to write a C++ implementation of breadth first search and read my solution line by line. There was also an instance where my interviewer missed my second interview and we had to reschedule. All in all though, these things happen, and I felt the interviews were effective at testing my knowledge and they were pretty prompt about getting back to me.
Preguntas de entrevista [1]
Pregunta 1
I wouldn't say there was a most difficult question. There were numerous data structure/algorithm questions involving linked lists, hash tables, and operations on binary representations of algorithms. There were also questions about operating systems. I remember virtual memory and paging came up more than once.
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.