Park+ QA Engineer Interview: Rounds, Questions and Preparation

What the job involves

QA Engineers at Indian unicorns and high-growth startups like Park+ test consumer-facing apps and internal tools across Android, iOS, and web, often in fast release cycles. They write and run manual and automated tests, log clear bugs, verify fixes, and work closely with developers and product managers. The role also involves API testing, basic database checks, and ensuring smooth experiences for millions of users.

Role and technical knowledge

1. 1

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

   Explain that verification checks if we are building the product right through reviews and static testing, while validation checks if we built the right product through dynamic testing. Give a simple app example like a login screen.

2. 2

   How would you test a parking slot booking feature in an app like Park+?

   Cover functional checks like searching by location, selecting a slot, payment, and booking confirmation. Also mention edge cases like double booking, network failure, and refund flow.

3. 3

   What is the difference between severity and priority in a bug? Give an example.

   Severity is technical impact, priority is business urgency. Use an example like a typo on the home screen being low severity but high priority before a launch.

4. 4

   What is an API and how do you test one using Postman?

   Explain that an API lets apps talk to servers. Mention checking status codes, response body, headers, authentication, and error cases in Postman.

Practical testing scenarios

1. 5

   You find a bug that crashes the app only on Android 12 when the user has no internet. How do you report it?

   Include clear steps to reproduce, device and OS details, expected vs actual result, screenshots or logs, and severity. Mention checking if it is reproducible.

2. 6

   How would you test a payment flow in a fast-growing consumer app?

   Cover successful payment, failed payment, timeout, refund, duplicate charge, and different payment methods. Mention checking database and backend logs.

3. 7

   Write test cases for a simple login screen with email and password.

   Include valid login, invalid password, empty fields, SQL injection attempt, password masking, and forgot password link. Show structured test case format with steps and expected result.

4. 8

   What is regression testing and when would you run it before a release?

   Explain that it checks old features still work after new changes. Mention running it before every major release or after a bug fix in a shared module.

Automation and tools basics

1. 9

   What is the difference between manual and automation testing? When would you choose one over the other?

   Manual is good for exploratory, usability, and one-time tests. Automation is good for repetitive, regression, and large-scale tests. Mention cost and time trade-offs.

2. 10

   Have you used Selenium or Appium? Explain a simple test you wrote or would write.

   Describe locating elements, performing actions, and asserting results. If you have no experience, explain a basic login test you would automate and why.

3. 11

   What is a test case management tool and why do startups use one?

   Mention tools like TestRail or Zephyr for organizing, reusing, and tracking test cases. Explain that startups need speed and traceability.

4. 12

   How do you test an API that returns a list of nearby parking spots?

   Check response time, correct data format, pagination, empty results, invalid location, and authentication. Mention using Postman and verifying against the database.

Behavioural and HR questions

1. 13

   Tell me about a time you found a mistake in your own work. How did you handle it?

   Show honesty and ownership. Explain what you did to fix it and what you changed to avoid repeating it. Relate it to testing or a college project.

2. 14

   Why do you want to work as a QA Engineer at a high-growth startup like Park+?

   Connect to the fast pace, learning opportunities, and impact on real users. Mention interest in mobile apps, parking, or payments if relevant.

3. 15

   A developer says your bug is not reproducible. How do you respond?

   Stay calm and collaborative. Offer to sit together, share screen recording, device logs, and exact steps. Suggest adding more logging if needed.

4. 16

   How do you handle tight deadlines when you have many test cases to run?

   Prioritize based on risk and business impact. Communicate early, automate what you can, and focus on critical user flows first.