Explore: Interview experience · HR interview questions · Overview · Placement papers · Preparation guide
Zoho’s fresher hiring is unusually C-heavy and application-building focused, and famously does not filter by CGPA or branch - candidates are judged almost entirely on written-test and coding-round performance.
Interview experience
Zoho interview experiences covering Resume Screening, Aptitude & C Programming Test, Basic Programming Round, Advanced Programming/Application Round, +2 more. Round-wise notes, common questions, and what candidates report clears each stage.
HR interview questions
Zoho HR interview questions with sample answer frameworks - motivation, relocation, STAR stories, and culture-fit prompts.
| Round | Duration | What they test |
|---|---|---|
| Resume Screening | 2-5 days | Application only - no CGPA cutoff |
| Aptitude & C Programming Test | 90-120 min | Pen-and-paper aptitude + C output prediction (pointers, arrays, recursion) |
| Basic Programming Round | 2-3 hours | 5 coding problems - pattern printing, array/string manipulation |
| Advanced Programming/Application Round | 90-120 min | Build a complete mini-application with file handling |
| Technical Interview | 30-45 min | Code review of your own submissions, C/data-structures follow-ups |
| HR Interview | 20-30 min | Background, relocation, learning mindset |
These answers are compiled from public candidate reports and prep guides, not from an official Zoho notice, and drives differ by campus, role and year. The instruction screen of your own test is the final word.
| Question | Answer |
|---|---|
| How many questions and how long? | The first round is usually 20 questions: 10 aptitude and 10 C output questions, in about 60 minutes. PrepInsta’s 2026 pattern lists 20 aptitude and C questions in 60 minutes, 5 basic programming problems in 180 minutes and 2 advanced programming problems in 60 minutes. |
| Is it pen-and-paper or online? | Both are reported. Many campus and off-campus drives run a written first round, and a 2025 off-campus candidate had to write C outputs with no options given. Coding rounds are on a computer, sometimes your own laptop with any IDE. |
| Does it have negative marking? | No. PrepInsta’s Zoho pattern page states there is no negative marking, and no candidate report mentions one. |
| Is there a sectional cutoff? | Each round is an elimination round, so you must clear the written test before you see the coding rounds. PrepInsta’s 2026 pattern page shows its own estimated cutoffs of 80% for the written round and 85% for each programming round, but Zoho publishes no cutoff. |
| How much is the cutoff? | Not published, and there is no CGPA cutoff. Shortlists are relative to the batch and steep: an August 2024 off-campus MTS drive had over 3,000 candidates in round one, and 100-200 moved on. |
| Is there coding, and which languages? | Yes, in two or three rounds. Basic programming uses any common language; the advanced programming round is usually limited to C, C++ or Java, which PrepInsta’s 2026 page and its on-campus candidate account both confirm. |
| Which language is the output section in? | Usually C (pointers, enums, arrays, strings). A December 2025 SDE report had 10 Java output questions instead, so check your role. |
| Is there an incubation stage? | In some off-campus MTS drives, yes. A 2024 Tenkasi drive had a three-week incubation where candidates built an application with Tomcat, Cassandra and MySQL, with daily code reviews, before the HR round. |
These themes come from GeeksforGeeks candidate reports for Zoho’s 2024-2025 campus and off-campus drives. They show the level and style, not a fixed list.
| Role | Reported questions and topics |
|---|---|
| Member Technical Staff (off-campus) | String manipulation and shortest path in the preliminary coding round; Sudoku Solver, a max-finder problem and a DP problem in advanced coding; a console “taxpayer” application extended stage by stage; DSA and OOP in the interview (August 2024). |
| Software Development Engineer | Decode String, equilibrium point, next greater element, rotate an array by K, longest palindromic substring, printing odd and even numbers with two threads, minimum number of platforms, BST questions, Spring Boot and MVC, and modelling college entities with inheritance (December 2025). |
| Software Debug Engineer | Written C outputs on pointers, enums, arrays and strings; then Valid Parentheses, Best Time to Buy and Sell Stock, longest substring without repeating characters, median of two sorted arrays in O(log(n+m)) and N-Queens in an offline programming test (2025). |
| Software Developer (campus) | Five basic programs (pattern printing, two sorting and two array problems), then an application round such as a Zomato-like food app, a taxi booking system or an e-commerce console app, then a resume-based technical interview. |
Asked across every role: explain and optimise code you wrote in an earlier round, OOP design for a console application, and willingness to work from Chennai or a rural office such as Tenkasi.
A pen-and-paper written test combining general aptitude with C output-prediction questions. The C section is the real filter - it goes deep on pointer arithmetic, memory, and recursion rather than surface-level syntax.
Common questions
A longer, 2-3 hour coding round with 5 problems, typically weighted toward pattern-printing and array/string manipulation. Code clarity and correct logic matter more than raw problem count solved.
Common questions
Instead of isolated problems, you build a small but complete application with file-based persistence - candidates report library-management systems, quiz apps, and address-book applications as common briefs.
Common questions
Full round-by-round narratives are on the Zoho interview experience page.
The most distinctive round: rather than fresh problems, the interviewer reviews the code you wrote in the Basic Programming and Application rounds and asks you to explain, optimize, and defend it.
Common questions
A conversational closing round on background, relocation, and long-term intent - candidate reports describe it as friendly rather than adversarial.
Common questions
Sample answer frameworks for each of these are on the Zoho HR interview questions page.
Zoho is unusual among large product companies for explicitly not filtering by CGPA or degree branch - hiring decisions rest almost entirely on written-test and coding-round performance. This is a deliberate policy, not an oversight: candidates from mechanical, ECE, and other non-CS backgrounds with strong self-taught C skills regularly clear the process alongside CS candidates. If you’re weighing whether a lower CGPA rules Zoho out, it doesn’t - but the C-fundamentals bar in the written test and the code-review-style technical interview are correspondingly harder to bluff through than a typical resume-filtered process.
Zoho has two very different entry routes. Graduate hiring for roles such as Member Technical Staff and Software Developer is the process this page covers: a written aptitude and C test, basic and advanced programming rounds, an application-building round, and technical and HR interviews. It is open to graduates from any branch, with no CGPA cutoff.
Zoho Schools of Learning is Zoho’s own training programme for students straight after school. Its official site says applicants must be 17-20 years old, targets +2 and diploma students, and asks college graduates not to apply. The programme runs two years with a stipend of Rs. 10,000 a month in year one and Rs. 15,000 in year two, and students who complete it are inducted as Zoho employees. It has its own selection process (an entrance exam or an examless evaluation) and is not the same as campus or off-campus graduate hiring, so check which one an announcement refers to before you prepare.
An array name is not a pointer variable - it is the array itself, and in most expressions it decays to a pointer to its first element. The differences show up where decay does not happen: sizeof(arr) on an array of 10 ints gives 40 bytes, while sizeof(ptr) gives the pointer width (usually 8), and &arr has type pointer-to-array rather than pointer-to-pointer. You also cannot assign to an array name, so arr = something is a compile error, whereas a pointer can be reassigned freely. This is exactly why sizeof stops working inside a function that takes the array as a parameter: the parameter is genuinely a pointer, so you must pass the length separately.
Pointer arithmetic is scaled by the size of the pointed-to type, so p + 1 advances by sizeof(*p) bytes, not one byte. For an int pointer on a typical machine that is 4 bytes; for a char pointer it is 1; for a pointer to a 12-byte struct it is 12. That is why arr[i] is defined as exactly *(arr + i), and why the surprising i[arr] also compiles. Subtracting two pointers into the same array yields the number of elements between them, again divided by the element size. Arithmetic that moves outside the array, or on a void pointer, is undefined behaviour in standard C.
malloc(n) allocates n bytes and leaves the contents uninitialised, so reading them before writing is undefined behaviour. calloc(count, size) allocates count times size bytes, zero-fills them, and also checks the multiplication for overflow, which makes it the safer choice for arrays. Both return NULL on failure, and that return value must be checked before use. free returns the block to the allocator but does not change your pointer, so the variable still holds the old address - dereferencing it afterwards is a use-after-free and freeing it twice corrupts the heap, which is why the convention is to set the pointer to NULL right after freeing. realloc resizes a block and may move it, so you must assign its return value rather than assuming the old pointer is still valid.
Given char *s = "hello";, the assignment s[0] = 'H'; is undefined behaviour and on most modern systems it crashes with a segmentation fault. A string literal lives in a read-only data segment, and the pointer points into it, so writing through it attempts to modify read-only memory. The correct way to get a modifiable copy is char s[] = "hello";, which allocates a 6-byte array on the stack (five characters plus the terminating null byte) and copies the literal into it - writing to s[0] is then perfectly legal. This distinction between char *s and char s[] is one of Zoho’s most reliable output-prediction traps, and declaring literals as const char * makes the compiler catch it.
C passes every argument by value, so a function receiving two ints gets copies; swapping the copies leaves the caller’s variables untouched. Passing addresses instead - void swap(int *a, int *b) with a temporary and the dereferences *a and *b - lets the function write through to the caller’s storage. That is why scanf takes &x for an int: it needs the address to store into. The same reasoning explains why a function that must allocate memory for the caller takes a pointer-to-pointer, or returns the new pointer, rather than assigning to a plain pointer parameter.
Define struct Node { int data; struct Node *next; };. To insert at the head, malloc a node, set its data, point its next at the current head, and reassign head to the new node - that is O(1). To insert at the end you walk to the last node, which is O(n) unless you keep a tail pointer. To delete a node you need the previous node so you can set prev->next to the node’s next, then free the removed node; deleting the head is the special case where you move the head pointer first. Losing the next pointer before freeing, or forgetting to free at all, are the two bugs Zoho interviewers check for.
The compiler aligns each member to its natural boundary, so a struct containing a char, then an int, then a char typically occupies 12 bytes rather than 6: three padding bytes after the first char to align the int, and three trailing bytes so the struct’s own size is a multiple of its strictest alignment. Reordering the members largest-first - int, then the two chars - shrinks it to 8. This is why sizeof a struct is often larger than the sum of its members, a favourite Zoho written-test question. It also means you must never compare two structs with memcmp, since the padding bytes hold indeterminate values.
Open with fopen(path, mode) and always check for a NULL return, since a missing file or a permissions problem is the common failure. Use “r”, “w”, or “a” for text, adding “b” for binary and “+” for read-write; note that “w” truncates an existing file immediately, which has cost many candidates their saved data mid-round. For record-style persistence, fwrite and fread on a struct array are the simplest approach, with fseek and ftell for random access, while fprintf and fgets suit human-readable text formats. Always fclose when done, because buffered writes are only guaranteed to reach disk on close or an explicit fflush - a crash before that loses the data.
No. PrepInsta’s Zoho pattern page states there is no negative marking, and no candidate report mentions one. The first round is usually 10 aptitude and 10 C output questions in about an hour, and some drives make you write the output without options, so careful tracing matters more than guessing.
It is a written round of about 20 aptitude and C output questions in 60 minutes, then a basic programming round of about 5 problems (up to 3 hours), then an advanced programming or application-building round. Every round eliminates, and there is no CGPA cutoff. Some off-campus MTS drives add an incubation stage before HR.
Zoho’s fresher hiring runs 5-6 stages: 1. Resume screening (2-5 days) - CGPA is explicitly not a filter. 2. Aptitude & C Programming Test (90-120 min) - pen-and-paper format. 3. Basic Programming Round (2-3 hours) - 5 coding problems, mostly pattern-printing and array/string manipulation. 4. Advanced Programming/Application Round (90-120 min) - build a complete mini-application (e.g. library management, quiz app) with file handling. 5. Technical Interview (30-45 min) - a code review of what you wrote in earlier rounds, plus C/data-structures questions. 6. HR Interview (20-30 min) - background, relocation, learning mindset. Total duration: 2-3 weeks from application to offer.
The written test leans hard on C output-prediction (pointers, arrays, loops, recursion) - tests deep understanding of pointer arithmetic and memory, not just syntax. The programming rounds are pattern-printing, array/string manipulation, and logic-building problems, followed by building a complete small application (address book, quiz app, library system) with file-based persistence. The technical interview is largely a live code review of your own submissions from earlier rounds - expect to explain and optimize code you already wrote, and answer pointer/memory/data-structure questions on the spot.
Typically 5-6 stages for freshers: resume screening, an aptitude + C programming written test, a basic programming round (5 coding problems), an advanced/application-building round, a technical interview, and an HR interview. Off-campus drives sometimes compress or reorder a couple of these, but the C-heavy, application-building shape stays consistent.
No - this is one of Zoho’s most distinctive hiring quirks. Zoho evaluates candidates purely on the written test and coding-round performance rather than filtering by CGPA or even branch (candidates from mechanical, ECE, and other non-CS branches with strong self-taught C skills have cleared the process). If your C fundamentals and problem-solving are strong, a lower CGPA does not disqualify you here the way it might elsewhere.
The technical interview (30-45 min) is largely a code review of what you wrote in the Basic Programming and Application rounds - the interviewer asks you to explain your approach, optimize sections, and handle edge cases in your own code, rather than posing brand-new problems. Expect follow-up questions on pointers, memory management, and how you’d implement core data structures (arrays, linked lists, stacks, queues) in C. Interviewers reportedly respond well to a genuine learning mindset even when the code isn’t perfect.
Practice C output-prediction questions specifically - Zoho’s written test tests pointer and memory understanding harder than most companies’ aptitude rounds. Practice writing code on paper, not just in an IDE, since the early rounds are pen-and-paper. Build 1-2 complete small C applications with file handling (a to-do list, address book, or quiz app) before the interview, since the Application round expects a working, modular program, not just isolated functions. Review and be ready to defend your own code from earlier rounds - the technical interview reuses it directly.
Long-term commitment, willingness to relocate to Chennai and possibly rural campuses (Tenkasi/Palladam-style offices appear in candidate reports), genuine interest in Zoho’s product culture and Made in India story, and a learning mindset. The round is conversational, but location rigidity or “I will leave soon for MBA” answers still fail people who cleared coding rounds.
Yes on many drives. Technical HR (when present) still probes projects, DSA/SQL, puzzles, and scenario thinking. General HR focuses on family background, hobbies, Why Zoho, salary expectations, and location preference. Strong coding performance sometimes shortens or skips Technical HR - confirm from your drive schedule.
Good fit: You like building small tools end-to-end, you can sit with a notebook and dry-run pointer code, and you are open to Chennai or a rural Zoho office. Internships help on the resume screen but are not a substitute for Round 1 tracing. If you already debug segfaults without panicking, you are ahead of half the written pool.
Harder path: You only practiced MCQ aptitude plus online judges with autocomplete; you freeze without printf debugging; you refuse relocation. Zoho’s HR round is friendly but blunt on location and long-term commitment - treat those as real filters, not soft talk. A high CGPA with weak C usually dies in output prediction; a mid CGPA with strong C often survives.
Use this as a default four-week loop before a Zoho drive. Adjust to your invite timeline.
10-day crash version: Days 1-4 timed DSA, days 5-7 resume projects + CS fundamentals, days 8-9 mock interviews out loud, day 10 HR STAR stories on the HR page.
Candidate-reported fresher/early-career packages for Zoho often cite MTS ₹5-7 LPA. Treat forum numbers as ranges, not guarantees - confirm the written offer letter for your team and location.
Interview process details and sample questions on this site are editorially organized from public candidate reports and hiring write-ups, with round structure, prep notes, and company-specific framing added by our team. For round-by-round stories, see the Zoho interview experience page. For OA papers and coding drills, use Zoho on placementpapers.app. Test quick answers and role-wise questions draw on PrepInsta’s Zoho recruitment pattern page (2026 pattern), the official Zoho Schools of Learning site (zohoschools.com) and GeeksforGeeks Zoho interview experiences for MTS (off-campus, August 2024), SDE (2025), Software Debug Engineer (2025) and campus Software Developer roles.
