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

TwitchSoftware Engineer
Reported Apr 2026

Twitch Software Engineer interview with an unexpected behavioral call

I went through Twitch's early pipeline for a Software Engineer role, starting with a Codesignal pre-screen to earn an invitation. The behavioral intro call caught me off guard, and I didn't progress. The Codesignal pre-screen was a coding assessment. The intro and recruiter call focused on behavioral questions I hadn't expected, and I felt that my answers weren't strong. I didn't advance. My take…

RejectedOnline Assessment0
StubhubSoftware Engineer
Reported Apr 2026

Stubhub Software Engineer interview with repeated scheduling problems

The process started with scheduling, and it quickly became clear that it wasn't being handled with much care. The recruiter didn't show up for the originally scheduled interview at all. After I reached out to reschedule, I didn't get a real response. I joined the rescheduled call anyway, only for the recruiter to arrive late and act as if the situation was an inconvenience rather than something t…

RejectedHR Screen0
ZscalerSoftware Engineer
Reported Apr 2026

Zscaler Software Engineer interview with a 75-minute DSA round

After an online assessment, I went through pre-interview sessions about Zscaler's journey and the interview process. They helped me understand what the company was looking for and what the next steps would feel like. The technical interview lasted about 75 minutes and focused mainly on medium-level DSA and problem-solving. The interviewer was genuinely friendly, which helped me think more clearly…

Online Assessment0
Drw HoldingsQuantitative Analyst
Reported Apr 2026

Drw Holdings Quantitative Analyst timed probability assessment

I started with a timed online math and probability assessment. The questions felt genuinely hard, and the time limit was strict. My impression was that it tested how quickly I could work through probability mechanics. When I didn't make it through that stage, the process effectively ended there. In another attempt, I got further and kept running into probability and options concepts. After an ini…

Online Assessment0
DocusignSoftware Engineer
Reported Apr 2026

Docusign Software Engineer interview: API script and HackerRank-style exercises

My process was shorter and heavily front-loaded. It began with a quick recruiter screen, then moved into a panel-style technical evaluation. The questions covered coding and system design, and nothing felt wildly unexpected. They were standard areas they wanted to see me handle calmly. The process continued in a way that felt somewhat drawn out but still organized. I had four interviews in total,…

HR Screen0
NavanSoftware Engineer
Reported Apr 2026

Navan Software Engineer: four-interview onsite for a fullstack role

I went through a fairly structured sequence for a fullstack role. After the earlier steps, I had a frontend-focused round, then a hiring manager discussion, and eventually an onsite with multiple interviews. The frontend round focused specifically on that part of the stack, while the hiring manager conversation centered on my experience and how it matched the role. The onsite was the longest part…

Technical Screen0
GrammarlySolutions Engineer
Reported Apr 2026

Grammarly Solutions Engineer interview with a presentation and live demo

I went through an organized hiring process that lasted several rounds and felt professional from start to finish. Communication stayed consistent. The recruiter and hiring team set expectations early, followed up on timelines and next steps, and kept me informed after each stage. Each conversation had a clear purpose. There were about five to six rounds overall, and the team explained what they w…

Other0
ZscalerSoftware Engineer
Reported Apr 2026

Zscaler Software Engineer interview with three to four DSA questions

I was asked to take a coding test, and it ended up having roughly three to four questions. The main topics were the DSA areas I expected, including graphs, dynamic programming, and trees. I was also able to choose the language I wanted from Python, Java, or C++. I didn't get an offer, but the experience felt like an average-difficulty coding screen rather than something unusually tricky or obscur…

Online Assessment0
KlaviyoFull Stack Engineer
Reported Apr 2026

Klaviyo Full Stack Engineer interview with API design and system improvement rounds

My first contact was a quick recruiter screen. After that, I received the CodeSignal link for the online assessment. Once I completed it, the process moved into a longer onsite structure covering past work, technical thinking, and collaboration. The onsite included several technical and behavioral interviews. In one round, I went deep into past work and system design decisions, explaining the arc…

HR Screen0
DocusignSoftware Engineer
Reported Apr 2026

Docusign Software Engineer interview with timed DSA and DBMS problems

My process quickly became an assessment-style experience. I completed two closely related DSA problems in a timed format. One seemed to rely on graph-style reasoning. There was also a DBMS question that was trickier than the coding problems. It involved joins and aggregate-style thinking, so I had to slow down and pay close attention to what the question was asking. Recruiting coordination was an…

RejectedOnline Assessment0
GrammarlySoftware Engineer
Reported Apr 2026

Grammarly Software Engineer: technical screen, CS fundamentals, backend, and project walkthrough

The process was structured and moved at a steady pace. Before my application was submitted, I completed an initial technical screen. Once the application moved forward, I had a recruiter screening. After that, I met with an interviewer for a computer science fundamentals assessment that lasted about an hour. I then had a backend engineering round that lasted another hour. The final part of that p…

Technical Screen0
DrwSoftware Engineer
Reported Apr 2026

Drw Software Engineer interview reaching the fourth technical round

I made it as far as the fourth technical round. The process felt like a series of technical screens that built on one another. Eventually, I reached a C++-focused interview with a C++ problem. After that, the conversation shifted to my personal projects, which was a welcome change from the problem-solving questions. I had already completed an HR call earlier in the process. Overall, the structure…

HR Screen0
Rocket LabSystems Engineer
Reported Apr 2026

Rocket Lab Systems Engineer interview with four rounds and a technical coding assessment

I had a fairly straightforward interview process. The steps felt organized, even though the timeline varied. It started with a recruiter conversation about behavioral topics and my background. The later rounds followed a simple structure. Overall, it seemed to involve four rounds, and there wasn't a self-style presentation unless you were interviewing for an internship track. The technical portio…

HR Screen0
AKUNA CAPITALQuantitative Analyst
Reported Apr 2026

AKUNA CAPITAL Quantitative Analyst: Probability, Math, and In-Office Final Round

I went through a multi-round process that ended with an in-office final step. Before that, the early stages felt like a series of online hurdles that filtered people quickly. Once I reached the last round, the environment felt supportive. Everyone I met in person was nice and made it easier to focus. Probability and math came up repeatedly on the technical side. In the later stages, I was asked m…

RejectedOnline Assessment0
ZscalerSoftware Engineer
Reported Apr 2026

Zscaler Software Engineer interview: four DSA questions in an online assessment

I went through an online assessment with four DSA questions covering easy, medium, hard, and more complex material. It felt like a filter: if I cleared that set, I'd move on to a video call. The process was tied to an off-campus program for the 2027 batch, so it felt structured around moving candidates through a pipeline rather than having a deep back-and-forth interview. I completed the set but…

Online Assessment0
DecagonSoftware Engineer
Apr 2026

CSAT Tracker Question on the Phone Screen

I interviewed for 45 minutes and got one question. I'd solved it before, but I still wrote two bugs. Luckily I caught and fixed both while testing, and it passed in the end. Thanks to the interviewer for going easy on me. The question was the one that comes up most often for the phone screen: design a customer satisfaction (CSAT) tracking class. Scores are fixed in the range 1 to 5. __init__(self…

Technical Screen0
MicrosoftMachine Learning Engineer
Apr 2026

Technical Screen Ended Early After a Broken HackerRank Link

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

RejectedTechnical ScreenXP0
WorkdaySoftware EngineerSenior+
Apr 2026

Downleveled After a Four-Round Onsite

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

OfferOnsiteXP0
ShopifyMachine Learning Engineer
Apr 2026

Four-Round Onsite, Rejected for Lacking Depth in ML System Design

The phone screen was pair programming, and you were allowed to use AI (they recommended using the Cursor IDE). It was a question I'd seen mentioned in other interview report threads — a shorten URL problem, similar to a LeetCode-style question. The interviewer added some follow-ups. Since AI was allowed, it wasn't too hard overall — communication mattered more, so understanding what the interview…

RejectedOnsite0
DoorDashSoftware Engineer
Mar 2026

Building a Dasher Payout API

I received the Code Craft task as a Dasher payout calculation API problem. Dasher Payout Calculation API Overview The prompt said that, as part of a migration from a monolith to a microservice architecture, the team was building a new Payments Service. My task was to implement the Dasher payout logic, which required calling an upstream dependency to retrieve the relevant data. Goal Create this en…

Technical Screen0

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