I had two rounds. The first one was an HR interview, and the second was a technical interview with a Staff Engineer. For the first round, he didn't even know what role I was being interviewed for, whether it was for DEV or QA. Zscaler won't find good candidates if they keep putting him as an interviewer.
It was scheduled for 45 minutes (coding + technical). He took 43 minutes for the technical portion. He came with pre-fixed words in networking and kept disapproving until he got the exact word from the candidate. This will never work. You have to check the person's overall understanding and the experience they have in that area.
After 43 minutes, he gave a coding problem: finding the longest matching substring in two strings. When I started writing the code, after a few minutes, he kept interfering and not letting me finish the code or think. He kept asking why I wrote it that way and so on. You have to give enough time for the candidate to finish the code, at least 15 minutes, and then you can ask about the workflow.
Networking concept and coding.
Finding the longest matching string in two given strings.
The following metrics were computed from 2 interview experiences for the Zscaler Senior Software Engineer role in United States.
Zscaler's interview process for their Senior Software Engineer roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having mixed feelings for Zscaler's Senior Software Engineer interview process in United States.