QA Hangar
Company Pulse

IQVIA, Bangalore

Approved anonymous reviews from software testers. Anonymous by default.

All companies

IQVIA, Bangalore

4.5 / 52 reviews· 50% would recommend

Rating distribution

  • 5★
    1
  • 4★
    1
  • 3★
    0
  • 2★
    0
  • 1★
    0

Culture axes

  • QA culture4.5
  • Work-life4.0
  • Growth3.0
  • Management3.0

QA interview loop at IQVIA, Bangalore

Difficulty 8/10
  1. 1

    Bar-raiser / hiring manager

    45 min

    Ownership stories, on-call incidents, leading quality without authority.

  2. 2

    QA fundamentals

    45 min

    Test design, boundary/equivalence, defect life-cycle, severity vs priority.

  3. 3

    Live coding / pairing

    60 min

    Automate a small flow end-to-end; explain trade-offs while typing.

  4. 4

    Automation deep-dive

    60 min

    Selenium/Playwright architecture, waits, POM vs screenplay, flaky test triage.

  5. 5

    API + SQL round

    45–60 min

    REST verbs, contract testing, JSON assertions, joins, window functions.

Median time-to-offer from peer reports: ~19 days. Prep with our QA interview question bank.

Green flags to look for

  • Test environments look like prod — not last quarter's snapshot.
  • Automation runs on every PR — not a nightly wishful cron.
  • QA is invited to grooming, not handed a finished spec.
  • Bug reports get triaged inside 24h with a named owner.

Red flags to grill in your loop

  • Manual regression cycles longer than the sprint itself.
  • PMs push scope changes on the day of release.
  • Automation is measured by count of scripts, not defects caught.
  • Flaky tests get muted, not fixed.

QA tech stack signals

PlaywrightSeleniumPostman / APIJenkinsSQLGit

Common industry defaults — replace with peer-reported stack as reviews arrive.

Live culture signals

  • Fresh reviews (90 days)2
  • Would-recommend rate50%
  • Culture vs site average+22%
  • Est. time-to-offer~19 days

Questions testers reported being asked

  • Case design

    Given a spec, write 6 test cases for the login endpoint — happy, negative, boundary, security.

  • Strategy

    Design a test strategy for a payment refund flow across web, mobile and BE.

  • Release

    You have 15 minutes before a release and one flaky E2E — quarantine or block? Defend it.

  • Automation

    Walk me through how you'd stabilise a Playwright suite that fails 1 in 10 runs.

  • Debugging

    How would you catch a race condition in a checkout that only reproduces in prod?

  • SQL

    Write SQL to find users who placed 3 or more orders in the last 30 days.

Role-specific prep kit for IQVIA, Bangalore

Playwright interview questionsSelenium interview questionsAPI testing questionsSQL for QAFull QA interview hubATS-check your resume before applying
Hiring at IQVIA, Bangalore? Check Jobs Radar for the latest openings.

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.
  • 4/5·Anonymous QA · Junior · 2026· Bangalore
    7/18/2026

    Pros

    Good office work life

    Cons

    Contractors will get only contract extended no hike in salary from past 2 years

  • 5/5·Anonymous QA · 2026· Recommends
    7/13/2026

    Pros

    Good Work Environment

    Cons

    No Hike especially for contractors, they will only extend your contract