A recruiter found me on Hired, then reached out on LinkedIn, which I thought was odd, perhaps to skip out on paying Hired.com.
The recruiter provided good information, explained the role, and talked about the process, which involved a coding challenge, then an onsite interview.
The recruiter asked a few trivia questions, then sent a link to a CodeSignal test. It was a 90-minute timed test with two medium LeetCode questions and a SQL stored procedure question combining three tables and performing counts and aggregates – not trivial.
Overall, it was more difficult than the Amazon interview process. I don't know how you could pass that without having seen both coding challenges before.
IMO, it's a way too high a bar for a company like Zoom, which sounded like it was in chaos with re-orgs and replacing an entire 500-person engineering organization from China with US-based employees. I suspect there is some gatekeeping going on with engineers not being happy that so many people were getting the hook and replaced wholesale.
LeetCode: Making File Names Unique
SQL stored procedure to aggregate data from 3 tables and calculate remaining available seats, similar to one on Chegg.
"You're working on the tech support team of an airline company, and your boss has asked you to implement a feature that shows the number of available seats on every flight.
Information about the airline is stored in three tables."
The following metrics were computed from 1 interview experience for the Zoom Java Backend Engineer, Platform role in San Francisco, California.
Zoom's interview process for their Java Backend Engineer, Platform roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Zoom's Java Backend Engineer, Platform interview process in San Francisco, California.