SoftwareTestPilot
32 Q&A · 0–1 YOE · Tech + HR

QA Interview Questions for Freshers (2026)

32 real QA interview questions written for 0–1 YOE candidates — fundamentals, test case design, SDLC/STLC + Agile, tools + automation + API + SQL basics, and 6 HR/behavioural questions. Salary bands, prep roadmap and links to every specialist hub included.

  • 6 min read
  • Difficulty: Easy → Medium
  • 0–1 YOE
  • Updated July 2026
  • Avinash Kamble
Back to Pillar
Avinash Kamble
Founder & QA Engineer at SoftwareTestPilot
Published:
0 / 32 reviewed
0%

1. QA Fundamentals for Freshers

Easy Very Common 1 minQ1 / 32

Q1.What is software testing?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Interviewers open with "software testing" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Software testing is the process of evaluating a system to find defects, verify it meets requirements, and validate it solves the user's problem. Combines verification (building the product right) and validation (building the right product).

Tips to remember
  • Open with a one-sentence definition of software testing, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise software testing cleanly.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ3
Q2 →
Easy Very Common 1 minQ2 / 32

Q2.What is the difference between QA and QC?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Interviewers open with "difference between QA and QC" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

QA (Quality Assurance) is process-oriented and preventive — audits, reviews, standards. QC (Quality Control) is product-oriented and corrective — inspection and testing to find defects. QA improves the process; QC verifies the product.

Tips to remember
  • Open with a one-sentence definition of difference between QA and QC, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise difference between QA and QC cleanly.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ4
← Q1Q3 →
Easy Very Common 1 minQ3 / 32

Q3.What is verification vs validation?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

Interviewers open with "verification vs validation" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Verification — are we building the product right? Static, done via reviews and walkthroughs. Validation — are we building the right product? Dynamic, done via test execution and UAT.

Tips to remember
  • Open with a one-sentence definition of verification vs validation, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise verification vs validation cleanly.
RelatedQ1Q5
← Q2Q4 →
Easy Very Common 1 minQ4 / 32

Q4.What are the 7 principles of testing?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Interviewers open with "7 principles of testing" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

(1) Testing shows defects, not absence. (2) Exhaustive testing is impossible. (3) Early testing saves cost. (4) Defects cluster. (5) Pesticide paradox — same tests stop finding bugs. (6) Testing is context-dependent. (7) Absence-of-errors fallacy.

Tips to remember
  • Open with a one-sentence definition of 7 principles of testing, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise 7 principles of testing cleanly.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ2Q6
← Q3Q5 →
Easy Very Common 1 minQ5 / 32

Q5.What is severity vs priority?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

Interviewers open with "severity vs priority" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Severity = business impact. Priority = urgency to fix. A misspelled homepage headline is low severity but high priority; a crash on a rarely used admin screen is high severity but low priority.

Tips to remember
  • Open with a one-sentence definition of severity vs priority, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise severity vs priority cleanly.
  • Tie contract checks to the consumer/provider workflow and where the contract is stored — that's the senior detail panels wait for.
RelatedQ3Q7
← Q4Q6 →
Easy Very Common 1 minQ6 / 32

Q6.What is the bug life cycle?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Interviewers open with "bug life cycle" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

New → Assigned → Open → In Progress → Fixed → Retest → Verified → Closed. Alternate states: Rejected, Deferred, Duplicate, Not-Reproducible, Reopened. Every transition is logged in Jira for audit.

Tips to remember
  • Open with a one-sentence definition of bug life cycle, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise bug life cycle cleanly.
RelatedQ4Q8
← Q5Q7 →
Easy Very Common 1 minQ7 / 32

Q7.What is the difference between smoke and sanity testing?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Interviewers open with "difference between smoke and sanity testing" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Smoke is wide + shallow — 'does the build even start?' Run on every build. Sanity is narrow + deep — verify a specific fix or small change works. Smoke is broader; sanity is deeper.

Tips to remember
  • Open with a one-sentence definition of difference between smoke and sanity testing, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise difference between smoke and sanity testing cleanly.
RelatedQ5Q9
← Q6Q8 →
Easy Very Common 1 minQ8 / 32

Q8.What is regression testing?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Interviewers open with "regression testing" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Regression re-runs a curated suite after every change to confirm existing features still work. Typically automated, gated in CI, and prioritised by risk — recent changes, high-traffic flows, past defect-heavy modules.

Tips to remember
  • Open with a one-sentence definition of regression testing, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise regression testing cleanly.
  • Give the severity-vs-priority example from your own project — generic definitions score the lowest on this one.
RelatedQ6Q10
← Q7Q9 →
Confidence check

If you can confidently answer the QA Fundamentals for Freshers questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

2. Test Case & Test Design

Easy Very Common 1 minQ9 / 32

Q9.How do you write a good test case?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Hands-on "how would you write a good test case" questions reveal whether you've actually shipped QA — Freshers code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Unique ID, clear title, precondition, atomic steps, single expected result, traceability to a requirement, priority, no dependency on other tests. Another tester should reproduce it exactly from your steps alone.

Tips to remember
  • Walk through write a good test case as numbered steps and call out the tool, command, or API used at each step.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise write a good test case cleanly.
  • Say who reads the report and what decision it drives — evidence-for-humans framing beats a tool name list.
RelatedQ7Q11
← Q8Q10 →
Easy Very Common 1 minQ10 / 32

Q10.What is boundary value analysis (BVA)?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Interviewers open with "boundary value analysis (BVA)" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

BVA tests at the edges of input ranges — min, min-1, min+1, max, max-1, max+1. For a text field 5–15 chars: test 4, 5, 6, 14, 15, 16 characters. Bugs cluster at boundaries.

Tips to remember
  • Open with a one-sentence definition of boundary value analysis (BVA), then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise boundary value analysis (BVA) cleanly.
  • Apply the technique live to a small example (a login field, an age input) instead of only naming it.
RelatedQ8Q12
← Q9Q11 →
Easy Very Common 1 minQ11 / 32

Q11.What is equivalence partitioning?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

Interviewers open with "equivalence partitioning" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

EP divides inputs into partitions where behaviour should be identical, then tests one value per partition. For age 18–60: one from <18, one from 18–60, one from >60 — three tests instead of dozens.

Tips to remember
  • Open with a one-sentence definition of equivalence partitioning, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise equivalence partitioning cleanly.
  • Apply the technique live to a small example (a login field, an age input) instead of only naming it.
RelatedQ9Q13
← Q10Q12 →
Easy Very Common 1 minQ12 / 32

Q12.What is decision table testing?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Interviewers open with "decision table testing" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Lists every combination of conditions and expected actions. For loan approval (age, income, credit score), each row becomes a test case. Guarantees complete logical coverage.

Tips to remember
  • Open with a one-sentence definition of decision table testing, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise decision table testing cleanly.
  • Apply the technique live to a small example (a login field, an age input) instead of only naming it.
RelatedQ10Q14
← Q11Q13 →
Easy Common 1 minQ13 / 32

Q13.What is positive vs negative testing?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

Interviewers open with "positive vs negative testing" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Positive — valid inputs, happy path. Negative — invalid inputs (letters in a number field, expired token, malformed JSON). System must handle both without crashing or exposing data.

Tips to remember
  • Open with a one-sentence definition of positive vs negative testing, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise positive vs negative testing cleanly.
  • Cover token expiry and refresh in your answer; most candidates only describe the happy-path login.
RelatedQ11Q15
← Q12Q14 →
Easy Common 1 minQ14 / 32

Q14.How do you write a bug report?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Hands-on "how would you write a bug report" questions reveal whether you've actually shipped QA — Freshers code or only read about it. Interviewers listen for concrete steps, the tools you'd reach for first, and the failure mode you'd guard against.

Detailed explanation

Title, environment (browser/OS/build/device), preconditions, exact repro steps, actual vs expected result, severity, priority, screenshots/video, console + network logs, reproducibility %, and a link to the failing test case.

Tips to remember
  • Walk through write a bug report as numbered steps and call out the tool, command, or API used at each step.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise write a bug report cleanly.
  • Say who reads the report and what decision it drives — evidence-for-humans framing beats a tool name list.
RelatedQ12Q16
← Q13Q15 →
Confidence check

If you can confidently answer the Test Case & Test Design questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

3. SDLC, STLC & Agile Basics

Easy Common 1 minQ15 / 32

Q15.What is the difference between SDLC and STLC?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Interviewers open with "difference between SDLC and STLC" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

SDLC covers building the product end-to-end (requirements → design → dev → test → deploy → maintain). STLC covers only QA activities inside SDLC: requirement analysis → test planning → test design → environment setup → execution → closure.

Tips to remember
  • Open with a one-sentence definition of difference between SDLC and STLC, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise difference between SDLC and STLC cleanly.
  • Explain setup/teardown ordering and what runs per-test vs per-suite; ordering mistakes are the follow-up question.
RelatedQ13Q17
← Q14Q16 →
Easy Common 1 minQ16 / 32

Q16.What are the phases of STLC?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Interviewers open with "phases of STLC" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

(1) Requirement analysis. (2) Test planning. (3) Test case design. (4) Test environment setup. (5) Test execution. (6) Test closure. Entry + exit criteria gate each phase.

Tips to remember
  • Open with a one-sentence definition of phases of STLC, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise phases of STLC cleanly.
  • Explain setup/teardown ordering and what runs per-test vs per-suite; ordering mistakes are the follow-up question.
RelatedQ14Q18
← Q15Q17 →
Easy Common 1 minQ17 / 32

Q17.What is Agile testing?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Interviewers open with "Agile testing" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Testing embedded in every sprint alongside development, not as a downstream gate. QA joins refinement, adds acceptance criteria, automates as features land, and gives daily quality signal instead of a big-bang test phase.

Tips to remember
  • Open with a one-sentence definition of Agile testing, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Agile testing cleanly.
  • Anchor the answer to a ceremony and an artefact (definition of done, story acceptance criteria) from a team you worked in.
RelatedQ15Q19
← Q16Q18 →
Easy Common 1 minQ18 / 32

Q18.What is Scrum and QA's role in it?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

Interviewers open with "Scrum and QA's role in it" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Scrum is an Agile framework: 2–4 week sprints, daily standups, sprint planning, review, retrospective. QA participates in all ceremonies, owns Definition-of-Done (automated tests + no P1/P2 open), and demos user-visible quality at review.

Tips to remember
  • Open with a one-sentence definition of Scrum and QA's role in it, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Scrum and QA's role in it cleanly.
  • Anchor the answer to a ceremony and an artefact (definition of done, story acceptance criteria) from a team you worked in.
RelatedQ16Q20
← Q17Q19 →
Easy Common 1 minQ19 / 32

Q19.What is a Definition of Done?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

Interviewers open with "Definition of Done" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

A team-owned checklist a story must satisfy before being called 'done' — e.g., code merged + peer-reviewed + unit tests passing + acceptance criteria automated + P1/P2 defects closed + deployed to staging + PO signed off.

Tips to remember
  • Open with a one-sentence definition of Definition of Done, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Definition of Done cleanly.
  • Anchor the answer to a ceremony and an artefact (definition of done, story acceptance criteria) from a team you worked in.
RelatedQ17Q21
← Q18Q20 →
Easy Common 1 minQ20 / 32

Q20.What is a user story and acceptance criteria?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Interviewers open with "user story and acceptance criteria" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

User story: 'As a <role>, I want <feature>, so that <benefit>'. Acceptance criteria are testable conditions the story must meet. QA turns each criterion into a test case before development starts.

Tips to remember
  • Open with a one-sentence definition of user story and acceptance criteria, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise user story and acceptance criteria cleanly.
  • Anchor the answer to a ceremony and an artefact (definition of done, story acceptance criteria) from a team you worked in.
RelatedQ18Q22
← Q19Q21 →
Confidence check

If you can confidently answer the SDLC, STLC & Agile Basics questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

4. Tools, Automation & API Basics

Easy Common 1 minQ21 / 32

Q21.What is Selenium?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

Interviewers open with "Selenium" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Selenium is an open-source browser-automation library — WebDriver drives Chrome/Firefox/Edge/Safari via native driver binaries. Bindings in Java, Python, C#, JS. Industry-standard for UI automation. See our Selenium Q&A hub.

Tips to remember
  • Open with a one-sentence definition of Selenium, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Selenium cleanly.
RelatedQ19Q23
← Q20Q22 →
Easy Common 1 minQ22 / 32

Q22.What is Playwright and why is it popular?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

Interviewers open with "Playwright and why is it popular" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Playwright (Microsoft) is a modern browser-automation library with auto-waits, first-class trace viewer, parallel execution, network stubbing, and cross-browser out-of-the-box. See Playwright Q&A.

Tips to remember
  • Open with a one-sentence definition of Playwright and why is it popular, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Playwright and why is it popular cleanly.
  • State that you never mix wait strategies and never use a hard sleep, then give the timeout value you actually run in CI.
RelatedQ20Q24
← Q21Q23 →
Medium Common 1 minQ23 / 32

Q23.What is a Page Object Model (POM)?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

Interviewers open with "Page Object Model (POM)" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

POM encapsulates a page's locators and actions in a class. Tests call loginPage.loginAs(user) instead of raw driver.findElement. Benefits: single point of change on UI updates, reusable actions, cleaner tests.

Tips to remember
  • Open with a one-sentence definition of Page Object Model (POM), then a concrete QA — Freshers example — never start with history or theory.
  • Be ready to whiteboard the Page Object Model (POM) snippet live — panels often ask you to type it, not describe it.
  • Add one sentence on what does NOT belong in a page object (assertions, test data) — that boundary is what separates mid from senior answers.
RelatedQ21Q25
← Q22Q24 →
Easy Occasional 1 minQ24 / 32

Q24.What is API testing?

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

Interviewers open with "API testing" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

API testing validates requests/responses at the service layer — status codes, headers, payload schema, business rules, auth. Freshers should know Postman + basic REST (GET/POST/PUT/DELETE, 2xx/4xx/5xx codes).

Tips to remember
  • Open with a one-sentence definition of API testing, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise API testing cleanly.
  • Assert status, schema and business payload — naming all three signals you test contracts, not just happy paths.
RelatedQ22Q26
← Q23Q25 →
Easy Occasional 1 minQ25 / 32

Q25.What are the common HTTP status codes?

Asked byAccentureInfosysCognizantWipro
Why interviewers ask this

Interviewers open with "common HTTP status codes" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

200 OK, 201 Created, 204 No Content, 301 Redirect, 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, 500 Server Error.

Tips to remember
  • Open with a one-sentence definition of common HTTP status codes, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise common HTTP status codes cleanly.
  • Assert status, schema and business payload — naming all three signals you test contracts, not just happy paths.
RelatedQ23Q27
← Q24Q26 →
Easy Occasional 1 minQ26 / 32

Q26.What SQL do QA freshers need?

Asked byMicrosoftAccentureInfosysCognizant
Why interviewers ask this

This QA — Freshers question checks whether you can go beyond textbook knowledge on What SQL do QA freshers need and reason about it the way a working QA engineer does — with a definition, an example, and the edge case that usually comes up next.

Detailed explanation

SELECT with WHERE, ORDER BY, LIMIT; INNER + LEFT JOIN; GROUP BY + COUNT/SUM/AVG; simple sub-queries; INSERT + UPDATE + DELETE (understanding, not always writing). See SQL Q&A for testers.

Tips to remember
  • Anchor the answer in a real QA — Freshers project — panels reward specificity on What SQL do QA freshers need over textbook wording.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise What SQL do QA freshers need cleanly.
  • Say how you clean up or roll back the data you touch — DB questions are really data-hygiene questions.
RelatedQ24Q28
← Q25Q27 →
Confidence check

If you can confidently answer the Tools, Automation & API Basics questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

5. HR & Behavioural for Freshers

Easy Occasional 1 minQ27 / 32

Q27.Why do you want to be a QA engineer?

Asked byCognizantWiproAmazonCapgemini
Why interviewers ask this

"Why" questions on you want to be a QA engineer probe your reasoning, not your memory. Strong candidates connect the choice to a business or reliability outcome — flaky tests, slower feedback loop, or missed defects — instead of parroting a rule.

Detailed explanation

Answer with (1) genuine interest — 'I like breaking systems to understand them', (2) 1 project you tested (college app, hackathon, tutorial), (3) alignment — 'QA is the last line before users see the product; that responsibility drew me in.' Avoid 'I couldn't get a dev role.'

Tips to remember
  • Tie the "why" for you want to be a QA engineer back to a measurable outcome — flake rate, execution time, defect leakage — instead of an opinion.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise you want to be a QA engineer cleanly.
  • Assert status, schema and business payload — naming all three signals you test contracts, not just happy paths.
RelatedQ25Q29
← Q26Q28 →
Easy Occasional 1 minQ28 / 32

Q28.What are your strengths and weaknesses?

Asked byInfosysCognizantWiproAmazon
Why interviewers ask this

Interviewers open with "your strengths and weaknesses" to confirm you can define the concept in one crisp line before going deeper. In QA — Freshers rounds this filters out candidates who only remember syntax and can't articulate the underlying idea to a non-expert teammate.

Detailed explanation

Strengths: analytical thinking + attention to detail + written communication — back each with a 1-line example. Weaknesses: pick something coachable ('I over-document; I'm learning to prioritise'), never a fake strength like 'I'm too perfectionist'.

Tips to remember
  • Open with a one-sentence definition of your strengths and weaknesses, then a concrete QA — Freshers example — never start with history or theory.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise your strengths and weaknesses cleanly.
RelatedQ26Q30
← Q27Q29 →
Easy Occasional 1 minQ29 / 32

Q29.Where do you see yourself in 5 years?

Asked byAmazonCapgeminiTCSMicrosoft
Why interviewers ask this

This QA — Freshers question checks whether you can go beyond textbook knowledge on Where do you see yourself in 5 years and reason about it the way a working QA engineer does — with a definition, an example, and the edge case that usually comes up next.

Detailed explanation

Show ambition without overreach: 'Master automation + framework design in 2 years, transition to SDET in 3, lead a QA squad or move to a niche like performance/security by year 5.' Ties personal growth to the company's needs.

Tips to remember
  • Anchor the answer in a real QA — Freshers project — panels reward specificity on Where do you see yourself in 5 years over textbook wording.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Where do you see yourself in 5 years cleanly.
  • Use percentiles (P90/P95) and a concrete SLA rather than averages — averages hide the failures interviewers care about.
RelatedQ27Q31
← Q28Q30 →
Easy Occasional 1 minQ30 / 32

Q30.Why should we hire you?

Asked byWiproAmazonCapgeminiTCS
Why interviewers ask this

"Why" questions on should we hire you probe your reasoning, not your memory. Strong candidates connect the choice to a business or reliability outcome — flaky tests, slower feedback loop, or missed defects — instead of parroting a rule.

Detailed explanation

3 sentences: (1) match — one skill from the JD you already have, (2) proof — a project or number, (3) attitude — willingness to learn stack X. Example: 'I know Selenium + Postman, built a POM framework on my GitHub, and I can pick up your API-first stack in 4 weeks.'

Tips to remember
  • Tie the "why" for should we hire you back to a measurable outcome — flake rate, execution time, defect leakage — instead of an opinion.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise should we hire you cleanly.
  • Add one sentence on what does NOT belong in a page object (assertions, test data) — that boundary is what separates mid from senior answers.
RelatedQ28Q32
← Q29Q31 →
Easy Occasional 1 minQ31 / 32

Q31.Do you have any questions for us?

Asked byTCSMicrosoftAccentureInfosys
Why interviewers ask this

This QA — Freshers question checks whether you can go beyond textbook knowledge on Do you have any questions for us and reason about it the way a working QA engineer does — with a definition, an example, and the edge case that usually comes up next.

Detailed explanation

Always yes. Ask: 'What does a great QA look like on your team after 6 months?' or 'How does QA participate in sprint planning here?' Signals you think about impact, not just the job.

Tips to remember
  • Anchor the answer in a real QA — Freshers project — panels reward specificity on Do you have any questions for us over textbook wording.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Do you have any questions for us cleanly.
  • Tie contract checks to the consumer/provider workflow and where the contract is stored — that's the senior detail panels wait for.
RelatedQ29
← Q30Q32 →
Easy Occasional 1 minQ32 / 32

Q32.Tell me about yourself.

Asked byCapgeminiTCSMicrosoftAccenture
Why interviewers ask this

This QA — Freshers question checks whether you can go beyond textbook knowledge on Tell me about yourself and reason about it the way a working QA engineer does — with a definition, an example, and the edge case that usually comes up next.

Detailed explanation

60-second answer: (1) degree + graduation year, (2) 1 project or internship with a QA angle, (3) skills learned (Selenium/Postman/SQL), (4) 1 line on why QA, (5) 1 line on why this company. Rehearse aloud until it's natural — not memorised.

Tips to remember
  • Anchor the answer in a real QA — Freshers project — panels reward specificity on Tell me about yourself over textbook wording.
  • Keep the answer to 60–90 seconds; anything longer signals you can't summarise Tell me about yourself cleanly.
  • Say how you clean up or roll back the data you touch — DB questions are really data-hygiene questions.
RelatedQ30
← Q31
Confidence check

If you can confidently answer the HR & Behavioural for Freshers questions above, you're well prepared for this section of your interview. Move on, or rehearse the trickier ones aloud with our AI mock interviewer.

Quick revision

  1. Q1: What is software testing — Software testing is the process of evaluating a system to find defects, verify it meets requirements, and validate it solves the user's problem.
  2. Q2: What is the difference between QA and QC — QA (Quality Assurance) is process-oriented and preventive — audits, reviews, standards.
  3. Q3: What is verification vs validation — Verification — are we building the product right?
  4. Q4: What are the 7 principles of testing — (1) Testing shows defects, not absence.
  5. Q5: What is severity vs priority — Severity = business impact.

Frequently asked questions

1.What questions are asked in a QA fresher interview?
Definitions (SDLC vs STLC, verification vs validation, severity vs priority), test design (BVA, EP, decision table), bug life cycle, one SQL query, one API status code question, and 2–3 HR questions ('why QA?', 'strengths/weaknesses'). This page covers all 32 real questions.
2.How should a fresher prepare for a QA interview?
(1) Master ISTQB Foundation glossary. (2) Write 20 test cases for a real app (login, cart, search). (3) Learn Postman + one automation tool (Selenium or Playwright basics). (4) Practise 5 SQL queries daily for 2 weeks. (5) Rehearse 5 HR answers aloud with an AI mock interviewer.
3.Do freshers need to know coding for QA jobs?
For manual QA at service companies (TCS, Infosys, Wipro, Cognizant): basic SQL + Postman is enough. For automation/SDET roles at product companies: expect a coding round in Python/Java/JavaScript (arrays, strings, hashmaps, one recursion problem).
4.What is the salary of a QA fresher in India (2026)?
Service companies: ₹3.5–5 LPA. Mid-tier product companies: ₹6–10 LPA. Top product companies (Google, Microsoft, Amazon SDET): ₹18–32 LPA base + joining bonus. Location and stack (automation vs manual) add another 20–40%.
5.Is ISTQB certification required for QA freshers?
Not required, but ISTQB Foundation (CTFL) adds signal on the resume — especially for freshers with a non-CS degree. Cost ~₹10K in India, ~$229 in the US. Study time 40–60 hours. Passing it does NOT replace hands-on practice.
6.Which is better for freshers — manual or automation?
Start with manual for 3–6 months to master fundamentals (test design, bug life cycle, domain understanding). Then move to automation. Skipping manual and jumping straight to Selenium/Playwright is the #1 reason freshers fail interview rounds on 'basic' questions.
7.How many interview rounds are there for QA fresher roles?
Service companies: 3 rounds (aptitude, technical, HR). Product companies: 4–5 rounds (online assessment, technical, framework/SQL, hiring manager, HR/bar-raiser). Bank on 1–3 weeks end-to-end.
8.What projects should a QA fresher put on the resume?
One real automation project on GitHub (Selenium/Playwright + POM + CI on a public app like OpenCart or SauceDemo), 20 documented manual test cases, one API testing project in Postman, and one SQL-heavy data-validation project. Real repos beat certificates.

QA — Freshers jobs hiring now

Live, indexable QA — Freshers openings — updated daily in Jobs Radar.

Browse all QA jobs on Jobs Radar

Loading current openings…

Home