01
Write SQL to verify an order was saved correctly.
Show answer
SELECT status, amount FROM orders WHERE order_id = 'ORD123';
-- compare with the UI, then check the matching rows in order_items
Software Testing Managerial Round Questions & Answers
35 questions for the managerial round stage — 21 medium, 14 hard.
About the managerial round round
The managerial round is usually with a hiring manager or team lead. It mixes real-work scenarios, prioritisation and stakeholder questions with behavioural questions about ownership, conflict and learning.
Tips for the managerial round round
- Use the STAR format for every story: Situation, Task, Action, Result.
- Show trade-offs: what you chose, what you gave up and why.
- Be honest about mistakes and focus on what you changed afterwards.
- Ask the manager about team goals and how success is measured in the role.
Solved — managerial roundStart 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
02
What are suspension and resumption criteria in a test plan?
Show answer
Suspension criteria define when testing should be paused because continuing would waste effort, for example when a blocker bug stops the main flow, the build fails smoke testing or the environment is down. Resumption criteria define what must happen to restart, such as a new build that passes smoke testing or the environment restored. Writing these down avoids arguments and shows clearly why testing time was lost.
03
What does Won't Fix mean and who decides it?
Show answer
Won't Fix means the bug is acknowledged as real, but the team decides not to fix it, usually because the impact is very low, the feature is being retired or the cost of fixing is higher than the benefit. The decision is made by the product owner, often in triage with dev and QA leads. The tester should make sure the reason is recorded and, if user-facing, documented as a known issue.
04
A manager says the app has 50,000 daily users, so the load test must run 50,000 virtual users at once. How do you respond?
Show answer
Explain that daily users are not concurrent users. Of 50,000 users a day, only a fraction are active at the same moment, and even they pause between actions because of think time. Use analytics to find the real peak concurrency and request rate, for example 1,500 concurrent users at peak hour, and model that with a safety margin. Running 50,000 users clicking at once tests a load that never happens and wastes effort.
05
How do you test battery and memory usage of a mobile app?
Show answer
Run typical user sessions on a real device and measure battery drain, CPU and memory with platform profiling tools or the device's battery statistics. Compare with the previous version. Look for background work continuing after the app is closed, GPS left on, frequent network polling and memory that keeps growing, which signals a leak. Test on low-RAM devices too, where the OS kills heavy apps quickly.
06
What do testers look for during a requirement review?
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.
07
How do you test a mobile app when the device storage is almost full?
Show answer
Fill the device storage close to the limit, then install or update the app and confirm a clear message if it cannot proceed. Inside the app, try downloads, photo capture, caching and saving drafts. The app should show a helpful error, not crash or corrupt data. Also check what happens to the local database when a write fails, and whether the app recovers after space is freed.
08
What is use case testing?
Show answer
Designing tests from user flows described in use cases to verify complete real-world interactions.
09
How would you test a login page for security?
Show answer
Check SQL injection, brute-force lockout, password masking, session timeout, HTTPS, cookie flags, error messages not revealing users and password reset flow.
10
Customer records are being moved from an old system to a new one. How do you test the migration?
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.
11
How do you test an application with no documentation?
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.
12
What is defect clustering?
Show answer
The observation that a small number of modules contain most defects, so testing should focus on those areas.
13
What automated accessibility tools exist and what are their limits?
Show answer
Common tools are axe DevTools, Lighthouse in Chrome, WAVE and accessibility linters in CI. They quickly catch missing alt text, low contrast, missing labels and invalid ARIA. Their limit is that they find only roughly a third of WCAG issues. They cannot judge whether alt text is meaningful, focus order is logical, error messages make sense or a custom widget works with a screen reader, so manual testing is still required.
14
What is error guessing?
Show answer
Using experience to guess where defects likely hide, such as empty fields, special characters or unexpected sequences, and designing tests for them.
15
What is the difference between GET and POST?
Show answer
GET retrieves data and has parameters in the URL; POST sends data in the body to create or process something.
16
A manager wants to cut QA time in half. How do you explain the value of testing?
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.
17
What is accessibility testing?
Show answer
Checking that people with disabilities can use the product, using screen readers, keyboard navigation, colour contrast and WCAG guidelines.
18
Your team wants to copy production data into the QA environment for realistic testing. What do you advise?
Show answer
Do not copy raw production data into test environments. Use synthetic data generated for the test cases, or masked production data where names, phone numbers, emails, ID numbers and card details are replaced while formats and relationships are kept. Restrict access to test databases and record the data rules in the test plan. This keeps testing realistic and follows India's data protection law and company policy.
19
Write a JQL query for open high or highest priority bugs in the current sprint of project PAY.
Show answer
project = PAY
AND issuetype = Bug
AND statusCategory != Done
AND priority in (Highest, High)
AND sprint in openSprints()
ORDER BY priority DESC, created ASC
20
How do you test a mobile app's offline mode and data sync?
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.
21
An API returns 200 OK but the body contains an error message. Is that a bug?
Show answer
Usually yes. Status codes should reflect the result so clients and monitoring can react correctly; an error with 200 can hide failures and break retries. A validation error should return 400 or 422, a missing resource 404 and a server failure 500. Check the API contract first: some legacy APIs document this pattern. If it is not documented, log it as a defect with the request and response attached.
22
A client needs WCAG 2.2 AA compliance before launch in two weeks. How do you plan the testing?
Show answer
Agree on scope: key user journeys and page templates, not every page. Day one, run automated scans on all templates to fix easy issues fast. Then do manual checks of each journey with keyboard, NVDA, VoiceOver on mobile, zoom and contrast. Log issues with WCAG references and severity, and get blockers fixed first. Retest fixes and deliver a conformance summary with known issues. Be honest if full compliance is not realistic.
23
Your team has 500 manual regression test cases and wants to start automating. Where do you start?
Show answer
Do not automate all 500. First clean the suite: remove duplicates and outdated cases. Rank the rest by business risk, run frequency and stability. Start with a smoke set of 20 to 30 critical journeys and move rule-heavy checks to the API level. Choose a tool that fits the team's skills, build a simple framework with page objects and CI runs, then expand in batches while tracking time saved and flakiness.
24
How do you test in-app purchases or subscriptions on mobile?
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.
25
A security reviewer asks you to confirm that passwords and personal data are stored safely. What do you check in the database?
Show answer
Query the users table after signup and confirm the password is not stored in plain text or reversible encoding, but as a salted hash from a slow algorithm such as bcrypt or Argon2. Two users with the same password should have different hashes. Check that card numbers are not stored at all or are tokenised, that personal data like Aadhaar numbers is masked or encrypted, and that logs and audit tables do not copy the raw values.
26
How do you decide testing is complete when some bugs are still open?
Show answer
Testing is complete when agreed exit criteria are met, not when the bug count is zero. Check that planned tests ran, critical and high bugs are fixed or formally accepted, and remaining open bugs have workarounds and low user impact. Present the list with risk to the product owner, who decides on release. Record accepted bugs as known issues, so nothing is hidden and they are planned for a later release.
27
Your team says nightly database backups are working. How do you prove that a restore actually works?
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.
28
How do you plan testing for a feature that depends on a third-party service?
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.
29
SQL: find duplicate emails.
Show answer
SELECT email, COUNT(*)
FROM users
GROUP BY email
HAVING COUNT(*) > 1;
30
Product is running an A/B test on the checkout button. What does QA need to verify?
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.
31
How do you test an application when requirements change frequently?
Show answer
Keep tests modular, prioritise by risk, use exploratory testing, automate stable parts and keep close contact with product owners.
32
Tell me about a time you found an important bug that others missed.
Show answer
Model answer: Situation: before a release of an insurance app, all regression tests had passed. Task: I was doing a final exploratory round. Action: I renewed a policy on the last day of the month and saw that the premium was calculated for 31 days in a 30-day month. I logged it with exact data and the formula difference. Result: the date logic was fixed before release, and I added month-end cases to the suite.
33
What is compliance testing?
Show answer
Compliance testing checks that software meets external laws, standards or internal policies, not just functional requirements. Examples include payment security standards for card data, data protection rules for personal data, accessibility guidelines and RBI rules for banking apps. Testers verify items such as consent capture, data retention, audit logs and masking. Findings are usually documented as evidence for auditors, so traceability and clear records matter as much as the tests.
34
How do you handle a product owner who keeps adding scope in the middle of a sprint?
Show answer
Model answer: Situation: our product owner added two small changes to a story mid-sprint, which pushed testing to the last day. Task: protect quality without being rigid. Action: I showed the extra test effort in stand-up and asked the Scrum Master to help decide what to swap out. Result: one change moved to the next sprint, and the team agreed new requests go through the backlog.
35
Release is tomorrow and you can't test everything. What now?
Show answer
Risk-based testing: cover critical user flows, recent changes and high-defect areas first. Clearly communicate the untested risks and get stakeholder sign-off.
Frequently asked questions
What happens in the Software Testing managerial round round?
The managerial round is usually with a hiring manager or team lead. It mixes real-work scenarios, prioritisation and stakeholder questions with behavioural questions about ownership, conflict and learning.
How do I clear the managerial round round?
Use the STAR format for every story: Situation, Task, Action, Result. Show trade-offs: what you chose, what you gave up and why. Be honest about mistakes and focus on what you changed afterwards.
Which round comes next?
A typical order is online assessment, telephonic screening, one or two technical rounds, a managerial round and HR. Use the other round pages to practise each stage.
Practise every interview round
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