Jupiter 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 for functionality, performance, and security before release. They write automated test scripts, perform manual exploratory testing, and work closely with developers in agile sprints to catch bugs early. The role demands strong analytical skills, attention to detail, and familiarity with modern testing tools and CI/CD pipelines.

Role and Technical Knowledge

1. 1

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

   Verification checks if the product is built correctly (reviews, inspections), while validation checks if the correct product is built (actual testing). Give examples from a fintech app like checking if a payment API meets specs (verification) versus testing if a user can successfully transfer money (validation).

2. 2

   How would you test a UPI payment flow in a fintech app?

   Cover positive and negative scenarios: successful payment, insufficient balance, invalid UPI ID, network failure, duplicate transactions, and timeout handling. Mention checking transaction status, notifications, and database updates.

3. 3

   What is the difference between smoke testing and sanity testing?

   Smoke testing checks critical functionalities after a new build to decide if further testing is possible. Sanity testing checks specific functionalities after minor changes. Relate to a startup scenario where quick build validation is crucial.

4. 4

   Explain the bug life cycle with an example.

   Describe stages: New, Assigned, Open, Fixed, Retest, Verified, Closed, Reopened. Use an example like a login button not working on a specific device, and explain how it moves through each stage with clear communication.

Practical Scenarios and Problem Solving

1. 5

   You have a login page with email and password fields. Write test cases for it.

   Include cases for valid credentials, invalid email format, empty fields, password masking, SQL injection attempts, account lockout after multiple failures, and forgot password link. Also test on different browsers and mobile devices.

2. 6

   How would you test an API endpoint that returns user transaction history?

   Check response status codes, data format (JSON), authentication, authorization, pagination, sorting, and error handling for invalid user IDs. Use Postman to send requests and validate responses against expected schema.

3. 7

   A bug is reported in production but you cannot reproduce it in your testing environment. What do you do?

   Gather more details from the reporter (steps, device, OS, logs), check production logs, try to replicate with similar conditions, and collaborate with developers to identify environment differences. Suggest adding logging or monitoring for future.

4. 8

   How do you decide which test cases to automate?

   Automate repetitive, stable, and high-risk test cases that run frequently, like regression tests for core features. Avoid automating unstable or one-time tests. Mention using frameworks like Selenium for web and Appium for mobile.

Tools and Technologies

1. 9

   What is the difference between Selenium WebDriver and Selenium IDE?

   Selenium IDE is a record-and-playback tool for simple tests, while WebDriver is a programming interface for creating robust, scalable automation scripts. WebDriver supports multiple languages and browsers, making it suitable for complex startup applications.

2. 10

   How do you perform API testing using Postman?

   Explain creating requests with different HTTP methods, adding headers and body, writing test scripts in JavaScript to validate status codes and response data, and using collections and environments for organized testing.

3. 11

   What are some common SQL queries you use for database testing?

   Mention SELECT with WHERE, JOINs to verify data across tables, COUNT and GROUP BY for aggregations, and UPDATE/DELETE for test data setup. Give an example like verifying a user's transaction history matches the UI.

4. 12

   How would you integrate automated tests into a CI/CD pipeline?

   Describe using Jenkins or GitLab CI to trigger test suites on code commits, running tests in parallel, and reporting results. Emphasize early feedback and maintaining test stability.

Behavioural and HR Questions

1. 13

   Tell me about a time you found a critical bug. How did you handle it?

   Use STAR method: describe the situation, the bug's impact, your actions to report and track it, and the outcome. Highlight collaboration with developers and preventing similar issues.

2. 14

   Why do you want to work as a QA Engineer at a fast-growing startup like Jupiter?

   Show passion for quality and interest in fintech. Mention the dynamic environment, opportunity to learn new tools, and impact on user experience. Avoid generic answers; relate to the company's mission.

3. 15

   How do you handle tight deadlines when you have limited time to test?

   Explain prioritizing critical test cases, using risk-based testing, and communicating clearly with the team about coverage. Mention automating regression tests to save time.

4. 16

   Describe a time you disagreed with a developer about a bug. How did you resolve it?

   Focus on data-driven discussion, providing evidence like logs or screenshots, and understanding the developer's perspective. Show willingness to compromise and escalate if needed for quality.