Two rounds: 1. research interview, where it is expected to give an overview of past & ongoing projects. During the process, many in-depth questions were raised. 2. coding interview, which is ML/DL relevant, not LeetCode style.
Otras evaluaciones sobre las entrevistas para el cargo de Research Intern en NVIDIA
I was given 2 rounds of interview with two team members, first being project deep dive, second being technical tailored to team needs, mostly about deep learning fundamentals, generative modeling, and machine learning infrastructure.
Acudí a una entrevista en NVIDIA (Santa Clara, CA)
Entrevista
Basically some team open discussion on research
The manager and team members directly talk with me on my research, related questions, potential projects
After that, 1 week later got offer
Preguntas de entrevista [1]
Pregunta 1
Seed-free attack discovery
How can we design a red-teaming agent that, given only a target model and a policy spec (no human seeds), can autonomously discover new classes of failures instead of just rediscovering known jailbreaks?
Objective for the red-teaming agent
What is the “right” objective for an automated red-teamer—maximize violation rate, diversity of failure modes, severity, or some coverage metric over a threat taxonomy—and how do we estimate these online under a fixed query budget?
Search algorithms under a strict budget
Can we use bandits / Bayesian optimization / tree search over prompt templates and mutations to maximize the number of distinct verified failures per 1,000 queries? How would we define and estimate “distinctness”?
Generalization across models and updates
How can we train or adapt a red-teaming agent that transfers across model families and model updates, rather than overfitting to one specific checkpoint?
Closed-loop verification
What is an effective architecture for the verify-loop (judge models, tools, simulators) so that the agent can autonomously filter false positives and refine attacks, without human in the loop?
