GeeksforGeeks Question · Jun 2025

ZOHO Interview Experience for Fresher 2025 {Offcampus}

SWE Phone Screen Easy

Question Details

Hey everyone! I recently appeared for the Zoho off-campus drive held on April 4th, and I wanted to share my experience here. The drive saw a huge turnout of around 1500+ c...

Full Details

Hey everyone! I recently appeared for the Zoho off-campus drive held on April 4th, and I wanted to share my experience here. The drive saw a huge turnout of around 1500+ candidates, and by the end, only about 10–12 students were shortlisted. Though I couldn’t make it past the third round, I learned a lot and hope this post helps someone preparing for it in the future. Recruitment Process Overview: Aptitude + Java Snippets Coding Round Low-Level Design (LLD)

Round 1 Aptitude + Java Snippets This was the first and major filtration round.
1. Total Questions: 20 10 Aptitude Questions: Medium level (time, speed, probability, logical reasoning) 10 Java Code Snippet Questions: Tough and conceptually heavy 2. Duration: 75 minutes 3. Level: Tough
4. Shortlisted Candidates: Only 90–100 from 1500+ Tip: Make sure you’re strong in both logic-building and Java fundamentals. And yes, practice aptitude thoroughly — it was definitely the toughest round.

Round 2 Coding Round This was a coding round with 7 questions of medium level. Topics Included: Trees (e.g., Validate BST) HashMaps Arrays & Strings Sliding Window problems (both fixed and variable size) Questions Asks: Validate BST length of longest substring having distinct characters Check palindrome FInd first missing Positive Number of substring having exactly k characters Find the first non repeating character in a string in 1 pass Obstacles: Around 40–50 candidates cleared this round. Tip: Focus on conceptual clarity and edge case handling. Practicing on platforms like GeeksForGeeks really helps here.

Round 3 Low-Level Design (LLD) This round was unexpectedly challenging. Design a Task Manager application, and the interview was structured in progressive steps: Starting from basic design Adding persistence using local file storage Handling multiple edge cases and improving functionality step by step Obstacles : Only 10–15 students made it to the next technical face-to-face round mostly all of them got selected ig. Additional Tips Prepare well for Aptitude: This is the most difficult and most important round. LLD Practice is essential : Go beyond just DSA. Get Comfortable with online IDEs: You'll be expected to code in them during interviews. Stay Consistent and Positive : Even if it doesn't work out, every experience counts. Final Outcome Unfortunately, this is where my journey ended. Despite performing decently, I wasn’t shortlisted after LLD. I noticed that most of the candidates selected for the

next round were from Tamil Nadu , and while it may have been coincidence, I felt there may have been some bias — especially considering that a few others and I implemented almost the same solutions as some of the selected candidates. But that’s life — sometimes it's about more than just the code.

Free preview — 6 questions shown. Unlock all Zoho questions →

About This Question

This is a reported interview question from a zoho interview for a swe role during the phone screen round reported in 2025.

It covers the following topics: Two Pointers, Trees, Strings, Sliding Window, Arrays, Binary Tree, Sql, Probability Stats, Hash Table .

Difficulty rating: Easy

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.