01
What is defect leakage?
Show answer
Defects found after release that testing should have caught; leakage % = defects in production / total defects x 100.
Dream11 Software Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Dream11 hiring for Software Testing roles
Dream11 is an Indian sports technology platform and the flagship brand of Dream Sports, which also includes FanCode and other businesses. Its engineering and analytics teams build systems that handle very high traffic during live matches. It hires for software engineers, SDETs, data engineers, data analysts and data scientists.
For Software Testing roles, this Dream11 practice set focuses most on Accessibility & Usability Testing (5), Agile, SQL and API Testing (5), Manual Testing Basics (4), Performance and Security Basics (4). It has 1 easy, 28 medium, 11 hard questions, so you can start easy and work up to the harder ones.
- Company type
- Product
- Headquarters
- Mumbai, India
- Main India offices
- Mumbai
Dream11 Software Testing interview process
- Online assessment or assignment
- Technical round 1
- Technical round 2 (design or case)
- Hiring manager round
- Culture fit round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for Dream11Start 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
Write a pytest test using requests that checks a GET call returns 200 and a non-empty list.
Show answer
import requests
BASE_URL = 'https://qa-api.example.com'
def test_get_products_returns_list():
response = requests.get(f'{BASE_URL}/products', timeout=10)
assert response.status_code == 200
body = response.json()
assert isinstance(body, list)
assert len(body) > 0
assert 'id' in body[0]
03
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.
04
What is the OWASP Top 10 and why should testers know it?
Show answer
The OWASP Top 10 is a widely used list of the most critical web application security risks, published by an open community project. It includes broken access control, cryptographic failures, injection, insecure design, security misconfiguration, vulnerable components and authentication failures. Testers use it as a checklist to include basic security checks in their testing and to speak the same language as security teams.
05
How do you write test cases when only wireframes are available and the UI is not ready?
Show answer
Use the wireframes and the user story as the test basis. Write test scenarios and high-level cases for the flows, field validations, navigation and error states shown in the design. Note open questions, such as missing empty states or error messages, and clarify them with the designer. Keep exact UI text and steps light so they are easy to update. Once the build arrives, refine the cases and add any missing details.
06
Tell me about a time exploratory testing helped you find a critical bug.
Show answer
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.
07
What is the testing pyramid?
Show answer
A model with many fast unit tests at the base, fewer API or integration tests in the middle and a small number of UI tests at the top.
08
How do you test a web page using only the keyboard?
Show answer
Put the mouse away. Press Tab and Shift+Tab to move through every link, button and field, and check that the order is logical and the focus outline is always visible. Use Enter and Space to activate buttons and links, arrow keys for menus, radio groups and sliders, and Escape to close dialogs. Check that nothing traps focus, hidden items do not receive focus and a skip to main content link works.
09
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.
10
What is a performance baseline?
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.
11
What is a sprint planning meeting and what does QA contribute?
Show answer
The team selects stories for the sprint. QA helps estimate testing effort, clarifies acceptance criteria and flags dependencies and risks.
12
Leadership asks for a one-page quality update before a release. Which bug metrics do you report?
Show answer
Keep it short and decision-oriented. Show open bugs by severity, the created versus resolved trend, blockers with owners and dates, defect leakage from the last release and modules with the most defects. Give a clear recommendation, such as ready, ready with known issues or not ready, with reasons. Use a shared dashboard for detail, and one slide or email summary for leaders who need only the risk picture.
13
What is root cause analysis for defects?
Show answer
Finding why a defect was introduced, such as unclear requirements or missed reviews, to prevent similar defects in future.
14
Your automated accessibility scan shows zero errors. Is the page accessible?
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.
15
A web app gets slower the longer a user keeps it open. How do you check for a memory leak as a manual tester?
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.
16
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
17
How do you convert existing manual test cases into automated scripts?
Show answer
Pick a small set of stable, high-value regression cases first. Review each one: make steps precise, remove judgement-based checks and define clear expected results. Prepare test data that the script can create and clean up. Build reusable page objects and helpers for common steps like login. Automate, run several times to confirm stability, then link each script to its manual case ID and mark the manual case as automated.
18
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.
19
A training portal is adding recorded video lessons and podcasts. What accessibility checks do you run?
Show answer
Check that prerecorded videos have accurate, synchronised captions, not just auto-generated ones with errors, and that audio-only content like podcasts has a transcript. Important visual information that is not spoken should have audio description or be covered in the transcript. Media should not autoplay with sound, and player controls must work by keyboard and be announced by screen readers. Also check that nothing flashes more than three times per second.
20
Why are stable locators like data-testid or roles preferred over position-based XPath?
Show answer
A position-based XPath such as /html/body/div[3]/div[2]/button breaks whenever a developer adds a wrapper div or reorders the layout, even though the feature still works. That creates false failures and maintenance work. Locators based on a dedicated data-testid attribute or the accessible role and name, like a button named Submit, stay valid through design changes and describe intent clearly. Testers should ask developers to add test IDs.
21
What is recovery testing?
Show answer
Recovery testing checks how well the system recovers from crashes, hardware failures, network loss or other failures. For example, kill the server during a file upload, or disconnect the network during payment, and verify the system restores a consistent state, does not lose or duplicate data and resumes or shows a clear message. It also measures recovery time against agreed targets, which matters for banking and healthcare systems.
22
What is a performance bottleneck and where do bottlenecks usually occur?
Show answer
A bottleneck is the component that limits the whole system's performance, so adding load beyond it increases response times or errors. Common places are slow database queries or missing indexes, too few database connections or threads, CPU or memory limits on servers, slow third-party APIs, large uncompressed files and chatty code that makes many small calls. Monitoring each layer during a test shows which resource saturates first.
23
What is boundary value analysis?
Show answer
Testing at the edges of input ranges, such as 17, 18 and 19 for an age limit of 18, since errors cluster at boundaries.
24
What is cause-effect graphing?
Show answer
Cause-effect graphing is a black box technique that models input conditions (causes) and output actions (effects) with logical relations like AND, OR and NOT. The graph is converted into a decision table, and each column becomes a test case. It is useful when outputs depend on combinations of inputs, such as loan approval based on income, age and credit score. It helps find missing or contradictory rules in the requirement.
25
What is normalization and why should a tester understand it?
Show answer
Normalization organises tables to reduce duplicate data, for example storing the customer address once in a customers table instead of repeating it in every order. Testers should understand it because it explains where data lives and which joins are needed to verify a screen. It also shows risk: in a denormalized report table, the same value is copied in many places, so updates must be tested to confirm every copy changes.
26
A hotfix build arrives and you have only 15 minutes before deployment. How do you sanity check it?
Show answer
Read the hotfix ticket to know exactly what changed. First verify the fix with the original reproduction steps and data. Then check the directly connected flows, for example if the fix is in coupon calculation, test applying, removing and paying with a coupon. Finish with a quick smoke of login and the main business flow. Report the result immediately, mentioning what was and was not covered.
27
A developer asks you to test a feature that has no acceptance criteria. How do you proceed?
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.
28
What is risk-based testing?
Show answer
Prioritising tests by the likelihood and impact of failure, so critical areas get the most coverage when time is limited.
29
The app crashes only on one older Android version. What are your steps?
Show answer
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.
30
How would you test rate limiting on a public API?
Show answer
Find the documented limit, for example 100 requests per minute per key. Send requests just below and above the limit and check that extra requests get 429 Too Many Requests with a Retry-After header. Verify the counter resets after the window and that limits apply per key or per IP as designed. Check that one user hitting the limit does not block others, and that normal traffic is not throttled.
31
A monthly report query runs on millions of rows and takes minutes. How do you test and report its performance?
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.
32
The test environment is down for two days just before release. What do you do?
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.
33
How do you test pagination, sorting and filtering through an API?
Show answer
Send page, size, sort and filter parameters, then verify counts, order, boundaries (first, last, empty page) and invalid parameter handling.
34
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.
35
Your test repository has many duplicate and outdated test cases. How do you clean it up?
Show answer
Export the cases and group them by module and requirement. Mark duplicates, merge them into one well-written case, and retire cases for removed features. Check which cases have not been executed or failed in months and confirm whether they are still valid. Link the remaining cases to requirements so gaps are visible. Do it module by module with peer review, and set a rule that every story update also updates its test cases.
36
What is idempotency in APIs and how do you test it?
Show answer
An operation is idempotent if repeating the same request gives the same result as doing it once. GET, PUT and DELETE should be idempotent; POST usually is not. To test, send the same request several times and check the server state does not change after the first call. For payments, check that retrying with the same idempotency key does not create a second charge, which protects users during network retries.
37
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.
38
You join a project in the middle of a release. How do you plan your testing?
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.
39
Analytics show many users drop off at step three of a five-step checkout. How do you investigate the usability problem?
Show answer
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.
40
Notifications arrive late, and some screens look broken, only on certain Android phone brands. Why can this happen and what do you test?
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.
Tips to crack the Dream11 Software Testing interview
- Practise system design for sudden traffic spikes, such as many users joining just before a cricket match starts.
- Prepare analytics cases on user engagement, retention and contest participation around major tournaments.
- Keep up with regulatory changes affecting online gaming in India, as they directly shape the company's business.
- 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; Dream11 interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Dream11 Software Testing interview?
Candidates usually go through 5 stages: Online assessment or assignment; Technical round 1; Technical round 2 (design or case); Hiring manager round; Culture fit 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 Dream11 Software Testing interview?
This practice set leans on Accessibility & Usability Testing (5), Agile, SQL and API Testing (5), Manual Testing Basics (4), Performance and Security Basics (4). Revise those first, then practise explaining one or two of your own projects end to end, because most Dream11 interviewers ask you to walk through real work.
Are these the exact questions asked at Dream11?
No. These are curated practice questions that match the skills and difficulty usually tested in product interviews like Dream11's. They are not a leaked or verified list of past questions.
Where does Dream11 hire Software Testing professionals in India?
Dream11 has large teams in Mumbai. Openings and locations change often, so check the Dream11 careers page and filter by city and experience.
Software Testing questions for similar companies
Product
NetApp
Software Testing interview questions
Bengaluru
View questionsProduct
Rapido
Software Testing interview questions
Bengaluru
View questionsProduct
Expedia Group
Software Testing interview questions
Gurugram, Bengaluru
View questionsProduct
Chargebee
Software Testing interview questions
Chennai, Bengaluru
View questionsProduct
Nutanix
Software Testing interview questions
Bengaluru, Pune
View questionsProduct
Postman
Software Testing interview questions
Bengaluru
View questionsMore 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