Interview Experiences

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

Share yours, earn XP

8 stories

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

StackadaptSoftware Engineer
Reported Jun 2026

Stackadapt Software Engineer three technical rounds

After a recruiter reached out and invited me to schedule, the process quickly became a sequence of conversations that felt somewhat shuffled compared with what I had been told. I completed an HR screen, then manager and culture-style interviews, followed by three technical rounds. Each technical round combined live coding with a system design prompt. What caught me off guard was that the intervie…

HR Screen0
StackadaptSoftware Engineer
Reported Jun 2026

Stackadapt Software Engineer case study with unstable evaluation standards

My process started positively, but the final stage was deeply disappointing and left me uneasy about the evaluation standards. I was asked to complete what was presented as a case-study assignment for an enterprise agent solutions developer role. Although it was part of the interview, the work felt close to a real product and architecture project compressed into a short timeline. The most frustra…

Take-home Project0
StackAdaptSoftware Engineer
Apr 2026

An OOP Recipe and Inventory Coding Question

This was more of an OOP-style question, and the problem itself wasn't hard. You're given two concepts. Recipe stores the dish name, how long it takes, and the ingredients it needs. Supply stores ingredients and their inventory counts. A dish can also appear as an ingredient — for example, one dish in Recipe can be used as an ingredient for another dish. Based on this, you implement a series of fu…

RejectedTechnical 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
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
StackadaptAccount Executive
Reported Dec 2025

Stackadapt Account Executive interview with shifting final rounds

My experience with the recruiter and recruiting manager was frustrating from the start because the logistics never felt stable. I was repeatedly told I'd be meeting one person, only for the meeting to change at the last minute. It became hard to keep track of who the actual hiring manager was, especially after I went through multiple rounds with people who all had the same title. I also received…

RejectedHR Screen0
StackadaptAccount Executive
Reported Dec 2025

Stackadapt Account Executive interview: 10-day project and presentation

The process felt more rigorous than I expected from the outside. After a recruiter screen, I interviewed with a Director about a week later. The conversation focused heavily on scenarios, and I also got deeper industry knowledge questions than I was ready for. The pacing and format changed as the rounds went on. Next was a project and presentation round with a Director and a Manager. I had 10 day…

OfferHR Screen0
StackAdaptSoftware Engineer
Mar 2025

Windowed Map Coding Question, Rude Interviewer

The question was to implement a Windowed Map — a KV store with a time window. Data arrives at irregular intervals, and only the data within the most recent window size / time window is kept; anything outside the window is expired and no longer visible to the user. You need to implement 3 methods (as efficiently as possible): Get(key): if the key exists and hasn't expired, return the value; otherw…

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