1. Role Expectations at 3 Years Experience (Manual Testing)
With 3 years of experience in manual testing, you are expected to work as an independent QA Engineer who can take ownership of features or modules. Interviewers look for strong fundamentals, real project exposure, and analytical thinking, not just theoretical knowledge.
What interviewers expect at this experience level
- Clear understanding of manual testing concepts
- Ability to analyze requirements and identify test scenarios
- Writing effective, reusable test cases
- Executing functional, regression, integration, and system testing
- Logging high-quality defects with severity, priority, and RCA
- Good understanding of STLC, SDLC, and Agile
- Exposure to API testing, SQL validation, and cross-browser testing
- Participation in UAT and production support
- Clear communication with developers and stakeholders
At 3 years, interviews focus heavily on real-time scenarios, defect reasoning, and decision-making skills.
2. Core Manual Testing Interview Questions & Structured Answers
Q1. What is manual testing?
Answer:
Manual testing is the process of validating application functionality without automation tools to ensure it meets business requirements and user expectations.
At 3 years, manual testing also involves thinking like an end user, identifying edge cases, and preventing defects early.
Q2. What types of testing have you performed?
Answer:
- Functional testing
- Smoke testing
- Sanity testing
- Regression testing
- Integration testing
- System testing
- Cross-browser testing
- UAT support
- Basic API testing
- Database validation
Q3. Explain SDLC and your role in it.
Answer:
SDLC (Software Development Life Cycle) phases:
- Requirement Analysis
- Design
- Development
- Testing
- Deployment
- Maintenance
My role as a tester:
- Review requirements for clarity and testability
- Identify test scenarios and risks
- Design and execute test cases
- Log and track defects
- Perform smoke testing after deployment
- Support UAT and production issues
Q4. Explain STLC with real-time relevance.
Answer:
STLC (Software Testing Life Cycle) includes:
- Requirement Analysis
- Test Planning
- Test Case Design
- Test Environment Setup
- Test Execution
- Test Closure
In Agile projects, STLC activities are iterative and continuous, aligned with sprint cycles.
Q5. Difference between verification and validation?
Answer:
- Verification: Reviewing requirement and design documents
- Validation: Executing test cases on the application
Verification ensures the product is built correctly; validation ensures the correct product is built.
Q6. What is functional testing?
Answer:
Functional testing validates application behavior against business requirements by checking inputs, outputs, and business rules.
Q7. What is regression testing and when do you perform it?
Answer:
Regression testing ensures that existing functionality is not broken after:
- Bug fixes
- New feature additions
- Configuration changes
It is typically performed before every release.
Q8. Difference between smoke testing and sanity testing?
Answer:
| Smoke Testing | Sanity Testing |
| Broad testing | Narrow testing |
| Build stability check | Change verification |
| Performed on new build | After bug fixes |
Q9. What test design techniques do you use?
Answer:
- Boundary Value Analysis – testing boundary limits
- Equivalence Partitioning – grouping input values
- Error Guessing – based on experience
Q10. How do you prioritize test cases?
Answer:
Test cases are prioritized based on:
- Business criticality
- User impact
- Risk and complexity
- Frequency of usage
3. Agile & Scrum Interview Questions (3 Years Level)
Q11. What is Agile testing?
Answer:
Agile testing is continuous testing where QA collaborates with developers and product owners throughout the sprint to ensure early defect detection.
Q12. Which Agile ceremonies have you participated in?
Answer:
- Sprint planning
- Daily stand-ups
- Sprint review
- Retrospective
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 analyze the impact, update test cases, communicate changes, and ensure impacted areas are retested.
4. Scenario-Based Interview Questions + RCA
Scenario 1: User Can Access Application After Logout
Issue: User presses browser back button after logout
RCA:
- Session not invalidated at server level
- Browser cache enabled
Fix:
- Invalidate session on logout
- Disable cache for secure pages
Scenario 2: Duplicate Records Created
Issue: User clicks submit button multiple times
RCA:
- No double-submit prevention
- Missing backend validation
Fix:
- Disable submit button after click
- Add backend duplicate check
Scenario 3: Application Accepts Invalid Characters
RCA:
- Missing input validation
Fix:
- Validate input at UI and backend
Scenario 4: API Returns 200 for Invalid Input
RCA:
- Missing backend validation
Fix:
- Return proper HTTP status codes
5. Test Case Examples (UI, API, DB, Performance)
UI Test Case Example
| Field | Value |
| Test Case ID | TC_LOGIN_01 |
| Scenario | Invalid login |
| Steps | Enter wrong credentials |
| Expected Result | Error message |
| Priority | High |
API Test Case Example (Manual)
- Send invalid payload
- Validate status code = 400
- Validate error message
Database Validation Example
SELECT status
FROM orders
WHERE order_id = 1005;
Performance Sanity Validation
- Page load time < 3 seconds
- No timeout under normal load
6. Bug Reports & Defect Management
What makes a good bug report?
- Clear summary
- Steps to reproduce
- Expected vs actual result
- Screenshots/logs
- Proper severity and priority
Sample Bug Report
| Field | Value |
| Summary | Login successful with invalid password |
| Severity | High |
| Priority | High |
| RCA | Missing password validation |
7. Tools Knowledge (Expected at 3 Years)
JIRA
- Defect creation and tracking
- Sprint board usage
TestRail
- Test case management
- Traceability
Postman
- Manual API testing
- Negative scenarios
Selenium (Awareness)
- Understanding automation purpose
- Identifying automation candidates
SQL (Basic to Intermediate)
SELECT COUNT(*) FROM users WHERE status=’ACTIVE’;
JMeter (Awareness)
- Response time and load basics
8. Domain Exposure (If Applicable)
Banking
- Login, transactions, security
Insurance
- Policy lifecycle
ETL / Data
- Source-to-target validation
E-commerce
- Cart, checkout, payments
9. Common Mistakes Candidates Make at 3 Years Experience
- Giving fresher-level answers
- Not explaining real project defects
- Weak RCA explanations
- Avoiding API or SQL topics
- Ignoring Agile practices
10. Quick Revision Cheat Sheet
- SDLC vs STLC
- Smoke vs sanity vs regression
- Test design techniques
- Bug lifecycle
- Severity vs priority
11. FAQs + CTA
FAQ 1: Is automation mandatory for manual testers at 3 years?
Automation knowledge is recommended but not mandatory for manual roles.
FAQ 2: Should I know API testing?
Yes. Basic API testing knowledge is expected.