Interview Experiences

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

Share yours, earn XP

4437 stories

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

IMCSoftware Engineer
Reported Jul 2025

IMC Software Engineer home assignment and code review

I started with a home assignment that was split into two parts. They estimated about six hours of work and gave me three days to complete it, so it felt manageable at first. The first part involved implementing something straightforward, along with smaller requirements such as writing a README and adding unit tests. Some of the solution requirements felt subjective and depended on the approach, w…

RejectedTake-home Project0
DropboxProduct Manager
Reported Jul 2025

Dropbox Product Manager interview: offer withdrawn after VP round

My loop started with a long setup: a recruiter call, followed by Zoom conversations that combined case-study work with situational questions. I spoke with a hiring manager and then had a more technical conversation with an engineering manager. After that came a presentation-focused stretch. I met with several product managers to present a case study and also had a culture discussion with product…

WithdrewHR Screen0
GarminSoftware Engineer
Reported Jul 2025

Garmin Software Engineer interview with two-hour theory-heavy onsite

I interviewed for a mid-level .NET and Software Engineer type role at Garmin, and I felt the process didn't match my seniority level or the time I put into it. The in-person technical interview lasted two hours and focused heavily on theory rather than problem solving. I missed a few questions but otherwise did okay. Afterward, I was told they really wanted someone senior for a mid-level position…

RejectedOnsite0
SmartsheetAccount Executive
Reported Jul 2025

Smartsheet Account Executive interview: concern about being "a thread"

My process started with an interview with the line manager. I then met with an EMEA sales manager and sat down with a colleague. The early rounds felt straightforward, and I got the sense they were trying to understand my experience and whether I'd fit the team. The tone was casual, with more discussion about where I'd worked and what I'd done than any kind of tricky assessment. The colleague rou…

Other0
AKUNA CAPITALSoftware Engineer
Reported Jul 2025

AKUNA CAPITAL Software Engineer HackerRank OA, coding rounds, and final day

I went through an OA and then a series of technical rounds that ended with a demanding final day. The initial HackerRank assessment was followed by an exchange-engine-style coding focus in a later interview, where I had to implement a simplified version and explain what I was doing as I went. By the final stage, the interviews were intense and back-to-back. There were four in a row, including tec…

Online Assessment0
DoorDashData Scientist
Jul 2025

Five Onsite Rounds, Rejected After a Metrics-Heavy Loop

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

RejectedOnsiteXP0
SnapchatTechnical Program Manager
Jun 2025

Seven Rounds Over Two Months, No Offer

Sharing my Snap TPM interview from a while back. Round 1 with the HM: A quick 30-minute chat with the hiring manager, mainly talking through two projects I'd worked on before and digging into the details. They also gave me a heads-up on what to focus on in each of the following rounds. Round 2, with the HM again: This round was more free-form — the HM asked a wide range of questions covering stat…

RejectedOnsite0
Capital OneProduct Manager
Jun 2025

A Four-Round Power Day

Interview timeline: 5/14 recruiter call 5/27 first round — Product Mini Case 6/4 Power Day 6/6 recruiter notified me I passed *There were two weeks between the recruiter call and the first round because the team wasn't scheduling interviews that particular week. Product Mini Case (1 hour) Mainly an interviewer-led product casing session. The recruiter told me in advance they'd pick one of three C…

OfferOnsite0
xAISoftware Engineer
Jun 2025

Three Onsite Rounds, Caught My Own Bug

A premium story — unlock it to read the full loop.

OnsitePremium0
ChimeProduct Manager
Reported Jun 2025

Chime Product Manager interview with two panels and a 90-minute PRD exercise

My process moved quickly once it started, but the bar felt high and a few details didn't land the way I expected. I went through a recruiter screen, then a hiring director conversation, followed by two panel interviews. The first panel went reasonably well, and I got good feedback. The second was rougher for me. There was also a PRD writing exercise that took about 90 minutes, although it sounded…

RejectedHR Screen0
DiscordSoftware Engineer
Reported Jun 2025

Discord Software Engineer interview: technical screen felt pointless

I had a Discord interview where I followed the instructions closely but still didn't progress, which left me frustrated with the technical screen. The recruiter screen involved slow scheduling and initial coordination. During the technical screen, I solved and handled what the interviewer asked, but the conversation felt "pointless," with little discussion or flexibility. Although I had a good te…

RejectedHR Screen0
ChimeSoftware Engineer
Reported Jun 2025

Chime Software Engineer interview: React and JavaScript component task

I faced a front-end-focused technical challenge centered on building React/JavaScript components and implementing the data logic behind them. In the first round, I worked in a shared virtual environment to create components in a React/JS app. The components had to render data, and I had to implement the logic that processed the data before rendering. The UI scaffold was already provided. The diff…

Technical Screen0
DiscordSoftware Engineer
Reported Jun 2025

Discord Software Engineer interview building a multi-client socket chat server

I was evaluated on building a chat server over sockets. The process felt practical and hands-on, even though I didn't move forward. During the recruiter and setup stage, I was told to prepare for a chat app using TCP clients and sockets. I practiced with the resources provided. In the live coding interview, I implemented a server that could handle multiple clients. I was allowed to look up docume…

RejectedTechnical Screen0
GarminSoftware Engineer
Reported Jun 2025

Garmin Software Engineer interview focused on HR, compensation, and fit

I interviewed for a Software Engineer role at Garmin. The first round was mostly about HR, compensation, and fit, and it ended quickly. The HR phone screen covered my resume and behavioral questions, with a strong focus on motivation and discipline. There was no offer. In one case, the salary discussion didn’t align, and in the other, I didn’t continue after the early HR fit check. Location: Olat…

HR Screen0
DatavantSoftware Engineer
Reported Jun 2025

Datavant Software Engineer interview disrupted by rescheduling

The part that defined my experience wasn’t the interviews. It was the coordination. I was scheduled for an HR screen and then a technical screen, but rescheduling became a mess. It took about two weeks and several different coordinators to move the interview. On the day of the rescheduled interview, I arrived early, only for the interviewer not to show up. The recruiter and coordinator didn’t res…

HR Screen0
LinkedInMachine Learning Engineer
May 2025

K-Means Stopping Criteria May Have Led to a Downlevel

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

Technical ScreenXP0
Chainlink LabsSoftware Engineer
Reported May 2025

Chainlink Labs Software Engineer interview: multi-stage process with system design and executive discussion

My process felt long and multi-stage, with several steps to narrow things down. It started with recruiter touchpoints, followed by several technical interviews with engineers. The difficulty was serious rather than casual. I worked through algorithm questions and then moved into system design, including distributed-systems concepts. As I progressed, the technical rounds became more focused on arc…

RejectedTechnical Screen0
GustoSoftware Engineer
Reported May 2025

Gusto Software Engineer interview, take-home and pair session

My process felt rigorous and time-heavy. It stood out because it involved more than a single technical screen, with multiple signals being collected. I was surprised by how much effort the interview required overall, including a take-home component, follow-up work, and extended technical work that didn't feel proportional to the compensation. The questions were framed as "real work," but they wer…

OfferTake-home Project0
RoktSoftware Engineer
Reported May 2025

Rokt Software Engineer interview with coding, system design, and behavioral rounds

My process dragged on much longer than it should have. Recruiters were difficult to reach and gave me incorrect information about what the interviews would involve. Some interviewers also came across as though they didn't want to be there. At times, the whole process felt cold and stressful instead of inviting. Communication problems kept making the process feel unreliable. In some interviews, th…

No responseOther0
RoktSoftware Engineer
Reported May 2025

Rokt Software Engineer interview with a full-day bar raiser

The later stage became the most memorable part of my process, and not in a good way. After the earlier rounds, I was brought into an Amazon-style bar raiser interview. The tone felt scripted and as if the decision had already been made. The interviewer began by asking me to walk through a specific period from my resume. They mostly stayed quiet and gave very little feedback while I spoke. There w…

Other0

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