Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About BigBasket hiring for Software Testing roles
BigBasket is an Indian online grocery company, majority owned by the Tata Group, that delivers fruits, vegetables, staples and household products. It runs scheduled delivery and quick commerce services such as BB Now across many cities. Its Bengaluru technology and business teams hire software engineers, data analysts, data scientists, supply chain analysts and product managers.
For Software Testing roles, this BigBasket practice set focuses most on Test Case Design (6), Manual Testing Basics (5), Agile, SQL and API Testing (5), Accessibility & Usability Testing (5). It has 2 easy, 28 medium, 10 hard questions, so you can start easy and work up to the harder ones.
Company type
E-commerce & consumer tech
Headquarters
Bengaluru, India
Main India offices
Bengaluru
BigBasket Software Testing interview process
Online coding or analytics assessment
Technical round 1
Technical round 2 (design or case)
Hiring manager round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for BigBasketStart 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
A developer asks you to test a feature that has no acceptance criteria. How do you proceed?
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.
02
How do you chain requests in Postman by passing a token from login to the next call?
// Tests tab of the Login request
const body = pm.response.json();
pm.environment.set('authToken', body.token);
// Next request header:
// Authorization: Bearer {{authToken}}
// Postman replaces {{authToken}} with the saved value
03
A CAPTCHA on the signup page blocks screen reader users. What do you recommend?
Log it as a high-severity accessibility bug because it fully blocks a group of users from signing up. An image-only CAPTCHA fails WCAG unless an alternative is offered. Recommend options such as invisible or risk-based bot checks, an email or OTP verification step, an audio alternative plus another modality, and rate limiting on the server. Retest the full signup with NVDA and TalkBack after the change.
04
Managers say the automation test report is hard to understand. What should a useful report include?
A useful report shows total tests run, passed, failed and skipped, the run time, the environment, build number and browser. For each failure it should show the test name, the failing step, the error message, and a screenshot, video or trace, plus logs. Trends across runs help spot flaky tests. Linking failures to Jira bugs or manual case IDs helps managers see real product risk, not just numbers.
Start with low-cost steps. Add an OWASP-based security checklist to the definition of done for stories touching login, payments or personal data. Train testers on access control, injection and session checks. Add automated dependency and vulnerability scans to the CI pipeline. Include negative authorization tests in API suites. Arrange a penetration test before major releases and track security bugs separately with clear severity rules.
07
Analytics show many users drop off at step three of a five-step checkout. How do you investigate the usability problem?
First look at what step three asks: maybe address entry, a surprise delivery charge or forced signup. Check analytics for errors, rage clicks and time spent, and watch session recordings if available. Test it yourself on mobile and slow networks. Then run a quick usability test with five users on that step. Present evidence with likely causes and options, such as guest checkout or showing charges earlier, and measure after the change.
08
How do you decide testing is complete when some bugs are still open?
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.
09
A monthly report query runs on millions of rows and takes minutes. How do you test and report its performance?
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.
10
How do you verify database schema changes in a new release?
Get the migration script or change list. Compare the schema before and after: new tables and columns, data types, lengths, default values, NULL rules, indexes and constraints. Check that existing data was migrated correctly, for example a new status column filled for old rows. Run the main app flows to confirm queries still work. Finally, confirm the rollback script works on a copy, so the release can be reversed safely.
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.
12
A requirement says the page should load fast. How do you turn it into a test case?
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.
Verify a correct OTP within validity logs the user in. Verify a wrong OTP shows an error and an expired OTP is rejected. Check the OTP length and that only digits are allowed. Test resend: it is disabled during the countdown, and the old OTP stops working after resend. Check the maximum number of wrong attempts locks verification. Verify auto-read on mobile, paste support, and behaviour when the network drops during submission.
14
Tell me about a time exploratory testing helped you find a critical bug.
Model answer: Situation: a new leave management module had passed all scripted cases. Task: I had a one-hour exploratory session. Action: I applied leave, then changed my manager in the profile while the request was pending. Result: the request disappeared for both managers and could never be approved. It was fixed before release, and the team added role-change scenarios to the regression suite.
15
An API returns 200 OK but the body contains an error message. Is that a bug?
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.
16
Production has a critical bug. What are your steps?
Reproduce and assess impact, inform stakeholders, help developers fix and verify in staging, run regression and check monitoring after the hotfix, then do a post-mortem.
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.
Turn on the screen reader, for example NVDA with a browser, and listen rather than look. Navigate by headings to check the structure is logical, by landmarks to find main regions and by Tab through controls. Each control should announce a clear name, role and state, such as 'Subscribe, checkbox, not checked'. Check images, form errors, dynamic updates like cart counts and dialogs. Note exactly what was announced in bug reports.
20
Search works fine in QA but is very slow in production. Could a missing database index be the reason, and how do you check?
Yes, very likely. An index lets the database find rows quickly, like the index of a book. With a small QA table, a full table scan is still fast, but with millions of production rows it becomes slow. Compare indexes on the searched columns in both environments and ask a developer to check the query plan. Test key queries on production-size data in staging, and include data volume in future performance checks.
Check that the app asks for permission only when the feature is used, with a clear reason. Test allow, deny, and deny with do not ask again. When denied, the app must not crash and should explain how to enable it in settings. Revoke permission from settings while the app is in background and return. Test allow only once or only while using the app options on newer OS versions.
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.
26
During a load test, some booking requests fail with a 'deadlock detected' error. What is happening and how do you report it?
A deadlock happens when two transactions each hold a lock the other needs, so neither can continue. The database detects it and kills one transaction with an error. During testing it usually appears under concurrent load, for example two users booking the last seats at once, as random failures or 'deadlock detected' entries in logs. Testers report the exact actions and timing, and developers fix it with consistent lock order or shorter transactions.
Login is a blocker because no other testing can proceed. Confirm it quickly: retry with valid test accounts, check another browser and confirm the right environment and build number. Then log a blocker bug with steps, screenshot and console or network errors, inform the developer and lead immediately, and mark the build as rejected in smoke testing. Meanwhile, prepare test data or review test cases until a fixed build arrives.
29
How do you test form accessibility, including labels and error messages?
Check that every field has a visible label tied to it, so clicking the label focuses the field and a screen reader announces it. Required fields must be indicated in text, not only by colour or an asterisk without explanation. Submit with errors and check that messages are specific, appear next to the field, are announced by the screen reader and focus moves to the first error. Also check autocomplete for name, email and address.
A flaky test passes and fails on the same code without any change. Common causes are timing problems such as fixed sleeps or missing waits, tests depending on each other or on shared data, unstable locators, animations, third-party services, test order in parallel runs and environment issues like slow servers. Flaky tests destroy trust in the suite, so teams quarantine them, find the root cause and fix it rather than adding retries forever.
A keyboard trap is when focus moves into a component and the user cannot move out using the keyboard, for example an embedded video player or date picker that captures Tab forever. Mouse users never notice, but keyboard and screen reader users are stuck and must reload the page. It fails WCAG criterion 2.1.2. Test every widget by tabbing in and out, and check that Escape closes popups and returns focus.
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.
34
Tell me about a time you organised or ran a bug bash before a release.
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.
Vulnerability scanning uses automated tools to look for known weaknesses, such as outdated libraries, missing security headers or open ports. It is fast, repeatable and can run in the pipeline, but gives false positives. Penetration testing is a deeper, mostly manual exercise by security experts who try to exploit weaknesses and chain them like a real attacker. Teams scan regularly and run penetration tests before major releases or yearly.
37
How do you capture screenshots, videos and traces when an automated test fails?
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.
38
Why should we hire you as a manual tester over someone with more automation experience?
Answer with strengths and honesty. For example: I am strong at understanding requirements, designing test cases with techniques like boundary values and finding bugs through exploratory testing, which automation depends on to be useful. I also write SQL and test APIs in Postman. I am learning Playwright and have automated a few smoke tests, so I can grow into automation while adding value from the first week.
39
How do you test a mobile app when the device storage is almost full?
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.
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.
Tips to crack the BigBasket Software Testing interview
Practise DSA for engineering roles, and SQL plus Excel for analyst roles, as these are commonly tested in screening.
Think through grocery supply chain problems like demand forecasting, inventory freshness and delivery slot planning before case rounds.
Use the BigBasket app and note improvement ideas, which helps in product sense and why-BigBasket discussions.
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; BigBasket interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the BigBasket Software Testing interview?
Candidates usually go through 4 stages: Online coding or analytics assessment; Technical round 1; Technical round 2 (design or case); Hiring manager 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 BigBasket Software Testing interview?
This practice set leans on Test Case Design (6), Manual Testing Basics (5), Agile, SQL and API Testing (5), Accessibility & Usability Testing (5). Revise those first, then practise explaining one or two of your own projects end to end, because most BigBasket interviewers ask you to walk through real work.
Are these the exact questions asked at BigBasket?
No. These are curated practice questions that match the skills and difficulty usually tested in e-commerce & consumer tech interviews like BigBasket's. They are not a leaked or verified list of past questions.
Where does BigBasket hire Software Testing professionals in India?
BigBasket has large teams in Bengaluru. Openings and locations change often, so check the BigBasket careers page and filter by city and experience.