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

The Voleon GroupData Scientist
Reported Mar 2026

The Voleon Group Data Scientist interview: Python, data analysis, and model building

My process involved a lot of rounds and felt very thorough, almost standardized. After an initial step, I had two technical interviews followed by two soft-skill interviews focused on project and team management. The topics varied, but the structure stayed consistent. I was evaluated across several dimensions rather than only on coding. The technical interviews centered on Python coding tasks tha…

0
PlaidSoftware Engineer
Reported Mar 2026

Plaid Software Engineer interview with an opaque new-grad-style loop

I went through a new-grad-style loop that felt oddly opaque. It started with an OA, followed by a phone screen and then a voice interview. The bar was hard to read because I wasn't getting consistent signals about what would count. During the phone step, the code I submitted wasn't even fully functional, yet I still moved forward. By the voice interview, my code and explanations felt solid. I did…

Online Assessment0
DiscordSoftware Engineer
Reported Mar 2026

Discord Software Engineer interview: chat-server coding and virtual onsite

I interviewed for a Software Engineer role through a recruiter screen, a technical screen, and a virtual onsite. Overall, it felt like a standard process with mixed outcomes and a few awkward moments. During the recruiter screen, we discussed my experience and fit, including behavioral questions. In one case, I was unexpectedly asked to describe a trade-off situation. The technical screen was a l…

HR Screen0
StackadaptSoftware Engineer
Reported Mar 2026

Stackadapt Software Engineer interview with four rounds and a three-hour session

My interview felt intense from the beginning. I went through four rounds back to back, including one session that lasted around three hours. The questions were difficult. The interviewers were kind, but the pace and scope made it hard to give a complete answer. One technical round was especially rough. I had to complete both a LeetCode-style medium problem and a system design prompt within the sa…

Technical Screen0
CloudflareAccount Executive
Reported Mar 2026

Cloudflare Account Executive interview with a mock discovery call

From the recruiter call onward, the process moved quickly, though it was also confusing at times. I met multiple interviewers, including hiring managers and people from different functions. Some of them seemed impatient, as if they were looking for a specific "sales-ready" trait instead of trying to get to know me conversationally. The recruiter was nice, but the introductions and context weren’t…

0
DropboxSoftware Engineer
Reported Mar 2026

Dropbox Software Engineer interview with a proctored CodeSignal assessment

I started with Dropbox’s automated assessment. The CodeSignal-style test was proctored and had multiple levels that became stricter as I progressed. I could use Google in a very limited way, mainly for documentation about specific functions I was trying to use, but I still had to solve the core tasks under increasingly tight constraints. After that, I had a recruiter phone screen and moved into t…

Online Assessment0
IMCSoftware Engineer
Reported Mar 2026

IMC Software Engineer interview with graph and scheduling assessments

After I applied, I was asked to complete two online assessments, both focused on programming-style problem solving. One centered on graphs, and the other covered scheduling. A short time later, I moved to a one-way online interview with three questions. They were technical and focused heavily on how I think about programming languages and core data structures. The format was straightforward, but…

Online Assessment0
Glean (CA)Software Engineer
Reported Mar 2026

Glean (CA) Software Engineer: practical coding and system design onsite

A recruiter reached out to me, and the first technical screening round involved a middle-to-hard LeetCode-style problem. After that, I moved into an onsite loop with three rounds: two coding rounds and one system design round. One coding round involved another LeetCode-style problem. The other was more open-ended and practical. I spent most of the time coding while the interviewer checked in only…

Technical Screen0
CrowdstrikeAccount Executive
Reported Mar 2026

Crowdstrike Account Executive: fast-tracked interviews and a final panel

My process started with a straightforward recruiter conversation, followed by a small number of follow-ups rather than a long gauntlet. I had been in contact with the hiring side early on, and after a conversation they sent me an application link and connected me with the recruiting team. The conversations stayed professional and focused heavily on my cybersecurity sales background and how it fit…

HR Screen0
CrowdstrikeSolutions Engineer
Reported Mar 2026

Crowdstrike Solutions Engineer interview: remote hiring-manager and sales interviews followed by silence

A recruiter contacted me, and the process became a remote interview cycle with a hiring manager and members of the sales team. I kept moving through the interviews and felt that I had passed the rounds, so I expected the next steps to come quickly. Instead, the process went silent after I finished. I emailed for an update, but I still didn’t hear back. The lack of communication felt careless and…

No response0
ConfluentAccount Executive
Reported Mar 2026

Confluent Account Executive interview and the IBM acquisition

I started with a recruiter conversation about how the recent IBM acquisition might affect hiring. The recruiter was transparent, but I came away with more uncertainty than clarity, especially about what the acquisition would mean for the day-to-day work in the Inside Sales role. In the later interviews, I kept asking for specifics: how the role fit into the larger sales organization, what the KPI…

0
Notion LabsSolutions Engineer
Reported Mar 2026

Notion Labs Solutions Engineer interview: technical screen and months without closure

I went into the process expecting something simple and informative. It started with a recruiter screen covering the usual background questions, my timeline, and my interest in Notion. The recruiter was straightforward and explained how the process worked. I was told I'd hear back quickly, but after that conversation I kept waiting. Silence became the main pattern after the early stages. I later r…

No responseHR Screen0
AsanaSoftware Engineer
Reported Mar 2026

Asana Software Engineer interview: CodeSignal, coding round, and onsite

The process started with a CodeSignal assessment, followed by a dedicated coding round. After that, I attended an onsite that included system design and a behavioral interview, all in a fairly standard sequence. The questions leaned toward LeetCode, but they didn't feel too extreme. Many covered the kinds of problems I could find online with the right search terms. I didn't move forward, although…

RejectedOnline Assessment0
MercorSoftware Engineer
Reported Mar 2026

Mercor Software Engineer interview with a rushed interview and a no-show

My application moved quickly at first and then ended without much closure. After speaking with a recruiter and taking an online assessment, I submitted my solution and received a denial about two weeks later. The experience was okay overall, but I never got any feedback, so I couldn't tell what went wrong. Later, I had a separate and more upsetting experience. I was rejected after a very brief in…

Online Assessment0
ExperianSoftware Engineer
Reported Mar 2026

Experian Software Engineer, unclear team details and concurrency discussion

I went through a fairly standard multi-stage process, but the experience felt messy. It began with a recruiter phone call where the interviewer spoke extremely quickly and the connection kept breaking. It was difficult to ask questions or clarify anything. Next, I had an online interview with a manager. The interviewer was late, and the conversation didn’t feel grounded in what the team actually…

Other0
Clipboard HealthFrontend Engineer
Reported Mar 2026

Clipboard Health Frontend Engineer, repository take-home and debugging follow-up

I went through a largely take-home-driven process that was somewhere between average and difficult. It usually started right after I applied and often ended with a rejection after little actionable feedback. For the automated or online take-home, I cloned a provided repository, often involving Node.js, NestJS, React, or a backend API, and built logic to calculate results in the style of "top work…

RejectedTake-home Project0
CanonicalSoftware Engineer
Reported Mar 2026

Canonical Software Engineer interview with multiple assessments and late-stage rounds

I interviewed for the Software Engineer role through a drawn-out but structured process. I completed several assessments, followed by interviews covering coding, systems concepts, and behavioral collaboration. I started with a written-style screen, then completed logic and personality testing. The technical stages included long interview sessions, another technical segment later in the process, a…

RejectedOnline Assessment0
GarminSoftware Engineer
Reported Mar 2026

Garmin Software Engineer interview with DSA and project discussions

I went through a fairly standard, multi-round software and DSA process over a couple of weeks. It included mostly resume and project discussion, along with one or more light to moderate technical assessments. The recruiter screen lasted about 20 to 45 minutes and focused on my background, why I wanted to work at Garmin, and a few behavioral prompts. In the remote technical interview, which took p…

Technical Screen0
ASMLSoftware Engineer
Reported Mar 2026

ASML Software Engineer interview: HireVue screening on experience, company knowledge, and logistics

After applying, I was contacted and moved into an AI interview on the HireVue platform. The prompts were fairly broad. They covered my experience in the role, what I knew about ASML, and logistical considerations. The questions were clear enough, but I didn't progress beyond that stage. I came away feeling that the screening was designed to cast a wide net rather than explore any particular techn…

Other0
CanonicalSoftware Engineer
Reported Mar 2026

Canonical Software Engineer interview with questionnaire and Python assessment

I interviewed for the Software Engineer role through a multi-assessment process that started with a long questionnaire and two tests, before any deeper technical discussion. I answered around 30 questionnaire questions. The first assessment was a non-standard test made up of different types of tasks. The second assessment focused on Python. I didn’t receive an offer. Early filtering leaned heavil…

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