1. Role Expectations at 2 Years Experience (Manual Tester)
With 2 years of experience in manual testing, you are expected to function as a self-reliant QA engineer, not a beginner. Interviewers focus on practical project exposure, clarity of concepts, and defect reasoning ability.
What interviewers typically expect at this level
- Strong understanding of manual testing fundamentals
- Ability to analyze requirements independently
- Writing clear, detailed test cases
- Performing functional, regression, smoke, and sanity testing
- Logging high-quality defects with severity, priority, and evidence
- Good understanding of STLC, SDLC, and Agile
- Exposure to API testing, SQL, and cross-browser testing
- Participation in UAT and production support
- Ability to explain real defects with RCA
At 2 years, interviews are experience-driven, not definition-driven.
2. Core Manual Testing Interview Questions & Structured Answers
Q1. What is manual testing?
Answer:
Manual testing is the process of validating software functionality by executing test cases manually without automation tools to ensure it meets business requirements and user expectations.
At 2 years, manual testing also means:
- Thinking from an end-user perspective
- Identifying edge cases
- Preventing production issues
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
Tester responsibilities:
- Review and understand requirements
- Identify test scenarios
- Design and execute test cases
- Log and track defects
- Perform smoke testing after deployment
- Support UAT and production issues
Q4. Explain STLC with a real-time 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, STLC activities are iterative and continuous within sprints.
Q5. Difference between verification and validation?
Answer:
- Verification: Reviewing requirement and design documents
- Validation: Executing test cases on the application
Verification prevents defects early; validation confirms functionality.
Q6. What is functional testing?
Answer:
Functional testing verifies that application behavior aligns with business requirements by validating inputs, outputs, and business rules.
Q7. What is regression testing and why is it important?
Answer:
Regression testing ensures existing functionality works correctly after:
- Bug fixes
- New feature additions
- Configuration changes
It prevents unexpected failures in stable areas.
Q8. Difference between smoke testing and sanity testing?
Answer:
| Smoke Testing | Sanity Testing |
| Broad testing | Narrow testing |
| Build stability | Change verification |
| Done on new build | Done after bug fixes |
Q9. What test design techniques do you use?
Answer:
- Boundary Value Analysis
- Equivalence Partitioning
- Error Guessing
These techniques help identify edge cases and reduce test count.
Q10. How do you prioritize test cases?
Answer:
Based on:
- Business criticality
- User impact
- Risk and complexity
- Frequency of usage
3. Agile & Scrum Interview Questions (2 Years Level)
Q11. What is Agile testing?
Answer:
Agile testing is continuous testing aligned with development, where QA works closely with developers and product owners to provide fast feedback.
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 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 clicks browser back button after logout
RCA:
- Session not invalidated on server side
- Browser cache enabled
Fix:
- Invalidate session on logout
- Disable cache for secured 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 validation
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 correct 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 = 2001;
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 2 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
SQL (Basic)
SELECT COUNT(*) FROM users WHERE status=’ACTIVE’;
JMeter (Awareness)
- Response time concepts
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 2 Years Experience
- Giving fresher-level answers
- Not explaining real defects
- Weak RCA explanations
- Avoiding API or SQL topics
- Ignoring Agile concepts
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 scripting is not mandatory for manual roles.
FAQ 2: Should I know API testing?
Yes. Basic API testing is expected.