RepostedZscaler logo

Zscaler · OA → Phone screen → Onsite

In process

Zscaler Intern, QA and SRE Rounds: 7 Experiences (Part 3 of 6)

Software engineer · InternshipBachelor's degreeSep 2026
Shared by

Zscaler India campus intern, QA and SRE reports from 2023–2024: a four-question OA with a copying check, then rounds on C, networking, Linux and SQL work.

At a glance

  • Process: a HackerRank OA (90–130 minutes, three or four coding questions, often with CS MCQs) and a plagiarism review, then two or three interviews of 30 minutes to almost 2 hours (10, 11, 12, 13).
  • Asked recently: networking and OS in all three current reports; linked lists and bit tricks (10); Python data cleaning and SQL (13); Linux boot and troubleshooting with no live DSA for SRE (11).
  • Difficulty: OA questions ranged widely, with the hardest compared to a competitive-programming problem rated around 2000 (10). Follow-ups were built from the candidate's own words, so short definitions did not hold up (11).
  • Practise first: Run-Length Encoding (the a1 rule from 15).

Coverage: India campus hiring: summer intern, SRE/DevOps intern, Associate Software Engineer / QA intern, C++ ASE intern + PPO, Java Dev / DevTest intern + PPO, DevTest engineer and Associate Software Engineer. Bengaluru and Gandhinagar where stated. Entries 10–16: three current reports (Dec 2023 – May 2024, plus one undated) and four from 2023 in History.

In this series

  • Part 1: OA formats, the compiled question bank, and entries 01–02.
  • Part 2: entries 03–09, 2023–2025: mixed-language OAs, C/C++ depth and a Java drive.
  • Part 3 (current): entries 10–16: C coding, SRE/DevOps fundamentals, QA and DevTest.
  • Part 4: entries 17–24, 2023: UI, DevTest, C development and ASE drives.
  • Part 5: entries 25–32, 2021–2022: SDE-1, Java API, QA and cloud operations.
  • Part 6: entries 33–36, 2019–2020 campus drives.

What came up

Every current report spent real time on networking and operating systems, whatever the role. Coding depth depended on the track: SRE had none live, QA had Python data work.

Topic Reports Last seen
Networking (TCP, DNS, TLS, subnets) 3 of 3 May 2024 (report date)
Operating systems and Linux 3 of 3 May 2024 (report date)
Linked lists and recursion 1 of 3 May 2024 (report date)
Bit manipulation 1 of 3 May 2024 (report date)
C string handling (IPv4 validation) 1 of 3 May 2024 (report date)
Python data cleaning 1 of 3 Dec 2023 (report date)
SQL 1 of 3 Dec 2023 (report date)
Projects and behavioral 1 of 3 Dec 2023 (report date)

A candidate can appear in more than one row; entry 11 is undated and counted.

Questions we found

Algorithms / Data Structures

Question Reports Last seen
Detect and remove a cycle in a linked list 1 May 2024 (report date)
Recursive Fibonacci with time and space analysis 1 May 2024 (report date)
Add two numbers with bit operations only 1 May 2024 (report date)
Validate an IPv4 string in C 1 May 2024 (report date)
A long linked-list operations problem 1 May 2024 (report date)
Python data cleaning: date formats, duplicates, slicing, CSV, sets, dictionaries 1 Dec 2023 (report date)
Prime-number program 1 Dec 2023 (report date)

SQL

Question Reports Last seen
Create a table; explain GROUP BY; return the max salary with employee name and ID 1 Dec 2023 (report date)

Behavioral (BQ)

Question Reports Last seen
How do you improve a weak skill? 1 Dec 2023 (report date)
What would you do if a manager did not recognize your work or kept overloading you? 1 Dec 2023 (report date)
Why this role? 1 Dec 2023 (report date)

3 detailed candidate timelines, loops, and screens

10: Summer intern: a copying check, C coding and linked lists

Report date: May 15, 2024 · Role: Summer Intern · Process: Campus hiring · Result: Not stated

  1. OA: four coding questions of widely varying difficulty, the hardest like a competitive-programming problem rated about 2000. Two solved fully, two partly. They warned that OA snapshots were reviewed for copying.
  2. Interview 1: introduce yourself (academics, grades, competitive programming, projects, stack); detect and remove a linked-list cycle; recursive Fibonacci with complexity; OS basics; add two numbers using only bit operations.
  3. Interview 2: finish a partly solved OA problem (with a little help); validate an IPv4 string in C, done with guidance since they knew little C; a long linked-list operations problem, partly solved; networking questions, where they said honestly that some were beyond what they had studied.

13: Associate SWE / QA intern: Python data work, networking and SQL

Report date: Dec 19, 2023 · Role: Associate Software Engineer / QA Engineer Intern · Process: On-campus · Result: Selected

  1. OA: about 150 shortlisted; 30 MCQs on networks, OS, DBMS and code snippets; four coding tasks (matrix transpose, array manipulation, a mean calculation and a hard string task they forgot). They solved three; friends with two also advanced.
  2. Interview 1 (about 1 hour, 34 students): screen-shared Python data cleaning: change a date format, remove duplicates, slice lists and strings, read and store CSV-style data, use sets and lists, print dictionaries several ways (one task's output was cut off in the report). They did not know Linux programming. Then DNS, TCP vs UDP, subnet masks, IPv4, NAT, retransmission, the handshake and why DNS uses UDP; then SQL: create a table, explain GROUP BY, return the top salary with name and ID, and keys and constraints.
  3. Interview 2 (about 65 minutes, 8 students): a working project's architecture, more networking and easy SQL, a prime-number program, how they improve a weak skill, what they would do if a manager did not recognize their work or kept overloading them, and why this role.
  4. Not among the two asked to a third round, they still made the final list of five.

11: SRE/DevOps intern: deep fundamentals, no live DSA

Report date: not given · Role: SRE/DevOps Intern · Process: On-campus · Result: Selected

  1. OA (2 hours, HackerRank): four coding questions (two easy, one medium, one hard) plus MCQs on networks, OS, DBMS and puzzles.
  2. Technical 1 (1 hour): Linux boot, memory management, processes vs threads and multithreading, HTTP, the TCP handshake, SSL/TLS, DNS, DHCP, basic Linux commands and troubleshooting scenarios.
  3. Technical 2 (1 h 45 min, three interviewers): more networks, OS, DBMS and Linux, with follow-ups built from their own answers. No DSA in either interview.

History (before November 2023)

These four reports are more than three years old, so they stay out of the counts and tables above.

12: C++ ASE intern + PPO: pointers, endianness and subnets

Interview date: Sep 2023 · Role: Associate Software Engineer, C++ Developer Intern + PPO · Process: On-campus · Result: Selected

  1. OA (130 min): about 600–700 eligible; four medium coding questions, all solved. Some who solved all four failed the plagiarism check. 27 advanced.
  2. Interview 1 (about 30 min): explain an OA solution; every TCP/IP layer and its protocols; the session layer and why encryption is needed; DNS in detail. 11 advanced.
  3. Interview 2 (almost 2 hours): C++ pointers (void, size by architecture, const pointer vs pointer to const, ptr + 10, why two pointers cannot be added) with small examples in CodePair; little- vs big-endian with a drawn byte map and a function to detect host endianness; given IP1, IP2, Mask1 and Mask2, decide if both are on the same network (classful handled, classless not, with hints).
  4. Five were asked to a third round, not them; they were still selected the next day with three of those five.

15: DevTest engineer: the a1 compression rule

Interview date: Sep 2023 · Role: DevTest Engineer · Location: Gandhinagar, Gujarat · Result: Accepted offer

  1. An OA, then three technical rounds: core fundamentals, DSA, and mixed.
  2. The saved coding task: a string compression variant where every run carries its count, so a single a becomes a1, with an output buffer twice the input length.

16: Associate Software Engineer: three OA questions, one broad interview

Interview date: Sep 2023 · Role: Associate Software Engineer · Process: Campus placement · Result: No offer

  1. Three OA coding questions; only 11 students reached the online interview.
  2. About an hour on networks, OS and C++ fundamentals; no individual questions were listed.

14: Java Dev / DevTest intern + PPO: three coding interviews

Interview date: May 2023 · Role: Java Dev / DevTest Intern + PPO · Location: Bengaluru · Result: No offer

  1. OA (90 min): three medium coding questions plus MCQs.
  2. Interview 1: networks and OS; a string + HashMap task; Two Sum in a binary search tree.
  3. Interview 2: pair with a target sum in a sorted array; search in a rotated sorted array.
  4. Interview 3: Balanced Parentheses plus a follow-up variation; more OS and networks.

Patterns across the reports

  1. A plagiarism review after the OA. 10 warned that OA snapshots were checked, and in 12 some who solved all four questions failed that check.
  2. Not being sent to round three was not a rejection. In 12 and 13, candidates left out of the extra round were still selected.
  3. Networking everywhere. TCP, DNS and subnets came up in 10, 11 and 13 regardless of role.

Common questions

Does Zscaler check the campus OA for copying?

Yes, in two reports: snapshots were reviewed (10), and some full scores were disqualified (12).

Does the Zscaler SRE intern interview include DSA?

Not live: both interviews were Linux, OS, networks and DBMS (11). The OA still had four coding questions.

What does Zscaler ask QA interns?

Python data-cleaning tasks, networking, SQL and a project walkthrough (13).

Keep practicing

In this series

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.