Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Policybazaar hiring for Software Testing roles
Policybazaar, part of PB Fintech, is an Indian online insurance marketplace for comparing and buying health, life, motor and other insurance. Its sister platform Paisabazaar covers loans and credit cards. Its technology and analytics teams work on lead management, pricing comparison and customer experience. It hires for software engineers, testers and analysts.
For Software Testing roles, this Policybazaar practice set focuses most on Bug Life Cycle and Jira (7), STLC and Test Planning (7), Automation Basics for Manual Testers (5), Agile, SQL and API Testing (4). It has 2 easy, 29 medium, 9 hard questions, so you can start easy and work up to the harder ones.
Company type
Fintech
Headquarters
Gurugram, India
Main India offices
Gurugram
Policybazaar Software Testing interview process
Online assessment or assignment
Technical or case round
Hiring manager round
HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for PolicybazaarStart 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 a pytest test using requests that checks a GET call returns 200 and a non-empty list.
Native apps are built for one platform and use device features fully, so testing focuses on OS versions, device features, install and update. Hybrid apps wrap web code in a native shell, so you test both the web view rendering and the native bridges like camera access. Mobile web apps run in a browser, so testing is closer to cross-browser and responsive testing. All three need network, screen size and performance checks.
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);
Test monitoring compares actual testing progress with the plan, using metrics like test cases executed, pass rate, open defects and effort spent. Test control is the action taken when monitoring shows a gap, such as re-prioritising tests, adding testers, changing the schedule or tightening entry criteria. For example, if half the time has passed but only a quarter of cases are executed, the lead must act and inform stakeholders.
08
Product is running an A/B test on the checkout button. What does QA need to verify?
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.
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.
10
What new success criteria in WCAG 2.2 should testers know?
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.
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.
13
Write test cases for a coupon code field at checkout.
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.
The Page Object Model is a design pattern where each page or major component gets a class that holds its locators and actions, such as LoginPage with a login method. Tests call these methods instead of using locators directly. When the login button changes, you update one place instead of fifty tests. Tests become readable, like steps a manual tester would write, and duplication drops. Keep assertions mostly in tests, not page objects.
15
Your automated accessibility scan shows zero errors. Is the page accessible?
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.
A bug bash is a short, time-boxed session where people from across the team, including developers, product and support, test the product together to find as many issues as possible before a release. To run one, share a build, scope and test accounts, assign focus areas, give a simple bug template and a shared board, then triage findings at the end. It brings fresh eyes and finds usability issues formal tests miss.
17
The app crashes only on one older Android version. What are your steps?
Reproduce it on that exact OS version, using a real device or an emulator image, and note the device model and app build. Capture the crash log and stack trace. Check if the code uses an API or library not supported on that version, or a permission or storage behaviour that changed. Log the bug with logs and the minimum supported version from the requirement, so the team can decide to fix it or raise the minimum version.
18
How do you decide which automated tests run on every pull request and which run nightly?
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.
19
As a QA lead, how do you measure the quality of test case design?
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.
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.
22
What is the difference between static and dynamic testing?
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.
24
Your team wants to copy production data into the QA environment for realistic testing. What do you advise?
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.
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.
Defect removal efficiency shows how many defects the team found before release. DRE = defects found before release divided by (defects found before release plus defects found after release), multiplied by 100. If QA found 90 bugs and users reported 10, DRE is 90 percent. A falling DRE means testing is missing more defects, and the escaped bugs should be analysed to improve test coverage.
27
What is the difference between retesting and regression testing?
Retesting, or confirmation testing, checks that a specific bug that was fixed now works, using the same steps as the original bug. Regression testing checks that the fix or a new change has not broken other, previously working features. Retesting is planned for failed cases only, while regression covers a wider set of passing cases. Retesting usually comes first, then regression around the changed area.
Re-check environment, data, browser and steps; check the logs; try the reporter's setup; add video and console logs; mark it 'cannot reproduce' only after discussing with the developer, and keep monitoring.
-- Create a parent and child, delete the parent, child rows must disappear
INSERT INTO customers (id, name) VALUES (501, 'Cascade Test');
INSERT INTO orders (id, customer_id, total) VALUES (7001, 501, 250);
DELETE FROM customers WHERE id = 501;
SELECT COUNT(*) FROM orders WHERE customer_id = 501;
-- Expected: 0
-- Also test inserting an order for a non-existent customer: it must fail
31
The sprint ends tomorrow and two stories are still in testing. What do you do?
Tell the Scrum Master and product owner today, not at the review. Focus testing on the acceptance criteria and the riskiest paths of the story with the most value, and ask a developer to help with test data or simple checks. If a story cannot be finished with quality, it should be carried over, not marked done with untested parts. Raise the cause in the retrospective, such as late handover.
32
How do you test an application when requirements change frequently?
-- Compare counts and sums side by side; both columns must match
SELECT
(SELECT COUNT(*) FROM staging_orders) AS src_count,
(SELECT COUNT(*) FROM dw_orders) AS tgt_count,
(SELECT SUM(amount) FROM staging_orders) AS src_amount,
(SELECT SUM(amount) FROM dw_orders) AS tgt_amount;
37
How do you test session management in a web application?
Check that a new session ID is created after login, and that the session expires after the defined idle time. Verify logout invalidates the session on the server, so pressing back or reusing the old cookie does not work. Check that cookies use Secure, HttpOnly and SameSite flags. Test concurrent logins if they are limited, and that changing the password ends other sessions. Session IDs must not appear in URLs.
A development model where each development phase has a matching testing phase, such as requirements with acceptance tests and design with integration tests.
39
Your team wants to use an AI tool to generate test cases and automation scripts. What benefits and risks do you point out?
AI assistants can draft test cases from requirements, suggest edge cases, generate first versions of scripts and test data, and some tools self-heal locators when the page changes. Risks are confident but wrong output, tests that assert the wrong behaviour, hidden locator changes that mask real bugs and leaking confidential data into external tools. Treat AI output like a junior's draft: review it, run it and keep human judgement on what matters.
40
Release is tomorrow and you can't test everything. What now?
Risk-based testing: cover critical user flows, recent changes and high-defect areas first. Clearly communicate the untested risks and get stakeholder sign-off.
Tips to crack the Policybazaar Software Testing interview
Learn insurance basics like premium, sum insured, claim settlement ratio and term versus health plans.
Prepare analytics cases on lead conversion, call centre efficiency and renewal rates.
Practise testing scenarios for quote comparison and policy purchase flows, including payment and document uploads.
Keep a one-minute story ready for every project on your CV: problem, your part, tools, result.
Practise the hard questions on this page aloud; Policybazaar interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Policybazaar Software Testing interview?
Candidates usually go through 4 stages: Online assessment or assignment; Technical or case round; Hiring manager round; HR round. The exact rounds change with the role, team, location and your experience, so confirm the process with the recruiter.
Which topics should I prepare for the Policybazaar Software Testing interview?
This practice set leans on Bug Life Cycle and Jira (7), STLC and Test Planning (7), Automation Basics for Manual Testers (5), Agile, SQL and API Testing (4). Revise those first, then practise explaining one or two of your own projects end to end, because most Policybazaar interviewers ask you to walk through real work.
Are these the exact questions asked at Policybazaar?
No. These are curated practice questions that match the skills and difficulty usually tested in fintech interviews like Policybazaar's. They are not a leaked or verified list of past questions.
Where does Policybazaar hire Software Testing professionals in India?
Policybazaar has large teams in Gurugram. Openings and locations change often, so check the Policybazaar careers page and filter by city and experience.