The Good Glamm Group QA Engineer Interview: Rounds, Questions and Preparation

What the job involves

A QA Engineer at an Indian unicorn or high-growth startup like The Good Glamm Group tests web and mobile apps for e-commerce, content, and community features. Day to day you write test cases, log bugs in tools like Jira, run regression cycles before releases, and work closely with developers and product managers to ship fast without breaking the user experience.

Role and company knowledge

1. 1

   What does a QA Engineer do differently at a fast-growing startup compared to a large service company?

   Mention faster release cycles, more ownership, wearing multiple hats, and testing across web and mobile with limited resources. Avoid saying startups skip testing.

2. 2

   How would you test a new 'add to cart' flow on a beauty e-commerce app?

   Cover functional checks like adding, updating quantity, removing items, and edge cases like out-of-stock, expired offers, and network failure. Show you think about both UI and backend.

3. 3

   What is the difference between verification and validation in testing?

   Verification checks if you built the product right (reviews, walkthroughs), validation checks if you built the right product (actual testing). Give a simple example from an app feature.

4. 4

   Why do you want to work as a QA Engineer in the Indian startup ecosystem?

   Connect to fast learning, direct impact on user experience, and interest in consumer tech like e-commerce or content platforms. Be specific about why QA matters for growth.

Technical QA knowledge

1. 5

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

   List stages like New, Assigned, Open, Fixed, Retest, Verified, Closed, and Reopened. Explain what a tester does at each stage and when a bug is deferred or rejected.

2. 6

   How do you decide which test cases to include in a regression suite before a major app release?

   Focus on high-traffic flows, recently changed code, critical business logic like payments and login, and previously buggy areas. Mention prioritising based on risk and time available.

3. 7

   What is the difference between smoke testing and sanity testing?

   Smoke testing checks if the build is stable enough for further testing. Sanity testing checks a specific fix or narrow area after a minor change. Give a quick example from a mobile app update.

4. 8

   How would you test an API endpoint that returns a user's order history?

   Cover status codes, response schema, authentication, pagination, empty states, and error handling. Mention using Postman and checking data consistency with the database.

Practical scenarios

1. 9

   You find a critical bug 30 minutes before a release. What do you do?

   Say you immediately report it with clear steps and evidence, assess impact with the team, and recommend either a hotfix or a rollback. Show you can stay calm and communicate clearly.

2. 10

   A developer says your bug is 'not reproducible'. How do you handle it?

   Provide detailed steps, screenshots or video, device and OS details, and try to reproduce on a different environment. Offer to pair with the developer to debug together.

3. 11

   How would you test a discount coupon feature that applies only to first-time users on a mobile app?

   Cover new vs existing user accounts, coupon expiry, multiple coupons, backend validation, and edge cases like app reinstall or different login methods. Mention both positive and negative tests.

4. 12

   You have to test a new feature but there is no documentation. What is your approach?

   Talk to the product manager or developer, explore the feature as a user, create your own test scenarios, and document your findings. Show initiative and curiosity.

Behavioural and HR questions

1. 13

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

   Pick a real example from college projects or internships. Show you took ownership, fixed it quickly, and learned to double-check your work.

2. 14

   How do you handle pressure when multiple releases are happening at the same time?

   Mention prioritising based on impact, using checklists, communicating blockers early, and staying organised with tools like Jira. Avoid saying you just work longer hours.

3. 15

   Describe a situation where you had to explain a technical issue to a non-technical person.

   Use a college project or group work example. Focus on simplifying language, using analogies, and confirming the other person understood.

4. 16

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

   Show growth towards automation, performance testing, or QA lead responsibilities. Mention learning new tools and taking more ownership of release quality.