real interview stories, told over a cup of tea ♡
NVIDIA Interview Experiences
3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.
- 3935
- Experiences
- 857
- Companies
- 532
- Offers
23 results
- GPU Hash Partition Phone Screen in C++, Two Weeks to the Next RoundNVIDIA · Software Engineer · Senior+ · Technical Screen · Oct 2026In progress
I asked a friend to refer me to a lot of NVIDIA positions. This was the first one to respond, and I really felt how slow the process is. After the phone screen it took two weeks just to schedule the next interview. The interviewer was a bit of a nerd. The topic was GPU partitioning, in C++. Given an array and P partitions, do a hash partition, and the output has to return the offsets. It is the c…
- Three Onsite Rounds, Rejected Three Days LaterNVIDIA · Software Engineer · Onsite · Oct 2026Rejected
After I passed the one phone screen round, they told me to go straight to the onsite. There were only three rounds in total, which made me realize I wasn't going to be that lucky, and sure enough, three days after the interview I was told I was rejected. The first round was straight to a director: BQ plus a deep dive. He felt like a smiling tiger, rambling about this and that, and then suddenly s…
- Three System Design Rounds and a Director RoundNVIDIA · Software Engineer · Onsite · Oct 2026In progress
I interviewed last Friday. There were four rounds, and in the first three the interviewers were all senior SDEs, with one system design question per round: A task scheduler Implement a version-controlled download service. For example, if you want to download python2.7 and you find that your machine is missing a few of its dependency packages, you have to download those as well. I thought about th…
- Verification Role, Offer After Eight WeeksNVIDIA · Software Engineer · New Grad · Onsite · Sep 2026Offer
The interview mostly revolved around FIFO, round-robin arbiter, valid/ready handshake, scoreboard/reference model, constraints, SVA and functional coverage. They give you a small design/spec and have you discuss it from the angle of verification architecture, corner cases, assertions and coverage. They also ask brain teasers, and there are a lot of them online. The coding/RTL part is mainly basic…
- GPU Search Engine Team Phone Screen on Counting Distinct StringsNVIDIA · Software Engineer · Technical Screen · Jul 2026
This is for a team at Nvidia that is turning an open-source search engine into a GPU implementation. I personally have no hardware or GPU experience at all. They replied the day after I applied and said they wanted a phone screen, and I found out early on, after looking into the background of the interviewer, that the interviewer was a hardware engineer. I assumed they cared about my search engin…
- NVIDIA Embedded Engineer interview: bit manipulation and register operationsNVIDIA · Embedded Engineer · Technical Screen · Jul 2026
I interviewed at the Yokneam site with a team leader and another employee. They began by explaining the company and role, then asked me to introduce myself and walk through a university project. I needed to explain in real detail how it was implemented and why I had made particular design choices. The technical section then became very hardware and low level. I got a bit-manipulation question, fo…
- NVIDIA Embedded Engineer interview: firmware protocol system designNVIDIA · Embedded Engineer · Jul 2026
My process started with an OA that immediately felt demanding. It covered LeetCode-style questions from easy through medium, plus C++ data-structure properties. After the OA, I had a technical interview with a team member. The difficult part was a firmware system-design-style problem framed around a firmware protocol, with computer-networking concepts as well. The scope felt broad, not purely alg…
- NVIDIA Embedded Engineer interview: two-hour C coding screenNVIDIA · Embedded Engineer · HR Screen · Jul 2026
HR called to coordinate a time, then I joined a two-hour technical interview. I did not make it past that first interview, which was disappointing, although the format was straightforward. They began by talking about the role and company, then asked for a self-introduction. I discussed a project I had worked on and answered several questions about it before the conversation shifted to coding. The…
- NVIDIA QA Engineer interview: HackerRank and pending onsiteNVIDIA · QA Engineer · Online Assessment · Jul 2026In progress
I applied for a QA Automation Student position and began with an online HackerRank assessment. It included Python programming and technical questions. After I completed the assessment, a recruiter contacted me and invited me to continue with an onsite technical interview. When I last checked, the process was still ongoing, so I did not have a final result. What stood out was how quickly the recru…
- NVIDIA QA Engineer interview: project walkthrough, DSA, and a long timelineNVIDIA · QA Engineer · HR Screen · Jul 2026In progress
After an initial recruiter step, I moved toward an on-site technical interview. First came a difficult DSA-focused round. Then, in a virtual interview, I had to explain a project line by line from a random starting point and also solve DSA-style problems. I later had an HR conversation. The process seemed designed to pressure-test my understanding from what I had written through coding. By the on…
- NVIDIA QA Engineer interview: unique-word Python scriptNVIDIA · QA Engineer · Technical Screen · Jul 2026
I received a concrete Python task: write a script that took an input string containing duplicate words, kept only the unique words, and returned one space-separated string sorted in descending order. The question was narrowly scoped, so I could focus on correctness and the details. It made the evaluation straightforward. Rather than asking me to discuss several concepts at once, the interview che…
- NVIDIA Software Engineer Interview Experience: A two-month process with a home exam and C/C++ day interviewNVIDIA · Software Engineer · Take-home Project · Jul 2026Rejected
My process lasted roughly two months, with a lot of waiting between steps. I did not make it through, but I could see the overall shape of how they evaluated me. The sequence was simple: a home exam, a day interview, and then a manager interview. The home exam and day interview were the technical evaluation. The day interview included a C/C++ question, and the difficulty ranged from difficult to…
- NVIDIA Software Engineer interview with a 45-minute resume discussion and coin riddleNVIDIA · Software Engineer · Jul 2026
I started with a short, focused first round that spent about 45 minutes on the details in my resume. The expectation was that I could explain my background confidently before the technical deep dive. Then the conversation shifted to core computer-science topics, and I had to use a whiteboard to show my reasoning. I got a practical DSA question and a brainteaser-style riddle. The riddle was easy t…
- NVIDIA Software Engineer interview: practical problems and delayed rejectionNVIDIA · Software Engineer · Online Assessment · Jul 2026Rejected
After an online assessment, I had interactive technical interviews where I was expected to explain my approach, not only reach an answer. One session began with a review of my resume projects and a couple of behavioral questions, then moved to a problem that felt like a realistic day-to-day task for the role. The interviewers were generally straightforward, and I appreciated their focus on fit ra…
- NVIDIA Solutions Architect interview: EVPN shifted to DevOpsNVIDIA · Solutions Architect · Technical Screen · Jul 2026
The NVIDIA interview opened with EVPN questions, which I answered confidently. It then shifted almost entirely to DevOps, a direction I did not expect for a Solutions Architect position. Nothing in the rest of the conversation connected to my AI or HPC background. By the end of the call, I felt that much of the questioning did not match the advertised role. I did not receive an offer. My main tak…
- NVIDIA QA Engineer Interview Experience: Python, systems, and VP troubleshootingNVIDIA · QA Engineer · HR Screen · Jun 2026
The process started with an HR interview, then moved into a technical conversation on Python, Linux, networking, QA methodology, and systems knowledge. It felt like they were assessing how my experience would translate to QA work on a real platform, rather than whether I knew the right buzzwords. The last stage was a more demanding VP interview. We discussed previous projects, troubleshooting sce…
- Two Unstructured Screens and No Follow-upNVIDIA · Software Engineer · Technical Screen · Jun 2026No response
NVIDIA's interview process came with very little background information from the recruiter. I did not know how many rounds there would be or what each round would cover. They use Workday. I received an email saying they had selected me from the general applicant pool and asking me to fill in my availability online, but it still did not explain what the interview would cover. After the first round…
- Phone Screen on a High-Performance String ClassNVIDIA · Software Engineer · Technical Screen · Dec 2025
NV phone screen I was asked to implement a high-performance class to handle large strings, with functions like cmp, cat, substr, and so on. I created a simple class that uses a char array to store short strings. First I was asked to write the constructor: Q: For strncpy(buf, s, len), characters get copied one at a time — how can this be sped up? A: Use memcpy. Q: Is that the same as strncpy? A: ?…
- Two Phone Screens, a Six-Round Virtual Onsite, and an OfferNVIDIA · Data Scientist · Onsite · Oct 2025Offer
I want to talk about the mindset and the whole prep process for this interview. If you're not interested, feel free to skip straight to the write-up below. The most important thing: be humble and ask others for help (don't be shy about it — if you want to learn from people, you have to spend time building relationships. It's not about getting someone to hand you all the answers, it's about genuin…
- Two Screens, a Six-Round Virtual Onsite, and an Unofficial Offer the Same DayNVIDIA · Data Scientist · Onsite · Oct 2025Offer
My girlfriend has a friend who works at NVIDIA, and they referred me. About two weeks later I got my first round video interview. I want to talk about the mindset and the prep process for the whole interview loop — if that doesn't interest you, feel free to skip straight to the interview notes below. The most important thing: humble yourself and ask others for help (don't be shy about it — if you…
- First Onsite Round Covers ML Frameworks, Compilers, and Product SenseNVIDIA · Technical Marketing Engineer, AI Software · Onsite · Sep 2025
Onsite interview 1/4. The first interviewer was 45 minutes, first asked about my resume, then an AI technical interview, since the role is technical marketing for AI Software. The interview was split into three parts. Part 1: Deep Learning Fundamentals Q1: In Machine Learning, what are the high-level trends happening at the framework level? I answered with the evolution from numpy to PyTorch to J…
- One Round, Four Parts: Resume, ML Trivia, and Live NumPy CodingNVIDIA · Technical Marketing Engineer · Technical Screen · Sep 2025
Technical Marketing Engineer - NVIDIA AI. NVIDIA has five rounds total, two with coding and three without coding. My interviewer was a data scientist. She asked me how many coding rounds I'd already had, and I said only one, so she said okay, then this round has to include coding, we can't just do a pure Q&A chat. Here's the whole flow, four parts: resume, technical fundamentals, coding, and ques…
- PyTorch vs Jax, Then a Question About Bashing AMDNVIDIA · Technical Marketing Engineer, AI Software · Onsite · Jul 2025
Onsite interview 1/4. The first interviewer, 45 minutes, first asked about my resume, then it was an AI technical interview, since the role is technical marketing for AI Software. The interview had three parts. Part 1: Deep Learning Fundamentals Q1: In Machine Learning, what are the high-level trends happening at the framework level? I answered with the evolution from numpy to PyTorch to Jax. He…
