Wipro
Approved anonymous reviews from software testers. Anonymous by default.
QA interview loop at Wipro
- 1
System / test-strategy design
60 minDesign a test strategy for a payments/checkout system, quality gates in CI/CD.
- 2
QA fundamentals
45 minTest design, boundary/equivalence, defect life-cycle, severity vs priority.
- 3
API + SQL round
45–60 minREST verbs, contract testing, JSON assertions, joins, window functions.
- 4
Automation deep-dive
60 minSelenium/Playwright architecture, waits, POM vs screenplay, flaky test triage.
- 5
Bar-raiser / hiring manager
45 minOwnership stories, on-call incidents, leading quality without authority.
Median time-to-offer from peer reports: ~14 days. Prep with our QA interview question bank.
Green flags to look for
- Bug reports get triaged inside 24h with a named owner.
- Devs pair with QA on flakiness instead of skipping the test.
- QA is invited to grooming, not handed a finished spec.
- Test data seeded via API, not hand-crafted UI clicks.
Red flags to grill in your loop
- PMs push scope changes on the day of release.
- Only QA is on the release call at 11pm.
- Automation is measured by count of scripts, not defects caught.
- No blameless post-mortems after a prod incident.
QA tech stack signals
Common industry defaults — replace with peer-reported stack as reviews arrive.
Live culture signals
- Fresh reviews (90 days)0
- Would-recommend rate—
- Culture vs site average—
- Est. time-to-offer~14 days
Questions testers reported being asked
- API
What signals in an API response would make you fail a test even if status is 200?
- Judgement
How do you decide what NOT to automate?
- Debugging
How would you catch a race condition in a checkout that only reproduces in prod?
- Release
You have 15 minutes before a release and one flaky E2E — quarantine or block? Defend it.
- Architecture
Explain the trade-offs between Page Object Model and Screenplay pattern.
- Strategy
Design a test strategy for a payment refund flow across web, mobile and BE.
Role-specific prep kit for Wipro
Insider FAQ — before you accept
＋What does the QA interview loop actually look like here?
Based on peer reports, expect a recruiter screen, a QA fundamentals round, an automation deep-dive (Selenium/Playwright), an API + SQL round, and a hiring-manager conversation. Ask the recruiter upfront whether there is a live coding round — that single question changes how you prep.
＋Do QA engineers here own test strategy or just execute it?
Look for it in the reviews below. A healthy signal: testers are in grooming, own the test plan, and can veto a release. A weaker signal: QA gets a finished spec and a deadline. Ask in your loop: 'Show me the last release where QA said no.'
＋What automation stack should I brush up on before the interview?
Whatever the pros/cons below mention most. If nothing is listed yet, assume the industry default: Selenium or Playwright + a Java/JS/Python runner, Postman or RestAssured for API, Jenkins/GitHub Actions for CI. Warm up on flakiness, waits and parallelisation — that's where 70% of tough questions live.
＋Is manual testing respected or treated as a stepping-stone?
This is culture, not process. Skim the 'Cons' below for phrases like 'only automation gets promoted' or 'manual testers left out of design reviews'. If it's absent, treat that as neutral and ask directly in the loop.
＋How is on-call and release ownership handled for QA?
Ask specifically: who joins the release bridge, who signs off, and what happens at 11pm on a Friday if a critical bug surfaces. Reviews mentioning weekend releases or lone-QA sign-off are the loudest red flag on this page.
＋What salary band should a mid-level SDET target here?
Cross-check the QA salary guides linked in the prep kit above — bands vary by city and years of experience, but the recruiter almost always negotiates within a ±15% window of their internal grid. Anchor with data, not a wish.
Approved reviews
Sign in to see members-only reviews.