OYO QA Engineer Interview: Rounds, Questions and Preparation

What the job involves

A QA Engineer at Indian unicorns and high-growth startups like OYO tests web and mobile products for functionality, performance, and reliability under rapid release cycles. Day to day, you write test cases, execute manual and automated tests, log bugs, and work closely with developers and product managers to ensure a seamless user experience. You often own quality for a feature end to end, from requirement review to post-release monitoring.

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 (reviews, static testing) while validation checks if we built the right product (dynamic testing, actual execution). Give a simple example like reviewing a requirement doc vs testing a login flow.

2. 2

   How would you test a hotel booking flow on a mobile app like OYO's?

   Cover search, filters, room selection, date picker, payment gateway, booking confirmation, and cancellation. Mention positive, negative, and edge cases like invalid dates, payment failure, and network loss.

3. 3

   What is the bug life cycle? Explain the states a bug goes through.

   List states: New, Assigned, Open, Fixed, Retest, Verified, Closed, Reopened, Deferred, Rejected. Explain each briefly and mention who moves it between states (tester, developer, manager).

4. 4

   What are the different levels of software testing?

   Name unit, integration, system, and acceptance testing. Briefly describe each and where they fit in the development cycle, especially in agile startups with continuous integration.

Practical Scenarios and Problem Solving

1. 5

   You find a critical bug 2 hours before a release. What do you do?

   Show prioritization: log the bug with clear steps, inform the lead and developer immediately, assess impact and workaround, and recommend whether to delay release or ship with a known issue based on severity.

2. 6

   How would you test an API endpoint that returns a list of available hotels?

   Mention checking status codes, response time, data schema, pagination, filtering, authentication, and error handling for invalid parameters. Also test with different user roles and empty results.

3. 7

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

   Provide detailed environment details, steps, screenshots, and logs. Offer to pair with the developer to reproduce it together and check if it is environment-specific or intermittent.

4. 8

   How would you test a payment gateway integration for a booking app?

   Cover successful payment, failed payment, timeout, refund, partial payment, and security aspects like encryption. Mention testing with different cards, UPI, and wallets, and verifying order status in the database.

Automation and Tools

1. 9

   What is the difference between Selenium and Appium?

   Explain that Selenium is for web automation while Appium is for mobile app automation (Android and iOS). Mention that both support multiple languages and can be integrated with frameworks like TestNG.

2. 10

   Write a simple SQL query to find all users who made more than 3 bookings in the last month.

   Use SELECT, FROM, WHERE with date functions, GROUP BY user_id, and HAVING COUNT(*) > 3. Explain each clause and mention indexing for performance.

3. 11

   How do you decide which test cases to automate?

   Automate repetitive, high-risk, and regression tests that run frequently. Avoid automating one-time or UI-heavy tests that change often. Mention ROI and maintenance cost.

4. 12

   What is a test pyramid and why is it important?

   Describe the pyramid with many unit tests at the base, fewer integration tests in the middle, and few UI tests at the top. Explain that it ensures fast feedback and reduces flaky tests.

Behavioural and HR Questions

1. 13

   Tell me about a time you found a bug that others missed. How did you handle it?

   Use STAR method: describe the situation, your thorough testing approach, the bug you found, and how you communicated it to prevent a bad release. Highlight attention to detail.

2. 14

   How do you handle pressure when multiple releases are planned and deadlines are tight?

   Show prioritization based on risk and impact, clear communication with stakeholders, and willingness to work extra hours if needed. Mention using checklists and automation to save time.

3. 15

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

   Connect personal interest in quality and user experience with the startup's rapid pace and scale. Mention eagerness to learn, take ownership, and grow with the company.

4. 16

   Describe a time you disagreed with a developer or manager. How did you resolve it?

   Focus on data and user impact, not ego. Explain how you presented evidence, listened to their perspective, and reached a solution that improved the product.