1. Role Expectations at 3 Years Experience (Manual Testing)
At 3 years of experience, you are expected to function as an independent manual tester, not a fresher and not yet a lead.
Interviewers assess whether you can:
- Own complete modules or features
- Understand business requirements without hand-holding
- Design effective test scenarios and test cases
- Identify edge cases and risks
- Report clear, high-quality defects
- Perform basic to intermediate Root Cause Analysis (RCA)
- Work confidently in Agile teams
- Support UAT and production issues
- Collaborate with developers and stakeholders
- Use tools like Jira and TestRail effectively
At this level, interviews focus on thinking ability, scenario handling, and real project exposure, not just definitions.
2. Core Manual Testing Interview Questions & Structured Answers
Manual Testing Fundamentals (3-Year Depth)
1. What is manual testing?
Manual testing is the process of validating application functionality without automation tools, by executing test cases manually and comparing actual results with expected results.
At 3 years, manual testing is about:
- Understanding business intent
- Finding functional gaps
- Preventing customer-impacting defects
2. What types of testing have you performed?
- Functional testing
- Smoke testing
- Sanity testing
- Regression testing
- Integration testing
- System testing
- UAT support
3. What is functional testing?
Functional testing ensures the application behaves as per business requirements.
Examples:
- Login validation
- Order placement
- Payment processing
4. Smoke testing vs Sanity testing?
| Smoke Testing | Sanity Testing |
| Broad coverage | Narrow, focused |
| Checks build stability | Checks specific fixes |
| Entry criteria for testing | Post-fix validation |
5. What is regression testing and how do you handle it?
Regression testing verifies that existing functionality is not broken after:
- New features
- Bug fixes
- Configuration changes
At 3 years, you should:
- Identify critical business flows
- Prioritise regression cases
- Avoid redundant test cases
6. Verification vs Validation?
| Verification | Validation |
| Static process | Dynamic process |
| Reviews & walkthroughs | Actual execution |
| “Are we building it right?” | “Are we building the right product?” |
3. SDLC & STLC Interview Questions (3 Years)
7. Explain SDLC.
SDLC (Software Development Life Cycle) defines how software is built and maintained.
| Phase | Description |
| Requirement | Business needs gathering |
| Design | System architecture |
| Development | Coding |
| Testing | Verification & validation |
| Deployment | Release |
| Maintenance | Enhancements & fixes |
8. What is your role in SDLC as a tester?
- Review requirements
- Identify test scenarios
- Design and execute test cases
- Log and track defects
- Perform regression testing
- Support UAT and releases
9. Explain STLC.
STLC (Software Testing Life Cycle) includes:
- Requirement Analysis
- Test Planning
- Test Case Design
- Test Environment Setup
- Test Execution
- Test Closure
At 3 years, you are actively involved in test case design and execution, and partially in planning.
10. Difference between SDLC and STLC?
| SDLC | STLC |
| Product lifecycle | Testing lifecycle |
| Covers all teams | QA-specific |
| Ends with maintenance | Ends with test closure |
4. Test Case Design Interview Questions (3 Years)
11. What is a test case?
A test case is a documented set of:
- Preconditions
- Test steps
- Test data
- Expected results
Used to validate a specific requirement.
12. How do you write effective test cases?
Effective test cases are:
- Clear and unambiguous
- Independent
- Traceable to requirements
- Cover positive, negative, and boundary scenarios
13. Sample Manual Test Case – Login
| Field | Value |
| Test Case ID | TC_Login_Valid |
| Scenario | Valid user login |
| Steps | Enter valid credentials |
| Expected Result | User navigates to dashboard |
14. What are positive and negative test cases?
- Positive test case: Valid input, expected behaviour
- Negative test case: Invalid input, error handling
Example:
- Negative: Invalid password
- Negative: Empty username
15. What is Boundary Value Analysis (BVA)?
BVA tests values at minimum and maximum limits.
Example:
- Password length allowed: 8–16
Test values: 7, 8, 16, 17
5. Defect Management & Bug Reporting
16. What is a defect?
A defect is a deviation between expected and actual behaviour of the application.
17. Defect life cycle.
- New
- Assigned
- Open
- Fixed
- Retest
- Closed / Reopened
18. Severity vs Priority.
| Severity | Priority |
| Impact on system | Urgency to fix |
| Decided by QA | Decided by business |
19. Sample Bug Report (Real Project Example)
Title: User able to place order without selecting address
Environment: QA
Steps:
1. Login
2. Add item to cart
3. Skip address selection
4. Click Place Order
Expected: Address validation message
Actual: Order placed successfully
Severity: High
Priority: High
20. What is Root Cause Analysis (RCA)?
RCA identifies why a defect occurred and how to prevent it in future.
At 3 years, RCA usually involves:
- Missed test scenario
- Requirement misunderstanding
- Data or environment issues
6. Scenario-Based Interview Questions (3 Years)
21. Developer rejects your bug as “Not a defect.” What will you do?
- Re-check requirement
- Reproduce the issue
- Share evidence (screenshots/logs)
- Explain business impact calmly
22. Bug appears in UAT but not in QA. Why?
- Environment difference
- Test data mismatch
- Role/permission issues
- Missed negative scenario
23. Production defect reported. What is your action plan?
- Understand business impact
- Reproduce issue in lower environment
- Inform lead and stakeholders
- Add regression test case
24. Real-Time RCA Example
Issue: Discount not applied when cart value equals minimum threshold
Root Cause: Boundary condition not tested
Action: Added boundary test cases to regression suite
7. Backend & API Validation (Expected at 3 Years)
25. Why should manual testers know SQL?
SQL helps to:
- Validate backend data
- Verify transactions
- Support RCA
- Ensure data integrity
26. Sample SQL Query
SELECT order_status, total_amount
FROM orders
WHERE order_id = 3456;
27. Why is API testing important for manual testers?
API testing:
- Validates business logic without UI
- Is faster than UI testing
- Helps detect backend defects early
28. Sample API Validation (Postman)
- Method: POST
- Endpoint: /createOrder
- Validate status code and response message
8. Agile & Manual Testing (3 Years)
29. What is Agile testing?
Agile testing follows iterative development, where testing happens continuously in sprints.
30. Role of manual tester in Agile.
- Attend sprint planning
- Understand acceptance criteria
- Test user stories
- Execute regression
- Support sprint review and sign-off
31. Agile ceremonies you participated in:
- Sprint Planning
- Daily Stand-ups
- Sprint Review
- Retrospective
9. Tools Used by Manual Testers (3 Years)
| Tool | Usage |
| Jira | Defect tracking |
| TestRail | Test case management |
| Postman | API testing |
| Selenium | Automation awareness |
| SQL | Backend validation |
| JMeter | Performance awareness |
10. Domain Exposure Examples
Banking
- Login & authentication
- Fund transfer
- Account summary
Insurance
- Policy creation
- Premium calculation
- Claims processing
E-Commerce
- Product search
- Cart & checkout
- Payment gateway
11. Common Mistakes at 3 Years Experience
- Giving fresher-level answers
- No real project examples
- Weak defect explanation
- Ignoring SQL/API basics
- Focusing only on definitions
12. Quick Revision Cheat Sheet
- Manual testing fundamentals ✔
- SDLC & STLC ✔
- Test case writing ✔
- Defect life cycle ✔
- RCA basics ✔
- Agile testing ✔
- SQL & API awareness ✔
13. FAQs – Manual Testing Interview Questions 3 Years Experience
Q: Is automation mandatory at 3 years?
Not mandatory, but automation awareness is expected.
Q: Is SQL compulsory?
Basic SQL knowledge is strongly preferred.
Q: What matters most in interviews?
Real-time examples, clarity of thought, and defect understanding