Mstock QA Engineer Interview: Rounds, Questions and Preparation

What the job involves

QA Engineers at Indian unicorns and high-growth startups like Mstock test web and mobile products for functionality, performance, and security before release. They write and run manual test cases, build automation scripts, log bugs, and work closely with developers in fast sprint cycles. Freshers are expected to learn quickly, think like a user, and communicate defects clearly.

Role and Technical Knowledge

1. 1

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

   Explain verification as checking if we built the product right through reviews and static testing, and validation as checking if we built the right product through actual execution. Give a small example like reviewing a test plan versus running test cases.

2. 2

   How would you test a stock trading app's buy order flow at a startup like Mstock?

   Cover positive and negative cases, login and KYC checks, balance validation, market hours, order types, partial fills, cancellation, and confirmation screens. Mention edge cases like network drop, insufficient funds, and duplicate taps.

3. 3

   What is the bug life cycle and what statuses does a defect go through?

   List New, Assigned, Open, Fixed, Retest, Verified, Closed, and Reopened or Deferred. Explain who moves the bug at each stage and why clear reproduction steps matter.

4. 4

   What is the difference between smoke testing and sanity testing?

   Smoke testing checks whether the build is stable enough for further testing, while sanity testing checks a specific fix or small change after a minor update. Give an example from a mobile app release.

Practical Scenarios and Tools

1. 5

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

   Describe capturing logs, device model, OS version, steps to reproduce, screenshots or video, and severity. Mention checking if it is reproducible on other devices and tagging the developer with clear priority.

2. 6

   How would you test an API endpoint that returns a user's portfolio holdings?

   Cover status codes, authentication tokens, response schema, data correctness against the database, pagination, error handling for invalid user IDs, and performance under load. Mention using Postman and SQL to verify data.

3. 7

   Write a few test cases for a login screen with mobile number and OTP.

   Include valid login, invalid number format, wrong OTP, expired OTP, resend OTP limits, blank fields, and rate limiting. Mention both UI behavior and backend validation.

4. 8

   What SQL query would you write to find users who placed more than three orders today?

   Show a GROUP BY with HAVING COUNT, filtering by date and status. Explain how you would use this to validate data after a release and why joins might be needed for user details.

Behavioural and Teamwork

1. 9

   Tell me about a time you found a mistake in a project or assignment. How did you handle it?

   Use a simple STAR structure. Highlight how you noticed the issue, communicated it early, fixed it, and what you learned to prevent repeats. Show ownership without blaming others.

2. 10

   How would you handle a developer who says your bug is not reproducible and closes it?

   Stay calm and factual. Explain sharing detailed steps, logs, and a screen recording, and offering to reproduce it together. Mention escalating politely if it affects users and following the team's process.

3. 11

   Describe a situation where you had to learn a new tool or technology quickly.

   Pick a real example like learning Postman, Selenium, or SQL for a college project. Focus on how you found resources, practiced, and applied it under a deadline.

4. 12

   Why do you want to work as a QA Engineer at a fast-growing startup rather than a large service company?

   Talk about ownership, faster releases, direct impact on users, and learning across manual and automation testing. Connect it to your interest in fintech or consumer apps and willingness to adapt.

HR and Career Fit

1. 13

   What do you know about our company and why do you want to join us?

   Research the company's product, recent news, and user base. Mention specific features or challenges that interest you and how your QA skills can help improve reliability.

2. 14

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

   Show a clear path from manual testing to automation, API testing, and possibly performance or security testing. Mention taking more ownership of test planning and mentoring juniors.

3. 15

   How do you handle tight deadlines when you have to test a release in a few hours?

   Explain prioritizing critical user flows, using smoke and regression checklists, and communicating risks clearly to the team. Mention staying focused and avoiding shortcuts that skip core checks.

4. 16

   What are your salary expectations for this role?

   Give a reasonable range based on research for fresher QA roles in Indian startups. Say you are open to the company's standard package for the role and focus on learning and growth.