Manual Testing Interview Questions for 2.5 Years Experience

1️⃣ Role Expectation at 2.5 Years Experience

At 2.5 years, you are expected to work independently, not as a fresher and not yet as a lead.

Interviewers expect you to:

  • Own modules end-to-end
  • Analyze business requirements deeply
  • Design test scenarios without supervision
  • Identify high-risk areas
  • Handle production/UAT defects
  • Perform basic mentoring of juniors
  • Participate actively in Agile ceremonies
  • Provide Root Cause Analysis (RCA)

❗ At this level, how you explain your thinking matters more than definitions.


2️⃣ Core Manual Testing Interview Questions & Structured Answers

1. What is the role of a manual tester with 2.5 years of experience?

A manual tester at this level ensures quality ownership by:

  • Reviewing requirements proactively
  • Designing risk-based test scenarios
  • Executing functional, integration, and regression tests
  • Logging high-quality defects
  • Supporting UAT and production issues
  • Providing RCA for escaped defects

2. Explain SDLC and your involvement in each phase.

SDLC PhaseTester Responsibility
Requirement AnalysisIdentify ambiguities & risks
DesignReview testability
DevelopmentSmoke & early validation
TestingFunctional & regression
DeploymentSanity & production checks
MaintenanceRegression & defect fixes

3. Explain STLC with real project activities.

STLC PhaseReal-Time Actions
Requirement AnalysisRequirement review, queries
Test PlanningEffort estimation, scope
Test Case DesignScenario-based cases
Environment SetupBuild & data readiness
Test ExecutionDefect logging & tracking
Test ClosureMetrics & sign-off

4. What is risk-based testing?

Risk-based testing focuses on high-impact and high-probability failure areas first.

Example:
Payment, login, and data-saving features are tested before UI alignment issues.


5. Difference between Test Scenario and Test Case?

Test ScenarioTest Case
High-level validationStep-by-step
What to testHow to test
Derived from requirementDerived from scenario

6. What types of testing have you performed?

  • Functional testing
  • Integration testing
  • Regression testing
  • Smoke & sanity testing
  • Exploratory testing
  • UAT support

7. Explain Severity vs Priority with real example.

SeverityPriority
Impact on systemUrgency to fix
Decided by testerDecided by lead/PO

Example:
Typo on homepage → Low severity, High priority (client demo).


8. What is defect leakage?

Defects that escape testing and are found in UAT or production.

How to reduce leakage:

  • Strong regression suite
  • Requirement reviews
  • RCA for production defects

9. Explain defect life cycle.

New → Assigned → Open → Fixed → Retest → Closed
(Rejected / Deferred / Reopened when needed)


10. What testing metrics have you used?

  • Test case execution %
  • Defect density
  • Defect leakage
  • Reopen rate
  • Pass/Fail trends

3️⃣ Agile & Scrum Interview Questions (2.5-Year Depth)

11. What is Agile testing?

Agile testing is continuous testing aligned with development, ensuring early feedback and faster delivery.


12. Tester responsibilities in Agile sprint.

  • Participate in grooming
  • Write test scenarios early
  • Execute stories within sprint
  • Perform sprint-level regression
  • Validate sprint demo

13. What is sprint retrospective?

A meeting to discuss:

  • What went well
  • What didn’t
  • Improvement actions for next sprint

14. How do you handle requirement changes mid-sprint?

  • Analyze impact
  • Update test cases
  • Inform team
  • Focus on critical workflows

4️⃣ Scenario-Based Questions with RCA (Very Important)

15. Scenario: Defect marked “Not Reproducible”.

Steps:

  • Re-check steps
  • Confirm environment
  • Attach logs/screenshots
  • Reproduce with developer

16. Scenario: Critical defect found just before release.

Actions:

  • Assess business impact
  • Inform lead & PO
  • Decide release vs rollback
  • Regression on fix

17. Scenario: Production issue reported by client.

RCA Process:

  1. Collect logs
  2. Reproduce in lower env
  3. Identify root cause
  4. Add regression case

18. Scenario: Data mismatch between UI and DB.

  • Validate API response
  • Check DB query
  • Verify data sync
  • Raise defect with evidence

5️⃣ Real Project Defect Examples (With RCA)

Defect 1: Payment Failure

  • Issue: Amount debited, order not created
  • Severity: Critical
  • Root Cause: Transaction rollback missing
  • Impact: Financial loss

Defect 2: Role Access Issue

  • Issue: Normal user sees admin options
  • Root Cause: Incorrect role mapping
  • Severity: High

6️⃣ Test Case Examples (UI, API, DB, Performance)

UI Test Case

StepActionExpected
1Enter usernameAccepted
2Enter passwordMasked
3Click LoginDashboard displayed

API Test Case (Postman)

  • Method: POST
  • Endpoint: /api/login
  • Expected status: 200
  • Response time < 2 sec

Database Validation (SQL)

SELECT order_status, amount 

FROM orders 

WHERE order_id = 10234;

Validate:

  • Status updated
  • Amount correct

Performance Testing Idea

  • 1000 concurrent users
  • Login response < 3 sec
  • No server errors

7️⃣ Tools Interview Questions (Hands-On Focus)

19. How do you use JIRA?

  • Create & track defects
  • Link defects to stories
  • Add evidence & comments
  • Monitor defect status

20. What is TestRail used for?

  • Writing test cases
  • Tracking execution
  • Generating reports

21. How do you use Postman?

  • API request validation
  • Response code verification
  • JSON response checks

22. Selenium knowledge expected at 2.5 years?

  • Conceptual understanding
  • Script execution awareness
  • Collaboration with automation team

23. How do you use SQL in testing?

  • Validate backend data
  • Check business rules
  • Verify transactions

24. How is JMeter used?

  • Load testing
  • Stress testing
  • Response time analysis

8️⃣ Domain Exposure Questions

Banking Domain

  • Fund transfer
  • Balance validation
  • Transaction history

Insurance Domain

  • Policy lifecycle
  • Premium calculation
  • Claim processing

ETL

  • Source vs target validation
  • Data transformation
  • Null & duplicate checks

9️⃣ Common Mistakes at 2.5 Years Level

❌ Only theoretical answers
❌ No RCA explanation
❌ Cannot explain production issues
❌ Weak Agile understanding
❌ No metrics knowledge


🔟 Quick Revision Cheat Sheet

  • SDLC vs STLC
  • Risk-based testing
  • Severity vs Priority
  • Defect leakage
  • Agile ceremonies
  • Test metrics

1️⃣1️⃣ FAQs

Is manual testing still relevant?

Yes—especially for domain-heavy, exploratory, and UAT testing.

Should I know automation?

Basic understanding is expected, not expert coding.

What differentiates strong candidates at 2.5 years?

  • Clear project explanation
  • Real defect examples
  • RCA thinking
  • Business understanding

Leave a Comment

Your email address will not be published. Required fields are marked *