READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 96 of 153
Interview experiences · Nuro
Nuro Intern Software Engineer Interview Experience — A Thread-Safe Video Player and a Symmetric-Points LeetCode
Only 1 round, which consisted of 2 interviews. The first was a coding system design question, and the second was a traditional LeetCode problem. Here is the first question: You're given a Frame class and a VideoPlayer class with the following operations: Read(): reads and returns the next frame of the video, or indicates that the end of the video has been reached. Render(frame): renders a frame o…
Interview experiences · Nuro
Nuro Intern Software Engineer Interview Experience — Minesweeper and a Non-Thread-Safe Video Player in One 90-Minute Round
We interviewed together on: Coding Algorithm + Coding System, 1 hour 30 minutes total. Coding Algorithm: a Minesweeper problem. The interviewer split it into Part 1 and Part 2. Part 1: without clicking any cell, output the board after revealing it — mainly testing whether you know what number to output for cells next to a mine. Part 2: DFS. On Part 2 I got stuck because I didn't fully clarify the…
Interview experiences · Nuro
Nuro Software Engineer interview experience
A recruiter first contacted me about availability, then we had an initial screening call about my background and experience. It was a standard conversation for setting context and understanding what I had done. About a week later, I had a technical interview with the hiring manager, and the questions became much more domain-specific. The interview focused on systems engineering rather than generi…
Interview experiences · Nuro
Nuro Software Engineer Interview Experience — In-Person Onsite and an MVCC Follow-Up
Phone Screen: Coding: Given point coordinates, points less than k apart needed to be merged into a group. I used union-find. The follow-up asked what to do if there were a lot of points and they were very sparse, and how to reduce the computation. System design: Design a metrics-aggregation system. Each vehicle collects data about obstacles on the road, such as locations. There weren't many vehic…
Interview experiences · Nuro
Nuro Software Engineer Interview Experience — Scheduling Rounds and an Onsite Rejection
I had my Nuro onsite last week and received a rejection email yesterday. I'm sharing the experience to give something back to the forum. Phone: Coding: Essentially Course Schedule II, solved with topological sorting. The follow-up asked how to change the code for multiple threads. System design: A question that had appeared on the forum, though I hadn't seen it at the time. A video needs three pr…
Interview experiences · Nuro
Nuro Software Engineer Interview Experience — Unprepared System Design Plus an Easy Coding Round
HR reached out and I just did the interview casually without much prep. The phone screen was 45 mins system design + 45 mins coding. System Design The question was to design a self driving car simulation job scheduler system. 10K simulation cases every week, each job has multiple phases, and the phases have dependencies on each other. Each case have several phases Weekly run of 10000 cases I hadn…
Interview experiences · Nutanix
Nutanix Account Executive interview: clear recruiter, manager and country-manager process
I started with a recruiter interview that felt professional and easy to talk through. The recruiter explained what they would focus on and encouraged me to understand the company background so I could speak about it in context. The process then continued with the hiring manager and a higher country-level manager, with prompt updates and feedback. The format was clear, so I did not spend time wond…
Interview experiences · Nutanix
Nutanix Account Executive interview: recruiter-led offer discussion
I started with a clear, professional exploratory call with a recruiter. Soon after, I spoke with the sales manager who would have been my direct boss and then the country leader. The recruiter followed up to say the process had been positive and discussed what an offer and the next steps would likely look like. That follow-through made the direction of the process much clearer. Leadership was inv…
Interview experiences · Nutanix
Nutanix Senior+ Software Engineer Interview Experience — Guidelines Promised Three Rounds, Got Two Algorithm Interviews Instead
The phone screen just asked a few casual questions, then they sent an OA on HackerRank — 3 questions, an hour and a half total. After I finished it I got the interview, and what was pretty ridiculous is that the guidelines they sent and what the actual interview turned out to be were completely different. The intro said 3 rounds: one coding round, one "Advanced problem-solving coding" round, and…
Interview experiences · Nutanix
Nutanix Software Engineer interview experience: graph states and C++ debugging
I had a compact two-round process that was intense but fair. The first round lasted roughly 35 minutes and combined problem solving with debugging. I worked on a graph prompt that began simply and gained constraints and state transitions, so choosing the right state representation and keeping the solution efficient mattered. That round also included debugging a multi-page C++ linked-list program,…
Interview experiences · NVIDIA
NVIDIA Data Scientist Interview Experience — 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…
Interview experiences · NVIDIA
NVIDIA Data Scientist Interview Experience — 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…
Interview experiences · NVIDIA
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…
Interview experiences · NVIDIA
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…
Interview experiences · NVIDIA
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…
Interview experiences · NVIDIA
NVIDIA New Grad Software Engineer Interview Experience — Verification Role, Offer After Eight Weeks
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…
Interview experiences · NVIDIA
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…
Interview experiences · NVIDIA
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…
Interview experiences · NVIDIA
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…
Interview experiences · NVIDIA
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…
Interview experiences · NVIDIA
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…
Interview experiences · NVIDIA
NVIDIA Software Engineer Interview Experience — 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: ?…
Interview experiences · NVIDIA
NVIDIA Software Engineer Interview Experience — 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…
Interview experiences · NVIDIA
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…