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

LinkedInData EngineerSenior+
Feb 2026

Aced the Coding Round, Rejected the Next Day

Unfortunately I got laid off by my old company a few weeks ago. Through a good friend's referral, I got an interview for a LinkedIn Staff Data Engineer - Information Security role. The interviewer was really friendly — the whole thing was very warm and supportive. The interview was an hour total. We started with some small talk, then he asked two questions: Tell me about a project you worked on,…

RejectedTechnical Screen0
PinterestData Scientist
Feb 2026

Onsite Loop Interrupted by Recruiter Conflict, Two Rounds Rescheduled

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

In progressOnsiteXP0
GoogleData Scientist InternIntern
Feb 2026

Coding Round Plus a Short Manager Chat, Rejected Three Weeks Later

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

RejectedHR ScreenXP0
ConfluentAccount Executive
Reported Feb 2026

Confluent Account Executive interview with a defense-sector role mismatch

My experience started with a recruiter who seemed supportive, but the initial description of the role, especially its stated focus on the defense sector, didn't match what I later heard from the interviewers. That mismatch made me wary of how clearly the role had been defined. Once I entered the interviews, it was hard to pin down the day-to-day responsibilities and scope. Both conversations star…

HR Screen0
ScaleMachine Learning Engineer
Reported Feb 2026

Scale Machine Learning Engineer interview: coding round followed by ML theory

After speaking with a recruiter, I went through a compact sequence: a manager screen, a coding round, and a final discussion focused on machine learning theory. The process felt broad and deep at the same time, which made it difficult to approach as one straightforward type of interview. Even when I felt comfortable with the technical parts, the theory discussion kept bringing me back to fundamen…

RejectedOther0
Glean (CA)Backend Engineer
Reported Feb 2026

Glean (CA) Backend Engineer interview: multiple one-hour DSA rounds

I started with an introductory round with the hiring manager and then met with the head of engineering. After that came multiple coding and DSA rounds, each lasting around an hour. The setup felt condensed but clear. They moved from conversation into hands-on technical evaluation pretty quickly. The process was described as difficult, and the structure reflected that. Instead of one challenge, I…

Other0
VoleonData Scientist
Reported Feb 2026

Voleon Data Scientist interview with Python modeling and analysis

I went through a thorough, structured interview process with Voleon. It started with an initial interview, followed by two technical interviews, two soft-skill interviews, and a final tech-focused interview. There were a lot of rounds, and I got the sense that they were trying to cover several different areas instead of testing only one skill. The technical interviews involved Python coding tasks…

RejectedTechnical Screen0
The Voleon GroupData Scientist
Reported Feb 2026

The Voleon Group Data Scientist interview with five technical rounds

I started with an HR conversation that was fairly straightforward, mostly about fit and why I was interested. What stood out was how quickly the process moved into a technical sequence. I went through something like five rounds of technical interviews. The HR portion included basic questions such as why I wanted the position. The technical rounds kept coming back to live coding. I was allowed to…

RejectedHR Screen0
CrowdstrikeSoftware Engineer
Reported Feb 2026

Crowdstrike Software Engineer interview with recruiter and hiring manager calls

I had two recruiter-adjacent calls: first with a recruiter, then with a hiring manager. The hiring manager asked about my previous experience and projects, with some focus on call and metrics topics. The conversation seemed aimed at matching my background to what the team cared about. After the hiring manager call, everything stalled. I was ghosted and never heard back from the recruiter, which m…

No response0
BoxSoftware Engineer
Reported Feb 2026

Box Software Engineer interview with delayed final rounds and rejection

My experience started with a lot of momentum and then collapsed into confusion. After I applied, I completed three one-hour interviews covering coding, data structures, and system design. The recruiter's feedback was very positive, and I was described as the top candidate. I was asked to wait while the team looked for the right fit across several teams. That's when things became unclear. After I…

RejectedOther0
HeadwaySoftware Engineer
Reported Feb 2026

Headway Software Engineer interview: unclear onsite design expectations

My process started with a recruiter touchpoint, followed by a technical screen and then a three-round onsite. Scheduling and feedback were responsive, but the actual evaluation didn't line up with what I expected. The onsite design segment especially didn't feel like a classic system design round. The constraints made it hard to tell what direction they wanted, so I spent more time guessing than…

Technical Screen0
CrowdstrikeSoftware Engineer
Reported Feb 2026

Crowdstrike Software Engineer interview for Falcon Exposure Management

I went through CrowdStrike's process for the Falcon Exposure Management team. The overall tone was highly technical, with a strong focus on problem-solving and system design. It felt designed to test reasoning above all else. The process started with a DSAT-style step and continued with the same emphasis on problem-solving and system design. The questions didn't feel like trivia. They focused mor…

Other0
DropboxSoftware Engineer
Reported Feb 2026

Dropbox Software Engineer interview after the CodeSignal assessment

I applied for the SWE Summer 2026 internship in Canada and was sent an online assessment through CodeSignal. After completing it, the only clear next step listed was to wait for a recruiter call. That was essentially the whole process I experienced: I passed the assessment, received an email saying I had moved forward, and then waited to see whether a recruiter would contact me. There wasn’t much…

Online Assessment0
CloudflareFrontend Engineer
Reported Feb 2026

Cloudflare Frontend Engineer interview with a repeated system design round

I went through an extensive sequence that started with conversations with the hiring manager and engineering manager about my background, then moved into several live coding and architecture or system design exercises. The later technical stages included an "orange cloud" behavioral interview, PM and cross collaboration rounds, and a final C-level executive conversation about why I wanted the job…

Technical Screen0
AsanaSoftware Engineer
Reported Feb 2026

Asana Software Engineer interview with repeated rescheduling

From the beginning, the scheduling and communication felt unreliable. I had multiple rounds where steps seemed to be skipped without much explanation, and I kept waiting for the next stage to move forward. Several interviews also had to be rescheduled because the interviewers didn't show up at the scheduled times. One HR conversation felt mostly like a checklist. The questions seemed to come from…

HR Screen0
IMCSoftware Engineer
Reported Feb 2026

IMC Software Engineer interview with coding, system design, and team fit

The process was structured and felt comprehensive. After applying, I completed an online activity and then had an initial screening call. The technical portion moved into coding interviews where I could choose the programming language. The work combined problem-solving discussions with system design questions. There were also team fit and culture checks, along with a feedback step where they revi…

Online Assessment0
BoxAccount Executive
Reported Feb 2026

Box Account Executive interview with delayed updates and limited feedback

I interviewed for an Account Executive role at Box. The process felt average to poor in terms of coordination, with delays and weak feedback that made it harder to stay confident and prepared. The recruiter screen included conversations that either went fine at first or failed to meet the expectations that had been set. The hiring manager and next-round interviews were virtual, and urgent request…

Rejected0
ZiplineSoftware Engineer
Reported Feb 2026

Zipline Software Engineer: take-home, system design, and a month-long ghosting

The process took longer than I expected, although it started out feeling genuinely fulfilling. I went through six stages overall: a recruiter call, a hiring manager screen, a take-home assessment, a technical interview connected to the assessment, a system design interview, and a product prioritization conversation. The later rounds also included a culture-fit discussion and an interview with a V…

No responseHR Screen0
Northrop GrummanSoftware Engineer
Reported Feb 2026

Northrop Grumman Software Engineer final round: limited technical discussion and quick rejection

My process started with a recruiter screen. About a week later, I sat through what was essentially the final round. That conversation mixed behavioral questions with only a few technical prompts. I don't remember anyone asking me to go deeply into my background, and the technical part never became a real technical discussion. The interview felt fairly light overall, and the timeline moved quickly…

RejectedHR Screen0
ExperianData Analyst
Reported Feb 2026

Experian Data Analyst interview with a data analysis walkthrough

My process started with HR-style questions and quickly shifted into scenarios related to the role. The interview lasted about 45 minutes, and I was asked a few technical questions tied to the work I would be doing rather than abstract trivia. A week after the initial interview, I completed an online assessment or assignment with the hiring team. Later, I had an in-person interview that lasted abo…

Online 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