RepostedZscaler logo

Zscaler · OA → Phone screen → Onsite

In process

Zscaler UI and DevTest Rounds: 8 Experiences (Part 4 of 6)

Software engineer · InternshipBachelor's degreeSep 2026
Shared by

Zscaler India campus drives (2023 and undated) for Java, C/DevTest and UI roles: DSA plus MCQ OAs, C and networking basics, and live React work.

At a glance

  • Process: a HackerRank OA of about two hours mixing coding and MCQs (20, 21) → two technical interviews → a manager or HR round (21). The UI process took about 8–10 days end to end (21).
  • Asked recently: C, networking and OS basics with bit-masking and string tasks (20); JavaScript execution, Promises, async code, React error boundaries, polyfills and debouncing, plus a live React edit (21); Java basics, OOP and exceptions shown in code (18).
  • Difficulty: the Dev C / DevTest tech-lead round cut 13 shortlisted students to 3 (20); the second interviewer would not accept a Java answer in a C round (20).

Coverage: 8 Zscaler India campus candidates (reports 17–24). Three are current: a Java developer in Mohali (November 2023) and two undated campus reports, a Dev C / DevTest intern and a UI developer intern plus full-time hire. Five reports from January to September 2023 sit in History: general SWE, a C/DevOps SDE intern drive, UI frontend, UI DevTest and Associate SWE.

In this series

  • Part 1: the overview and the first timelines.
  • Part 2: more timelines.
  • Part 3: timelines up to 16.
  • Part 4 (current): timelines 17–24: Java, C/DevTest and UI roles, mostly 2023.
  • Part 5: timelines 25–32.
  • Part 6: 2019–2020 timelines 33–36.

What came up

Each of the 3 current reports is a different track, so the topics split by role: Java fundamentals (18), C with networking and OS (20), and JavaScript and React (21).

Questions we found

UI developer (report 21)

Question Reports Last seen
Write a Promise in JavaScript 1 —
Remove duplicates from an array, in JavaScript 1 —
Edit supplied React code in CodePair 1 —
React error boundaries, polyfills and debouncing 1 —
null vs undefined; local vs session storage 1 —
Why apply to frontend after a backend internship? 1 —

Dev C / DevTest (report 20) and Java (report 18)

Question Reports Last seen
Java basics, OOP and exception handling, with code 1 Nov 2023
A bit-masking problem and a string problem 1 —
A DSA problem that had to be in C 1 —

3 current candidate reports

18: Java developer, basics shown in code

Interview date: November 2023 · Role: Java Software Developer · Location: Mohali, Punjab · Process: Campus drive · Result: No offer

  1. Explain Java basics, OOP and exception handling.
  2. Back each concept with a small code example rather than a definition. The exact tasks and round order were not shared.

20: Dev C / DevTest intern and a C-language disagreement

Date: not given · Role: Dev C / DevTest Intern · Process: Campus · Result: Not stated

OA (120 minutes, HackerRank)

  1. Eighteen questions: three DSA (basic array work, a 2D array and a priority queue) and 15 MCQs on networks and Linux commands. Thirteen students were shortlisted.

Technical interview one (tech lead)

  1. Introduction and resume, C basics, then deeper networking and basic OS.
  2. A bit-masking problem and a string-manipulation problem (not shared). Only three candidates moved on.

Technical interview two (senior technical manager)

  1. A DSA problem to be solved in C. Without hands-on C practice, the candidate used Java, and the interviewer did not accept it.
  2. OOP, the resume and hobbies.

21: UI developer intern plus full time: JavaScript and live React edits

Date: not given · Role: UI Developer Internship + FTE · Process: On-campus · Result: Selected, about 8–10 days in total

OA (about two hours)

  1. HTML, CSS and JavaScript MCQs, three coding questions and a DOM-manipulation task with several tests. Everything passed except one DOM test.

Technical interview one

  1. Internships and a project; HTML and CSS questions; how JavaScript runs.
  2. Write a Promise in JavaScript, with follow-ups, then asynchronous programming.
  3. Remove duplicates from an array. The interviewer wanted JavaScript; the candidate only knew the C++ approach and explained it, which was accepted, and the interviewer showed the JavaScript version.

Technical interview two

  1. Rapid-fire React, CSS and JavaScript: error boundaries, polyfills, debouncing, null versus undefined, and local versus session storage.
  2. Edit supplied React code in a HackerRank CodePair session; the candidate finished the changes.

Manager plus HR (about 40 minutes)

  1. Why a backend intern applied for frontend, the internship project, and basic HTML, CSS, JavaScript and React. The selection list came four or five days later.

Common questions

What is on the Zscaler campus OA?

A HackerRank test of about two hours mixing coding and MCQs: three DSA tasks plus networking and Linux MCQs for Dev C / DevTest (20); three coding tasks, a DOM task and web MCQs for UI (21).

What does Zscaler ask UI developer candidates?

JavaScript execution, Promises and async code, React error boundaries, polyfills, debouncing, browser storage and a live React edit (21).

Can you use any language in a Zscaler C interview?

Not in report 20: the senior manager expected C and did not accept a Java solution.

History (before Nov 2023)

These five reports are older than three years. They count toward this part but stay out of the summary and tables above.

H23: UI DevTest summer intern with DSA, SQL, UNIX, Git and Postman

Report date: September 2023 · Role: UI DevTest Summer Intern · Process: On-campus · Result: Selected, later a PPO

  1. OA: one DSA question in Java or JavaScript, one JavaScript implementation task and seven HTML/CSS/JavaScript MCQs (prompts not shared).
  2. Technical one (about 45 minutes): two DSA and two SQL questions; the resume and projects, including the candidate's own part in a group project; real-world uses of OOP; UNIX commands with syntax; Git commands; clone vs fork, pull request vs push, and resolving a merge conflict.
  3. Technical two (about 70 minutes): two more DSA and two more SQL questions; a deep dive into a hackathon project; HTTP error codes; C concepts; CRUD in Postman; the APIs used in projects; achievements and skills.
  4. No HR round. Selection came a week later, and a PPO followed the internship.

H17: General SWE, a competitive-programming OA, then projects

Interview date: June 2023 · Role: Software Engineer · Location: Bengaluru · Process: Campus · Result: No offer

  1. Eligibility was 60% or a 6.0 GPA.
  2. The OA had four competitive-programming questions on math, arrays, strings and graphs (prompts not kept).
  3. The next round focused on projects.

H19: SDE intern drive with separate C and DevOps tracks

Interview date: February 2023 · Role: SDE Intern · Location: Bengaluru · Process: College drive · Result: No offer

  1. C Development candidates could use only C or C++; DevOps candidates any language.
  2. Four OA coding questions; three areas were robot movement, cycle detection in a graph and basic bit manipulation.

H22: UI frontend, modified LeetCode tasks and design thinking

Offer date: January 2023 · Role: UI Frontend Developer Intern + FTE · Process: On-campus, tier-3 college · Result: Selected

  1. OA (90 minutes): eleven questions: a JavaScript task, two LeetCode medium problems with changed constraints, a DOM task in JavaScript, and HTML/CSS/JavaScript MCQs.
  2. Technical one (60 minutes): introduction and current internship, two DSA questions, then build or discuss a frontend app in any framework, with design and optimization follow-ups.
  3. Technical two (70 minutes): projects, another frontend design with optimizations, and JavaScript, React and React Native questions.
  4. HR (30 minutes): other offers, what the candidate knew about Zscaler, standard questions; they were told on the spot they were selected and discussed pay and location.

H24: Associate SWE fresher with matrix DP, locks and networking

Report date: January 2023 · Role: Associate Software Engineer, fresher · Process: On-campus · Result: Rejected

  1. Minimum-cost path through a matrix (movement rules not kept); a minimum-jumps (Jump Game) variant; Data Stream as Disjoint Intervals.
  2. Multithreading, semaphores, mutexes and critical sections.
  3. TCP and the OSI model; what happens after clicking a link; DHCP, IP, IPv4 vs IPv6, the data link layer and DNS.

Keep practicing

In this series: Part 1 · Part 2 · Part 3 · Part 4 (current) · Part 5 · Part 6

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.