Zoho Software Engineer Interview Experience (2025) — Unconventional Process

I received an offer from Zoho last month for a Software Engineer position on their Zoho CRM team. The interview process was refreshingly different from the typical Bay Area tech companies — less LeetCode hazing, more focus on practical problem-solving and product understanding.

I started prepping for Zoho in August — honestly, I was nervous. Zoho has a reputation for asking unconventional questions, and I'd heard stories about their "think out of the box" approach. Here's exactly what happened.

Quick Stats

• Role: Software Engineer, Zoho CRM Platform
• Location: Chennai, India (onsite)
• Year: 2025
• Timeline: ~3 weeks from campus placement to offer
• Rounds: Written test → 2 technical interviews → 1 managerial round
• Difficulty: Medium — unconventional problem-solving
• Outcome: Offer accepted
• Compensation: ₹18 LPA base / ₹20–22 LPA total comp

I was a fresher from a tier-1 engineering college (IIT Madras). Zoho came to our campus for placements.

Stage 1: Written Test

The first round was a 2-hour written test on campus. It had three sections that were quite different from what I'd practiced.

Section A: Aptitude (45 minutes) This wasn't your typical quantitative aptitude. The questions were puzzles and lateral thinking problems:

• "If you have a 3-gallon jug and a 5-gallon jug, how do you measure exactly 4 gallons?"
• "A man pushes his car to a hotel and tells the owner he's bankrupt. Why?"
• Pattern recognition questions that weren't straightforward

I think I spent too much time on the jug problem — it's classic, but I wanted to be absolutely sure my solution was optimal. Probably should have moved on faster.

Section B: Programming (60 minutes) Three coding problems:

1. Given a string, find the longest substring without repeating characters
2. Implement a queue using two stacks
3. Design a simple LRU cache

These were LeetCode-medium level. I used Python for all three. The LRU cache question was the most interesting — I implemented it using a dictionary and doubly linked list. The time complexity was O(1) for both get and put operations.

Section C: Design (15 minutes) A simple design question: "Design a basic text editor with undo functionality."

I outlined the key features: text insertion, deletion, and undo/redo. I suggested using a stack to store previous states for undo functionality. The question was open-ended, and I think they wanted to see how I structured my thoughts rather than a perfect solution.

Stage 2: Technical Interview 1

This round was with a senior engineer from the CRM team. It started with a discussion of my written test solutions, then moved to new problems.

Question 1: "Given a binary tree, print it level by level in spiral order."

I explained the approach: use a queue for BFS, but alternate the direction at each level. I implemented it with a flag to track direction. The interviewer asked about the time complexity — O(n) since we visit each node once.

Question 2: "Design a URL shortening service like bit.ly."

This was a system design question. I broke it down:

• Requirements: Generate short URLs, redirect to original URLs, handle high traffic
• Design: Hash function for shortening, database to store mappings, cache for frequently accessed URLs
• Scaling: Load balancer, multiple database shards, CDN for global distribution

The interviewer asked: "How do you handle collisions in your hash function?" I explained that I'd use a combination of base62 encoding and a unique ID, with a fallback to append random characters if collision occurs.

Question 3: "Why do you want to join Zoho instead of a FAANG company?"

I was honest — I said Zoho builds complete products from scratch, which gives engineers more ownership. At FAANG, you might work on a small component of a larger system. At Zoho, you see the full product lifecycle. The interviewer nodded — I think this was the "right" answer.

Stage 3: Technical Interview 2

This round focused more on problem-solving and analytical thinking.

Question 1: "There are 25 horses, and you want to find the top 3 fastest. You can race only 5 horses at a time. What's the minimum number of races needed?"

This is a classic puzzle. I worked through it:

• Race 5 groups of 5 horses each (5 races)
• Race the winners of each group (6th race)
• The winner of the 6th race is the fastest overall
• For 2nd and 3rd, we need to consider specific horses from the 6th race

The answer is 7 races. The interviewer asked me to explain my reasoning clearly, which I did.

Question 2: "Given a sorted array that has been rotated, find a target element."

I used a modified binary search. The key insight is that one half of the array is always sorted, even after rotation. I checked which half is sorted, then determined if the target lies in that half.

Time complexity: O(log n). Space: O(1). The interviewer asked about edge cases — duplicates, empty array, array not rotated. I handled all of them.

Question 3: "Explain the difference between process and thread in operating systems."

I explained that a process is a program in execution with its own memory space, while threads are lightweight units within a process that share memory. Processes are isolated from each other, threads within a process can communicate easily. I also mentioned context switching overhead — process switching is more expensive than thread switching.

Stage 4: Managerial Round

This was with an engineering manager. The focus was on cultural fit and long-term potential.

Questions:

• "Tell me about a project you're proud of."
• "How do you handle disagreements with team members?"
• "What do you do when you're stuck on a problem?"
• "Where do you see yourself in 5 years?"

For the disagreement question, I talked about a group project where we had different opinions on the tech stack. I explained how we evaluated each option objectively, built prototypes, and made a data-driven decision. The manager seemed to appreciate that I focused on the process rather than the outcome.

One Thing That Stood Out

Zoho doesn't ask about your GPA or college ranking. They genuinely care about problem-solving ability. I've seen friends with lower GPAs get offers because they performed well in the interviews. This is different from many Indian tech companies that filter heavily based on academic credentials.

Compensation

Offer: ₹18,00,000 base salary plus a variable bonus component (up to ₹2–4 LPA based on performance). Total comp comes to approximately ₹20–22 LPA.

For Chennai, this is very good for a fresher. The cost of living is reasonable, and Zoho's campus facilities are excellent — free food, transportation, and a good work environment.

What Makes Zoho Different

Zoho builds its entire product suite in-house. They don't use many third-party services. This means engineers work on everything from the database layer to the frontend. You get exposure to the full stack, which is rare for freshers.

The interview process reflects this — they test your ability to think through problems end-to-end, not just write algorithms.

Advice for Candidates

• Practice puzzles: Zoho loves lateral thinking problems. Spend time on brain teasers.
• Focus on fundamentals: Data structures, algorithms, and basic system design are important.
• Be honest: If you don't know something, say so. They value intellectual honesty.
• Think aloud: In the interview, explain your thought process clearly. They want to see how you think, not just the final answer.

I'm joining Zoho next month and excited to work on the CRM platform. Feel free to ask questions in the comments!