ZebraTechnologies Interview Experience for SD (Java) On-Campus
Interview Experience
There were three rounds for this internship and both were not very tough.
Round 1 [Resume Shortlisting]Around 70 people applied and 35-40 were shortlisted for interview.I ...
Full Details
There were three rounds for this internship and both were not very tough.
Round 1 [Resume Shortlisting] Around 70 people applied and 35-40 were shortlisted for interview. I included my four projects, internship which I did in my own university on a cycle management app and my profile of GFG.
Round 2 [Technical] Mode: [Online] Interviewer: [Team lead with 6 yrs of experience] Duration: [35-40 mins] Description: Introduction: He started with his introduction and then asked me to introduce myself. Technical Questions: List the technical question topics asked - Technical questions on Projects, DBMS, Data Structures Question 1: He deep dived into my projects, and asked questions on it. 1) What is hashing and how you have used it in your project - I told to hash the password strings. 2) Describe the process you used to hash your password - I told salt and pepper technique. 3) I used MONGODB in my projects, so he asked about MONGODB, explain collections and documents, explain the process of sharding, and why MongoDB. - I answered all as I was prepared for these questions and he was satisfied. 4) Describe the designing and the most difficult part of your chatting app - I had a project which was similar to whatsapp, so he dived into its designing and my experience while creating it. - I answered it by explaining everything verbally and he was satisfied. Question 2: He gave me simple data structure question as only 15 minutes we left 1) How would you calculate the max and second max element of the array, sorting and built-in functions not allowed, expected T.C = O(n) and space-O(1). - I answered it by taking two variables and a for loop. Overall Difficulty: This round was not much difficult.
Round 3 [Managerial/Technical] I got an email that I am shortlisted for the second round after two days and the second round is scheduled after three days. Mode: [Online] Interviewer(s): [Manager with 15 yrs of experience] Duration: [25-30 mins] Description: Introduction: Interviewer was very chill and started with his introduction and then I introduced myself and my skills. Technical Questions: List of technical question topics asked - Docker, Kubernetes, and some general questions He did not asked anything from my projects, I think he got a good feedback from the previous interviewer. Question 1: As I mentioned Docker and Kubernetes in my resume - 1) What is Docker, uses of it, why Docker, alternatives of Docker, DockerFile, Docker Image, Docker Containers - I answered all 2) What is Kubernetes, what is the use of it, alternatives of Kubernetes - I did not know the alternatives of Kubernetes, rest I answered all. 3) Some General questions like explain Git and GitHub. Behavioral Questions: List any behavioral questions asked - Some basic questions were asked, Question 1: What are you expectations from the company? Question 2: Strength and Weaknesses Overall Difficulty: This round was easy. End of the Interview: The ending 5 mins, I asked him about the company and he explained me about the products of the company and then I asked for a feedback and it was positive, He told me that I am well versed with my resume and the technologies but I should have worked on different Tech stacks and should not have focused only on MERN stack as all my projects were on MERN stack. Result But Hopefully I was one of the 3 people who got the internship offer out of 40 resume shortlisted people.
About This Question
This is a candidate experience report from a zebra interview for a eng manager role (intern level) during the phone screen round reported in 2024.
It covers the following topics: Strings, Networking, Stack Queue, Sorting, System Design, Arrays, Stack .
Difficulty rating: Easy
About Zebra Interview Reports
This question was reported by a candidate who interviewed at Zebra. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Zebra are the higher-signal extractions to take from this report.
For broader preparation context, the Zebra interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Zebra reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Zebra Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Zebra reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.