Round 1 Aptitude Filter round·Engineering·Easy·20 min

Zoho Software Developer Interview — Round 1 Aptitude Filter

20 min · 1 credit · scorecard at the end

Take this on a laptop or desktop — not your phone. The live interview needs a full screen and keyboard (including a sketch whiteboard on coding rounds). You can buy now, but start it from a computer.

ZeroPitch Research Desk

Updated 2026-05-25 · Newly added · be among the first to take it

Field: Engineering
Company: Zoho
Role: Software Developer
Duration: 20 min
Difficulty: Easy
Completions: New
Updated: 2026-05-25

How to prepare

What this round tests, what strong and weak answers sound like, and the traps to sidestep.

What this round is about

Topic focus. Quantitative aptitude across percentages, ratio-proportion, time-speed-distance and permutation-combination, then logical reasoning across series and blood relations, then four to five C output prediction items on nested loops, pointers, recursion and complexity.
Conversation dynamic. Priya pushes the per-item budget hard. She acknowledges what you just did in one sentence then moves to the next item. She does not coach you. She will redirect you to the next item if you sit on one for more than ninety seconds.
What gets tested. Your pacing discipline under a real clock, your habit of writing the intermediate arithmetic step out loud, your accuracy at tracing pointer increments and recursion stack frames in your head, and whether you remember to convert units before computing.
Round format. A 20-minute compressed mirror of the real Zoho Round 1 paper at the Chennai campus. Aptitude items first, then C output items, then a short reflection on which bucket cost you the most time.
Time budget. Roughly seven minutes on the aptitude bucket, eight on the C output bucket, and the last five for reflection plus skipped-item return. Priya keeps the clock visible and does not extend for slow openers.

What strong answers look like

Step-before-answer narration. On a percentage problem you say cost price is 100, marked price is 140, selling price after 20 percent discount is 112, so the profit percent is 12. The arithmetic is visible.
Unit conversion before computation. On a time-speed-distance question with seconds in the answer and km per hour in the speed, you convert first. You say 36 km per hour equals 10 metres per second, then proceed.
Stack-frame tracing. On a recursion question you say the base case fires at n equals 0 returning 1, then the unwind multiplies the chain back, giving the final printed value.
Skip-and-return pacing. When an item burns ninety seconds without resolution you mark it, write a best guess, and move on. You return only if you have spare time at the end.
Loop dry-run on a small input. When a C nested-loop item appears, you trace it on n=3 or n=4 on paper before claiming the output. The candidates who get tripped up are the ones who eyeball the loop bounds without writing the iteration table.

What weak answers look like (and how to avoid them)

Three minutes on one item. The single biggest Round 1 killer. Mitigate by setting a personal ninety-second cap per item and moving on hard at that limit.
Guessing percent answers without writing the step. Avoid by always naming the cost price assumption first, even on a fast item.
Missing the km per hour to metres per second conversion. Avoid by reading the question twice and naming the unit aloud before you compute.
Confusing the recursive case with the base case. Avoid by writing the function's stop condition on paper before tracing any further.
Off-by-one on nested-loop bounds. Treating an inner loop with bound i as if it always runs n times. Mitigation: when the inner range depends on the outer index, sum the iteration count row by row before claiming a complexity or output.

Pre-interview checklist (2 minutes before you start)

Pull up scratch paper. Have a blank pad or notes app open so you can write the intermediate arithmetic step Priya will ask for.
Recall the four formulas. Net percent change for two-step discount, relative speed for two trains, ratio cross-multiplication, nPr and nCr factorial form.
Have the C tracing checklist ready. Cell-by-cell pointer increment, stack frame for recursion, explicit iteration count for nested loops with index-dependent inner bound.
Set a per-item ninety-second cap. Decide now that you will skip and return rather than sink three minutes into one tricky item.
Re-read every question aloud once. Before computing. Catches unit traps and misread phrasings.
Plan the skip-and-return cycle. Mark items you skipped with a small dot so you can find them on the return pass.

How the AI behaves

Probes every claim. Asks you to name the intermediate arithmetic step before accepting a final percent or ratio answer.
No mid-round praise. Will not say great answer or that is correct. Acknowledges by repeating one specific thing you just said, then pushes to the next item.
Interrupts on long thinking. If you sit on a single item for more than ninety seconds, Priya will redirect you to the next item and tell you to come back if time allows.
Refuses to give you the answer. If you are stuck, she rephrases the question or asks for the next step. She does not tell you the formula or the result.
Anchors on your reasoning, not your final number. Priya cares whether you wrote a clean step before the result. A wrong final number with a sound step gets more credit than a right number from a guess.

Common traps in this type of round

Sinking into the tricky output item. Spending three minutes on a pointer-arithmetic question and never finishing the paper.
Skipping the intermediate step. Guessing the percent answer in your head and producing a string of off-by-one errors.
Ignoring the unit. Computing in km per hour when the answer needs metres per second.
Treating the base case as the recursive case. Producing an infinite-loop intuition on a finite recursion.
Index-dependent inner loop miscount. Counting nested iterations as n times n when the inner bound is i, producing a wrong complexity claim.
Imbalanced prep. Preparing only programming and losing the blood-relations and series block, or only aptitude and losing the pointer items.

Reference

The full breakdown

How you're scored, the questions candidates ask most, and the research this interview is built on. Skim it — or just start the interview.

Interview framework

You will be scored on these 6 dimensions. The full rubric with definitions is below.

Arithmetic Step Articulation

How clearly you narrate the cost-price assumption, marked-price calculation, and selling-price step before stating any percent or ratio answer.

25%

Output Tracing Accuracy

How well you write the stack frame, pointer cell, or iteration count on paper before claiming an output or complexity result.

25%

Pacing Discipline

Whether you cap each item near ninety seconds and skip-and-return rather than sinking into a single tricky question for the rest of the paper.

20%

Unit And Edge Care

How reliably you convert km per hour to metres per second, name the base case before the recursive case, and reconcile units before computing.

15%

Reflection Specificity

Whether you name a specific item by topic, a specific bucket weakness, and a specific drill resource in the reflection rather than saying you need more practice.

10%

Reasoning Step Clarity

How clearly you describe each intermediate move so a panellist could replay your reasoning from the transcript.

What we evaluate

Your final scorecard breaks down across these dimensions. The full rubric and tier criteria are revealed inside the interview itself.

Common questions

What does the Zoho Round 1 aptitude and basic programming round actually test?

Zoho Round 1 is a paced filter that tests four buckets. Quantitative aptitude covers percentages, ratio-proportion, time-speed-distance and permutation-combination. Logical reasoning covers series, blood relations and syllogism. Programming covers C output prediction across nested loops, pointers, recursion and complexity. The point is to filter for candidates who can keep moving under a 60 to 90 second per item budget. This simulation runs the same buckets in a 20-minute compressed format with a Zoho engineer persona who pushes you to keep pacing.

How should I structure my answer when Priya asks a percentage or time-speed-distance question?

Say the intermediate arithmetic out loud before stating the final number. For a percent question, name the cost price assumption, name the marked-price calculation, then name the discount calculation, then state the answer. For a time-speed-distance question, convert km per hour to metres per second first if the question involves seconds, then write the relative-speed formula, then divide. Showing the step lets Priya catch a wrong arithmetic move and lets you self-correct without having to redo the whole question.

What are the most common mistakes that cause candidates to fail Zoho Round 1?

The four killers are sinking three minutes into one tricky output question and never finishing the paper, guessing percent answers without writing the intermediate step, forgetting to convert km per hour to metres per second on a train-crossing question, and confusing the recursive case with the base case when tracing a C function. The single most fatal habit is blocking on item three or four for too long. Every candidate who clears Round 1 has the discipline to skip and return rather than sit on one item.

How is this AI interviewer different from the real Zoho panel?

The AI persona, Priya, is calibrated against the real Zoho Round 1 pattern reported by candidates on PrepInsta, CCBP, GeeksforGeeks and Medium write-ups. She runs the same per-item budget, pushes the same pacing pressure, and refuses to give you the answer when you are stuck. The differences are practical: this is a 20-minute voice rehearsal, not a 60-minute paper test, so you get fewer items but each one is probed for the reasoning step. The AI never gives mid-round praise.

How is my Round 1 performance scored in this simulation?

Scoring runs against five live dimensions: Pacing Discipline, Arithmetic Cleanliness, Output Tracing Accuracy, Reasoning Step Articulation, and Unit and Edge Care. Each gets a 1 to 5 live signal that drives the report. The transcript-backed scorecard names the specific item where your pacing or arithmetic broke, so you can drill that bucket on PrepInsta or IndiaBix before the real campus drive. There is no negative marking inside the simulation but Priya notes when you are guessing.

What should I do in the first two minutes before this round starts?

Pull up scratch paper or a notes app. Recall the four formulas Priya will lean on: net percent change for two-step discount, relative speed for two trains, ratio cross-multiplication, and the nPr or nCr factorial form. Have the C output checklist ready: trace pointer increments cell by cell, write the recursion stack frame on paper, count nested loop iterations explicitly. Decide in advance that you will skip and return rather than sink three minutes into one item. Re-read the question aloud once before computing.

How do I handle a C output question when I cannot trace the recursion in my head?

Write the stack frame on paper, one row per recursive call. Note the value of each parameter at each level. Identify the base case before the recursive case. Trace the unwind from the base case back to the top, noting what each level prints. If you have more than ninety seconds in the budget, you will get the answer. If you have less, mark the item, write your best guess, and move on. Do not sit and stare at the code in your head.

What does a strong Round 1 answer sound like?

A strong answer narrates the step before naming the result. On a percentage problem it sounds like: I will assume cost price is 100, marked price is 140, after 20 percent discount the selling price is 112, so the profit percent is 12. On a recursion question it sounds like: the base case fires at n equals 0, returning 1, then the unwind multiplies 1 times 2 times 3, so the output is 6. The answer is verifiable because the reasoning is visible. That is what Priya is listening for.

What is the Zoho Round 1 cut-off and how many candidates clear it?

Candidate reports across PrepInsta, GeeksforGeeks and Medium consistently report a cut-off near 60 to 65 percent of total marks on Round 1. Roughly 30 to 40 percent of attendees clear and are called for Round 2 (basic programming on Turbo C). In a pooled drive of 2,000 to 3,000 candidates, this means 600 to 1,200 progress. SMVEC and other tier-2 Tamil Nadu cohorts convert in line with the overall average when their prep is structured around all four aptitude buckets, not only programming.

Should I prepare programming or aptitude more heavily for Round 1?

Both. Failure-mode reports consistently show candidates who prepared only programming and then lost the blood-relations and series block, and candidates who prepared only aptitude and then lost the pointer and recursion items. The paper is roughly half aptitude and half programming. Skipping a full bucket costs you 25 percent of the paper before you start. The correct prep ratio is roughly equal time on quantitative aptitude, logical reasoning, and C output prediction, with extra polish on the bucket you find weakest.

Sources this interview is built on

Real candidate-report URLs (Glassdoor / AmbitionBox / PrepInsta / GeeksforGeeks / Medium) reviewed when authoring the questions, persona, and rubric. Verify the realism yourself.