The recruiter's phone screen really sold me on the company culture and the specific team I applied for. I was pretty excited at the prospect of working there after that call.
I had to wait about a week before scheduling the next round. It was supposed to be a chat with the hiring manager, I believe, but it was changed last minute to an interview with one of the engineers. This also turned out to be a partly technical interview, which I wasn't informed of prior. The interviewer had me write code in a Google Doc, which was not ideal.
I was then rejected a week after that interview.
I started out pretty excited about this position. However, a week of radio silence between the first interview and the scheduling of the second, as well as a week of radio silence between the second interview and the rejection, wore out some of the shine from my initial interest. I also answered all the technical questions correctly, so I'm a bit surprised and disappointed that I didn't get a chance at something more rigorous.
Write code to find the nth Fibonacci number.
Given a simple table schema, write some aggregation queries.
The following metrics were computed from 5 interview experiences for the Zoom Data Engineer role in United States.
Zoom's interview process for their Data Engineer roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Zoom's Data Engineer interview process in United States.