Zscaler data scientist interviews, as three candidates describe them, mix project deep dives with SQL, coding, and case studies. Their reports cover 4-5 rounds, uneven communication, and slow follow-up.
$158K
Avg. Base Comp
$237K
Avg. Total Comp
4-5 rounds
Typical Rounds
Not reported
Process Length
Across three candidate reports, the one thing every candidate describes is a project deep dive. One candidate says the hiring manager pushed hard on the details and decisions in their past work. Another calls a project-focused round among the best interviews they've had. A third was asked to talk through a project and answered some basic SQL questions. Prepare two or three projects you can explain end to end, including the trade-offs you made.
The technical screens differed by candidate. One candidate describes a HackerRank round with three advanced SQL queries that layered window functions and aggregations, plus a timed DSA section. Another, interviewing for a senior role, describes a Codepad round that asked for several machine learning algorithms implemented from scratch without libraries. A third found the SQL questions basic. SQL fluency and core ML implementation are both worth practicing.
Case studies appear in one account, with a hiring manager case study, a second case study with a peer team, and a final VP conversation on behavioral fit and a business case. That candidate was also asked on the spot about tuning LLM models, so be ready to reason aloud about unfamiliar ML topics.
Process quality varied. Candidates mention rescheduled rounds, repeated compensation questions, confusion over which rounds were already done, and long silences after the final interview. One reports roughly four weeks end to end. Keep notes of what you've covered with each interviewer, and follow up politely.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Zscaler process.
I got an interview call from HR first, and that conversation was mostly about the role, expectations, and my salary expectations. After that, the process moved into five rounds, but it felt pretty unclear from the start and the communication was not great. What stood out to me was that HR asked again about compensation after the first two rounds, which made the process feel a bit disorganized.
The actual interviews were not especially deep from a technical standpoint. I was asked about a project I had worked on, along with some basic SQL questions. There was no strong sense that the interviewers were aligned on how to evaluate the role, and a couple of the rounds got rescheduled, which added to the frustration. Overall, it felt more like a loose screening process than a structured data science interview. After finishing everything, I never heard back again, even after trying to follow up by email and phone. That lack of response was disappointing and honestly left a bad impression. If you are interviewing here, I would be ready to talk clearly about one or two projects and brush up on basic SQL, but also be prepared for a process that may not be very organized.
Prep tip from this candidate
Be ready to walk through your past projects clearly and concisely, since that came up directly, and make sure your basic SQL is solid. Also expect compensation questions early and possibly again later in the process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Zscaler
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Variable Error | |
| String Subsequence | |
| Swapping Nodes | |
| SFTP Pipeline | |
| LRU Cache 1 | |
| Singly Linked List | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Top Three Salaries | |
| Customer Orders | |
| Comments Histogram | |
| Closest SAT Scores | |
| Subscription Overlap | |
| First to Six | |
| Monthly Customer Report | |
| Upsell Transactions | |
| Experiment Validity | |
| Download Facts | |
| First Touch Attribution | |
| Random SQL Sample | |
| Compute Deviation | |
| Button AB Test | |
| Employee Salaries (ETL Error) | |
| String Shift | |
| Average Quantity | |
| 500 Cards | |
| Top 3 Users | |
| Raining in Seattle |
Synthesized from candidate reports. Individual experiences may vary.
Two candidates report starting with an HR call about the role, expectations, and salary. One says compensation came up again after the first two rounds, so have a consistent expectation ready. Another candidate's process opened with the hiring manager instead.
The screen appears to vary by candidate. One describes a HackerRank round with three advanced SQL queries using window functions and aggregations, plus a timed DSA section. Another describes a Codepad round that required implementing machine learning algorithms from scratch. Another reports only basic SQL questions.
Candidates report that project discussions took up a large share of the loop. One hiring manager round was built around a case study and probed the details and decisions behind past projects. Another candidate had two rounds focused on projects. Expect follow-up questions to get specific quickly.
One candidate describes a second case study with a peer team, then a final VP round covering behavioral and cultural fit alongside a business case. That candidate found it more conversational than the technical rounds. Other candidates did not describe this stage, so it may not apply to every role or level.
Outcomes differed. One candidate declined an offer, while two received no offer. Two of them describe long silences or stalled follow-up, and one was told to wait three more weeks and then heard nothing for about a month. Plan to follow up with your recruiter while waiting.
