Real, anonymous reports from people who interviewed for Software Engineer at ZoomInfo, newest first and distilled into what to expect across the loop.
After a recruiter call with the hiring manager, I ended up doing a pretty straightforward sequence: a technical screen where we mostly talked through my past projects, the role, and whether my resume aligned, then a couple more technical conversations. Those later rounds looked like a mix of coding-style problem solving and debugging questions, and they pulled in a blend of topics—JavaScript, Java, and SQL came up alongside JavaScript/SQL-style thinking. The whole vibe was mostly practical, like they were checking how I reasoned rather than expecting me to memorize anything.
My process started with an online coding assessment that had a strict clock on it. The prompt centered on problem solving with string or pattern matching—very similar to the easier end of LeetCode, with the focus more on approach than memorizing trivia. I remember feeling like the time limit mattered more than the raw difficulty, because it forced me to lock into a clean solution quickly.
The interview process typically starts with a recruiter call, followed by a series of technical interviews and a behavioral round, often spanning several weeks. Candidates noted variations in the number of steps and the pacing, with some experiencing a well-organized flow while others felt the process was lengthy and disjointed.
Candidates faced a mix of coding challenges, including algorithmic problems and practical database questions, often resembling LeetCode-style prompts. The focus was on problem-solving and reasoning rather than rote memorization, with some candidates finding the technical evaluations clear and others feeling they were overly verbose or domain-specific.
Behavioral rounds often utilized STAR-style questions to assess past experiences and fit within the team. Candidates reported that these discussions were generally respectful and aimed at understanding their approach to problem-solving rather than just technical skills.
There were mixed experiences regarding the clarity and consistency of evaluation criteria across rounds, with some candidates feeling confident in their performance while others sensed a lack of alignment in expectations. This inconsistency sometimes led to confusion about the reasons for rejection.
The overall atmosphere varied significantly, with some candidates describing supportive and engaging interactions while others felt rushed or disconnected. Positive experiences often highlighted a respectful and professional environment, whereas negative ones noted a lack of communication and clarity.
Feedback and follow-up communication post-interview were inconsistent, with some candidates receiving timely updates and others experiencing delays or a complete lack of response. This affected their overall impression of the process and left some feeling undervalued.