Skip to content
Software Testing
All courses OffersPlacement Report
‹ Back to previous sectionCourse homeAll page URLs

Software Testing Interview Questions for Product Companies

40 questions weighted to the interview style of product companies — 2 easy, 28 medium, 10 hard.

How product companies interview for Software Testing

Product companies run deeper interviews with fewer, harder questions. Expect hands-on problem solving, scenario and design questions, follow-ups that test your depth, and a round on ownership and impact. Your projects should show measurable results.

This set focuses on Agile, SQL and API Testing (7), Database Testing (6), Testing Types (5), Test Case Design (4).

Hiring manager round Online coding assessment Technical round 1 (DSA) HR round Technical round 1
Solved — product companiesStart practicing
3 QUESTIONS FREESign up to unlock the full question bank and track your progress.Unlock every question and answer, then continue practising company-wise and package-wise.
3 questions free Unlock the rest in seconds
01

Write test cases for an ATM withdrawal.

Test Case DesignMedium
Save to ▾
Show answer
Valid card and PIN, wrong PIN, three failed attempts, amount above balance, amount above daily limit, invalid denomination, machine out of cash, network failure and receipt printing.
02

What is data mapping testing?

Database TestingMedium
Save to ▾
Show answer
Data mapping testing checks that each field on a screen, file or API goes to the correct table and column with the correct format. For example, the Date of Birth field on the signup form must land in users.dob as a date, and the State dropdown must store the state code, not the label. Testers use a mapping document, enter known values in the UI or API and query the database to compare field by field.
03

What is visual regression testing in automation?

Automation Basics for Manual TestersMedium
Save to ▾
Show answer
Visual regression testing takes screenshots of pages or components and compares them with approved baseline images to detect unexpected layout, font, colour or spacing changes that functional assertions miss. When a difference crosses a threshold, a person reviews it and either accepts the new baseline or logs a bug. Dynamic content like dates and ads must be masked, and the same browser and screen size must be used to avoid noise.
04

How do you test database integrity using SQL?

Agile, SQL and API TestingMedium
Save to ▾
Show answer
Verify inserted, updated and deleted rows match UI actions, check constraints, duplicates, NULLs and totals with COUNT and SUM queries.
05

How would you test a payment gateway?

Test Case DesignHard
Save to ▾
Show answer
Success, failure and pending flows, timeouts, refunds, double-click payments, every method (UPI, cards, net banking), rounding, security (no card data stored) and reconciliation with bank reports.
06

What is a performance baseline?

Performance and Security BasicsMedium
Save to ▾
Show answer
A performance baseline is a set of measurements of the current system under a known load, such as response times, throughput, error rate and resource usage. Every new build or release is compared with it to spot regressions. For example, if the checkout API had p95 of 800 milliseconds at 200 users last release and now shows 1.5 seconds, the change needs investigation. A benchmark compares against an industry or competitor standard.
07

Customer records are being moved from an old system to a new one. How do you test the migration?

Testing TypesHard
Save to ▾
Show answer
Compare record counts per table before and after. Check field mapping, data types, formats, encodings and default values for a sample of records, including edge cases like nulls, special characters and very old records. Verify relationships are kept, such as each order still linked to its customer. Run key business reports in both systems and compare totals. Test the rollback plan and confirm the new application works with migrated data.
08

SQL: find orders whose total does not match the sum of their order items.

Agile, SQL and API TestingHard
Save to ▾
Show answer
SELECT o.order_id, o.total_amount, SUM(i.quantity * i.unit_price) AS items_total FROM orders o JOIN order_items i ON i.order_id = o.order_id GROUP BY o.order_id, o.total_amount HAVING o.total_amount <> SUM(i.quantity * i.unit_price);
09

Notifications arrive late, and some screens look broken, only on certain Android phone brands. Why can this happen and what do you test?

Mobile TestingMedium
Save to ▾
Show answer
Android phone makers ship their own skins and settings on top of Android, so the same app can behave differently. Common problems are aggressive battery savers that kill background tasks and delay notifications, different permission screens, custom fonts and display scaling, camera differences and modified WebViews. Pick devices from the brands most used by your audience and test background work, notifications, camera and layout on each.
10

A manager wants to cut QA time in half. How do you explain the value of testing?

Manual Testing BasicsHard
Save to ▾
Show answer
Use data, not opinion. Show defects caught before release by severity, production incidents and their cost, and defect leakage trends. Explain what risk increases if testing is cut, then offer options: risk-based testing of critical flows, more automation for regression, and developers owning unit tests. Agree on which risks the business accepts in writing. This turns the discussion into a trade-off decision instead of a conflict.
11

How do you test time zone handling for timestamps stored in a database?

Database TestingHard
Save to ▾
Show answer
Check how timestamps are stored, ideally in UTC with a time zone aware type. Create a record from a user in IST and another in a different zone, then query the raw value and compare it with what each user sees on screen. Test boundaries such as orders placed just before midnight IST, which fall on the previous UTC date, and daylight saving changes for foreign users. Reports grouped by date are a common bug area.
12

What do testers look for during a requirement review?

Manual Testing BasicsMedium
Save to ▾
Show answer
Check that each requirement is clear, complete, consistent and testable. Look for vague words like fast or user-friendly, missing error handling, undefined limits, conflicting rules and missing roles or states. For each requirement ask how you would test it and what the expected result is. Record questions in a review log and get answers from the business analyst before writing test cases, so ambiguity does not turn into defects later.
13

Your automated accessibility scan shows zero errors. Is the page accessible?

Accessibility & Usability TestingMedium
Save to ▾
Show answer
Not necessarily. Automated tools catch only a part of WCAG issues, such as missing labels and contrast. A clean scan still needs manual checks: keyboard-only navigation, focus order, a screen reader pass, meaningful alt text and link names, error handling, zoom and reflow and dynamic content. Report the result as 'no automated violations found' and add the manual checklist outcome before claiming conformance.
14

Write test cases for a coupon code field at checkout.

Test Case DesignMedium
Save to ▾
Show answer
Apply a valid coupon and check the discount and final amount. Test invalid, expired and not-yet-active coupons. Check minimum order value, maximum discount cap and category restrictions. Verify one-time-use coupons cannot be reused and that only one coupon applies if stacking is not allowed. Check case sensitivity and leading or trailing spaces. Remove the coupon and confirm the total resets. Change cart items after applying and verify the discount is recalculated.
15

A user updates their phone number in the app, but the old number still appears in reports. What do you check?

Database TestingMedium
Save to ▾
Show answer
First query the main users table to see whether the update was saved. If it was, check where the report reads from: a view, a reporting copy, a cache or a nightly ETL table. The report may simply be stale until the next refresh, which may be by design. If the main table still has the old value, check the API request, the update query and any errors in logs, then log a bug with both query results.
16

A monthly report query runs on millions of rows and takes minutes. How do you test and report its performance?

Database TestingHard
Save to ▾
Show answer
Test on a database with production-like volume, not a small QA dataset. Measure the run time several times and note the filters used. Ask for or run the execution plan to see whether it does full table scans or uses indexes. Compare with the agreed target, such as under five seconds. Report the query, data volume, timings and plan, and retest after fixes such as indexes, date filters or summary tables.
17

A web app gets slower the longer a user keeps it open. How do you check for a memory leak as a manual tester?

Performance and Security BasicsHard
Save to ▾
Show answer
A memory leak happens when an application keeps holding memory it no longer needs, so usage grows the longer it runs. A manual tester may notice the app getting slower over a long session, a browser tab using more and more memory in Task Manager or the browser's memory panel, or a mobile app crashing after repeatedly opening and closing a screen. Report the steps, duration and memory readings over time.
18

How do you capture logs from an Android device for a bug report?

Mobile TestingMedium
Save to ▾
Show answer
Enable developer options and USB debugging, connect the phone and confirm it is visible with adb devices. Clear old logs with adb logcat -c, reproduce the bug, then save logs with adb logcat -d > crash_log.txt, filtering by the app package or error level if needed. For a crash, search for FATAL EXCEPTION. Attach the log, device model, OS version, app version and a screen recording to the bug.
19

You change the order ID in a URL and see another customer's order. What is this and what do you do?

Performance and Security BasicsHard
Save to ▾
Show answer
This is an insecure direct object reference, a form of broken access control and a critical security bug, because any user can read other users' data. Stop exploring further beyond what is needed to confirm it, record the request, accounts used and evidence, and log it as a critical bug with restricted visibility. Inform the lead and security contact immediately. The fix is a server-side ownership check on every request.
20

The test environment is down for two days just before release. What do you do?

STLC and Test PlanningMedium
Save to ▾
Show answer
Escalate immediately with the impact on the schedule. While it is down, prepare test data, review and update test cases, and test what you can elsewhere: API tests against another environment, UI on a developer machine or a staging copy. Track the lost hours in the status report. When the environment returns, run smoke first, then the prioritised list, and ask whether the release date or scope needs to change.
21

The developer says "it's not a bug". What do you do?

Bug Life Cycle and JiraMedium
Save to ▾
Show answer
Re-check the requirement, reproduce with clear steps and evidence (screenshots, logs), discuss with the BA/PO and record the final decision.
22

What is TDD vs BDD?

Agile, SQL and API TestingMedium
Save to ▾
Show answer
TDD writes unit tests before code to drive design; BDD describes behaviour in business language scenarios that become automated acceptance tests.
23

What is a sprint retrospective?

Agile, SQL and API TestingMedium
Save to ▾
Show answer
A team meeting at the end of a sprint to discuss what went well, what did not and what to improve next.
24

What new success criteria in WCAG 2.2 should testers know?

Accessibility & Usability TestingHard
Save to ▾
Show answer
WCAG 2.2, published in 2023, added criteria including Focus Not Obscured, so sticky headers must not hide the focused element; Dragging Movements, which needs a non-drag alternative; Target Size Minimum of 24 by 24 CSS pixels; Consistent Help placement; Redundant Entry, so users are not asked for the same information twice; and Accessible Authentication, which avoids memory puzzles at login. It also removed the old Parsing criterion.
25

SQL: find customers who placed more than three orders in the last 30 days.

Agile, SQL and API TestingMedium
Save to ▾
Show answer
SELECT c.id, c.name, COUNT(o.id) AS order_count FROM customers c JOIN orders o ON o.customer_id = c.id WHERE o.order_date >= CURRENT_DATE - INTERVAL '30' DAY GROUP BY c.id, c.name HAVING COUNT(o.id) > 3 ORDER BY order_count DESC;
26

What are SQL constraints?

Agile, SQL and API TestingMedium
Save to ▾
Show answer
Rules such as NOT NULL, UNIQUE, PRIMARY KEY, FOREIGN KEY and CHECK that keep data valid and consistent.
27

What is a test basis?

Manual Testing BasicsEasy
Save to ▾
Show answer
The test basis is the set of documents and knowledge from which test cases are derived. It includes requirement specifications, user stories with acceptance criteria, design documents, wireframes, API contracts, business rules and even existing system behaviour. A good test basis lets you trace each test case back to a requirement. If the test basis is weak or missing, testers must clarify it before or while testing.
28

SQL: find rows where mandatory columns are NULL or empty in a customers table.

Database TestingEasy
Save to ▾
Show answer
-- Mandatory fields: name, email, phone SELECT id, name, email, phone FROM customers WHERE name IS NULL OR TRIM(name) = '' OR email IS NULL OR TRIM(email) = '' OR phone IS NULL OR TRIM(phone) = ''; -- Expected result: no rows
29

What is accessibility testing?

Testing TypesMedium
Save to ▾
Show answer
Checking that people with disabilities can use the product, using screen readers, keyboard navigation, colour contrast and WCAG guidelines.
30

What is contract testing?

Testing TypesHard
Save to ▾
Show answer
Contract testing checks that a service provider and its consumers agree on the API format, such as request fields, response fields and status codes, without running a full end-to-end environment. The consumer defines what it expects, and the provider's build verifies it still meets that contract. It catches breaking changes early in microservice systems, where full integration environments are slow and fragile.
31

What are stubs and drivers?

Testing TypesMedium
Save to ▾
Show answer
Both are temporary pieces of code used in integration testing when some modules are not ready. A stub replaces a called lower-level module and returns fixed responses, used in top-down testing; for example, a stub payment service that always returns success. A driver replaces a calling higher-level module and sends inputs to the module under test, used in bottom-up testing. In API testing, mock servers play the role of stubs.
32

A requirement says the page should load fast. How do you turn it into a test case?

Test Case DesignMedium
Save to ▾
Show answer
The word fast is not testable, so ask the product owner for a measurable target, for example the page loads within 3 seconds on a 4G network for 95 percent of requests. Agree on the conditions: device, network, data size and whether it is first load or cached. Then write the test with those conditions and expected time. Record the agreed number in the story so the expected result is not open to opinion.
33

How do you write a good accessibility bug report?

Accessibility & Usability TestingMedium
Save to ▾
Show answer
Give a clear title, such as 'Checkout: Place Order button not reachable by keyboard'. Include the page URL, browser, operating system and assistive technology with versions. Write exact steps, what was announced or happened, and what was expected. Add the WCAG success criterion, such as 2.1.1 Keyboard, and the user impact. Attach a screenshot or audio recording, and suggest a fix when obvious. Severity should reflect whether users are fully blocked.
34

How do you test an application when requirements change frequently?

STLC and Test PlanningMedium
Save to ▾
Show answer
Keep tests modular, prioritise by risk, use exploratory testing, automate stable parts and keep close contact with product owners.
35

Write a CSS selector and an XPath for a Login button that has the attribute data-testid='login-btn' and the text Login.

Automation Basics for Manual TestersMedium
Save to ▾
Show answer
/* CSS selector using the test id */ button[data-testid='login-btn'] // XPath using the test id //button[@data-testid='login-btn'] // XPath using the visible text //button[normalize-space()='Login']
36

How do you test a database trigger?

Database TestingMedium
Save to ▾
Show answer
First read what the trigger should do and when it fires, such as AFTER UPDATE on the salary column writing a row to an audit table. Then perform the event that should fire it and query the target table to confirm the expected row and values. Also perform events that should not fire it and confirm nothing happens. Check multi-row updates, NULL values and rollback: if the main statement fails, the trigger's changes must not remain.
37

What is exploratory testing?

Testing TypesMedium
Save to ▾
Show answer
Learning, test design and execution at the same time, without scripted cases — time-boxed sessions with a charter (e.g. 'explore checkout with coupons'), noting bugs and ideas. Great for finding edge cases.
38

What is defect leakage?

Bug Life Cycle and JiraMedium
Save to ▾
Show answer
Defects found after release that testing should have caught; leakage % = defects in production / total defects x 100.
39

The UI shows the correct order total, but the database has a different value. What do you check?

Agile, SQL and API TestingMedium
Save to ▾
Show answer
Note the order ID and compare the UI value, the API response and the database value to find where they differ. Check if the UI calculates the total on the screen instead of using the saved value, whether taxes, discounts or rounding are applied at different layers and whether a later update job changed the record. Log the bug with all three values, because invoices and reports will use the database figure.
40

What is cross-site scripting (XSS)?

Performance and Security BasicsMedium
Save to ▾
Show answer
XSS is a vulnerability where an attacker's script is injected into a page and runs in other users' browsers, which can steal session data or change the page. It occurs when user input is shown without proper encoding. Testers enter a harmless script tag or an image tag with an onerror alert in comments, profile names and search boxes, then check if it executes when the page is displayed. Output encoding prevents it.

Product companies (31)

Product

Amazon

Software Testing interview questions

  • 40 questions
  • 5 rounds

Bengaluru, Hyderabad, Chennai +2

View questions
Product

Google

Software Testing interview questions

  • 40 questions
  • 5 rounds

Bengaluru, Hyderabad, Gurugram +2

View questions
Product

Meta

Software Testing interview questions

  • 40 questions
  • 5 rounds

Gurugram, Bengaluru, Hyderabad +1

View questions
Product

Microsoft

Software Testing interview questions

  • 40 questions
  • 5 rounds

Hyderabad, Bengaluru, Noida +2

View questions
Product

Adobe

Software Testing interview questions

  • 40 questions
  • 5 rounds

Noida, Bengaluru, Gurugram

View questions
Product

Oracle

Software Testing interview questions

  • 40 questions
  • 5 rounds

Bengaluru, Hyderabad, Noida +2

View questions
Product

Salesforce

Software Testing interview questions

  • 40 questions
  • 5 rounds

Hyderabad, Bengaluru, Mumbai +1

View questions
Product

ServiceNow

Software Testing interview questions

  • 40 questions
  • 5 rounds

Hyderabad, Bengaluru

View questions
Product

Atlassian

Software Testing interview questions

  • 40 questions
  • 5 rounds

Bengaluru

View questions
Product

LinkedIn

Software Testing interview questions

  • 40 questions
  • 5 rounds

Bengaluru, Gurugram, Mumbai

View questions
Product

Uber

Software Testing interview questions

  • 40 questions
  • 5 rounds

Bengaluru, Hyderabad, Gurugram

View questions
Product

Ola

Software Testing interview questions

  • 40 questions
  • 4 rounds

Bengaluru

View questions
Product

Freshworks

Software Testing interview questions

  • 40 questions
  • 5 rounds

Chennai, Bengaluru, Hyderabad

View questions
Product

Zoho

Software Testing interview questions

  • 40 questions
  • 5 rounds

Chennai, Tenkasi

View questions
Product

BrowserStack

Software Testing interview questions

  • 40 questions
  • 5 rounds

Mumbai, Bengaluru

View questions
Product

Dream11

Software Testing interview questions

  • 40 questions
  • 5 rounds

Mumbai

View questions
Product

SAP

Software Testing interview questions

  • 40 questions
  • 5 rounds

Bengaluru, Gurugram, Pune +1

View questions
Product

Sprinklr

Software Testing interview questions

  • 40 questions
  • 5 rounds

Gurugram, Bengaluru

View questions
Product

Postman

Software Testing interview questions

  • 40 questions
  • 4 rounds

Bengaluru

View questions
Product

InMobi

Software Testing interview questions

  • 40 questions
  • 5 rounds

Bengaluru

View questions
Product

Chargebee

Software Testing interview questions

  • 40 questions
  • 4 rounds

Chennai, Bengaluru

View questions
Product

Druva

Software Testing interview questions

  • 40 questions
  • 5 rounds

Pune

View questions
Product

ThoughtSpot

Software Testing interview questions

  • 40 questions
  • 4 rounds

Bengaluru

View questions
Product

Expedia Group

Software Testing interview questions

  • 40 questions
  • 4 rounds

Gurugram, Bengaluru

View questions
Product

Autodesk

Software Testing interview questions

  • 40 questions
  • 5 rounds

Bengaluru, Pune

View questions
Product

Red Hat

Software Testing interview questions

  • 40 questions
  • 4 rounds

Pune, Bengaluru

View questions
Product

Nutanix

Software Testing interview questions

  • 40 questions
  • 4 rounds

Bengaluru, Pune

View questions
Product

Workday

Software Testing interview questions

  • 40 questions
  • 4 rounds

Pune

View questions
Product

NetApp

Software Testing interview questions

  • 40 questions
  • 4 rounds

Bengaluru

View questions
Product

Urban Company

Software Testing interview questions

  • 40 questions
  • 4 rounds

Gurugram

View questions
Product

Rapido

Software Testing interview questions

  • 40 questions
  • 4 rounds

Bengaluru

View questions

Frequently asked questions

How are Software Testing interviews at product companies different?

Product companies run deeper interviews with fewer, harder questions. Expect hands-on problem solving, scenario and design questions, follow-ups that test your depth, and a round on ownership and impact. Your projects should show measurable results.

Which product companies are covered?

This page links to 31 product companies, including Amazon, Google, Meta, Microsoft, Adobe, Oracle, Salesforce, ServiceNow. Each has its own page with rounds and a separate practice set.

What rounds should I expect?

Common rounds at these companies include: Hiring manager round; Online coding assessment; Technical round 1 (DSA); HR round; Technical round 1. The exact process varies by company and role.

Other company types

IT services companiesConsulting companiesAnalytics companiesE-commerce & consumer tech companiesFintech companiesBanking & finance companiesHardware & semiconductors companiesTelecom companies

More ways to practise

Company-wise Software Testing questionsPackage-wise Software Testing questionsExperience-wise Software Testing questionsRole-wise Software Testing questionsCity-wise Software Testing questionsMost asked Software Testing questionsScenario-based questionsPractical / hands-on questionsHR & behavioural questionsSoftware Testing mock interviewOnline assessment questionsTechnical round questionsManagerial round questionsSoftware Testing topic sheets