hirecept

Software Testing and QA: Interview questions: manual, automation, API and scenarios

QA interviews cover testing basics and terminology, then test design, then automation and API testing, and often a few scenario questions such as testing a login page. This kit works for any employer hiring manual or automation testers.

17 questions · 3 rounds · updated Nov 2026

How the interview works

  1. Testing fundamentals: Life cycle, test types, design techniques, defect reporting.
  2. Automation and tools: Selenium, frameworks, API testing, SQL basics, performance.
  3. Scenarios: Testing everyday objects and features, handling disagreements.

Sample questions

  • 01

    You're asked to test a feature with no written requirements and a release in two days. What do you do?

    MediumScenarios

    Model answer

    What the interviewer checks

    Initiative, risk-based prioritisation and clear communication of what was and wasn't covered.

    How to answer

    1. Spend 30 minutes with the developer and product owner to agree what the feature should do. Write it as a short checklist of acceptance criteria and send it back to confirm. 2. Prioritise by risk: money, data loss, security and the most-used paths first. 3. Run exploratory sessions with a charter (for example "explore coupon stacking for 45 minutes") alongside the critical regression checks. 4. Log bugs immediately with clear severity, so the fixes can land within the two days. 5. Before release, send a short status note: what was tested, what wasn't, known open issues and the risk level. The decision to ship is then informed.

  • 02

    An age field accepts 18 to 60 inclusive. Using boundary value analysis, which set of values should you test?

    MediumTest design

  • 03

    After a data migration, write SQL checks to confirm that no orders were lost or duplicated between old_orders and new_orders.

    MediumDatabase testing

    Approach and solution

    Approach

    Compare row counts and totals, then find rows missing on either side with anti-joins, then look for duplicates on the business key.

    -- 1. Counts and totals match
    SELECT (SELECT COUNT(*) FROM old_orders) AS old_count,
           (SELECT COUNT(*) FROM new_orders) AS new_count,
           (SELECT SUM(amount) FROM old_orders) AS old_total,
           (SELECT SUM(amount) FROM new_orders) AS new_total;
    
    -- 2. Rows missing from the new table
    SELECT o.order_id FROM old_orders o
    LEFT JOIN new_orders n ON n.order_id = o.order_id
    WHERE n.order_id IS NULL;
    
    -- 3. Duplicates in the new table
    SELECT order_id, COUNT(*) FROM new_orders
    GROUP BY order_id HAVING COUNT(*) > 1;

    Complexity: Each check is one pass or one join.

14 more questions, members only

  • Testing fundamentals7
  • Test design and scenarios4
  • Automation and tools6

Members also get how to answer each question and a preparation plan for this company.

See plans from ₹399

Every question and answer is written by Hirecept and the code is run before it is published. How a company runs its process comes from candidate reports and public pages, and companies change it, so treat that part as a guide, not a promise.