IT services
Wipro
Project-based questions on automation, defects, and tools.
These are our own practice questions for the kind of QA/SDET role this company hires for. They are not the company's real interview questions. Confirm the current process on the company's official careers page.
What they tend to probe
- Selenium or Playwright
- Defect triage
- Test case design
- SQL
- Jira and reporting
Question 1 · Test design · Easy
How would you test an elevator?
Answer guide
Treat it as a system: functional (call, floors, doors), non-functional (load limit, speed, power failure), safety (door sensor, alarm), usability, and concurrency (two calls at once). Structure beats a long random list.
Question 2 · Automation · Medium
Compare Selenium and Playwright for a team moving a 300-test suite. What would make you stay, and what would make you move?
Answer guide
Auto-waiting, speed, trace viewer, parallelism, browser coverage vs existing skills, grid investment, migration cost. Recommend a pilot on one module, not a big-bang rewrite.
Question 3 · Defects · Medium
Your team logs many duplicate and low-value bugs. What do you change?
Answer guide
Search-before-log habit, a bug template with steps, expected, actual, evidence, a short triage meeting, clear severity guide, and metrics that reward quality of reports, not count.
Question 4 · SQL · Medium
Find the second highest salary in an employees table and explain two ways.
Answer guide
Subquery with MAX below the MAX, or DENSE_RANK() = 2. Mention that LIMIT/OFFSET fails with duplicates and what you return if there is no second value.
Question 5 · Reporting · Easy
What would you put in a daily test status report for a client?
Answer guide
Executed vs planned, pass and fail, open defects by severity, blockers, risks, tomorrow's plan. Keep it to one screen. Flag a risk before it becomes a miss.
Question 6 · Framework · Hard
Your Selenium suite takes four hours. Get it under one hour without losing coverage.
Answer guide
Measure first. Parallelise, remove sleeps, move setup to API calls, split smoke and full regression, run in containers, delete duplicated checks. Report time per test to find the heavy ones.