Sattviko QA Engineer Interview: Rounds, Questions and Preparation

What the job involves

As a QA Engineer at an Indian unicorn or high-growth startup like Sattviko, you will test web and mobile applications, write and execute test cases, log bugs, and work closely with developers and product managers to ensure releases are stable and user-friendly. You will often own quality for a feature end-to-end, from requirement review to post-release monitoring, in a fast-paced, agile environment.

Role and Technical Knowledge

1. 1

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

   Verification checks if we are building the product right (reviews, inspections), while validation checks if we built the right product (actual testing). Give a simple example like a requirements review vs executing a test case.

2. 2

   Explain severity and priority with an example relevant to a food-tech or e-commerce app.

   Severity is impact on functionality, priority is urgency to fix. Example: a payment failure is high severity and high priority; a spelling mistake on the homepage is low severity but may be high priority before a launch.

3. 3

   What is the bug life cycle? Walk me through the stages.

   Cover New, Assigned, Open, Fixed, Retest, Verified, Closed, and Reopened. Mention that some bugs may be deferred or rejected, and explain why a tester might reopen a bug.

4. 4

   How do you decide what to include in a smoke test versus a regression test?

   Smoke test is a quick check of critical functionalities after a new build; regression test is a broader set to ensure new changes did not break existing features. Relate it to a startup release cycle where time is limited.

Practical Scenarios and Testing Approach

1. 5

   You are asked to test a new coupon code feature on a food delivery app. How would you approach it?

   Start with requirement analysis, then write test cases for valid/invalid codes, expiry, minimum order value, single-use, stacking, and edge cases like applying after payment. Mention checking backend validation and database entry.

2. 6

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

   Provide clear steps, screenshots, video, logs, environment details, and try to reproduce on different devices or builds. If still not reproducible, mark it as such but keep it open for monitoring and collaborate with the developer.

3. 7

   How would you test an API endpoint that returns a list of restaurants based on user location?

   Use Postman to check status codes, response time, data format, authentication, pagination, and error handling for invalid coordinates. Also test boundary values like no restaurants found or very large radius.

4. 8

   You have to test a mobile app that works on both Android and iOS. What is your strategy?

   Cover device fragmentation, OS versions, screen sizes, network conditions, and platform-specific behaviours like permissions and back button. Mention using emulators/simulators and real devices, and prioritizing based on user analytics.

Automation and Tools for Startups

1. 9

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

   A test case is a set of steps and expected results, often manual; a test script is an automated version written in code. Explain that test scripts are reusable and faster for regression but need maintenance.

2. 10

   How would you use Selenium to automate a login test for a web app?

   Mention locating elements by ID, name, or XPath, using WebDriver methods like sendKeys and click, adding assertions, and handling waits. Keep it simple and acknowledge that not all tests should be automated.

3. 11

   What are some challenges of automation in a fast-growing startup?

   Frequent UI changes, limited time, and lack of stable test data can make automation brittle. A strong answer suggests starting with stable, high-value test cases and using a hybrid approach.

4. 12

   How do you validate data in the database after performing an action in the UI?

   Write SQL queries to check that records are inserted, updated, or deleted correctly. Mention joining tables if needed and verifying that the UI reflects the database state, especially for order or payment flows.

Behavioural and HR Questions

1. 13

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

   Use STAR format: describe the situation, the bug, your action (reporting with details, following up), and the result (bug fixed, release saved). Highlight your attention to detail and communication.

2. 14

   Why do you want to work as a QA Engineer at a startup like Sattviko?

   Show enthusiasm for quality and fast-paced learning. Mention ownership, direct impact on users, and the chance to work across manual and automation. Avoid generic answers about 'good company culture'.

3. 15

   How do you handle pressure when multiple releases are happening at once?

   Talk about prioritizing based on risk and impact, communicating clearly with the team, and using checklists or smoke tests to cover critical paths first. Give an example from college projects or internships.

4. 16

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

   Show a growth path: from manual testing to automation, performance, or security testing. Mention gaining certifications or learning new tools, and a desire to contribute to overall product quality.