1. Role Expectations at 2 Years Experience (Manual Testing)
With 2 years of experience in manual testing, you are considered a solid QA engineer, not a fresher. Interviewers expect you to work independently on features, understand business workflows, and contribute meaningfully to product quality.
What interviewers typically expect at this level
- Strong understanding of manual testing fundamentals
- Ability to analyze requirements and identify test scenarios
- Writing clear and reusable test cases
- Performing functional, regression, smoke, and sanity testing
- Logging high-quality defects with clear reproduction steps
- Basic understanding of STLC, SDLC, and Agile
- Exposure to API testing, SQL queries, and cross-browser testing
- Ability to explain real project defects and RCA
At 2 years, interviews focus on practical knowledge and real examples, not theoretical definitions.
2. Core Manual Testing Interview Questions & Structured Answers
Q1. What is manual testing?
Answer:
Manual testing is the process of verifying software functionality by manually executing test cases without using automation tools to ensure the application meets business requirements and user expectations.
Q2. What types of testing have you performed?
Answer:
- Functional testing
- Smoke testing
- Sanity testing
- Regression testing
- Integration testing
- System testing
- Cross-browser testing
- User Acceptance Testing (UAT) support
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:
- Understand and review requirements
- Design test cases
- Execute test cases
- Log defects
- Perform smoke testing after deployment
Q4. Explain STLC with an example.
Answer:
STLC (Software Testing Life Cycle) includes:
- Requirement analysis
- Test planning
- Test case design
- Test environment setup
- Test execution
- Test closure
In Agile projects, these activities run continuously within sprints.
Q5. Difference between verification and validation?
Answer:
- Verification: Checking documents like requirements and designs
- Validation: Executing test cases on the application
Verification ensures correctness early; validation ensures functionality works.
Q6. What is functional testing?
Answer:
Functional testing verifies application behavior against business requirements by validating inputs, outputs, and business rules.
Q7. What is regression testing and when do you perform it?
Answer:
Regression testing ensures existing functionality works after code changes or bug fixes. It is performed:
- Before releases
- After major bug fixes
- After new feature integration
Q8. 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 fixes |
Q9. What test design techniques do you use?
Answer:
- Boundary Value Analysis
- Equivalence Partitioning
- Error Guessing
Q10. How do you analyze requirements?
Answer:
I analyze requirements to identify:
- Missing scenarios
- Validation rules
- Boundary conditions
- Negative scenarios
- Integration points
3. Agile & Scrum Interview Questions (2-Year Level)
Q11. What is Agile testing?
Answer:
Agile testing is continuous testing where QA works closely with developers throughout the sprint for faster feedback and better quality.
Q12. Which Agile ceremonies have you attended?
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
Q14. How do you handle changing requirements?
Answer:
I update test cases, communicate changes to stakeholders, and revalidate impacted areas.
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 on server side
- Browser caching enabled
Fix:
- Invalidate session during logout
- Disable cache for secured pages
Scenario 2: Duplicate Records Created
Issue: User clicks submit button twice
RCA:
- No double-submit prevention
- Backend missing validation
Fix:
- Disable submit button after click
- Add backend validation
Scenario 3: Application Accepts Special Characters
RCA:
- Missing input validation
Fix:
- Sanitize input at UI and backend
Scenario 4: API Returns Success for Invalid Data
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 | Error message |
| Priority | High |
API Test Case Example (Postman)
- Send invalid payload
- Validate status code = 400
- Validate error message
Database Validation Example
SELECT status
FROM orders
WHERE order_id = 123;
Performance Sanity Check
- Page load time < 3 seconds
- No timeout
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 works with invalid password |
| Severity | High |
| Priority | High |
| RCA | Missing validation |
7. Tools Knowledge (Expected at 2 Years)
JIRA
- Bug creation and tracking
TestRail
- Test case management
Postman
- Basic API testing
Selenium (Awareness)
- Understand automation purpose
SQL (Basic)
SELECT * FROM users WHERE status=’ACTIVE’;
JMeter (Awareness)
- Response time concepts
8. Domain Exposure (If Applicable)
Banking
- Login, transactions
Insurance
- Policy lifecycle
ETL
- Source-to-target validation
E-commerce
- Cart and checkout
9. Common Mistakes Candidates Make at 2 Years Experience
- Giving fresher-level answers
- No real defect examples
- Weak RCA explanations
- Ignoring Agile concepts
- Avoiding API or SQL topics
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 at 2 years?
Automation awareness is expected but not mandatory for manual roles.
FAQ 2: Should I know API testing?
Yes. Basic API testing knowledge is expected.