1. Role Expectations at 3 Years Experience (Manual Testing)
With 3 years of experience in manual testing, interviewers no longer see you as a junior tester. You are expected to function as a solid, independent QA Engineer who understands both business logic and technical flows.
What interviewers expect at this level
- Strong command over manual testing fundamentals
- Ability to analyze requirements independently
- Design test scenarios and detailed test cases
- Identify edge cases, negative scenarios, and integration risks
- Perform functional, regression, smoke, sanity, and UAT testing
- Write high-quality bug reports with proper RCA
- Actively participate in Agile ceremonies
- Basic exposure to API testing, SQL, and performance checks
- Confidence in explaining real-time project defects
At 3 years, interviewers test how you think, not just what definitions you remember.
2. Core Interview Questions & Structured Answers (Manual Testing)
Q1. What is manual testing?
Answer:
Manual testing is the process of verifying software functionality by executing test cases manually without using automation tools, focusing on user behavior, business logic, and usability.
At 3 years experience, manual testing means:
- Validating business flows end-to-end
- Identifying usability and real-user issues
- Acting as the last quality gate before release
Q2. What types of testing have you performed?
Answer:
- Functional testing
- Smoke testing
- Sanity testing
- Regression testing
- Integration testing
- System testing
- UAT support
- Cross-browser testing
- Basic API testing
- Production sanity testing
Q3. Explain SDLC and your role in each phase.
Answer:
SDLC (Software Development Life Cycle):
- Requirement Analysis
- Design
- Development
- Testing
- Deployment
- Maintenance
My role as a tester:
- Requirement phase: Understand requirements, raise clarifications
- Design/Development: Prepare test scenarios and test cases
- Testing: Execute test cases, log defects
- Deployment: Perform smoke testing
- Maintenance: Support production issues and regression testing
Q4. Explain STLC with a real project example.
Answer:
STLC (Software Testing Life Cycle) includes:
- Requirement Analysis – Review BRD/user stories
- Test Planning – Decide test scope and approach
- Test Case Design – Write scenarios and test cases
- Test Environment Setup – Prepare data and access
- Test Execution – Execute tests and log bugs
- Test Closure – Prepare test summary report
In Agile projects, STLC activities run in parallel with sprints.
Q5. Difference between verification and validation?
Answer:
- Verification: Reviewing requirement and design documents
- Validation: Executing test cases on the application
Verification answers “Are we building the product right?”
Validation answers “Are we building the right product?”
Q6. What is regression testing? When do you perform it?
Answer:
Regression testing ensures that existing functionality is not broken after changes or bug fixes.
I perform regression testing:
- Before every release
- After major bug fixes
- After new feature integration
Q7. Difference between smoke and sanity testing?
Answer:
| Smoke Testing | Sanity Testing |
| Broad testing | Narrow testing |
| Build stability | Change verification |
| Done on new build | Done after bug fixes |
Q8. What is functional testing?
Answer:
Functional testing validates application behavior against business requirements by checking expected output for given inputs.
Q9. What test design techniques do you use?
Answer:
- Boundary Value Analysis
- Equivalence Partitioning
- Decision Table Testing
- Error Guessing
Q10. How do you analyze requirements?
Answer:
I look for:
- Missing requirements
- Ambiguous acceptance criteria
- Validation rules
- Boundary conditions
- Negative and edge scenarios
- Integration dependencies
3. Agile & Scrum Interview Questions (3-Year Level)
Q11. What is Agile testing?
Answer:
Agile testing is continuous testing where QA is involved from requirement discussion to release, ensuring faster feedback and better quality.
Q12. Which Agile ceremonies do you attend?
Answer:
- Sprint planning
- Daily stand-up
- Sprint review
- Retrospective
- Backlog grooming
Q13. What is your role in sprint planning?
Answer:
- Understand user stories
- Clarify acceptance criteria
- Estimate testing effort
- Identify risks and dependencies
Q14. How do you handle frequently changing requirements?
Answer:
I document changes, update test cases, communicate impact to stakeholders, and adjust regression scope accordingly.
4. Scenario-Based Interview Questions + RCA
Scenario 1: User Can Access Application After Logout
Issue: User clicks browser back button after logout
Root Cause Analysis (RCA):
- Session not invalidated at server side
- Browser cache enabled
Fix:
- Invalidate session on logout
- Disable cache for secured pages
Scenario 2: Duplicate Order Created in Production
Issue: User clicks submit button multiple times
RCA:
- No double-submit validation
- Backend missing idempotency check
Fix:
- Disable submit button after first click
- Add backend validation
Scenario 3: Application Crashes for Special Characters
RCA:
- Missing input validation
Fix:
- Sanitize inputs at UI and backend
Scenario 4: API Returns Success for Invalid Input
RCA:
- Missing backend validation
Fix:
- Enforce proper validation and HTTP status codes
5. Test Case Examples (Manual Tester Focus)
UI Test Case Example
| Field | Details |
| Test Case ID | TC_LOGIN_01 |
| Scenario | Invalid login |
| Steps | Enter wrong username/password |
| Expected Result | Error message |
| Priority | High |
API Test Case Example (Postman)
- Send invalid request payload
- Validate response status = 400
- Validate error message
Database Validation Example
SELECT status
FROM orders
WHERE order_id = 1234;
Performance Sanity Check
- Page load time < 3 seconds
- No timeout under normal load
6. Bug Reporting & Defect Management
What makes a good bug report?
- Clear and concise summary
- Exact steps to reproduce
- Expected vs actual result
- Screenshots/logs
- Proper severity and priority
Sample Bug Report
| Field | Value |
| Summary | Login works with invalid password |
| Steps | Enter invalid credentials |
| Expected | Login should fail |
| Actual | Login successful |
| Severity | High |
| Priority | High |
At 3 years, interviewers expect clear RCA, not just bug description.
7. Tools Knowledge (Expected at 3 Years)
JIRA
- Bug logging and tracking
- Workflow understanding
TestRail
- Test case creation
- Execution tracking
Postman
- API testing
- Status code validation
Selenium (Awareness)
- Understand purpose of automation
- Identify automation candidates
SQL (Basic to Intermediate)
SELECT * FROM users WHERE status=’ACTIVE’;
JMeter (Awareness)
- Response time
- Throughput concepts
8. Domain Exposure (If Applicable)
Banking
- Login, transactions, authorization
Insurance
- Policy creation, claims
ETL / Data
- Source-to-target data validation
E-commerce
- Cart, checkout, payments
9. Common Mistakes Candidates Make at 3 Years Experience
- Giving fresher-level answers
- No real project examples
- Weak RCA explanations
- Ignoring Agile practices
- Avoiding API and SQL questions
10. Quick Revision Cheat Sheet
- SDLC vs STLC
- Smoke vs sanity vs regression
- Test design techniques
- Bug lifecycle
- Severity vs priority
- Common production defects
11. FAQs + CTA
FAQ 1: Is automation mandatory at 3 years?
Automation awareness is expected, but scripting is not mandatory for pure manual roles.
FAQ 2: Should I know API testing?
Yes. Basic API testing knowledge using Postman is expected.