Zoho Interview | Set 3 (Off-Campus) 2025
Interview Experience
Hi! I recently attended theZOHO off-campus drive, and I’m sharing my detailed experience below.
Round 1 Aptitude and Technical Interview 1Aptitude (1 hr 20 mins – 20 Quest...
Full Details
Hi! I recently attended the ZOHO off-campus drive , and I’m sharing my detailed experience below.
Round 1 Aptitude and Technical Interview 1 Aptitude (1 hr 20 mins – 20 Questions) Covered topics like averages, probability, time & distance, alligation & mixture, ratios, HCF & LCM, and a few logic puzzles. Technical (45 mins – 10 Questions) These were mainly C output-based questions. Practising from geekquiz.com and GeeksforGeeks was very helpful. Topics included: Pointers Strings Matrices Nearly 60 candidates were selected out of about 600. They didn’t just take the top 60 scores—there was a cut-off, and whoever cleared it moved on.
Round 2 Coding Round 1 Questions They Asked: Run-Length String Expansion Input like a1b10 ,
Output: abbbbbbbbbb Position-Based Sorting Sort values at odd positions in descending order, even positions in ascending order. Print X-Shaped Pattern from a String For odd-length strings, format characters in an X-pattern. Substring Search Implement a custom function to find the first index of a substring in a main string.
Return -1 if not found. Merge Two Sorted Arrays Without Duplicates Reverse Words Using Recursion Example:
Input - I love india ,
Output - india love I Although I was fairly well-prepared and managed to attempt most questions confidently, I hit a moment during Question 6 , where I got slightly stuck with recursive logic.
Outcome 19 candidates cleared this round and were selected for the next.
Round 3 Complex Coding (3 Hours) Task: Design a Call Taxi Booking Application You’re given: 6 Points (A to F), each 15 km apart Travel time and fare calculation constraints Logic for taxi allocation, based on availability, location, and earnings Rejection if no taxi is available Also had to: Handle multiple customer bookings Display taxi details This round was challenging due to the interlinked logic requirements. Only 9 candidates moved forward after successfully completing this round with accurate implementations.
Round 4 Technical Interview 2 Questions were focused on: Projects (be thorough with what you mention) Core concepts in C and OOP Databases Scenario-based logic puzzles
Round 5 Technical Interview 3 More in-depth questions: C, C++ and Java topics (e.g., threads, synchronization)
Follow-up on previous coding rounds A few more live problem-solving tasks and technical puzzles
Round 6 HR General conversation including: Strengths and weaknesses Resume discussion Work culture and career expectations Final questions from my side Family background Scenario-based hypothetical questions (e.g., "If you could change 3 things in India…") General traits and behavior-based questions Final
Outcome I didn’t get a direct placement from Zoho, but I did receive an internship offer , with the potential to convert into a full-time role based on performance. The third round was the most challenging , both in terms of logic and coding depth. If you're preparing for Zoho or similar companies, hands-on coding and strong fundamentals are a must. Thanks once again to GeeksforGeeks and other preparation platforms that helped me throughout this journey.
About This Question
This is a candidate experience report from a zoho interview for a swe role (intern level) during the phone screen round reported in 2025.
It covers the following topics: Oop, Strings, Sql, Recursion, Sorting, Math, Probability Stats, Arrays .
Difficulty rating: Hard
More Zoho Interview Questions
About Zoho Interview Reports
This question was reported by a candidate who interviewed at Zoho. 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 Zoho are the higher-signal extractions to take from this report.
For broader preparation context, the Zoho 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 Zoho reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Zoho 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 Zoho 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.