1. Role Expectations at 2 Years Experience (Manual Testing)
At 2 years of experience, interviewers see you as a solid independent manual tester, not a fresher.
What is expected from you at this level:
- Strong understanding of manual testing fundamentals
- Independent requirement analysis
- Ability to design effective test scenarios & test cases
- Confident defect reporting with business impact
- Clear understanding of STLC & SDLC
- Active participation in Agile ceremonies
- Hands-on experience with Jira, TestRail
- Basic exposure to API testing, SQL, performance awareness
- Ability to guide 1–2 junior testers informally
At 2 years, interviewers evaluate how well you understand your project, not how many definitions you memorized.
2. Core Manual Testing Interview Questions & Structured Answers
Fundamentals & Process
1. What is manual testing? Explain with real project relevance.
Manual testing is the process of validating application functionality without automation, focusing on user behavior, business rules, and usability.
In real projects, manual testing helps:
- Understand end-user workflows
- Catch UI and logic issues early
- Validate business rules that automation may miss
2. Explain SDLC and your role as a tester.
| SDLC Phase | Tester’s Involvement |
| Requirement Analysis | Identify ambiguities & test scenarios |
| Design | Review flows, identify edge cases |
| Development | Prepare test cases & test data |
| Testing | Execute tests, log defects |
| Deployment | Sanity testing |
| Maintenance | Regression & RCA |
3. What is STLC? Explain each phase.
STLC focuses on testing activities:
- Requirement Analysis – Identify testable requirements
- Test Planning – Define scope, effort, approach
- Test Case Design – Functional, negative & boundary cases
- Test Environment Setup – QA readiness
- Test Execution – Execute & log defects
- Test Closure – Reports, metrics, lessons learned
4. Difference between SDLC and STLC?
| SDLC | STLC |
| Full software lifecycle | Only testing lifecycle |
| Business + dev + QA | QA focused |
| Ends at maintenance | Ends at closure |
5. What types of testing have you performed?
- Functional Testing
- Smoke Testing
- Sanity Testing
- Regression Testing
- Integration Testing
- System Testing
- UAT support
3. Manual Testing Concepts (2 Years Level)
6. What is Smoke Testing?
Smoke testing checks critical functionalities to confirm build stability.
Example:
- Application launch
- Login
- Core navigation
7. What is Sanity Testing?
Sanity testing validates specific fixes or enhancements after a new build.
8. What is Regression Testing?
Regression testing ensures new changes do not impact existing features.
9. Difference between Smoke and Sanity?
| Smoke | Sanity |
| Broad coverage | Narrow coverage |
| Build validation | Change validation |
| Before regression | After fix |
10. What is Integration Testing?
Integration testing validates data flow and interaction between modules.
Example:
- Order placement → Payment → Inventory update
4. Test Case Design Interview Questions
11. What is a test case?
A test case is a document that defines:
- Preconditions
- Steps
- Test data
- Expected result
12. Sample Manual Test Case – Login
| Field | Value |
| Test Scenario | Invalid login |
| Steps | Enter valid username + wrong password |
| Expected | Error message displayed |
13. What is a test scenario?
A test scenario is a high-level idea of what to test.
Example:
Verify user login functionality
14. Difference between test scenario and test case?
- Scenario → What to test
- Test case → How to test
15. Explain Boundary Value Analysis with example.
If allowed amount is 100–10,000:
- Valid: 100, 101, 9,999, 10,000
- Invalid: 99, 10,001
16. What is Equivalence Partitioning?
Dividing input values into valid and invalid groups to reduce test cases.
5. Defect Management & Bug Reporting
17. What is a defect?
A defect is any deviation between expected and actual application behavior.
18. Explain Bug Life Cycle.
- New
- Assigned
- Open
- Fixed
- Retest
- Closed / Reopened
19. Severity vs Priority
| Severity | Priority |
| Impact on system | Urgency to fix |
| Decided by QA | Decided by business |
20. Sample Real-Time Bug Report
Title: Amount debited but order not created
Environment: QA
Steps:
1. Place an order
2. Complete payment
3. Check order history
Expected: Order created
Actual: No order shown
Severity: Critical
Priority: High
21. What makes a good bug report?
- Clear title
- Reproducible steps
- Expected vs actual result
- Screenshots/logs
- Correct severity & priority
6. Agile Manual Testing Interview Questions
22. What is Agile methodology?
Agile is an iterative approach that delivers software in small increments with continuous feedback.
23. What is a Sprint?
A sprint is a fixed time-boxed iteration (usually 2 weeks).
24. Agile ceremonies you participated in:
- Sprint Planning
- Daily Stand-ups
- Sprint Review
- Retrospective
25. Role of a manual tester in Agile.
- Understand user stories
- Clarify acceptance criteria
- Write test cases early
- Perform continuous testing
7. Scenario-Based Questions + RCA
26. A defect you logged is rejected. What will you do?
- Re-check requirement
- Reproduce issue
- Provide evidence
- Discuss professionally with developer
27. A production defect occurred. What is your role?
- Understand issue
- Reproduce in lower environment
- Identify missed scenario
- Perform RCA
- Add preventive test cases
28. Explain RCA with example.
Issue: Duplicate orders created
Root Cause: Retry button scenario not tested
Action Taken: Added retry & network failure test cases
29. How do you handle tight deadlines?
- Risk-based prioritization
- Focus on critical flows
- Smoke + targeted regression
- Communicate risks clearly
8. Test Case Examples (Hands-On)
UI Test Case – Registration
Scenario: Mandatory field validation
Steps:
1. Leave email blank
2. Click Submit
Expected: Error message shown
API Awareness Test Case (Manual – Postman)
- Method: POST
- Endpoint: /api/login
- Validate:
- Status code
- Error message
- Status code
Database Validation (SQL)
SELECT status
FROM orders
WHERE order_id = 12345;
Expected result: SUCCESS
Performance Awareness Scenario
- Multiple users login simultaneously
- Application should respond within acceptable time
9. Tools Knowledge (2 Years – Manual Testing)
| Tool | Usage |
| Jira | Bug & story tracking |
| TestRail | Test case management |
| Postman | API testing basics |
| Selenium | Awareness only |
| SQL | Data validation |
| JMeter | Basic performance concepts |
10. Domain Exposure Examples
Banking
- Login
- Fund transfer
- Account statement
Insurance
- Policy creation
- Premium calculation
E-Commerce
- Cart
- Checkout
- Payment gateway
11. Common Mistakes at 2 Years Experience
- Giving fresher-level answers
- Not knowing end-to-end project flow
- Poor defect explanation
- Weak RCA understanding
- No API or SQL basics
12. Quick Revision Cheat Sheet
- SDLC & STLC ✔
- Smoke vs Sanity ✔
- Regression testing ✔
- Test case format ✔
- Bug life cycle ✔
- Severity vs Priority ✔
- Agile basics ✔
13. FAQs – 2 Years Experience Interview Questions Manual Testing
Q: Is automation required at 2 years?
No, but awareness is expected.
Q: Is SQL mandatory?
Basic queries are usually expected.
Q: What matters most at this level?
Project understanding, clear thinking, and defect handling.