1. Role Expectations for a Manual Tester with 3 Years Experience
At 3 years of experience, interviewers no longer evaluate you as a fresher or junior tester. You are expected to function as an independent QA contributor who can:
- Understand requirements without hand-holding
- Design effective test scenarios and test cases
- Identify functional, UI, integration, and security issues
- Perform root cause analysis (RCA) for defects
- Communicate clearly with developers, managers, and business teams
- Work confidently in Agile/Scrum environments
- Handle production issues and hotfix testing
- Use tools like JIRA, TestRail, Postman, SQL with confidence
At this level, answers must include real-time examples, not textbook definitions.
2. Core Manual Testing Interview Questions & Structured Answers
Q1. What is manual testing?
Answer:
Manual testing is the process of validating software functionality, usability, and reliability without automation tools, using human observation and reasoning. At my experience level, manual testing is not just execution—it involves test design, risk analysis, and defect prevention.
Q2. Explain SDLC and your role in it.
Answer:
SDLC (Software Development Life Cycle) defines phases like:
- Requirement Analysis
- Design
- Development
- Testing
- Deployment
- Maintenance
As a tester, I get involved from the requirement phase, perform requirement analysis, create test cases during design, execute tests during testing, support UAT, and validate fixes during maintenance.
Q3. 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 real projects, STLC overlaps with SDLC. For example, while developers code one module, I design test cases for the next sprint.
Q4. Difference between verification and validation?
Answer:
- Verification: Are we building the product right? (reviews, walkthroughs)
- Validation: Are we building the right product? (testing execution)
At 3 years experience, I actively participate in requirement walkthroughs to prevent defects early.
Q5. What types of testing have you performed?
Answer:
- Functional testing
- Regression testing
- Smoke and sanity testing
- Integration testing
- System testing
- UAT support
- Basic API testing
- Cross-browser testing
Q6. What is regression testing and when do you perform it?
Answer:
Regression testing ensures existing functionality is not broken after new changes. I perform it:
- After defect fixes
- After new feature integration
- Before major releases
I prioritize regression cases based on business impact and defect history.
Q7. Explain smoke vs sanity testing.
Answer:
- Smoke: Build-level check to verify stability
- Sanity: Focused testing on modified areas
Smoke is broad, sanity is deep and narrow.
Q8. How do you analyze requirements?
Answer:
I check for:
- Ambiguity
- Missing acceptance criteria
- Edge cases
- Validation rules
- Integration points
I raise questions early to avoid rework later.
3. Agile & Scrum Interview Questions (3-Year Level)
Q9. What is Agile testing?
Answer:
Agile testing is continuous testing aligned with development. Testing happens from day one, not as a separate phase.
Q10. What ceremonies do you participate in?
Answer:
- Sprint planning
- Daily stand-ups
- Backlog grooming
- Sprint review
- Retrospective
Q11. Your role in sprint planning?
Answer:
- Understand user stories
- Identify test scope
- Estimate testing effort
- Raise dependency and risk points
Q12. How do you write test cases in Agile?
Answer:
I write lightweight but effective test cases, often mapping directly to acceptance criteria.
4. Test Case Design – Real Examples
Sample UI Test Case
| Field | Description |
| Test Case ID | TC_Login_001 |
| Scenario | Valid login |
| Steps | Enter valid username/password → Click Login |
| Expected Result | User navigates to dashboard |
Boundary Value Example
For age field (18–60):
- Test values: 17, 18, 60, 61
API Test Case (Manual – Postman)
- Verify status code = 200
- Validate response JSON structure
- Validate error handling for invalid input
5. Bug Reporting & Defect Management
Q13. What makes a good bug report?
Answer:
A good bug report is clear, reproducible, and actionable.
Sample Bug Report
| Field | Value |
| Summary | Login allows access after logout |
| Steps | Login → Logout → Click Back |
| Expected | Login page |
| Actual | Dashboard shown |
| Severity | High |
| Priority | High |
Q14. Difference between severity and priority?
Answer:
- Severity: Impact on application
- Priority: Urgency of fix
6. Scenario-Based Questions + RCA
Scenario 1: Session Active After Logout
RCA: Session token not invalidated on server
Fix: Destroy session during logout API
Scenario 2: Duplicate Transactions in Banking App
RCA: Missing idempotency check
Fix: Add transaction reference validation
Scenario 3: UI Freeze on Submit
RCA: No loader and API timeout handling
Fix: Add spinner and timeout mechanism
7. Security Basics (Expected at 3 Years)
Q15. What is SQL Injection?
Answer:
An attack where malicious SQL queries manipulate the database.
Example:
‘ OR ‘1’=’1
Q16. What is XSS?
Answer:
Injection of malicious JavaScript into UI fields.
Example:
<script>alert(‘XSS’)</script>
Q17. What is CSRF?
Answer:
Forcing authenticated users to perform unwanted actions.
8. Tools Knowledge (Must-Have)
JIRA
- Bug tracking
- Workflow understanding
- Defect lifecycle
TestRail
- Test case management
- Execution tracking
- Reports
Postman
- Manual API testing
- Status code validation
- JSON verification
SQL (Basic)
SELECT * FROM users WHERE status=’ACTIVE’;
Selenium (Awareness)
- Understand automation scope
- Identify automation candidates
JMeter (Basic)
- Understand performance metrics
- Validate response time
9. Domain Exposure (Interview Advantage)
Banking
- Transactions
- Authorization
- Data integrity
Insurance
- Policy lifecycle
- Claims processing
E-commerce
- Cart, payment, refunds
10. HR & Managerial Questions
Q18. How do you handle conflicts with developers?
Answer:
I focus on facts, logs, and business impact, not personal opinions.
Q19. How do you handle tight deadlines?
Answer:
By prioritizing critical flows and communicating risks early.
Q20. Why should we hire you?
Answer:
I bring hands-on experience, strong testing fundamentals, and the ability to find real production-impact defects.
11. Common Mistakes at 3 Years Experience
- Giving fresher-level answers
- No real project examples
- Weak defect RCA explanations
- Not understanding Agile deeply
- Avoiding security and API questions
12. Quick Revision Cheat Sheet
- STLC & SDLC flow
- Agile ceremonies
- Test case design techniques
- Defect lifecycle
- Severity vs Priority
- Basic SQL & API testing
- Common production issues
13. FAQs + CTA
FAQ 1: Is automation mandatory at 3 years?
No, but awareness is expected.
FAQ 2: Should I know API testing?
Yes, basic API validation is mandatory.