Real, anonymous reports from people who interviewed for Software Engineer at Quinstreet, newest first and distilled into what to expect across the loop.
The process moved fast. I got contacted by HR and, within about a week, I ended up in a technical/behavioral interview sequence. In my timeline, it was quick enough that I could almost feel the momentum pushing me from one step to the next.
I went into the process expecting a normal progression—recruiter contact, interviews, and some kind of closure—but what I experienced was mostly silence. I completed multiple interview rounds, answered everything, and even followed up twice when nothing moved forward. Each time I was left without a response.
The interview process typically begins with an HR screen followed by a series of technical rounds, often moving quickly from one step to the next, though some candidates experienced delays and poor communication afterward.
Candidates reported a strong emphasis on core web technologies, including Java, Spring Boot, REST APIs, and front-end frameworks like React and Vue, with coding questions often resembling LeetCode problems.
Interviews included behavioral questions and detailed discussions about past projects, where candidates were expected to provide concrete examples of their work and problem-solving approaches.
Some candidates experienced a written test or timed assignment as part of the evaluation, which added a distinct layer to the interview process beyond live discussions.
A common concern among candidates was the lack of communication and feedback after interviews, with many feeling left in the dark regarding their status and outcomes.
While the technical questions were generally of average difficulty, the pacing and structure of the interview process contributed to a sense of fatigue and frustration for some candidates.