Real, anonymous reports from people who interviewed for Software Engineer at Quinstreet, newest first and distilled into what to expect across the loop.
Get your personalized Quinstreet 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.
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.
At one point, the process dragged long enough that it felt like I was being ignored on purpose after jumping through hoops. In another stretch, I got an immediate rejection message after the interview, even though I’d walked away feeling confident. I’d been interviewed on JavaScript, Vue, HTML, and CSS, and the next-day outcome felt abrupt and not handled with much care.
> 1 year
Average Positive Foster City, CA
I applied through Craigslist, and the first step was a phone interview. After that, I had a technical phone interview where the conversation leaned more toward problem-solving than pure background chat.
A short time later I was sent a written test by email, which felt like a distinct checkpoint before I moved on. The next stage was an onsite session that lasted about three hours. During that time, I worked through a technical question and answered it on a whiteboard, which made the interview feel very hands-on and slightly less abstract than the phone rounds.
> 1 year
Average Neutral Foster City, CA
I went through a fairly tedious interview process, and the thing that stuck with me most was how drawn out it felt. I remember thinking it would’ve be…
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 & Timeline
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.
HR screentechnical roundstimeline
Technical Focus Areas
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.
JavaREST APIsLeetCode
Behavioral & Resume Discussion
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.
behavioralresume walkthroughSTAR
Assessment Components
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.
written testtimed assignmentassessment
Communication & Feedback
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.
communicationfeedbackcandidate experience
Overall Difficulty & Experience
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.