Cropin Technology QA Engineer Interview: Rounds, Questions and Preparation

What the job involves

QA Engineers at Indian unicorns and high-growth startups test web and mobile products, write and run test cases, log bugs, and verify fixes in fast release cycles. They work closely with developers and product managers, often owning regression suites and helping automate repetitive checks. In agri-tech or SaaS startups, they also validate data-heavy workflows and integrations that must work reliably in low-bandwidth field conditions.

Role and Technical Knowledge

1. 1

   What is the difference between verification and validation in software testing?

   Explain that verification checks if the product is built correctly against specs, while validation checks if the right product was built and meets user needs. Give a simple example like reviewing a test plan versus actually running the app.

2. 2

   How would you test a login page for a mobile app used by farmers in low-network areas?

   Cover functional checks like valid and invalid credentials, password rules, and account lockout. Also mention network conditions, offline behaviour, session timeout, and device compatibility.

3. 3

   What is the bug life cycle and what statuses does a bug go through?

   List stages such as New, Assigned, Open, Fixed, Retest, Verified, Closed, and Reopened. Mention that a QA engineer usually moves a bug to Reopened if the fix does not work.

4. 4

   What is the difference between smoke testing and sanity testing?

   Smoke testing checks whether a new build is stable enough for further testing, while sanity testing checks a specific fix or small change. Use a build release example to make it clear.

Practical Scenarios and Test Design

1. 5

   You are asked to test a feature that uploads crop photos from the field. How would you design your test cases?

   Think about valid image formats, file size limits, poor connectivity, duplicate uploads, and server errors. Also include checks for image quality, metadata, and whether the upload resumes after a network drop.

2. 6

   How would you test an API that returns weather data for a farm location?

   Mention status codes, response schema, invalid coordinates, missing parameters, rate limits, and response time. Also cover how you would use Postman to save requests and run collections.

3. 7

   A developer says a bug you reported is not reproducible. What do you do?

   Show that you would gather clear evidence like steps, screenshots, device details, logs, and a screen recording. Then try to reproduce on a different device or build and involve the developer calmly to find the exact condition.

4. 8

   How would you decide what to include in a regression suite for a weekly release?

   Focus on high-risk and high-use areas like login, payments, and core data sync. Mention prioritising tests based on recent code changes, business impact, and past bug history.

Tools, Automation, and Data

1. 9

   Write a basic SQL query to find users who signed up but never placed an order.

   Use a LEFT JOIN between the users and orders tables and filter where the order ID is NULL. Explain that this kind of query helps validate data in the backend.

2. 10

   What is the difference between a test case and a test scenario?

   A test scenario is a high-level thing to test, like login, while a test case has detailed steps, data, and expected results. Give one example of each.

3. 11

   How would you use Selenium or Playwright in a startup QA process?

   Talk about automating stable, repetitive flows like login and smoke tests. Mention that you would not automate everything and would focus on high-value regression checks first.

4. 12

   What do you check in server logs when a feature fails in production?

   Mention looking for error codes, stack traces, timestamps, request IDs, and user or device context. Explain that logs help you confirm whether the issue is frontend, backend, or data related.

Behavioural and HR Questions

1. 13

   Tell me about a time you found a mistake in your own work and how you handled it.

   Pick a real example from a project or internship. Show that you took ownership, corrected it quickly, and changed your process to avoid repeating it.

2. 14

   Why do you want to work as a QA Engineer in a fast-growing startup rather than a large service company?

   Connect your interest to ownership, faster learning, and direct impact on the product. Mention that you enjoy varied work and close collaboration with developers and product teams.

3. 15

   How would you handle a situation where a developer repeatedly dismisses your bug reports?

   Stay professional and data-driven. Explain that you would share clear evidence, understand their constraints, and if needed involve the QA lead or product manager to prioritise the issue.

4. 16

   Where do you see yourself in two years as a QA Engineer?

   Show a realistic path such as getting stronger in automation, API testing, and performance basics. Mention that you want to grow into a test lead or automation-focused role over time.