
StackAdapt Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 36 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at StackAdapt.
Senior Software Developer
I was approached on LinkedIn for this role. The first stage was a 30-minute hiring manager interview, which was mainly focused on my past projects. After that, I got scheduled for a 1-hour screen interview. This interview had two parts: a LeetCode Medium problem and a System Design question. The interviewers didn't introduce themselves or explain their roles. They immediately started with the programming question, followed by System Design, which felt like a lot for just one hour. Unfortunately, I didn't pass this round.
- Can you discuss your previous projects?
- Could you solve LeetCode Medium 739, Daily Temperatures?
- How would you design a system to fetch URLs such that it does not hit the same host more than once per minute?
Application Developer
Interviewing with StackAdapt was a great process. I applied through their website after seeing the job on LinkedIn. My first meeting was with a recruiter, who asked about my background to see if I'd be a good fit. Next, I talked with the department manager about my past experience and projects. He then sent me a case study to complete, which had some questions that were easy to answer if you know the systems and languages. I put a lot of work into making it concise and professional. The final meeting was with the same manager and the Director to present the case study. They were welcoming and great during the presentation. Their questions were clear and they were interested in what I had to say. I received my offer the next day.
- Can you describe general questions about business application processes and potential issues, and how as a developer you would fix them?
- Tell me about your past experience and projects.
Software Engineer
Had an intro chat with the recruiter for about 30 mins, then another 30 min chat with the Engineering Manager where they asked some basic Javascript questions like console.log(Boolean({})). After that, there was a 1-hour FE pairing interview where I had to find bugs in a small React app and add a new feature. Didn't make it past this stage even though I fixed all bugs and added the feature. Recruiter communication was also a bit slow, had to follow up a few times.
- What is the output of console.log(Boolean({}))?
- What result does console.log(Boolean(NaN)) yield?
- Could you debug and fix the issues in the provided React code?
StackAdapt Software Engineer Interview Questions
Quoted word for word from StackAdapt interview reports.
“Given a text string and a two-character pattern string (both lowercase English letters), you can insert either character of the pattern into the text exactly once (at any position, including ends). What's the maximum number of times the pattern can appear as a subsequence in the modified text? A subsequence is formed by deleting zero or more characters from a string without changing the order of the remaining characters.”
Read reports →“What is the output of console.log(0, false)?”
Read reports →“What are the top 100 most frequent words in a list of 1 million words that contains duplicates?”
Read reports →“Find the k most frequent elements in a list and design a rate limiter”
Read reports →“Design a data structure to store a set of unique strings, supporting insert, delete, exists, and get uniform random element functions.”
Read report →“Can you generate all permutations of a given set of characters?”
Read report →“Can you list the various types of loops found in languages such as C?”
Read report →“How would you efficiently store and look up large, potentially intersecting IPv4 address ranges on limited hardware?”
Read report →“Can you design a data structure for storing unique strings that supports insertion, deletion, checking for existence, and retrieving a random element?”
Read report →Formats, difficulty and experience
Across all 36 StackAdapt interview reports.