1. Role Expectations – Manual Tester with 3 Years Experience
At 3 years of experience in manual testing, interviewers expect you to function as a self-driven QA engineer, not a fresher.
What companies expect:
- Strong understanding of STLC and SDLC
- Ability to analyze requirements independently
- Writing effective test cases with edge cases
- Performing functional, regression, smoke, sanity testing
- Logging high-quality bug reports with RCA
- Working in Agile/Scrum teams
- Collaborating with developers, product owners, and managers
- Basic exposure to API, SQL, performance concepts
- Using tools like JIRA, TestRail, Postman
2. Core Manual Testing Interview Questions & Answers (Technical Round)
1. What is manual testing? Why is it still important?
Manual testing is the process of validating software manually without automation tools to ensure it meets business requirements. It is important because:
- Exploratory testing needs human thinking
- UI/UX validation cannot be fully automated
- Early-stage projects rely heavily on manual testing
2. Explain SDLC phases with tester involvement
| SDLC Phase | Tester Role |
| Requirement | Review & clarify requirements |
| Design | Identify test scenarios |
| Development | Prepare test cases |
| Testing | Execute test cases & log defects |
| Deployment | Sanity testing |
| Maintenance | Regression testing |
3. Explain STLC in detail
STLC defines testing activities:
- Requirement analysis
- Test planning
- Test case design
- Test environment setup
- Test execution
- Test closure
Each phase has entry and exit criteria, which is crucial at 3 years experience.
4. What types of testing have you performed?
- Functional testing
- Smoke testing
- Sanity testing
- Regression testing
- Integration testing
- System testing
- UAT support
5. Difference between smoke and sanity testing
| Smoke Testing | Sanity Testing |
| Wide coverage | Narrow & deep |
| After new build | After minor fix |
| Checks stability | Checks correctness |
6. What is a test case? What are its components?
A test case verifies a specific requirement.
Components:
- Test Case ID
- Test Scenario
- Preconditions
- Test Steps
- Test Data
- Expected Result
- Actual Result
- Status
7. How do you write effective test cases?
- Understand business flow
- Cover positive & negative scenarios
- Include boundary conditions
- Make steps reusable and clear
8. What is a defect life cycle?
| Status | Meaning |
| New | Tester logs defect |
| Assigned | Assigned to developer |
| Open | Developer working |
| Fixed | Code fixed |
| Retest | Tester verifies |
| Closed | Issue resolved |
| Reopened | Issue persists |
9. Severity vs Priority
| Severity | Priority |
| Impact on system | Urgency of fix |
| Decided by tester | Decided by product |
| Technical | Business |
10. What makes a good bug report?
- Clear summary
- Reproducible steps
- Actual vs expected result
- Environment details
- Screenshots/logs
- Proper severity & priority
3. Agile & Process Interview Questions
11. What is Agile testing?
Agile testing is continuous testing aligned with sprint development, focusing on early feedback and collaboration.
12. Explain Scrum roles
- Product Owner – defines requirements
- Scrum Master – removes blockers
- Development Team – builds product
- QA – validates quality continuously
13. What ceremonies did you attend?
- Sprint planning
- Daily stand-up
- Sprint review
- Retrospective
14. How does testing fit into a sprint?
- Day 1-2: Test case creation
- Mid-sprint: Test execution
- End: Regression & demo support
4. Scenario-Based Interview Questions with RCA
15. Login works in QA but fails in production. What do you do?
Approach:
- Check environment differences
- Validate configuration files
- Check logs
- Verify DB connectivity
- Raise RCA document
RCA Example:
Incorrect DB URL in production config.
16. A defect is rejected by developer. How do you handle it?
- Re-verify requirement
- Attach proof (screenshots/logs)
- Discuss logically, not emotionally
- Escalate if needed
17. Application is slow after release. How will you test?
- Identify slow screens
- Check DB queries
- Analyze response time
- Suggest performance testing
5. Real-Time Defect Examples
Defect Example – Banking Application
Summary: Incorrect balance shown after fund transfer
Root Cause: Cache not refreshed after DB update
Severity: High
Impact: Financial mismatch
Defect Example – E-commerce
Issue: Order placed without payment
RCA: Missing validation in payment callback API
6. Test Case Examples
UI Test Case – Login Page
| Field | Value |
| Scenario | Valid login |
| Steps | Enter valid credentials |
| Expected | User navigates to dashboard |
API Test Case – Postman
POST /login
{
“username”:”user1″,
“password”:”pass123″
}
Expected: HTTP 200, token generated
SQL Validation Example
SELECT balance FROM accounts WHERE user_id=101;
Used to validate backend data.
7. Tools Knowledge (Mandatory for 3 Years)
JIRA
- Create defects
- Track status
- Link defects to stories
TestRail
- Test case management
- Test execution reports
Postman
- API testing
- Validate responses
- Status codes
Selenium (Basic Awareness)
- Understand automation scope
- Coordinate with automation team
JMeter (Conceptual)
- Performance testing basics
- Load vs stress testing
8. Domain Exposure Questions
Banking Domain
- Account management
- Transactions
- Security
Insurance Domain
- Policy lifecycle
- Claims processing
ETL Testing
- Source to target validation
- Data completeness & accuracy
9. HR & Managerial Questions
Why should we hire you as a manual tester?
I bring hands-on testing experience, strong defect analysis skills, Agile exposure, and the ability to improve product quality proactively.
How do you handle tight deadlines?
- Prioritize critical flows
- Communicate risks early
- Focus on high-impact testing
How do you handle conflict with developers?
By discussing facts, logs, and requirements rather than opinions.
10. Common Mistakes at 3 Years Experience
- Giving theoretical answers only
- Not explaining real projects
- Weak RCA explanations
- Poor bug documentation
- Ignoring Agile processes
11. Quick Revision Cheat Sheet
- STLC phases ✔
- Severity vs Priority ✔
- Agile ceremonies ✔
- Bug lifecycle ✔
- Real defect examples ✔
- SQL basics ✔
- API concepts ✔
12. FAQs
Is manual testing still relevant?
Yes. Manual testing is critical for exploratory, usability, and business validation.
Should I learn automation after 3 years?
Yes. Manual + automation makes you future-ready.
