Meesho QA Engineer Interview: Rounds, Questions and Preparation

What the job involves

QA Engineers at Indian unicorns and high-growth startups like Meesho test web and mobile products to ensure they work correctly at massive scale. They write manual test cases, automate regression suites, log and track bugs, and work closely with developers and product managers to ship features fast without breaking existing flows. Day to day involves understanding user stories, testing on real devices, and monitoring release health.

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 example like reviewing a test plan versus executing test cases.

2. 2

   How do you write a good test case? What are the key elements?

   Mention elements like test case ID, description, preconditions, steps, expected result, actual result, and status. Emphasise clarity, reusability, and traceability to requirements. Say that a good test case is independent and covers positive and negative scenarios.

3. 3

   Explain the bug life cycle. What happens after you log a bug?

   Walk through stages: New, Assigned, Open, Fixed, Retest, Verified, Closed, and Reopened. Mention that you as a QA retest the fix and close only if it passes. Highlight communication with developers for clarity.

4. 4

   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 functionality after a minor change to ensure it works. Give examples from a mobile app like login or payment flow.

Practical Scenarios

1. 5

   You find a bug that crashes the app only on a low end Android device. How do you report it?

   Describe capturing logs, screen recording, device model, OS version, steps to reproduce, and frequency. Mention severity and priority. Say you would attach evidence and tag the relevant developer. Emphasise that you would also check if it is reproducible on other devices.

2. 6

   How would you test a new 'refer and earn' feature on a shopping app?

   Cover test cases for referral code generation, sharing via different channels, successful signup, reward credit, duplicate referrals, expired codes, and edge cases like self referral. Mention testing on slow networks and checking backend database for reward entries.

3. 7

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

   Stay calm and collaborative. Ask for their environment details, share your exact steps with screenshots or video, and try to reproduce together. If still not reproducible, document it as environment specific and monitor. Show that you value teamwork over blame.

4. 8

   How do you decide what to test when you have very little time before a release?

   Prioritise based on risk and business impact. Focus on critical user flows like login, search, cart, and payment. Use smoke and sanity tests. Mention that you would communicate clearly with the team about what is covered and what is not.

Automation and Tools

1. 9

   What is the difference between manual testing and automation testing? When would you automate?

   Manual testing is human driven and good for exploratory, usability, and one time tests. Automation is script based and good for repetitive, regression, and large scale tests. Say you would automate stable features that run frequently.

2. 10

   How do you test a REST API using Postman?

   Mention creating requests with correct methods like GET and POST, adding headers and body, checking status codes, response time, and response body. Talk about using collections, environment variables, and writing basic tests in the Tests tab.

3. 11

   Write a simple SQL query to find duplicate email addresses in a users table.

   Show a query like SELECT email, COUNT(*) FROM users GROUP BY email HAVING COUNT(*) > 1. Explain that you use SQL to validate backend data after UI actions. Keep it simple and correct.

4. 12

   What are some common challenges in mobile app testing?

   Mention device fragmentation, different screen sizes, OS versions, network conditions, interruptions like calls, and battery usage. Say you prioritise based on analytics of your user base. Show awareness of real device testing versus emulators.

Behavioural and HR

1. 13

   Tell me about a time you found a critical bug just before a release. What did you do?

   Use STAR format. Describe the situation, the bug you found, how you escalated it calmly, and how the team fixed it. Highlight ownership, clear communication, and focus on user impact.

2. 14

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

   Show passion for quality and user experience. Mention that startups offer ownership, fast learning, and direct impact. Connect it to your interest in testing at scale and working across teams.

3. 15

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

   Talk about prioritisation, time management, and communication. Give an example from college projects or internships. Say you break work into smaller tasks and keep stakeholders informed.

4. 16

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

   Show growth mindset. Mention moving from manual to automation, learning new tools, and possibly leading a small module. Align your goals with the company's need for quality at scale. Avoid saying you want to move to development.