01
What is compatibility testing?
Show answer
Checking the application works across browsers, devices, operating systems, screen sizes and network conditions.
Druva Software Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Druva hiring for Software Testing roles
Druva is a data protection and backup software company that offers a cloud-native SaaS platform for backup, recovery and data security. It protects data across endpoints, SaaS applications and cloud workloads for enterprises worldwide. The company was founded in Pune, and its large Pune engineering centre hires software engineers, quality engineers, cloud engineers and site reliability engineers.
For Software Testing roles, this Druva practice set focuses most on Automation Basics for Manual Testers (7), Test Case Design (4), Agile, SQL and API Testing (4), STLC and Test Planning (4). It has 30 medium, 10 hard questions, so you can start easy and work up to the harder ones.
- Company type
- Product
- Headquarters
- California, USA
- Main India offices
- Pune
Druva Software Testing interview process
- Online coding assessment
- Technical round 1 (DSA)
- Technical round 2 (OS, networking or design)
- Hiring manager round
- HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for DruvaStart 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
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.
03
Write test cases for a signup form.
Show answer
Mandatory fields, email format, password rules, duplicate email, terms checkbox, captcha, confirmation email and field length limits.
04
What does INVEST mean for user stories?
Show answer
INVEST is a checklist for good user stories: Independent, Negotiable, Valuable, Estimable, Small and Testable. For testers, testable is the most important: a story must have clear acceptance criteria so you can say pass or fail. Small stories are easier to test within a sprint. If a story fails INVEST, raise it in refinement rather than discovering the gaps during testing.
05
How do you plan regression testing for a monthly release?
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.
06
How do you balance manual testing and automation work in the same sprint?
Show answer
I agree the split with the team at sprint planning. Testing new stories manually comes first because it blocks the sprint goal. I then automate the stable flows from the previous sprint, so scripts are not rewritten while features change. For example, I block two afternoons a week for automation and report progress in stand-up. If a release is at risk, I pause automation and tell the lead openly.
07
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.
08
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.
09
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.
10
Write a Postman test script that checks the status is 201 and the response contains an id.
Show answer
pm.test('Status is 201', function () {
pm.response.to.have.status(201);
});
pm.test('Response has id', function () {
const body = pm.response.json();
pm.expect(body).to.have.property('id');
pm.expect(body.id).to.be.a('number');
});
11
A CAPTCHA on the signup page blocks screen reader users. What do you recommend?
Show answer
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.
12
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.
13
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
14
How do you manage testing for multiple projects with competing deadlines?
Show answer
Model answer: Situation: I was supporting two products whose releases fell in the same week. Task: deliver both without dropping quality. Action: I listed tasks by release date and risk, agreed priorities with both leads, blocked focus time for each product and shared daily status. I also asked a teammate to take retesting on one project. Result: both releases went out on time with no critical escapes.
15
SQL: find orders that have no matching customer record.
Show answer
-- orphan orders indicate a broken foreign key or bad data load
SELECT o.order_id, o.customer_id
FROM orders o
LEFT JOIN customers c ON c.customer_id = o.customer_id
WHERE c.customer_id IS NULL;
16
How do you test push notifications?
Show answer
Verify notifications arrive when the app is in foreground, background and closed. Check title, text, icon and that tapping opens the right screen with the correct data. Test with notifications disabled at OS level and inside app settings. Check behaviour after logout, reinstall and on multiple devices with the same account. Test grouping of many notifications, time-sensitive ones, and that no notification shows private data on the lock screen.
17
Managers say the automation test report is hard to understand. What should a useful report include?
Show answer
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.
18
What is the difference between static and dynamic testing?
Show answer
Static testing reviews documents and code without executing; dynamic testing executes the software to observe behaviour.
19
What are the seven principles of testing?
Show answer
Testing shows presence of defects, exhaustive testing is impossible, test early, defects cluster, the pesticide paradox, testing is context-dependent and absence-of-errors is a fallacy.
20
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.
21
An automated test passes on your laptop but fails in the CI pipeline. How do you troubleshoot?
Show answer
Check the CI logs, screenshots, video or trace to see exactly where it failed. Then compare the environments: headless versus headed browser, screen size, browser version, time zone, environment URLs and secrets, test data and network speed. Run the test locally in headless mode with the CI settings. Common causes are timing, missing data in the CI environment and tests depending on run order. Fix the cause, not with a sleep.
22
Describe a time an automated test caught a regression that manual testing would have missed.
Show answer
Situation: a small tax rounding change was made late on a Friday. Task: no manual regression was planned for pricing. Action: our nightly API suite failed one data-driven case where a 3-item cart was off by one rupee; I checked the trace, reproduced it manually and logged it with the failing input. Result: it was fixed before release, and the team agreed to keep pricing tests in the pull request suite.
23
How do you test zoom, text resizing and reflow?
Show answer
Set browser zoom to 200 percent and check that all text is readable and no content or buttons are cut off. Then zoom to 400 percent, or use a 1280 pixel wide window, which gives a 320 CSS pixel viewport; content should reflow into one column without horizontal scrolling, except for things like data tables and maps. Also increase text spacing and the operating system font size to check that labels do not overlap.
24
The same bug keeps reopening across three sprints. What do you do?
Show answer
Stop the retest loop and call a short session with the developer, lead and product owner. Check whether the fix addresses the root cause or only the symptom, whether everyone agrees on the expected behaviour and whether different environments or data are involved. Run a root cause analysis and agree on clear acceptance tests before the next fix. Add an automated regression check so it cannot silently return.
25
Tell me about a time you worked with developers to make an application easier to automate.
Show answer
Situation: our UI scripts broke almost every sprint because of generated IDs and CSS class changes. Task: as the QA lead I needed stable tests. Action: I showed developers the failure history, proposed adding data-testid attributes and accessible labels to key components and added a short checklist to the pull request template. Result: within two sprints locator-related failures dropped by most of the previous level and maintenance time fell sharply.
26
The UI shows the correct order total, but the database has a different value. What do you check?
Show answer
Note the order ID and compare the UI value, the API response and the database value to find where they differ. Check if the UI calculates the total on the screen instead of using the saved value, whether taxes, discounts or rounding are applied at different layers and whether a later update job changed the record. Log the bug with all three values, because invoices and reports will use the database figure.
27
During a load test, some booking requests fail with a 'deadlock detected' error. What is happening and how do you report it?
Show answer
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.
28
What is decision table testing?
Show answer
List conditions and actions in a table and cover every combination of conditions (rules) — ideal for business rules like loan approval: salary > X AND credit score > Y → approve.
29
Your backlog has 200 low-priority bugs and it is becoming unmanageable. How do you handle it?
Show answer
Run a backlog grooming session with the product owner. Close bugs that are obsolete, no longer reproducible or for retired features. Merge duplicates. Group the rest by module and user impact, and ask whether a few related bugs can be fixed together as one story. Agree to reserve a small share of each sprint for bug fixes. Set an ageing rule, for example review any bug older than 90 days.
30
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.
31
What is the difference between UI automation and API automation, and which gives faster feedback?
Show answer
UI automation drives the browser or app like a user, so it checks the full experience but is slower and breaks more often with design changes. API automation sends requests directly to services and checks responses, which is much faster, more stable and can run before the UI exists. API tests give faster feedback, so teams place most business rule checks at the API level and keep a smaller set of UI journeys.
32
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.
33
What are implicit waits, explicit waits and auto-waiting?
Show answer
An implicit wait, in Selenium, sets a global time the driver keeps retrying to find any element before failing. An explicit wait waits for a specific condition, such as an element being clickable or a spinner disappearing, and is more precise. Auto-waiting, built into Playwright and Cypress, automatically waits for elements to be visible, enabled and stable before acting. Mixing implicit and explicit waits in Selenium can cause unpredictable delays.
34
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.
35
How would you test a feature that is enabled for only 10 percent of users through a feature flag?
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.
36
The product team wants to skip UAT to ship faster. What do you advise?
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.
37
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.
38
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.
39
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.
40
How do you capture logs from an Android device for a bug report?
Show answer
Enable developer options and USB debugging, connect the phone and confirm it is visible with adb devices. Clear old logs with adb logcat -c, reproduce the bug, then save logs with adb logcat -d > crash_log.txt, filtering by the app package or error level if needed. For a crash, search for FATAL EXCEPTION. Attach the log, device model, OS version, app version and a screen recording to the bug.
Tips to crack the Druva Software Testing interview
- Revise operating systems, file systems and networking basics, since backup and storage products rely heavily on these concepts.
- Practise DSA problems in your main language and be ready to discuss how you would design a scalable backup service.
- Learn basic cloud services such as object storage and compute on AWS to connect your skills with Druva's platform.
- 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; Druva interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Druva Software Testing interview?
Candidates usually go through 5 stages: Online coding assessment; Technical round 1 (DSA); Technical round 2 (OS, networking or design); 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 Druva Software Testing interview?
This practice set leans on Automation Basics for Manual Testers (7), Test Case Design (4), Agile, SQL and API Testing (4), STLC and Test Planning (4). Revise those first, then practise explaining one or two of your own projects end to end, because most Druva interviewers ask you to walk through real work.
Are these the exact questions asked at Druva?
No. These are curated practice questions that match the skills and difficulty usually tested in product interviews like Druva's. They are not a leaked or verified list of past questions.
Where does Druva hire Software Testing professionals in India?
Druva has large teams in Pune. Openings and locations change often, so check the Druva careers page and filter by city and experience.
Software Testing questions for similar companies
Product
Sprinklr
Software Testing interview questions
Gurugram, Bengaluru
View questionsProduct
BrowserStack
Software Testing interview questions
Mumbai, Bengaluru
View questionsProduct
Software Testing interview questions
Bengaluru, Hyderabad, Gurugram +2
View questionsProduct
Salesforce
Software Testing interview questions
Hyderabad, Bengaluru, Mumbai +1
View questionsProduct
Autodesk
Software Testing interview questions
Bengaluru, Pune
View questionsProduct
Urban Company
Software Testing interview questions
Gurugram
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