1️⃣ Role Expectation for Manual Testers with 2–3 Years Experience
At 2–3 years of experience, you are no longer treated as a fresher.
Interviewers expect you to:
- Own modules end-to-end
- Independently analyze requirements
- Design effective test scenarios
- Handle complex defects and RCA
- Support UAT & production issues
- Guide juniors and collaborate with dev/BA
- Understand business impact, not just UI issues
You are evaluated on:
✔ Analytical thinking
✔ Risk-based testing
✔ Communication maturity
✔ Practical project exposure
2️⃣ Core Manual Testing Interview Questions & Structured Answers
1. What is the role of a manual tester in a project?
A manual tester ensures the application meets functional, business, and user expectations by:
- Reviewing requirements
- Designing test scenarios
- Executing test cases
- Identifying risks
- Reporting defects with RCA
- Supporting UAT and releases
2. Explain SDLC and where testing fits in.
Testing is involved throughout SDLC, not just execution.
| SDLC Phase | Tester Involvement |
| Requirement | Clarify, identify testable points |
| Design | Review testability |
| Development | Smoke & early testing |
| Testing | Functional, regression |
| Deployment | Sanity & production validation |
| Maintenance | Regression & defect fixes |
3. Explain STLC with real project activities.
| Phase | Real-Time Activities |
| Requirement Analysis | Identify gaps, risks |
| Test Planning | Effort, scope, timelines |
| Test Design | Scenarios, data |
| Environment Setup | Build readiness |
| Execution | Defect logging |
| Closure | Metrics, sign-off |
4. What is risk-based testing?
Risk-based testing prioritizes critical and high-impact features first based on:
- Business impact
- Failure probability
- Usage frequency
5. Difference between Test Scenario and Test Case?
| Test Scenario | Test Case |
| High-level | Detailed |
| Covers requirement | Covers validation |
| “What to test” | “How to test” |
6. What types of testing have you performed?
- Functional testing
- Regression testing
- Smoke & sanity
- System & integration
- UAT support
- Exploratory testing
7. Explain Severity vs Priority with example.
| Severity | Priority |
| Impact on system | Urgency to fix |
| Set by tester | Set by product/lead |
Example:
Login button alignment issue → Low severity, High priority (client demo)
8. What is Defect Leakage?
Defects missed in testing and found in UAT or production.
Reduction techniques:
- Better regression
- Requirement reviews
- RCA on escaped defects
9. Explain Defect Life Cycle.
New → Assigned → Open → Fixed → Retest → Closed
(Rejected / Deferred / Reopened)
10. What metrics have you tracked?
- Test case execution %
- Defect density
- Defect leakage
- Reopen rate
- Pass/Fail trend
3️⃣ Agile & Scrum Interview Questions (Mid-Level Depth)
11. What is Agile testing?
Agile testing is continuous testing aligned with development, focusing on early feedback.
12. Tester responsibilities in Agile sprint.
- Grooming participation
- Writing test scenarios early
- Continuous execution
- Regression per sprint
- Sprint demo validation
13. What is Sprint Retrospective?
A meeting to discuss:
- What went well
- What didn’t
- Action items for improvement
14. How do you handle changing requirements?
- Analyze impact
- Update test cases
- Inform team
- Focus on critical paths
4️⃣ Scenario-Based Interview Questions with RCA
15. Scenario: Defect reported as “Not Reproducible”. What do you do?
- Recheck steps
- Verify environment
- Share logs/screenshots
- Reproduce with dev
16. Scenario: Critical bug found just before release.
Action Plan:
- Assess impact
- Inform lead
- Decide go/no-go
- Regression on fix
17. Scenario: Production issue raised by client.
RCA Steps:
- Gather logs
- Reproduce in lower env
- Identify root cause
- Prevent recurrence
18. Scenario: Data mismatch between UI and DB.
- Validate API response
- Check DB queries
- Verify data sync
- Raise defect with evidence
5️⃣ Real Project Defect Examples
Defect 1: Payment Failure
Summary: Amount debited but order not created
Severity: Critical
Root Cause: Transaction rollback missing
Impact: Financial loss
Defect 2: Role Access Issue
Issue: User sees admin options
Root Cause: Incorrect role mapping
Severity: High
6️⃣ Test Case Examples (Multi-Layer Testing)
UI Test Case
| Step | Action | Expected |
| 1 | Enter credentials | Accepted |
| 2 | Click Login | Redirect |
API Test Case (Postman)
- Method: POST
- Endpoint: /api/login
- Status: 200
- Response time < 2 sec
Database Validation (SQL)
SELECT status FROM orders WHERE order_id=12345;
Validate:
- Status updated
- Amount correct
Performance Testing Idea
- 1000 concurrent users
- Login < 3 sec
- CPU usage stable
7️⃣ Tools Interview Questions (Hands-On)
19. How do you use JIRA?
- Defect creation
- Linking stories
- Status tracking
- Evidence attachment
20. Purpose of TestRail?
- Test case management
- Execution tracking
- Reports
21. How do you use Postman?
- API testing
- Request validation
- Response verification
22. Selenium knowledge at 2–3 years?
- Basic automation understanding
- Script execution awareness
- Collaboration with automation team
23. SQL usage in testing?
- Data validation
- Backend checks
- Business rule verification
24. JMeter usage?
- Performance testing
- Load & stress scenarios
- Response time analysis
8️⃣ Domain Exposure Questions
Banking
- Fund transfer
- Balance validation
- Transaction history
Insurance
- Policy lifecycle
- Premium calculation
- Claim processing
ETL
- Source vs target validation
- Transformation rules
- Null checks
9️⃣ Common Mistakes at 2–3 Years Level
❌ Only basic answers
❌ No RCA explanation
❌ Cannot explain production defects
❌ 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 in demand?
Yes—especially for domain-heavy and exploratory testing.
Should I know automation?
Basic understanding is expected, not mastery.
What makes a candidate strong at this level?
- Clear project explanation
- Real defect examples
- RCA thinking