My 45-minute virtual screen started with a deep dive into the projects on my résumé, especially anything that involved low-level C++ or GPU work (e.g., a CHIP-8 emulator and a CUDA lab).

I was asked to explain design choices, debugging stories, and how I measured correctness and performance.

The second half was a code-reading exercise: the interviewer pasted a short C++ snippet with several constructor calls (default, value, copy) and a destructor, plus a deliberate memory-management oversight.

I had to walk through main, state which constructor or destructor fired at each line, point out the difference between copy construction and assignment, and note the leaked heap object and uninitialized member.

No live coding; it was all verbal reasoning.

Overall, the interview focused on my ability to reason about object lifetime, memory safety, and how my past projects line up with a compiler/GPU role.

They gave me a short C++ class and main function and asked, line-by-line, which constructor or destructor runs at each step and why. I also had to point out any memory-management issues (copy vs. assignment, leaks, uninitialized members).