Real, anonymous reports from people who interviewed for Software Engineer at Quantcast, newest first and distilled into what to expect across the loop.
Get your personalized Quantcast 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.
After a recruiter screening and a take-home task that I found pretty easy, I did a follow-up call that lasted about an hour to talk through what I’d done and extend the work with new functionality. Then the process shifted into a more intense stretch: I had three back-to-back interviews that all felt like they were aiming for very high bar questions. The format was also a little off for me—each call usually had two people, with one actively speaking while the other just sat muted and watched.
The topics lined up with system-level depth and fundamentals: one round was system design, another focused on algorithms and data structures, and the third was behavioral. I remember feeling that they asked questions at a level people associate with top-tier companies, even though the compensation didn’t match that intensity. When it was all done, I ended up getting rejected, and what left me confused was that multiple interviewers seemed positive overall, yet the final decision still went against me—so it didn’t feel like it was purely technical.
7 months ago
Average Neutral United States
I went through a fairly typical recruiter-to-technical pipeline that heavily revolved around a take-home. First came a recruiter call, then I received the home task. After I completed it, I had an interview specifically to discuss the same assignment and extend it further. The take-home itself felt manageable, and the follow-up didn’t feel overly scary, but it was clear they expected me to explain my reasoning and walk through decisions as I built on the original work.
Once the take-home portion was cleared, the remaining steps became more traditional interviews: I had multiple final rounds that included system design, an algorithms-focused discussion, and another engineering-related conversation. Even though I felt like I answered well and the technical interviews took longer mostly because there was real back-and-forth, I still received a rejection email afterward. What bothered me most wasn’t the rejection by itself—it was the lack of closure. I asked the recruiter for technical feedback twice and didn’t get a response, and it ended up feeling unprofessional given how much time the process took.
9 months ago
Average Neutral London, England
My first step was a recruiter-style screening video call where we covered my background, talked about the company, and went through things like salary…
> 1 year
Average Negative Berlin
I went through a long, multi-phase interview process—seven stages total—that dragged out over roughly a month. It started with an online conversation,…
> 1 year
Difficult Positive London, England
I got routed into a code test that felt more demanding than I initially expected. I didn’t fully notice they were looking for a certain level of struc…
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
Recruiter & Initial Screening
The interview process typically begins with a recruiter screening call to discuss the candidate's background and expectations, followed by a take-home coding assignment that serves as a foundation for further discussions.
Candidates can expect multiple technical interviews focusing on algorithms, data structures, and system design, often involving live coding or discussions about their take-home projects, with an emphasis on structured problem-solving and reasoning.
Live codingAlgorithmsSystem design
Behavioral & Cultural Fit Interviews
In addition to technical rounds, there are behavioral interviews aimed at assessing cultural fit and interpersonal skills, where candidates are evaluated on their thought processes and team alignment.
BehavioralCultural fitTeam alignment
Interview Format & Structure
Interviews often feature a mix of one-on-one and panel formats, with some candidates noting a somewhat chaotic or unstructured experience, particularly during onsite interviews, which can include multiple back-to-back sessions.
Many candidates reported a lack of communication and feedback throughout the process, particularly after interviews, which left them feeling unvalued and confused about their performance and next steps.
Lack of feedbackCommunication issuesClosure
Overall Difficulty & Expectations
The overall difficulty of the interview process is noted to be high, with candidates feeling challenged by the technical questions and the level of depth expected, which may not align with the company's perceived compensation or culture.