1. Role Expectations for a Manual Tester with 2 Years Experience
At 2 years of experience, you are no longer treated as a fresher. Interviewers expect you to be a solid independent contributor who understands the why behind testing, not just the how.
At this level, a manual tester is expected to:
- Understand requirements and user stories clearly
- Write good-quality test cases independently
- Perform functional, regression, smoke, sanity testing
- Identify edge cases and negative scenarios
- Log high-quality bugs with RCA
- Work comfortably in Agile/Scrum teams
- Use tools like JIRA, TestRail, Postman, basic SQL
- Communicate clearly with developers and leads
You are evaluated on clarity of thought, practical examples, and confidence, 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 using automation tools, relying on human observation and analytical skills.
At my experience level, manual testing also involves test design, requirement analysis, and defect prevention, not just execution.
Q2. What are the types of testing you have performed?
Answer:
- Functional testing
- Smoke testing
- Sanity testing
- Regression testing
- Integration testing
- System testing
- Cross-browser testing
- Basic API testing
- UAT support
Q3. Explain SDLC and your role in it.
Answer:
SDLC (Software Development Life Cycle) includes:
- Requirement Analysis
- Design
- Development
- Testing
- Deployment
- Maintenance
As a tester, I start from requirement analysis, clarify doubts, write test cases during design, execute tests during testing, validate fixes during maintenance, and support production issues if required.
Q4. Explain STLC with real project 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 phases overlap. For example, while developers code one user story, I design test cases for upcoming stories.
Q5. Difference between verification and validation?
Answer:
- Verification: Checking documents, requirements, designs
- Validation: Executing test cases on the application
At 2 years, I actively participate in requirement walkthroughs to prevent defects early.
Q6. What is regression testing?
Answer:
Regression testing ensures that existing functionality is not affected after new changes or bug fixes.
I perform regression testing:
- After bug fixes
- After new feature integration
- Before release
Q7. Difference between smoke and sanity testing?
Answer:
| Smoke Testing | Sanity Testing |
| Build-level testing | Change-level testing |
| Broad coverage | Narrow & deep |
| Checks stability | Checks correctness |
Q8. What is functional testing?
Answer:
Functional testing validates the application against business requirements by checking expected outputs for given inputs.
Q9. How do you analyze requirements?
Answer:
I check for:
- Missing acceptance criteria
- Ambiguous statements
- Validation rules
- Boundary conditions
- Integration dependencies
I raise queries early to avoid rework later.
Q10. What test design techniques do you use?
Answer:
- Boundary Value Analysis
- Equivalence Partitioning
- Decision Table Testing
- Error Guessing
3. Agile & Scrum Interview Questions (2-Year Level)
Q11. What is Agile?
Answer:
Agile is an iterative development approach where software is delivered in small increments with continuous feedback.
Q12. What Agile ceremonies have you participated in?
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
- Identify testing scope
- Estimate testing effort
Q14. How do you test in Agile?
Answer:
Testing happens continuously. I test features within the sprint, perform regression before sprint closure, and support UAT if required.
4. Test Case Design – Practical Examples
Sample UI Test Case
| Field | Description |
| Test Case ID | TC_Login_01 |
| Scenario | Valid login |
| Steps | Enter valid credentials → Click Login |
| Expected Result | User navigates to dashboard |
Boundary Value Example
For password length (8–16):
- Test values: 7, 8, 16, 17
API Test Case (Postman – Manual)
- Validate status code = 200
- Verify JSON response structure
- Validate error message for invalid input
5. Bug Reporting & Defect Management
Q15. What is a defect?
Answer:
A defect is a deviation between expected and actual behavior of the application.
Q16. What makes a good bug report?
Answer:
A good bug report should be:
- Clear
- Reproducible
- Well-structured
- Business-impact oriented
Sample Bug Report
| Field | Value |
| Summary | User can access dashboard after logout |
| Steps | Login → Logout → Click Back |
| Expected | Login page |
| Actual | Dashboard visible |
| Severity | High |
| Priority | High |
Q17. Difference between severity and priority?
Answer:
- Severity: Impact on application
- Priority: Urgency of fix
6. Scenario-Based Questions + RCA
Scenario 1: Session Not Expiring After Logout
Root Cause: Session token not invalidated server-side
Fix: Destroy session during logout API
Scenario 2: Duplicate Orders in E-commerce App
Root Cause: Missing double-submit validation
Fix: Disable submit button and validate request ID
Scenario 3: Application Crashes on Special Characters
Root Cause: Missing input validation
Fix: Sanitize inputs at UI and backend
7. Security Basics (Expected at 2 Years)
Q18. What is SQL Injection?
Answer:
An attack where malicious SQL queries manipulate backend database.
Example:
‘ OR ‘1’=’1
Q19. What is XSS?
Answer:
Cross-Site Scripting allows execution of malicious JavaScript.
Example:
<script>alert(‘XSS’)</script>
Q20. What is CSRF?
Answer:
An attack where authenticated users are forced to perform unwanted actions.
8. Tools Knowledge (Hands-On Level)
JIRA
- Bug creation
- Status workflow
- Comments and attachments
TestRail
- Writing test cases
- Test execution
- Tracking results
Postman
- API request execution
- Status code validation
- Response verification
SQL (Basic Queries)
SELECT * FROM orders WHERE status=’FAILED’;
Selenium (Awareness)
- Understand purpose of automation
- Identify regression candidates
JMeter (Basic Awareness)
- Understand performance metrics like response time and throughput
9. Domain Exposure (If Applicable)
Banking
- Login, transactions, validations
- Authorization and security
Insurance
- Policy lifecycle
- Claims processing
E-commerce
- Cart, checkout, payment
10. HR & Managerial Questions
Q21. How do you handle conflicts with developers?
Answer:
I focus on reproducible steps, logs, and business impact, not opinions.
Q22. How do you handle tight deadlines?
Answer:
By prioritizing critical flows, communicating risks early, and focusing on high-impact scenarios.
Q23. What are your strengths?
Answer:
Strong testing fundamentals, attention to detail, and ability to find real user-impact defects.
11. Common Mistakes at 2 Years Experience
- Giving fresher-level answers
- Not explaining real-time examples
- Weak bug RCA explanation
- Poor Agile understanding
- Ignoring API and security basics
12. Quick Revision Cheat Sheet
- SDLC & STLC flow
- Agile ceremonies
- Test design techniques
- Bug lifecycle
- Severity vs Priority
- Basic SQL & API testing
- Common production issues
13. FAQs + CTA
FAQ 1: Is automation required at 2 years?
Not mandatory, but awareness is expected.
FAQ 2: Should I know API testing?
Yes, basic API testing is expected.