Skip to content

Software Testing Interview Questions for Architects & Directors (₹40–50 LPA)

40 questions with answers for architects & directors — 12 medium, 28 hard.

What ₹40–50 LPA interviews expect

Enterprise-level architecture Organisation-wide strategy Governance and compliance Executive communication

About ₹40–50 LPA Software Testing roles

Roles in the ₹40–50 LPA band are typically for architects & directors. Interviewers check whether you can already do the work expected at this level, so questions here are weighted towards STLC and Test Planning (7), Agile, SQL and API Testing (6), Testing Types (5), Automation Basics for Manual Testers (4).

Salary bands are indicative only. The same skills can pay differently across cities, company types and negotiation.

Solved in this bandStart 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

How do you capture screenshots, videos and traces when an automated test fails?

Save to ▾
Show answer
Most frameworks support this through configuration. In Playwright, set screenshot to only-on-failure, video to retain-on-failure and trace to on-first-retry in the config, then open the trace viewer to step through actions, network calls and the page state. In Selenium, call save_screenshot in a teardown hook when a test fails. Store these artefacts in CI so anyone can debug the failure without rerunning it.
02

What do testers look for during a requirement review?

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.
03

What do you check when testing an API in Postman?

Save to ▾
Show answer
Status code, response body and schema, headers, response time, error messages for invalid input, authentication (401/403) and that data is saved in the database.
04

What are transaction isolation levels and what is a dirty read?

Save to ▾
Show answer
Isolation levels control how much one transaction can see of another's uncommitted work. Common levels are Read Uncommitted, Read Committed, Repeatable Read and Serializable. A dirty read is reading data another transaction changed but has not committed; if it rolls back, you acted on data that never existed. Testers check isolation using two database sessions: update without committing in one and query in the other to see what is visible.
05

What is a stored procedure and how do you test it?

Save to ▾
Show answer
A stored procedure is a named block of SQL logic saved in the database and called with parameters, for example a procedure that calculates monthly interest. To test it, call it with valid, boundary and invalid inputs, check the returned values or result sets, verify the rows it inserts or updates, check error handling for bad parameters and confirm it rolls back on failure. Also check its run time with realistic data volumes.
06

How would you test a feature that is enabled for only 10 percent of users through a feature flag?

Save to ▾
Show answer
Test both states: flag on and flag off, so existing users are not affected. Verify the targeting rule assigns the right users and that a user stays consistently in the same group. Test switching the flag on and off in a live session and confirm data created with the flag on still works after it is turned off. Check analytics events for both groups and confirm the flag can be rolled back quickly.
07

How would you choose a device matrix for testing an app in India?

Save to ▾
Show answer
Use the app's analytics, or market data if it is a new app, to find the top devices, OS versions and screen sizes. In India, cover a strong share of budget and mid-range Android phones with low RAM, a few manufacturers' custom Android skins, the two or three latest Android versions, and recent iPhones if iOS is supported. Add a tablet if relevant. Review the matrix each quarter and use a cloud device lab for wider coverage.
08

Leadership asks whether test automation is worth the investment for your project. How do you estimate the ROI?

Save to ▾
Show answer
Compare cost and savings over time. Cost includes building scripts, framework setup, tools, CI infrastructure and ongoing maintenance, often a large share of total effort. Savings include manual execution hours saved per run multiplied by runs per year, earlier bug detection and faster releases. For example, a 40-hour manual regression run every two weeks saves about 1000 hours a year. Tests that run rarely or break often may never pay back.
09

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

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.
10

How do you test a REST API with authentication?

Save to ▾
Show answer
Check access with valid, expired and missing tokens, role-based permissions, error codes and that sensitive data is never exposed.
11

Which accessibility laws and standards matter for products used in India and abroad?

Save to ▾
Show answer
In India, the Rights of Persons with Disabilities Act 2016 requires accessible information and communication technology, and government sites follow the GIGW guidelines, which align with WCAG. Abroad, the US uses the ADA and Section 508, Europe uses EN 301 549, and the European Accessibility Act applies to many digital products and services from June 2025. Most of these point to WCAG AA as the practical testing target.
12

Tell me about a time you had to push back on a release date.

Save to ▾
Show answer
Model answer: Situation: a loan app release was planned on Friday, but the EMI schedule showed wrong values for some tenures. Task: give an honest recommendation. Action: I presented the failing cases, the number of affected customers and the compliance risk in the go or no-go meeting, and proposed a three-day delay with a fix plan. Result: management agreed, the fix shipped on Monday, and no complaints came in.
13

How do you plan testing for a feature that depends on a third-party service?

Save to ▾
Show answer
Identify the integration points and the service's sandbox, limits and test data. Plan to test with a mock or stub early for our logic and error handling, then against the real sandbox for integration. Include failure scenarios: timeout, slow responses, invalid data and the service being down. Add the dependency to the risk list, with contacts and a fallback plan, and confirm production credentials and monitoring before go-live.
14

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

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.
15

Your team says nightly database backups are working. How do you prove that a restore actually works?

Save to ▾
Show answer
Take a backup of a test database with known data, record row counts and a few checksums, then restore it to a separate server. Compare counts, sample records, constraints and users. Measure how long restore takes against the recovery time objective, and check that point-in-time restore loses no more data than the recovery point objective allows. A backup that has never been restored is not proven, so this test should run regularly.
16

Write test cases for a one-to-one chat feature.

Save to ▾
Show answer
Send and receive text messages and check order and timestamps. Test sent, delivered and read status. Send emojis, long messages, links and attachments within and over the size limit. Check messages sent while offline are queued and delivered on reconnect. Verify blocking a user stops messages. Test notifications when the app is in background. Check chat history after reinstall or on a second device, and that deleted messages disappear for both users if supported.
17

How do you design test cases for role-based access with admin, editor and viewer roles?

Save to ▾
Show answer
Build a permission matrix with roles as rows and actions as columns, such as create, edit, delete, publish and view, marking allowed or denied from the requirement. Write a positive test for each allowed cell and a negative test for each denied one. Test through the UI and also call the APIs directly, because hidden buttons are not security. Check role changes take effect immediately and that users cannot access other users' data by changing IDs.
18

What is the difference between DELETE and TRUNCATE?

Save to ▾
Show answer
DELETE removes selected rows and can be rolled back; TRUNCATE quickly removes all rows and resets the table.
19

How do you test in-app purchases or subscriptions on mobile?

Save to ▾
Show answer
Use the platform's sandbox or test accounts so no real money is charged. Test a successful purchase, cancellation, payment failure, pending payment, refund and restoring purchases on a new device. For subscriptions, test free trial, renewal, upgrade, downgrade, expiry and grace period, often with shortened test durations. Verify the server records the purchase and unlocks features, and that killing the app mid-purchase does not lose it.
20

What is a go or no-go meeting and what does QA present?

Save to ▾
Show answer
A go or no-go meeting is held before release to decide whether to deploy. QA presents test coverage against scope, pass and fail counts, open defects by severity with their impact, known issues and workarounds, any untested areas and the overall risk. QA gives a recommendation, but the business owner decides. The decision and accepted risks should be recorded in the meeting notes.
21

How do you test a REST API that is not ready yet?

Save to ▾
Show answer
Use mocks or stubs from the API contract such as Swagger, write test cases early and validate again when the real service is available.
22

How do you decide which automated tests run on every pull request and which run nightly?

Save to ▾
Show answer
Pull request checks must be fast, usually under ten to fifteen minutes, and highly reliable, so they include unit tests, API tests for changed services and a small UI smoke set of critical flows. The full UI regression, cross-browser runs, long data-driven suites and performance checks run nightly or before release. Tag tests by suite, measure run times and flakiness, and move tests between suites based on value and speed.
23

How do you plan regression testing for a monthly release?

Save to ▾
Show answer
Keep a tiered regression suite: a smoke set for every build, a core set of critical flows for every release and a full set run on a rotation or before major releases. Each month, add impact-based tests from the release changes and cases for recent production bugs. Automate stable, repeated cases and keep manual effort for new or changing areas. Schedule regression early enough to fix and retest found issues.
24

As a QA lead, how do you measure the quality of test case design?

Save to ▾
Show answer
Look at requirement coverage through the traceability matrix, the share of defects found by scripted tests versus exploratory testing or production, and defect leakage per module. Review samples for clear objectives, correct expected results and use of techniques like boundaries and negative cases. Track how many cases were updated or retired after changes. If many production bugs map to areas with passing tests, the design, not the execution, needs improvement.
25

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

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);
26

How do you test a mobile app's offline mode and data sync?

Save to ▾
Show answer
Turn off the network and perform supported actions, such as creating, editing and deleting records, and check they are saved locally with a pending status. Reconnect and verify everything syncs once, in order, with no duplicates. Test conflicts, where the same record is changed on two devices, and confirm the agreed rule applies. Test sync after app restart, on a slow network and when the server rejects a change.
27

What is the difference between smoke testing in CI and full regression?

Save to ▾
Show answer
Smoke tests run on every build for quick feedback; full regression runs less often, such as nightly or before release.
28

A developer asks you to test a feature that has no acceptance criteria. How do you proceed?

Save to ▾
Show answer
First ask the product owner or business analyst for the expected behaviour and write down the answers as draft acceptance criteria. Meanwhile, explore the feature, compare it with similar existing features and list assumptions. Share the assumptions in the story so everyone agrees before you sign off. Raise the missing criteria in the next refinement so future stories are not picked up without them.
29

Tell me about a time you organised or ran a bug bash before a release.

Save to ▾
Show answer
Situation: a new seller onboarding flow was due in a week and only two testers had seen it. Task: I wanted wider coverage quickly. Action: I set up a one-hour bug bash with developers, product and support, shared test accounts, focus areas and a simple bug form, then triaged findings with the lead. Result: we found 18 issues, including two blockers on low-end phones, and fixed them before launch.
30

Describe how you led a QA team through a very tight release.

Save to ▾
Show answer
Model answer: Situation: a regulatory change had to go live in ten days. Task: lead four testers. Action: I split work by risk, put our strongest tester on the calculation engine, ran daily 15-minute bug triage with developers and shared a single status dashboard. I also automated the repeated tax checks. Result: we released on the deadline with zero critical defects, and the client used our test evidence for their audit.
31

How do you reduce the number of defects slipping into production?

Save to ▾
Show answer
Shift left with early reviews, improve test design, automate regression, use better test data, add monitoring and learn from escaped defects.
32

What is defect prevention and what practical techniques does a QA team use?

Save to ▾
Show answer
Defect prevention focuses on stopping defects from being introduced instead of only finding them. Practical techniques include requirement reviews and clear acceptance criteria, Three Amigos sessions, design and code reviews, unit testing standards, coding checklists from past bugs, root cause analysis of escaped defects, and training on common mistakes. Track whether repeated defect types fall over time to prove the effort works.
33

A bug fix was made in the payment module. How do you decide the regression scope?

Save to ▾
Show answer
Ask the developer which code, services and database tables changed. Map them to impacted flows: all payment methods, refunds, partial payments, failed payment retries, invoices and order status updates. Add high-risk areas from past defects and anything that calls the same service. Run full payment regression because the business risk is high, plus a smoke test of the rest of the application before release.
34

How would you set up a testing approach for a new Agile team with no QA process?

Save to ▾
Show answer
Start small. Agree on a definition of ready and definition of done that include acceptance criteria and testing. Join refinement and run Three Amigos for every story. Set up a simple bug workflow and severity guide in the tracker, a shared test case repository and a smoke checklist for each build. Then add API checks and automated regression for stable flows. Review what works in each retrospective and adjust.
35

You join a project in the middle of a release. How do you plan your testing?

Save to ▾
Show answer
Spend the first day learning the scope: read the release notes, user stories and test plan, and ask the lead what is at risk. Get access to the environment, tracker and test repository. Pick up a clearly defined module, run its existing test cases to learn the application and note gaps. Ask questions early in stand-up. Within a few days, take ownership of retesting and regression for that module.
36

How do you test an application with no documentation?

Save to ▾
Show answer
Talk to developers and users, explore the product, review similar systems, create notes and mind maps, confirm assumptions and write test cases as you learn.
37

What is mutation testing?

Save to ▾
Show answer
Mutation testing measures the quality of a test suite. A tool makes small changes, called mutants, to the code, such as changing greater than to greater than or equal, and runs the tests. If a test fails, the mutant is killed; if all tests still pass, the mutant survived, which shows a weak spot in the tests. The mutation score is killed mutants divided by total mutants. It is strong but slow, so teams apply it to critical modules.
38

Product is running an A/B test on the checkout button. What does QA need to verify?

Save to ▾
Show answer
QA does not decide which version wins, but makes sure the experiment is trustworthy. Verify both variants work end to end, users are split in the agreed ratio, each user sees the same variant consistently across sessions, and analytics events fire correctly for each group. Also check that turning the experiment off returns everyone to the default. A broken tracking event can make the whole experiment's result wrong.
39

A manager wants 100 percent test automation. How do you respond?

Save to ▾
Show answer
I agree with the goal of faster and more reliable testing, but explain that 100 percent is neither possible nor useful. Exploratory testing, usability, visual judgement and brand-new features need people, and some flows like real payments or OTP are costly to automate reliably. I would propose clear targets instead, such as automating all critical regression and smoke flows, with metrics like regression time cut from three days to four hours.
40

The product team wants to skip UAT to ship faster. What do you advise?

Save to ▾
Show answer
Explain the risk: system testing proves the software matches the specification, but only users confirm it fits real business work. Propose a lighter option instead of none: a short, focused UAT on critical flows with two or three key users, or a staged rollout to a small user group with monitoring and quick rollback. If they still skip it, record the decision and the accepted risks with the product owner.

Frequently asked questions

What do Software Testing interviews for ₹40–50 LPA roles test?

At ₹40–50 LPA the focus is usually on: enterprise-level architecture, organisation-wide strategy, governance and compliance, executive communication. This page's set is weighted towards STLC and Test Planning (7), Agile, SQL and API Testing (6), Testing Types (5), Automation Basics for Manual Testers (4).

Which companies pay ₹40–50 LPA for Software Testing roles?

Pay depends on company type, city, skills and negotiation, not only experience. Use the company-wise pages to practise for the specific employers you are targeting, and treat salary bands as a rough guide.

How should I prepare for a ₹40–50 LPA Software Testing interview?

Solve every question here without looking at the answer first, mark the ones you miss, save them to Last-Minute Revision and revise them the night before. Prepare two project stories that show impact at the level expected for ₹40–50 LPA.