Interview Experiences

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

Share yours, earn XP

8 stories

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

NuroSoftware Engineer
Aug 2026

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…

RejectedOnsite0
NuroSoftware Engineer
Aug 2026

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…

RejectedOnsite0
NuroSoftware Engineer
Aug 2026

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…

Technical Screen0
NuroSoftware EngineerIntern
Aug 2026

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…

Technical Screen0
NuroSoftware Engineer
Reported Jul 2026

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…

Technical Screen0
NuroSoftware Engineer
May 2026

Recruiter Call, Two Phone Screens, Then an Extra Round and Silence

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

No responseTechnical ScreenXP0
NuroSoftware EngineerIntern
Feb 2026

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…

Technical Screen0
NuroData Scientist
Jul 2025

Merging Overlapping Vehicle-Run Intervals in SQL and Python

Dataset description The dataset had several fields: set id, run id, start time, end time, and set number. The set ids ran from 1 to 6 and represented different recorded segments from autonomous-vehicle sessions. For example, set 1 was about 30 seconds long, set 2 was 23 seconds, set 3 was 19 seconds, and so on. The run id identified the trip. It used a time-string format such as 20250101_122334,…

Technical Screen0

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