Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

21 stories

Likes earn the author +10 XP for the first 3 likes each day

NVIDIAQA Engineer
Reported Jul 2026

NVIDIA QA Engineer interview: unique-word Python script

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…

Technical Screen0
NVIDIAQA Engineer
Reported Jul 2026

NVIDIA QA Engineer interview: project walkthrough, DSA, and a long timeline

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…

In progressHR Screen0
NVIDIAQA Engineer
Reported Jul 2026

NVIDIA QA Engineer interview: HackerRank and pending onsite

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…

In progressOnline Assessment0
NVIDIAEmbedded Engineer
Reported Jul 2026

NVIDIA Embedded Engineer interview: firmware protocol system design

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…

0
NVIDIAEmbedded Engineer
Reported Jul 2026

NVIDIA Embedded Engineer interview: two-hour C coding screen

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…

HR Screen0
NVIDIASoftware Engineer
Reported Jul 2026

NVIDIA Software Engineer interview: practical problems and delayed rejection

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…

RejectedOnline Assessment0
NVIDIASolutions Architect
Reported Jul 2026

NVIDIA Solutions Architect interview: EVPN shifted to DevOps

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…

Technical Screen0
NVIDIAEmbedded Engineer
Reported Jul 2026

NVIDIA Embedded Engineer interview: bit manipulation and register operations

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…

Technical Screen0
NVIDIASoftware Engineer
Reported Jul 2026

NVIDIA Software Engineer Interview Experience: A two-month process with a home exam and C/C++ day interview

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…

RejectedTake-home Project0
NVIDIASoftware Engineer
Reported Jul 2026

NVIDIA Software Engineer interview with a 45-minute resume discussion and coin riddle

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…

0
NVIDIASoftware Engineer
Jun 2026

Two Unstructured Screens and No Follow-up

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…

No responseTechnical Screen0
NVIDIAQA Engineer
Reported Jun 2026

NVIDIA QA Engineer Interview Experience: Python, systems, and VP troubleshooting

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…

HR Screen0
NVIDIASoftware Engineer
May 2026

Two Easy Coding Questions, Then a Template Rejection

Locked — open it to unlock the full story with XP.

RejectedTechnical ScreenXP0
NVIDIASoftware Engineer
Feb 2026

Screening to Onsite, and LeetCode's NVIDIA Tag Didn't Help

Locked — open it to unlock the full story with XP.

RejectedOnsiteXP0
NVIDIASoftware Engineer
Feb 2026

Offer in Five Days, Five Back-to-Back Rounds

Locked — open it to unlock the full story with XP.

OfferOnsiteXP0
NVIDIASoftware Engineer
Dec 2025

Phone Screen on a High-Performance String Class

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: ?…

Technical Screen0
NVIDIAData Scientist
Oct 2025

Two Screens, a Six-Round Virtual Onsite, and an Unofficial Offer the Same Day

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…

OfferOnsite0
NVIDIAData Scientist
Oct 2025

Two Phone Screens, a Six-Round Virtual Onsite, and an Offer

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…

OfferOnsite0
NVIDIATechnical Marketing Engineer
Sep 2025

One Round, Four Parts: Resume, ML Trivia, and Live NumPy Coding

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…

Technical Screen0
NVIDIATechnical Marketing Engineer, AI Software
Sep 2025

First Onsite Round Covers ML Frameworks, Compilers, and Product Sense

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…

Onsite0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP