Interview Experiences

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

Share yours, earn XP

4433 stories

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

TwitchSoftware Engineer
Reported Mar 2026

Twitch Software Engineer interview with a two-hour assessment

I interviewed for a Software Engineer role at Twitch and went through an unusually long assessment. I never received clear follow-up afterward. The process began with a recruiter conversation. The online assessment was a single extended technical assessment that lasted about two hours. I wished I could see my scores, but I never received them. I didn't hear back, and the experience left me thinki…

No responseHR Screen0
Trexquant InvestmentQuantitative Analyst
Reported Mar 2026

Trexquant Investment Quantitative Analyst interview with a Markov-chain problem

The process started with an HR call about my background and fit. I then had a technical interview with a quant researcher. It included a LeetCode medium question, then shifted into a more research-oriented problem involving a Markov chain and expected steps using a cube-like setup. What I remember most is that they followed up on the mathematics and also wanted an efficient way to simulate the id…

HR Screen0
SamsaraAccount Executive
Reported Mar 2026

Samsara Account Executive interview where the evaluation felt impression-based

The beginning felt fairly normal. I had a recruiter screen with basic resume questions, then spoke with the hiring manager about the role. Those early interviews were quick and structured, so I thought I was in good shape. The tone changed once I got deeper into the process. During the manager conversation, I felt as if I'd already been marked down somehow because of how I "looked the part," even…

0
SamsaraQA Automation Engineer
Reported Mar 2026

Samsara QA Automation Engineer interview, HIL take-home project

I started with a pleasant Zoom call with the hiring manager, followed by a recruiter call that focused mostly on whether I wanted to continue. I was told the next steps would include coding and a take-home project. After I shared my availability, they scheduled four hours of interviews on one day. They didn’t explain beforehand that it would essentially function as a virtual onsite, so I tried to…

Onsite0
Aurora InnovationCloud Engineer
Reported Mar 2026

Aurora Innovation Cloud Engineer interview, C++ and system design

After connecting through the recruiter, I moved through a structured process: a recruiter call followed by technical discussions, system design, and coding. The recruiter and interviewers kept the tone comfortable, and I felt they were genuinely interested in how I’d approach realistic work scenarios instead of searching for one exact answer. The onsite lasted a few hours and included several tec…

Technical Screen0
DocusignSoftware Engineer
Reported Mar 2026

Docusign Software Engineer interview with three LeetCode-style rounds

My process started with a recruiter call about my background, the role, and the team I was targeting. After that, I had three LeetCode-style coding rounds, each lasting about an hour, along with a behavioral interview. The timeline stretched over several weeks, and I waited around three weeks after the final round to hear back. The technical difficulty wasn't the main issue for me. One round felt…

HR Screen0
OuraBackend Engineer
Reported Mar 2026

Oura Backend Engineer interview with architecture, coding, and take-home rounds

After I applied, I had an initial recruiter conversation about the role and my background. The recruiter explained clearly what the overall process would look like. A week or two later, I had a system architecture discussion with a team member. It felt structured and intentional. After that, I interviewed with the hiring manager. The process then became more practical. I did live coding with the…

OfferHR Screen0
SamsaraSolutions Engineer
Reported Mar 2026

Samsara Solutions Engineer interview: deal metrics and a take-home presentation

The process was more demanding than I expected. It went through several rounds, starting with HR and then moving into sales leadership. The overall acceptance rate felt low. They placed a lot of emphasis on showing a growth mindset, and the questions pushed me to be very specific about deal metrics. I had to prepare to go beyond surface-level answers. The interviews mixed behavioral prompts with…

HR Screen0
HubSpotSoftware Engineer
Reported Mar 2026

HubSpot Software Engineer interview: banking-system assessment and system design rounds

My process started with a coding assessment under tight constraints. The time pressure felt real, and the tasks were divided into multiple levels. Each level opened only after I completed the previous one. I didn't get through all the levels. The prompt involved designing a banking system, so it went beyond standard LeetCode mechanics. In another attempt, the CodeSignal online assessment was also…

RejectedOnline Assessment0
SamsaraSoftware Engineer
Reported Mar 2026

Samsara Software Engineer interview: hiring manager deep dive and TPS round

My process started with an HR call about project details and what I was looking for. That quickly led into a hiring manager deep dive, which also included a TPS round within the same hour. The TPS question wasn't too difficult and didn't feel like standard LeetCode. I didn't move forward after that, but the experience was reasonably straightforward. I understood what I was being evaluated on, and…

HR Screen0
Lucid MotorsSoftware Engineer
Reported Mar 2026

Lucid Motors Software Engineer interview: 30-minute screen, CoderPad, and four-hour loop

The structure of the process stood out to me. It began with a 30-minute screening call, followed by a 45-minute technical interview that included a CoderPad coding challenge. The final stage was a long, intensive loop that lasted about four hours. It focused on technical depth, problem-solving, and overall fit, and it was the most concentrated part of the process. I remember finishing the loop fe…

OfferHR Screen0
Lucid MotorsSoftware Engineer
Reported Mar 2026

Lucid Motors Software Engineer interview: C++, sensors, and Nvidia SoCs

My first contact was a fit conversation with the hiring manager, and it quickly set the tone for the rest of the loop. After that, I had interviews with several people. The discussions focused mostly on my C++ experience and how I had worked with sensors and Nvidia SoCs. Coding questions were mixed in, so the process wasn’t purely based on experience. What made the experience difficult was how ab…

Technical Screen0
WhatnotSoftware Engineer
Reported Mar 2026

Whatnot Software Engineer interview: one-way video with one-minute answers

I was pulled into a short, one-way video interview. The setup was straightforward: there were several questions, and I had to answer each one on camera within a tight preparation window, with only about a minute to respond to each prompt. The questions focused on behavior and my resume, with some emphasis on why Whatnot specifically. What surprised me was how quickly everything moved. I heard bac…

Online Assessment0
GeicoSoftware EngineerSenior+
Mar 2026

Recruiter Downgraded the Level Before the HM Screen Even Started

I saw this on an online job board. The job post was actually for a Distinguished Engineer, and I thought it would be a chance to get a taste of a super high-level IC role, a career jump of sorts, and I was fine taking a pay cut for that, so I applied. The recruiter then told me that their Distinguished level is calibrated against Google/Meta L8 ICs, which is two levels above my current scope, so…

RejectedTechnical Screen0
xAISoftware Engineer
Mar 2026

Flatten and Unflatten a Nested JSON Structure

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

Technical ScreenXP0
Morgan StanleyData Scientist
Mar 2026

Phone Screen Then a Live-Coding Tech Round

Phone screen: they asked me a simple Python question, then a statistics question, and then a Black-Scholes model question (I passed). The next round was the tech interview, covering Gen AI and statistics questions. They told me to have paper and pen ready, and said they'd also ask me Python coding, and possibly a stress testing framework question. The interview started with Gen AI — they asked me…

In progressTechnical Screen0
SnowflakeSoftware Engineer
Mar 2026

Mid-Level Three-Round Coding Loop, Rejected After Mixed Feedback

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

RejectedOnsiteXP0
Microsoft
Mar 2026

DNA Reassembly, Then an Euler Path Follow-up

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

RejectedTechnical ScreenXP0
Applied IntuitionSoftware Engineer
Mar 2026

45-Minute Screen on Merging 2D Line Segments

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

Technical ScreenXP0
BloombergSoftware Engineer
Mar 2026

Rejected After a Brutal VO Round

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

RejectedOnsiteXP0

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