Real, anonymous reports from people who interviewed for Frontend Engineer at Stackadapt, newest first and distilled into what to expect across the loop.
Get your personalized Stackadapt Frontend Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I made it to the later stages but didn’t reach the onsite final. My experience around the second round was pretty hands-on: I ended up working through what sounded like a feature addition along with debugging—finding bugs and getting new functionality wired up. It was still the right kind of momentum after that earlier step, because I could tell what needed to change and I was making progress.
That said, the bar felt tied to specific coding/problem work, and I also had another short technical session focused on algorithmic thinking: a single tree problem where I had to do the work and then talk through how to improve time complexity and how to design a data structure to filter duplicates. Even when I got the hang of the tasks and corrected issues, the process ended with rejection without feedback. I left feeling like I’d done the technical work, but I didn’t get any clarity on what missed the mark.
> 1 year
Difficult Neutral Toronto, ON
My process started with a fast connection between leadership and HR, and then it split into a behavior-light setup followed by technical evaluation. First, I was approached by a VP, and I was routed to HR for the opening round of general behavioral questions. After that, I moved into a technical interview with a senior front-end developer.
Later, I also went through a version that began with a short phone screen with the CTO, asked an algorithm/data structure question, and then progressed to a long on-site. On the on-site, a CTO explained different parts of digital advertising, and I met with engineering leadership for a whiteboard coding exercise and then another engineering-focused coding exercise. There was also a system design question, and the overall feel was that the on-site was made of multiple interviewers—several engineers asking me around a few LeetCode-style questions each.
> 1 year
Average Negative Canada
My first step was an initial phone screen that was very test-like. It was about 30 minutes, and it jumped straight into data structures and algorithm …
Unlock every Frontend Engineer interview experience
