Interview Experiences

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

Share yours, earn XP

4457 stories

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

AmazonSoftware Engineer
May 2026

A One-Hour Phone Screen With Two Sum Into Three Sum

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

Technical ScreenXP0
HarveySoftware Engineer
May 2026

Great Onsite, Rough Virtual Screen, Lost to Another Candidate

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

RejectedOnsiteXP0
GoogleSoftware Engineer
May 2026

Coding Rounds That Keep Changing the Requirements

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

OnsiteXP0
MercorSoftware Engineer
May 2026

A Product-Focused Recruiter Screen, Then Sorting Theory and a Concurrency Code Review

Round 1 — Background / recruiting round Self-introduction, plus walk through a project you've worked on recently. They dug deep into the project, but the follow-ups were all from a product angle rather than implementation details: was this decision made by your system or upstream? How do you define "it worked"? What's the success metric for this project? What's your understanding of what Mercor d…

Technical Screen0
The Voleon GroupData Scientist
Reported May 2026

The Voleon Group Data Scientist interview with OLS regression and Linux tasks

My interview began with a first round that felt like two parts combined. I was either given a dataframe or asked to do a simple join, then I had to run an EDA pass and perform an OLS regression in Python. I focused on p-values and R-squared, and I had to explain the regression assumptions and residual-style checks as I discussed the results rather than just report the numbers. The second half foc…

Technical Screen0
BrexSoftware Engineer
Reported May 2026

Brex Software Engineer interview with debugging and high pressure system design

I went through a recruiter call and then several technical rounds. The whole process felt hostile and disrespectful of my time. Even when the interviewers were outwardly neutral, I didn't feel much respect for the effort involved in sitting through multiple steps. The hardest part was that I never got clear feedback about why I was rejected, so I was left guessing where things went wrong. The tec…

RejectedTechnical Screen0
VantaAccount Executive
Reported May 2026

Vanta Account Executive fourth-round interview

My Vanta Account Executive process felt long, but it made me think more than I expected. It had five steps, and I reached the fourth round. The difficult part was not knowing where I stood relative to the other candidates. I kept waiting to understand what that stage meant in terms of the competition, and the uncertainty lingered. I appreciated the intentional, thought-provoking nature of the rou…

Other0
RemitlySoftware Engineer
Reported May 2026

Remitly Software Engineer online technical screening

After a recruiter call, I had an online technical screening split between getting to know me and solving a problem. It wasn’t a simple "here’s the pattern" LeetCode exercise, and it didn’t feel realistic to finish in a tight window without running into gaps. I spent a lot of time making sure I understood what was being asked and what passing behavior should look like. The coding round wasn’t just…

Online Assessment0
MercorSoftware Engineer
Reported May 2026

Mercor Software Engineer interview with a five-hour virtual super day

My process started with a recruiter call, followed by an AI-driven stage where I answered LeetCode-style questions and additional technical prompts. After that, I went through a longer "super day" style setup. Mine was virtual and lasted about five hours in total, combining system design, coding, and what they called vibe coding on the same day. It was on the harder side, although I also felt lik…

RejectedOther0
ZiplineSoftware Engineer
Reported May 2026

Zipline Software Engineer interview with an industry-expert recruiter

A recruiter reached out to me on LinkedIn and quickly talked up her background. She described herself as an industry expert and implied that she could "sniff out" whether I really knew what I was talking about. That framing threw me off before I had a chance to explain my experience. I didn’t want to feel put on the defensive, especially since I had already done significant work and expected a mo…

Rejected0
CoreWeaveSoftware Engineer
Reported May 2026

CoreWeave Software Engineer interview: concurrency screen and timed CoderPad task

I moved quickly once a recruiter contacted me. We scheduled a phone call for the next day, and the conversation felt efficient. We discussed why I wanted to join, what I considered my biggest mistake in my current role, my compensation expectations, and other fit questions. After that, I had a technical screen with a senior engineer focused on concurrency and multithreading. It was the kind of co…

Technical Screen0
BoxAccount Executive
Reported May 2026

Box Account Executive final presentation process

I interviewed for the Account Executive role at Box and went through a fairly standard process over a few rounds. The difficulty felt moderate, although the experience varied between feeling supported and wanting more clarity. The process included a recruiter screen about my background and fit for the role. There was also a virtual manager or hiring manager interview. In some accounts, that conve…

HR Screen0
RivianBackend Engineer
Reported May 2026

Rivian Backend Engineer interview with delayed feedback and missing follow-ups

I went through a frustrating, logistics-heavy interview process for a Software Engineer role. The difficulty felt average, and communication was often delayed or missing. The recruiter or HR screen covered basic engineering questions, production-line and equipment questions, and behavioral topics. The hiring manager meeting included more role-fit questions, after which communication slowed down.…

No responseHR Screen0
BoxSoftware Engineer
Reported May 2026

Box Software Engineer interview with a two-hour technical screen and LLD round

My Box Software Engineer interview felt like a classic LeetCode-style process, with more emphasis on data structures than algorithms. The first technical screen lasted about two hours. The interviewer joined at the beginning and again at the end just to discuss the results. The next coding and DSA round took about an hour, with the interviewer on the call the entire time. After that, there was a…

RejectedTechnical Screen0
RemitlySoftware Engineer
Reported May 2026

Remitly Software Engineer interview: live coding and power-day onsite

My process started with an HR phone call. I then had a fairly structured technical interview with a live coding problem and enough time to think through the approach, followed by a separate values and discussion segment. After that, I went through what felt like a larger "power day" onsite with multiple interviewers across different roles. Some rounds focused on my resume experience. The technica…

RejectedTechnical Screen0
Glean (CA)Software Engineer
Reported May 2026

Glean (CA) Software Engineer interview: difficult DSA problem-solving screen

My process started with a recruiter reach-out where we talked through the setup and the overall interview process. After that, I had a technical screen that felt more "in-house" than a generic LeetCode interview. It still relied on DSA knowledge, but the prompt put more emphasis on problem-solving within its structure. The question required me to apply data structures and algorithms. I could tell…

Technical Screen0
AirtableSoftware Engineer
Reported May 2026

Airtable Software Engineer interview with a sharp system design ramp

I started with an online assessment whose questions felt close to the kind of work Airtable actually does. After submitting it, I moved into a coding round focused again on data structures and algorithms, though it was framed more like a real-world task than pure LeetCode. The time limits and scoring varied, but the expectation stayed consistent: write clean code, handle edge cases, and make it w…

Online Assessment0
ZiplineSoftware Engineer
Reported May 2026

Zipline Software Engineer onsite cut short by a video setup

My early screens went well, including an initial check with the hiring manager and a coding portion. I was then invited onsite for the final rounds, and that's when the process started to feel badly mismanaged. When I arrived, the interviewers were working from home, so I had to join by video while sitting in a congested, makeshift phone setup. That made the whole experience feel pointless. Durin…

RejectedOnsite0
RivianSoftware Engineer
Reported May 2026

Rivian Software Engineer interview with panel interviews and a project presentation

I went through a fairly organized, conversation-heavy process. It started with an HR call, followed by a longer meeting with the hiring manager. After that, I had panel-style interviews with several interviewers from different teams. Each round included time for questions and follow-ups. The format combined behavioral and technical fit without feeling like a trick. In one of the later sessions, I…

RejectedHR Screen0
DropboxSoftware Engineer
Reported May 2026

Dropbox Software Engineer interview with a monitored CodeSignal test and Deep Dive

I started with a heavily monitored CodeSignal test. I had to keep my camera and microphone on, record my full screen for the entire test, and upload identity details. After I passed, the process quickly became chaotic. Communication broke down almost immediately. I kept waiting while the recruiter seemed to disappear for days, later attributing the delay to a company outing. When scheduling final…

RejectedOnline Assessment0

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