Companies / Wipro
Wipro practice pack
IT services. 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.
Skills this role is usually tested on
- Selenium or Playwright
- Defect triage
- Test case design
- SQL
- Jira and reporting
Business areas used for scenarios
- BFSI
- healthcare
- telecom
- consumer goods
6 questions
Answer out loud first, then open the guide. Most people read the guide too early.
- 1
How would you test an elevator?
easyTest designA strong answer covers
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.
- 2
Compare Selenium and Playwright for a team moving a 300-test suite. What would make you stay, and what would make you move?
mediumAutomationA strong answer covers
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.
- 3
Your team logs many duplicate and low-value bugs. What do you change?
mediumDefectsA strong answer covers
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.
- 4
Find the second highest salary in an employees table and explain two ways.
mediumSQLA strong answer covers
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.
- 5
What would you put in a daily test status report for a client?
easyReportingA strong answer covers
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.
- 6
Your Selenium suite takes four hours. Get it under one hour without losing coverage.
hardFrameworkA strong answer covers
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.
Now say it to an interviewer
Reading a guide is not the same as answering under a clock. Run a mock interview and get scored feedback.