1. Role Expectations for a 2-Year Manual Tester
At 2 years of experience, you are expected to work as an independent manual tester who can handle modules with minimal supervision.
What Interviewers Expect at This Level
- Strong understanding of manual testing fundamentals
- Clear knowledge of STLC and SDLC
- Ability to analyze requirements and write test cases
- Confident defect reporting and follow-ups
- Hands-on experience with Agile projects
- Basic exposure to API, DB, automation concepts
- Ability to explain real project defects
- Ownership of assigned features or modules
- Clear communication with developers and leads
Interviewers focus more on real project experience and clarity of explanation than memorized definitions.
2. Core Manual Testing Interview Questions & Structured Answers
1. What is manual testing?
Answer:
Manual testing is the process of validating software functionality by executing test cases manually without using automation tools, to ensure the application meets business requirements.
2. Why is manual testing still important?
Answer:
- Detects usability and UI issues
- Helps understand business flows
- Useful for exploratory testing
- Required when automation is not feasible
- Essential in early stages of development
3. Explain SDLC phases.
Answer:
- Requirement Analysis
- Design
- Development
- Testing
- Deployment
- Maintenance
Each phase contributes to building a quality product.
4. Explain STLC phases.
| STLC Phase | Description |
| Requirement Analysis | Understand requirements & identify test scenarios |
| Test Planning | Define scope, tools, effort, risks |
| Test Case Design | Write test cases |
| Test Environment Setup | Prepare test environment & data |
| Test Execution | Execute test cases & log defects |
| Test Closure | Reports, metrics, sign-off |
5. Difference between SDLC and STLC?
| SDLC | STLC |
| Development lifecycle | Testing lifecycle |
| Focus on building software | Focus on validating software |
| Ends with maintenance | Ends with test closure |
6. What is requirement analysis in testing?
Answer:
It is the process of reviewing requirements to understand functionality, identify test scenarios, detect ambiguities, and ensure the requirement is testable.
7. What is a test scenario?
Answer:
A test scenario is a high-level description of what needs to be tested, covering a complete user flow.
8. What is a test case?
Answer:
A test case is a detailed document containing steps, inputs, and expected results to verify a specific functionality.
9. Difference between test scenario and test case?
| Test Scenario | Test Case |
| High-level flow | Detailed steps |
| Covers multiple cases | Covers one condition |
| Business-oriented | Execution-oriented |
10. Types of testing you have performed?
Answer:
- Functional testing
- Smoke testing
- Sanity testing
- Regression testing
- Integration testing
- System testing
- UAT support
3. Defect Management & Bug Reporting Questions
11. What is a defect?
Answer:
A defect is a mismatch between the expected result and the actual result of the application.
12. Explain the defect life cycle.
New → Assigned → Open → Fixed → Retest → Verified → Closed
(Additional states: Reopened, Rejected, Duplicate, Deferred)
13. Difference between severity and priority?
| Severity | Priority |
| Technical impact | Business urgency |
| Defined by QA | Defined by business/PO |
14. How do you decide defect severity?
Answer:
- Impact on functionality
- Data loss or system crash
- User experience impact
15. How do you write an effective bug report?
Answer:
- Clear and concise title
- Steps to reproduce
- Actual result
- Expected result
- Environment details
- Screenshots/logs
- Severity and priority
16. Sample Bug Report
Title: Login fails with valid credentials
Steps:
- Open login page
- Enter valid username and password
- Click Login
Expected Result: User logs in successfully
Actual Result: Error message displayed
Severity: High
Priority: P1
4. Agile Interview Questions (2 Years Experience)
17. What is Agile?
Answer:
Agile is an iterative development methodology where work is delivered in small increments called sprints, focusing on flexibility and continuous improvement.
18. What Agile ceremonies have you attended?
Answer:
- Sprint planning
- Daily stand-up
- Sprint review
- Retrospective
- Backlog grooming
19. Role of a tester in Agile?
Answer:
Tester participates in requirement discussions, writes test cases early, executes tests within sprint, logs defects, and validates acceptance criteria.
20. What is a user story?
Answer:
A user story is a requirement written from the end-user perspective, usually with acceptance criteria.
21. What is Definition of Done (DoD)?
Answer:
A story is considered done when development, testing, defect fixing, and Product Owner approval are completed.
5. Scenario-Based Interview Questions with RCA
22. A defect is found in production. What do you do?
Answer:
- Inform the team immediately
- Collect issue details
- Try to reproduce in test environment
- Log defect
- Support root cause analysis
- Add regression test to prevent recurrence
23. Real-Time Project Defect with RCA
Issue: OTP not received during login
Root Cause: SMS gateway timeout
Fix: Retry mechanism added
Prevention: Added negative and timeout test cases
24. Developer says “cannot reproduce”. What do you do?
Answer:
- Share clear reproduction steps
- Provide screenshots/logs
- Mention environment and test data
- Perform joint testing if needed
25. How do you test when requirements are unclear?
Answer:
I ask questions to BA/lead, document assumptions, and confirm expected behavior before testing.
6. Test Case Examples (UI, API, DB, Performance)
UI Test Case Example – Login
| Field | Value |
| Scenario | Login with valid credentials |
| Steps | Enter username & password |
| Expected | User redirected to dashboard |
| Priority | High |
API Test Case Example (Postman)
Endpoint: /api/login
Validations:
- Status code = 200
- Error message for invalid input
- Response time < 2 seconds
Database Validation (SQL Example)
SELECT count(*)
FROM users
WHERE email = ‘test@test.com’;
Expected Result: 1
Performance Test Scenario
- 300 concurrent users
- Response time < 3 seconds
- No server crash
7. Tools Interview Questions
26. How do you use JIRA?
Answer:
- Log and track defects
- Update defect status
- View sprint boards
27. What is TestRail used for?
Answer:
Managing test cases, executing test runs, and tracking coverage.
28. How do you use Postman?
Answer:
For API testing, validating responses, and checking status codes.
29. Selenium exposure?
Answer:
Basic understanding and ability to identify automation-worthy test cases.
30. JMeter exposure?
Answer:
Basic awareness of performance testing concepts.
31. SQL knowledge?
Answer:
Basic SELECT, WHERE, COUNT queries for data validation.
8. Domain Exposure
Banking Domain
- Login & authentication
- Fund transfer
- Transaction history
Insurance Domain
- Policy creation
- Premium calculation
- Claims processing
ETL / Data Testing
- Source-to-target validation
- Data count checks
9. Common Mistakes 2-Year Manual Testers Make
- Giving textbook answers only
- Not explaining real project defects
- Weak bug explanation
- Poor Agile understanding
- Over-claiming automation skills
10. Quick Revision Cheat Sheet
- SDLC vs STLC
- Test scenario vs test case
- Defect lifecycle
- Severity vs Priority
- Agile ceremonies
- Basic SQL
- API basics
11. FAQs + CTA
Q: Is automation mandatory at 2 years for manual testers?
No, but basic awareness is expected.
Q: What do interviewers focus on most?
Real project experience and clarity of explanation.