StackAdapt Interview Experiences

8 results

• 

  Stackadapt Software Engineer case study with unstable evaluation standardsStackadapt · Software Engineer · Take-home Project · Jun 2026

  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…

• 

  Stackadapt Software Engineer three technical roundsStackadapt · Software Engineer · HR Screen · Jun 2026

  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…

• 

  An OOP Recipe and Inventory Coding QuestionStackAdapt · Software Engineer · Technical Screen · Apr 2026

  Rejected

  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…

• 

  Stackadapt Software Engineer interview with four rounds and a three-hour sessionStackadapt · Software Engineer · Technical Screen · Mar 2026

  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…

• 

  Stackadapt Account Executive interview: three rounds with clear feedbackStackadapt · Account Executive · Other · Jan 2026

  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…

• 

  Stackadapt Account Executive interview with shifting final roundsStackadapt · Account Executive · HR Screen · Dec 2025

  Rejected

  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…

• 

  Stackadapt Account Executive interview: 10-day project and presentationStackadapt · Account Executive · HR Screen · Dec 2025

  Offer

  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…

• 

  Windowed Map Coding Question, Rude InterviewerStackAdapt · Software Engineer · Technical Screen · Mar 2025

  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…