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

Walmart LabsSoftware EngineerSenior+
Mar 2026

System Design, Behavioral, and a Two Sum Variant Onsite

This was a Walmart hiring event. I had passed the phone interview before, and then this physical onsite had three rounds. First round: system design, Ticket Master, done on a whiteboard. The interviewer was friendly and reminded me that I might not be following the process in the right order. You need to write the functional requirements, the non-functional requirements, then the model, the API,…

Onsite0
AmplitudeSoftware Engineer
Mar 2026

OA, Phone Screen, Four Onsite Rounds, Then a Final Manager Chat

OA: Write a function to validate a group of employees according to a set of rules. Each employee can have a group of sub-employees under them, so each sub-employee also needs to be validated. Phone Screen: Add a new rule to the code from the OA, to validate whether there is a cycle in the employee list. Onsite (4 rounds): Implement a Snake game. Need to handle keyboard input (up/down/left/right m…

Onsite0
GustoSoftware EngineerSenior+
Mar 2026

A Repeat Design Question the Interviewer Couldn't Follow

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

RejectedOnsiteXP0
MetaSoftware Engineer
Mar 2026

Weak Signal on Coding 2 But the Offer Came Anyway

I feel really lucky, I got a great recruiter. From the initial reach out all the way to finalizing the offer they were thorough about everything, kept emphasizing "I'm on your side." In the debrief they told me Coding 2 had a weak signal, but the quorum still generously let it through. The interviewers were all nice too — when I interviewed for an intern role before I ran into people who were dis…

OfferOnsite0
AnthropicSoftware Engineer
Mar 2026

Onsite Loop with a 1-on-1 Chat System Design, File Dedup Coding, and a Culture Round I Couldn't Read

The phone screen was Q1 image processing — using PIL to do grayscale, scale, and resize. The first step handled small images, the second step handled large images, and improving performance meant using ProcessPoolExecutor. The recruiter had mentioned beforehand that I should be comfortable with parallelism/concurrency, which was basically a hint. Time was a bit tight and the interviewer had to nu…

In progressOnsite0
ScaleSoftware Engineer
Reported Mar 2026

Scale Software Engineer interview with many coding rounds and debugging

My process felt like an implementation marathon. I went through many coding-focused rounds, and it eventually became tiring and even boring instead of engaging. There were also behavioral and debugging rounds, and the debugging session was the most excruciating part for me. Some interviewers were good, but others turned off their cameras and stayed silent throughout the coding rounds. That made i…

Technical Screen0
PlaidCustomer Success Engineer
Reported Mar 2026

Plaid Customer Success Engineer take-home with client-style scenarios

My process started with a take-home technical assessment. It wasn’t a complex coding task. Instead, it involved real-life, client-style scenarios where I had to respond to technical issues the way a customer support engineer would. After I submitted it, there was essentially no communication. I received no feedback, had no recruiter contact, and had no real interaction during the process. The onl…

RejectedTake-home Project0
MercorSoftware Engineer
Reported Mar 2026

Mercor Software Engineer interview with an Apple Silicon compatibility check

The interview was conducted by an AI agent, and I could complete it by phone or computer. The process itself was fairly straightforward, with the AI asking questions based on my submissions. The problem came with the compatibility check in the middle of the process. They specifically checked whether I was using Apple Silicon Macs. That felt like a major miss to me because the tools I needed weren…

0
AsanaSoftware Engineer
Reported Mar 2026

Asana Software Engineer interview with a specific systems modeling problem

The overall experience felt professional, and most of the rounds ran cleanly. One interviewer came across as standoffish, which threw me off more than anything technical, but the logistics and tone were mostly well handled. The part I struggled with was the systems interview. It involved a very specific modeling problem that didn't resemble the general patterns I expected. Unless I'd previously b…

RejectedTechnical Screen0
CrowdstrikeSoftware Engineer
Reported Mar 2026

Crowdstrike Software Engineer interview with seven difficult coding questions

After applying, I went through an earlier pipeline that included college-placement-style steps and then an online assessment. The multiple-choice section was manageable for me, but the assessment overall felt harder than I expected, especially since the role was for an internship. The biggest problem was the mix of questions. I could solve the multiple-choice problems, but the seven coding questi…

Online Assessment0
DiscordSoftware Engineer
Reported Mar 2026

Discord Software Engineer interview: relaxed recruiter screen

I had a low-stakes, recruiter-first experience for a Software Engineer role, with a quick and mellow timeline. The recruiter screen was a relaxed conversation about my background and why Discord. We also discussed the team and the hiring motivation, and the overall mood was friendly and calm. I didn’t receive an offer. The stage felt easy and conversational, but it didn’t lead to any further move…

HR Screen0
BoxSoftware Engineer
Reported Mar 2026

Box Software Engineer interview: React todo list and full-stack tasks

My early Box process felt smooth and organized. I started with a recruiter screening where I introduced myself, walked through my job history, and shared my expectations for the role. The recruiter was understanding and helpful, and answered my questions as they came up. The technical part moved into practical frontend work. I fixed a dropdown implementation on the frontend and then built a simpl…

HR Screen0
DropboxSoftware Engineer
Reported Mar 2026

Dropbox Software Engineer interview: OA, phone screen, and delayed feedback

The early stages of my Dropbox process were the most frustrating. I had an OA and then a phone screen where the HR contact didn’t really dig into my background or ask many questions about me. Most of the call was about next steps, and then the process went quiet. What threw me off was how poorly the later communication matched what I was being told. I was repeatedly led to believe things were goi…

RejectedOnline Assessment0
Glean (CA)Solutions Engineer
Reported Mar 2026

Glean (CA) Solutions Engineer hiring manager interview rescheduled

My process started well. The team was responsive early on, and after the initial setup, everything seemed to move smoothly. During the hiring manager portion, though, the interviewer joined about 55 minutes late, which forced a reschedule. I completed the interview after that, but then I never really heard back from the recruiter or hiring manager. I followed up multiple times and received no sta…

Other0
VoleonData Scientist
Reported Mar 2026

Voleon Data Scientist interview focused on live coding

My interview process focused heavily on live coding rather than a lot of conversational questions. The main topics were Python operations and basic statistics and probability. The way they tested me made it feel like they wanted to see how I actually manipulated data instead of hearing me discuss it abstractly. I expected straightforward technical work. The coding itself didn't feel impossible, b…

0
DropboxProduct Manager
Reported Mar 2026

Dropbox Product Manager take-home case and presentation

After a recruiter screen, I moved into a sequence that increasingly felt like a full product loop. It included a hiring manager conversation, several meetings with product and other stakeholders, a take-home product case study, and a final presentation. The process took about a month. I was told it would be fast, but scheduling became stop-and-start, with meetings being moved on short notice. The…

HR Screen0
CrowdstrikeSoftware Engineer
Reported Mar 2026

Crowdstrike Software Engineer interview: recruiter redirect after a 10-minute delay

My first step with CrowdStrike was a recruiter call over Zoom. The interviewer joined almost 10 minutes late, which made the start a little awkward, but they were professional and polite once we began. We covered the usual basics about my background and work history, and the conversation stayed fairly light. What stood out was that they asked whether I might be a better fit for a similar role on…

0
AsanaSoftware Engineer
Reported Mar 2026

Asana Software Engineer interview: six-step Salesforce-focused process

My interviews followed a longer, structured process with six steps and plenty of feedback between rounds. Everyone I spoke with was professional and attentive, and the process never felt chaotic or improvised. The technical portion was for a role related to Salesforce development. The topics were what I expected: async processes, bulkification, trigger contexts, and the relevant syntax. The round…

0
MercorSoftware Engineer
Reported Mar 2026

Mercor Software Engineer interview through an adaptive AI platform

My interview took place entirely through an AI platform. It asked questions based on what I submitted and how that information aligned with the job description. Instead of typing answers, I recorded live audio and video responses while the AI monitored me. The most important thing for me was keeping my answers consistent with what I had already told it about my background. The AI kept tying its q…

Other0
ZiplineSoftware Engineer
Reported Mar 2026

Zipline Software Engineer interview: project deep dive and technical discussion

My process began with straightforward introductions. The interviewer first walked me through the role description, and we then discussed my resume and portfolio in more detail. From there, the conversation shifted to technical questions. I had enough time to answer them before we returned to company-related questions that came up during the discussion. Another part of the process focused closely…

0

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