Real, anonymous reports from people who interviewed for Software Engineer at Stackadapt, newest first and distilled into what to expect across the loop.
Get your personalized Stackadapt Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
My process began in a way that felt positive, but the final stage ended up being deeply disappointing and left me uneasy about the evaluation standards. I was asked to complete what was framed as a case-study assignment for an enterprise agent solutions developer role. Even though it was presented as part of the interview, the experience felt close to real product and architecture work pushed into a compressed timeline.
The most frustrating part was the mismatch between what I thought I was being evaluated on and how the panel treated the discussion. I prepared according to the requirements as they were communicated, but during the final interview the panel seemed to expect me to infer additional priorities that weren’t clearly emphasized. Instead of sticking to stable, explicit criteria from the assignment, the conversation felt adversarial and overly focused on narrow details—like they were hunting for a reason to reject rather than assessing the work in good faith.
2 months ago
Difficult Positive Toronto, ON
After a recruiter reached out and invited me to schedule, the process quickly turned into a sequence of conversations that felt a little shuffled compared to what I was told. I did an HR screen and then I went through manager and culture-style interviews, followed by three technical rounds.
Each technical round mixed live coding with a system design prompt. What caught me off guard was how sometimes the interviewers seemed unsure about how to balance the two parts—whether they should focus on just one prompt or cover both in the same session—so I couldn’t always predict what would be asked next. The rest of the interviewers were generally fine, and the HR/manager calls felt more normal and conversational.
5 months ago
Difficult Neutral Canada
My interview felt intense from the start. I ended up with a setup that ran multiple rounds back to back—four rounds total, with one session lasting ar…
6 months ago
Average Positive Toronto, ON
My process mostly felt manageable, and the recruiter interaction set a good tone for me. The first technical part had a clear rhythm: I worked on codi…
8 months ago
Average Positive Canada
My early interviews started with a lot of confusion around clarity. During technical discussions, the interviewers’ accents were so thick that it was …
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Flow
The interview process often felt disorganized, with candidates experiencing confusion about the sequence of interviews and the expectations for each round. Many reported a mismatch between the stated format and the actual content of the interviews, leading to uncertainty about what skills were being evaluated.
DisorganizationInterview FlowExpectations
Technical Rounds & Content
Technical interviews typically included a mix of live coding and system design prompts, but candidates noted inconsistencies in how these were balanced within the same session. The difficulty level was often perceived as high, with time constraints making it challenging to provide polished solutions.
Live CodingSystem DesignTime Pressure
Communication Barriers
Several candidates faced communication issues, including interviewer accents and unclear prompts, which hindered their ability to respond effectively. This added stress and detracted from their performance during technical assessments.
CommunicationInterviewer AccentsClarity
Evaluation Criteria & Feedback
Candidates expressed frustration over unclear evaluation criteria, feeling that interviewers sometimes focused on narrow details rather than assessing overall problem-solving abilities. Feedback was often vague, leaving candidates unsure of their performance.
Evaluation CriteriaFeedbackAssessment Standards
Behavioral & Cultural Fit
While some interviews included behavioral questions, many candidates felt that these were insufficiently integrated into the overall process, leading to a lack of insight into cultural fit. The focus was primarily on technical skills rather than interpersonal dynamics.
Behavioral QuestionsCultural FitSoft Skills
Candidate Experience & Environment
The interview environment varied, with some candidates reporting supportive interactions while others felt the process was adversarial and stressful. Technical setups, such as coding in non-ideal environments, contributed to a negative experience for some.