1p3a Experience · May 2026

nvidia software engineer tech phone screen interview experience

SWE Phone Screen newgrad
1 upvote 1 reply

Interview Experience

非常简单的题。总共两题,每题两问。 第一题: 一堆机器人compete,最高分数的两个先compete,然后分数抵消,大的留存下来。问最后剩下的那个机器人的分数是多少。第二问加了一些限制条件。用priority queue做就可以了 第二题: 基础DP,其实就是斐波那契数列的变种。要求时间空间最优O(N),O(1),然后第二问在状态转移的时候加入了限制条件,需要改状态转移的方程。 然后聊了一下agent RAG system怎么设计,怎么优化等等。 interviewer是一个印度的junior sde。感觉挺不耐烦的。全程HR都没有出现。一周之后收到了模板拒信。可能题没有一次bug free,我debug了一两次才全部通过?现在要求这么高了吗? 求大米!

Full Details

🔒

Unlock all NVIDIA questions

Full insider details, leaked discussions, and candidate experiences.

Get full access — from $50/mo

About NVIDIA Interview Reports

This question was reported by a candidate who interviewed at NVIDIA. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.

Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at NVIDIA are the higher-signal extractions to take from this report.

For broader preparation context, the NVIDIA interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.

How To Practice This Type of Question

Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.

Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in NVIDIA reports consistently are the ones worth investing in; one-off niche problems are not.

During Your NVIDIA Round

Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.

The single most predictive failure mode in NVIDIA reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.