Real, anonymous reports from people who interviewed for Software Engineer at Zoom Communications, newest first and distilled into what to expect across the loop.
Get your personalized Zoom Communications 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.
The process stretched out over roughly three months and it honestly started feeling inconsiderate of my time. After an initial recruiter touchpoint, I went through a lot of steps that kept getting pushed forward—eventually landing on a presentation that required real prep and then a VP interview. Even though I felt the conversations were positive, the gaps between steps became harder and harder to tolerate, and it became difficult to get the recruiters to respond.
At one point I had a strong call with the VP, who told me the hiring manager or recruiter would follow up “very soon.” Nothing happened after that. When I reached out, I was just ignored, and even follow-ups didn’t change anything. It was also frustrating that status updates weren’t consistently reflected in their system.
2 months ago
Average Negative United States
My recruiter lined up a full slate that included time with the hiring manager plus five engineer interviews total, which meant I spoke to a group of people quickly and back-to-back. The overall vibe was mixed. One engineer felt like he’d already made up his mind before we really got started—he ended up spending less time with me than the session allowed and didn’t seem genuinely interested in understanding my background.
What really bothered me was that it felt like he hadn’t reviewed my resume before the conversation. The other parts of the loop went fine, but the whole experience narrowed in on one technical gap: WebRTC. I discussed SIP, RTP, and the ICE framework, and I also mentioned there were APIs you can call. I didn’t bring up DTLS or RTCP, and that omission ended up mattering a lot.
10 months ago
Difficult Negative San Jose, CA
I ran into the hardest part early: an online CodeSignal assessment. It was lengthy enough that the whole thing felt like it was designed to drain conf…
> 1 year
Average Negative Seattle, WA
The scheduling itself was already strange. I was told to set up my interview through an automated AI chat bot, and on the day of the virtual interview…
> 1 year
Difficult Negative United States
My process took a long time—around two months—and the main emotional weight came from the delays and uncertainty. Early on, recruiters and coordinator…
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 & Stages
The interview process typically follows a structured sequence, starting with a recruiter call, followed by technical interviews and sometimes a final behavioral round. Candidates experienced varying numbers of rounds, with some reporting as many as five distinct interviews.
StructuredMultiple roundsRecruiter call
Technical Assessments
Candidates faced a range of technical assessments, including online coding challenges that often resembled LeetCode-style problems, with a focus on algorithms and data structures. The difficulty and pressure of these assessments were noted as significant stressors, impacting candidates' confidence.
Coding challengesLeetCodeTechnical assessments
Communication & Follow-up
Communication throughout the process was inconsistent, with many candidates experiencing long gaps without updates or feedback, leading to feelings of frustration and uncertainty. Some reported automated rejection messages without any closure or explanation.
CommunicationFeedbackFollow-up
Interview Atmosphere
The atmosphere during interviews varied, with some candidates describing it as relaxed and supportive, while others felt it was adversarial or unprofessional, particularly when interviewers seemed unprepared or disengaged. This impacted candidates' overall impressions of the company culture.
AtmosphereSupportiveProfessionalism
Final Stages & Outcomes
Candidates often reported a lack of closure after the final stages, with many not receiving offers and feeling that the process did not respect their time or effort. The experience of being ghosted or receiving generic rejection emails was common, leaving a negative impression.
ClosureOutcomesGhosting
Preparation Insights
Candidates suggested focusing on specific technical areas, such as WebRTC, algorithms, and system design, while also being prepared for behavioral questions that assess cultural fit. Some wished they had better prepared for the technical gaps identified during interviews.