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

UberData Scientist
Jan 2026

CDF Coding, ETA System Design, and a Second Round That Never Happened

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

RejectedTechnical ScreenXP0
StripeSoftware Engineer
Jan 2026

Online Assessment on a ChatGPT Billing Problem

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

Online AssessmentXP0
Otter.AiSoftware Engineer
Jan 2026

A Karat Phone Screen Blown by a Password Validator Bug

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

RejectedTechnical ScreenXP0
StripeSoftware EngineerIntern
Jan 2026

A Scheduling Problem That Kept Adding Twists

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

OnsiteXP0
BytedanceData EngineerNew Grad
Jan 2026

DP Problem on Video Selection with an Attention-Span Constraint

The earlier round 1 also went pretty smoothly, and they notified me about round 2 the next day. This round also wrapped up successfully. The interviewer, after the self-introduction, went straight into a behavioral round — mainly grilling me on my resume: briefly talk about your internship project, what you learned from it, what the most challenging project was, how communication worked within th…

In progressTechnical Screen0
OpenAIFrontend Software Engineer
Jan 2026

A ChatGPT System Design and a Messy Refactor Round

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

Technical ScreenXP0
SnapchatiOS Software Engineer
Jan 2026

Five Rounds of Virtual Onsite, Including a Live Xcode Grid Build

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

RejectedOnsiteXP0
PayPalData Scientist
Jan 2026

Passed Two Fraud Rounds Despite a Rocky Performance

I applied to a few PayPal positions before Christmas, and two of my applications got recruiter calls. One of them was for a Fraud DS role and moved to interviews fast. The interviewer was someone from the same team based in India, and the interview was at 10:30pm Eastern. They asked about fraud, statistics, SQL, and Python. The second round was with the hiring manager, also based in India, at aro…

In progressOnsite0
DatologyAISoftware Engineer
Jan 2026

A Text Editor, Then a Mock Spark RDD Where I Blanked on Intersect

Writing down the questions from my DatologyAI interviews back in January at the start of the year. At the time I couldn't find anything about them online 😂 so I'm filling in the gap. Jan 6: The first round was with an interviewer who works on frontend. The question was to implement a text editor: Implement a TextEditor supporting: type_in(char): type a character at the cursor backspace(): delete…

Technical Screen0
PlaidSoftware Engineer
Reported Jan 2026

Plaid Software Engineer interview focused on algorithmic design

My interviews focused mostly on general problem solving, with algorithmic design questions instead of classic LeetCode-style problems. The bar itself wasn't clearly communicated, and the process didn't feel very professional. I also dealt with untimely responses and a sense that nothing was being evaluated consistently as the interviews progressed. By the time the process ended, it felt more like…

0
AsanaSoftware Engineer
Reported Jan 2026

Asana Software Engineer interview with roughly six rounds

My interview process felt well organized overall and took place over about two weeks, with roughly six rounds. The interviewers were friendly and collaborative, and the questions generally matched what I had seen mentioned elsewhere, including coding and design topics related to the role. I received a rejection with a list of areas to improve. That was discouraging because when there are several…

Rejected0
AsanaSoftware Engineer
Reported Jan 2026

Asana Software Engineer interview: two-hour OOP coding session

My process started with a coding round, followed by a system design round, and then security became part of the evaluation too. After that, I had a longer, two-hour coding session focused on OOP. That coding block was less about solving one algorithm and more about writing classes and methods, then explaining my logic and time complexity. I had to talk through my thinking as I worked, not just pr…

OfferTechnical Screen0
DropboxSoftware Engineer
Reported Jan 2026

Dropbox Software Engineer interview with CodeSignal and code review

My Dropbox process followed a fairly standard rhythm: CodeSignal first, then technical and behavioral interviews, with recruiter check-ins between stages. After I applied, I received the online assessment and moved into interviews focused on coding and problem-solving. The structure felt straightforward, with clear checkpoints between steps. The technical interviews covered algorithm and data-str…

Technical Screen0
StackadaptAccount Executive
Reported Jan 2026

Stackadapt Account Executive interview: three rounds with clear feedback

The interview process felt unusually smooth and respectful to me. The recruiter communicated throughout, and the company’s values came through in how people treated me. I wasn’t ghosted, and the process was clear. I went through three rounds and spoke with five different people. Those conversations helped me learn about the role and how the team worked. Each one felt honest and grounded rather th…

Other0
PlaidCustomer Success Engineer
Reported Jan 2026

Plaid Customer Success Engineer interview with Quickstart homework and technical questions

I went through two stages. The first consisted of take-home exercises. I had to run Plaid’s Quickstart setup and write response emails to mock customers dealing with specific problems. I liked this part because it made me research what was happening and think through how to communicate in a calm, supportive way. The second stage was a one-on-one call. I was told it would be a short conversation w…

Take-home Project0
ScaleSoftware Engineer
Reported Jan 2026

Scale Software Engineer interview with practical frontend work

My interview path followed a fairly classic structure: a recruiter screen, a technical screen, and then meetings that expanded into onsite-style rounds. The technical portion included system design and practical problem-solving that combined algorithmic work with a frontend component, so it was more ambiguous than pure coding. The hardest part for me was figuring out what the interviewers expecte…

Technical Screen0
CoreWeaveSoftware Engineer
Reported Jan 2026

CoreWeave Software Engineer interview with a 60-minute CoderPad task

I had one main evaluation that stood out because it was so concrete. It was a 60-minute CoderPad session in Python, where I had to build a CLI tool for field technicians to reboot remote servers through an API. The setup included a locally running backend and a specific POST endpoint, and the work was divided into several parts during the session. What made it intense wasn’t the unfamiliar enviro…

Other0
CoreWeaveSoftware Engineer
Reported Jan 2026

CoreWeave Software Engineer interview with a Python CLI task

My earliest round was a recruiter screen that went well, followed by a coding assessment that felt practical rather than like the usual LeetCode-style exercise. The question was timed, but the framing was closer to real-world work. The recruiters and interviewers also seemed knowledgeable and genuinely approachable. As I moved further through the process, I ran into a different kind of hurdle: a…

HR Screen0
ConfluentFrontend Engineer
Reported Jan 2026

Confluent Frontend Engineer: JavaScript, React, and rolling-window data access

The process started with a recruiter chat and quickly moved into interviews tied to practical work instead of abstract puzzles. The recruiter call covered my background and expectations, after which I took a frontend coding challenge. That round focused on JavaScript and React. I also had a UI design discussion that moved into broader system basics before shifting to behavioral questions and team…

HR Screen0
PlaidSoftware Engineer
Reported Jan 2026

Plaid Software Engineer interview: three rounds with a three-hour final

I moved through a tight three-round sequence: an OA, an HR chat, and a final round. The timeline felt fast, and the recruiter was professional. The OA was split into two parts under one larger question, with difficulty around the medium LeetCode level. The final round lasted three hours, divided into 1.5 hours of technical work and 1.5 hours of conversation with a manager. The technical portion i…

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