01
How do you review test cases?
Show answer
Peer review for clarity, coverage of requirements, correct expected results, test data and traceability, then update and baseline them.
Zoho Software Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Zoho hiring for Software Testing roles
Zoho is an Indian software company offering a suite of business applications including Zoho CRM, Zoho Books, Zoho Mail and Zoho Creator. It is privately held and builds most of its technology in-house. It hires for software developers, QA engineers and technical support roles, with a selection process known for programming-heavy rounds.
For Software Testing roles, this Zoho practice set focuses most on Agile, SQL and API Testing (9), Accessibility & Usability Testing (6), Test Case Design (4), Bug Life Cycle and Jira (4). It has 1 easy, 26 medium, 13 hard questions, so you can start easy and work up to the harder ones.
- Company type
- Product
- Headquarters
- Chennai, India
- Main India offices
- Chennai, Tenkasi
Zoho Software Testing interview process
- Written test (aptitude + C programming output)
- Basic programming round
- Advanced programming round
- Technical interview
- HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for ZohoStart practicing
3 QUESTIONS FREESign up to unlock the full question bank and track your progress.Unlock every question and answer, then continue practising company-wise and package-wise.
3 questions free Unlock the rest in seconds
02
What metrics do QA teams track?
Show answer
Test execution rate, pass percentage, defect density, defect leakage, defect rejection ratio, requirement coverage and automation coverage.
03
How do you test pagination, sorting and filtering through an API?
Show answer
Send page, size, sort and filter parameters, then verify counts, order, boundaries (first, last, empty page) and invalid parameter handling.
04
Your automated accessibility scan shows zero errors. Is the page accessible?
Show answer
Not necessarily. Automated tools catch only a part of WCAG issues, such as missing labels and contrast. A clean scan still needs manual checks: keyboard-only navigation, focus order, a screen reader pass, meaningful alt text and link names, error handling, zoom and reflow and dynamic content. Report the result as 'no automated violations found' and add the manual checklist outcome before claiming conformance.
05
How do you test a modal dialog for accessibility?
Show answer
Open the dialog with the keyboard. Focus should move into it, usually to the first field or heading, and the screen reader should announce it as a dialog with its title. Tab must stay inside the dialog while it is open and the page behind must not be reachable. Escape and the close button should close it, and focus must return to the button that opened it. Also check it reads correctly when zoomed.
06
Customer records are being moved from an old system to a new one. How do you test the migration?
Show answer
Compare record counts per table before and after. Check field mapping, data types, formats, encodings and default values for a sample of records, including edge cases like nulls, special characters and very old records. Verify relationships are kept, such as each order still linked to its customer. Run key business reports in both systems and compare totals. Test the rollback plan and confirm the new application works with migrated data.
07
SQL: find orders whose total does not match the sum of their order items.
Show answer
SELECT o.order_id, o.total_amount,
SUM(i.quantity * i.unit_price) AS items_total
FROM orders o
JOIN order_items i ON i.order_id = o.order_id
GROUP BY o.order_id, o.total_amount
HAVING o.total_amount <> SUM(i.quantity * i.unit_price);
08
An automated test passes on your laptop but fails in the CI pipeline. How do you troubleshoot?
Show answer
Check the CI logs, screenshots, video or trace to see exactly where it failed. Then compare the environments: headless versus headed browser, screen size, browser version, time zone, environment URLs and secrets, test data and network speed. Run the test locally in headless mode with the CI settings. Common causes are timing, missing data in the CI environment and tests depending on run order. Fix the cause, not with a sleep.
09
How do you test a REST API that is not ready yet?
Show answer
Use mocks or stubs from the API contract such as Swagger, write test cases early and validate again when the real service is available.
10
How do you handle a bug found late in a release cycle?
Show answer
Assess impact and risk, discuss with product and dev, decide to fix, defer with a workaround or delay release, and document the decision.
11
Your backlog has 200 low-priority bugs and it is becoming unmanageable. How do you handle it?
Show answer
Run a backlog grooming session with the product owner. Close bugs that are obsolete, no longer reproducible or for retired features. Merge duplicates. Group the rest by module and user impact, and ask whether a few related bugs can be fixed together as one story. Agree to reserve a small share of each sprint for bug fixes. Set an ageing rule, for example review any bug older than 90 days.
12
The app crashes only on one older Android version. What are your steps?
Show answer
Reproduce it on that exact OS version, using a real device or an emulator image, and note the device model and app build. Capture the crash log and stack trace. Check if the code uses an API or library not supported on that version, or a permission or storage behaviour that changed. Log the bug with logs and the minimum supported version from the requirement, so the team can decide to fix it or raise the minimum version.
13
How do you test form accessibility, including labels and error messages?
Show answer
Check that every field has a visible label tied to it, so clicking the label focuses the field and a screen reader announces it. Required fields must be indicated in text, not only by colour or an asterisk without explanation. Submit with errors and check that messages are specific, appear next to the field, are announced by the screen reader and focus moves to the first error. Also check autocomplete for name, email and address.
14
Write test cases for a shopping cart.
Show answer
Add, remove, update quantity, price and tax calculation, coupon codes, stock limits, cart persistence after login and checkout navigation.
15
How do you test time zone handling for timestamps stored in a database?
Show answer
Check how timestamps are stored, ideally in UTC with a time zone aware type. Create a record from a user in IST and another in a different zone, then query the raw value and compare it with what each user sees on screen. Test boundaries such as orders placed just before midnight IST, which fall on the previous UTC date, and daylight saving changes for foreign users. Reports grouped by date are a common bug area.
16
Write test cases for a file upload feature.
Show answer
Allowed and disallowed formats, size limits, empty file, duplicate names, special-character names, cancel upload, slow network and multiple files.
17
Tell me about a time you pushed for an accessibility fix the team wanted to postpone.
Show answer
Situation: before a release, I found the payment form errors were not announced by screen readers and not reachable by keyboard. Task: the team wanted to defer it. Action: I recorded a short NVDA video showing a user could not finish payment, linked it to WCAG and our customer commitments, and proposed a small fix. Result: the fix took half a day, shipped in the release and we added keyboard checks to our definition of done.
18
What sensitive data checks do you do in API responses and logs?
Show answer
Check that responses return only needed fields, with no passwords, password hashes, full card numbers, full ID numbers or internal keys. Verify personal data is masked where required, for example only the last four digits of a phone number. Look at application and browser console logs for tokens or personal data. Check error responses do not expose stack traces, SQL or server versions. Raise any leak as a high-severity bug.
19
How do you convert existing manual test cases into automated scripts?
Show answer
Pick a small set of stable, high-value regression cases first. Review each one: make steps precise, remove judgement-based checks and define clear expected results. Prepare test data that the script can create and clean up. Build reusable page objects and helpers for common steps like login. Automate, run several times to confirm stability, then link each script to its manual case ID and mark the manual case as automated.
20
How do you decide which automated tests run on every pull request and which run nightly?
Show answer
Pull request checks must be fast, usually under ten to fifteen minutes, and highly reliable, so they include unit tests, API tests for changed services and a small UI smoke set of critical flows. The full UI regression, cross-browser runs, long data-driven suites and performance checks run nightly or before release. Tag tests by suite, measure run times and flakiness, and move tests between suites based on value and speed.
21
What is data masking and why is it used in test databases?
Show answer
Data masking replaces real sensitive values with realistic but fake ones, for example changing real phone numbers to valid-looking dummy numbers and real names to generated names. It lets teams test with production-like data volume and patterns without exposing customer information. It also supports compliance with India's Digital Personal Data Protection Act. Testers should check that masked data still passes validation rules and keeps relationships between tables intact.
22
How do you test location-based features in a mobile app?
Show answer
Test with location permission allowed, denied and approximate only. Use mock location tools to simulate different cities and moving routes. Verify the app shows nearby results correctly, updates location while moving and handles GPS turned off. Check accuracy indoors and with weak GPS, battery impact of continuous tracking and that background location is used only if needed and explained to the user.
23
What are ACID properties and how can a tester check them?
Show answer
ACID means Atomicity, Consistency, Isolation and Durability. Atomicity: a transfer that debits one account must also credit the other, or neither happens; test by forcing a failure midway. Consistency: constraints still hold after the transaction. Isolation: two users updating together do not see each other's half-done work; test with two sessions. Durability: committed data survives a restart; test by committing, restarting the service and querying again.
24
Leadership asks for a one-page quality update before a release. Which bug metrics do you report?
Show answer
Keep it short and decision-oriented. Show open bugs by severity, the created versus resolved trend, blockers with owners and dates, defect leakage from the last release and modules with the most defects. Give a clear recommendation, such as ready, ready with known issues or not ready, with reasons. Use a shared dashboard for detail, and one slide or email summary for leaders who need only the risk picture.
25
A page loads slowly only for some users. How do you investigate as a manual tester?
Show answer
Collect details from affected users: location, device, browser, network and time. Try to reproduce with similar conditions using browser network throttling. Use the browser developer tools network tab to find slow requests, large files or failing calls, and compare with a fast user. Check whether those users have more data, like a long order history. Share the slow request, timing and conditions in the bug for the developers.
26
A CAPTCHA on the signup page blocks screen reader users. What do you recommend?
Show answer
Log it as a high-severity accessibility bug because it fully blocks a group of users from signing up. An image-only CAPTCHA fails WCAG unless an alternative is offered. Recommend options such as invisible or risk-based bot checks, an email or OTP verification step, an audio alternative plus another modality, and rate limiting on the server. Retest the full signup with NVDA and TalkBack after the change.
27
What is error guessing?
Show answer
Using experience to guess where defects likely hide, such as empty fields, special characters or unexpected sequences, and designing tests for them.
28
What are stubs and drivers?
Show answer
Both are temporary pieces of code used in integration testing when some modules are not ready. A stub replaces a called lower-level module and returns fixed responses, used in top-down testing; for example, a stub payment service that always returns success. A driver replaces a calling higher-level module and sends inputs to the module under test, used in bottom-up testing. In API testing, mock servers play the role of stubs.
29
What is a sprint planning meeting and what does QA contribute?
Show answer
The team selects stories for the sprint. QA helps estimate testing effort, clarifies acceptance criteria and flags dependencies and risks.
30
Write a Postman test script that checks the status is 201 and the response contains an id.
Show answer
pm.test('Status is 201', function () {
pm.response.to.have.status(201);
});
pm.test('Response has id', function () {
const body = pm.response.json();
pm.expect(body).to.have.property('id');
pm.expect(body.id).to.be.a('number');
});
31
How do you test an API using Postman?
Show answer
Create a request with method, URL, headers and body, send it, check status and body, add test scripts and save it in a collection.
32
What is test coverage and how do you measure it?
Show answer
The extent of requirements or code exercised by tests. Measure requirement coverage with a traceability matrix and code coverage with tools.
33
How do you decide testing is complete when some bugs are still open?
Show answer
Testing is complete when agreed exit criteria are met, not when the bug count is zero. Check that planned tests ran, critical and high bugs are fixed or formally accepted, and remaining open bugs have workarounds and low user impact. Present the list with risk to the product owner, who decides on release. Record accepted bugs as known issues, so nothing is hidden and they are planned for a later release.
34
What is compliance testing?
Show answer
Compliance testing checks that software meets external laws, standards or internal policies, not just functional requirements. Examples include payment security standards for card data, data protection rules for personal data, accessibility guidelines and RBI rules for banking apps. Testers verify items such as consent capture, data retention, audit logs and masking. Findings are usually documented as evidence for auditors, so traceability and clear records matter as much as the tests.
35
SQL: find orders that have no matching customer record.
Show answer
-- orphan orders indicate a broken foreign key or bad data load
SELECT o.order_id, o.customer_id
FROM orders o
LEFT JOIN customers c ON c.customer_id = o.customer_id
WHERE c.customer_id IS NULL;
36
SQL: find duplicate emails.
Show answer
SELECT email, COUNT(*)
FROM users
GROUP BY email
HAVING COUNT(*) > 1;
37
The same bug keeps reopening across three sprints. What do you do?
Show answer
Stop the retest loop and call a short session with the developer, lead and product owner. Check whether the fix addresses the root cause or only the symptom, whether everyone agrees on the expected behaviour and whether different environments or data are involved. Run a root cause analysis and agree on clear acceptance tests before the next fix. Add an automated regression check so it cannot silently return.
38
How do you run a moderated usability test session?
Show answer
Define goals and three to five realistic tasks, such as 'Book a train ticket for next Friday'. Recruit participants who match real users. In the session, explain that you are testing the product, not them, ask them to think aloud, and avoid hinting even when they struggle. Record the screen with consent, note where they hesitate or fail, and finish with a short questionnaire. Then group findings by severity and frequency.
39
An API returns 200 OK but the body contains an error message. Is that a bug?
Show answer
Usually yes. Status codes should reflect the result so clients and monitoring can react correctly; an error with 200 can hide failures and break retries. A validation error should return 400 or 422, a missing resource 404 and a server failure 500. Check the API contract first: some legacy APIs document this pattern. If it is not documented, log it as a defect with the request and response attached.
40
How do you verify database schema changes in a new release?
Show answer
Get the migration script or change list. Compare the schema before and after: new tables and columns, data types, lengths, default values, NULL rules, indexes and constraints. Check that existing data was migrated correctly, for example a new status column filled for old rows. Run the main app flows to confirm queries still work. Finally, confirm the rollback script works on a copy, so the release can be reversed safely.
Tips to crack the Zoho Software Testing interview
- Practise C programming output and pointer questions, which commonly appear in Zoho's written test.
- Prepare for advanced programming rounds where you build a small application, such as a booking system, without external libraries.
- Learn about Zoho's privacy-focused, in-house product approach and its rural offices in places like Tenkasi.
- Keep a one-minute story ready for every project on your CV: problem, your part, tools, result.
- Practise the hard questions on this page aloud; Zoho interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Zoho Software Testing interview?
Candidates usually go through 5 stages: Written test (aptitude + C programming output); Basic programming round; Advanced programming round; Technical interview; HR round. The exact rounds change with the role, team, location and your experience, so confirm the process with the recruiter.
Which topics should I prepare for the Zoho Software Testing interview?
This practice set leans on Agile, SQL and API Testing (9), Accessibility & Usability Testing (6), Test Case Design (4), Bug Life Cycle and Jira (4). Revise those first, then practise explaining one or two of your own projects end to end, because most Zoho interviewers ask you to walk through real work.
Are these the exact questions asked at Zoho?
No. These are curated practice questions that match the skills and difficulty usually tested in product interviews like Zoho's. They are not a leaked or verified list of past questions.
Where does Zoho hire Software Testing professionals in India?
Zoho has large teams in Chennai, Tenkasi. Openings and locations change often, so check the Zoho careers page and filter by city and experience.
Software Testing questions for similar companies
Product
Autodesk
Software Testing interview questions
Bengaluru, Pune
View questionsProduct
Salesforce
Software Testing interview questions
Hyderabad, Bengaluru, Mumbai +1
View questionsProduct
Oracle
Software Testing interview questions
Bengaluru, Hyderabad, Noida +2
View questionsProduct
InMobi
Software Testing interview questions
Bengaluru
View questionsProduct
BrowserStack
Software Testing interview questions
Mumbai, Bengaluru
View questionsProduct
Urban Company
Software Testing interview questions
Gurugram
View questionsMore ways to practise
Company-wise Software Testing questionsPackage-wise Software Testing questionsExperience-wise Software Testing questionsRole-wise Software Testing questionsCity-wise Software Testing questionsMost asked Software Testing questionsScenario-based questionsPractical / hands-on questionsHR & behavioural questionsSoftware Testing mock interviewOnline assessment questionsTechnical round questionsManagerial round questionsSoftware Testing topic sheets