As a QA Engineer, you'll demonstrate your ability to analyze requirements, design test scenarios, identify defects, document findings, perform API testing, and automate critical user journeys.
We expect a team member who is detail-oriented, quality-focused, analytical, and capable of ensuring reliable software delivery through effective testing practices.
This assessment evaluates your practical testing skills, documentation standards, defect reporting ability, automation knowledge, communication skills, and overall QA mindset.
Submission Deadline: Tuesday, June 2, 2026, 10:00 PM
OrangeHRM Demo Application
https://opensource-demo.orangehrmlive.com/
Username: Admin
Password: admin123
Focus primarily on the following modules:
- Login
- Recruitment
- Candidates
- Vacancies
- Search & Filter Functionality
- Add Candidate
- Edit Candidate
- Delete Candidate
Candidates are encouraged to explore additional areas of the application and document any findings.
Perform complete manual testing of the application.
Cover:
- Positive Scenarios
- Negative Scenarios
- Boundary Value Testing
- Field Validation Testing
- Error Handling
Perform testing on:
- Google Chrome (Latest Version)
- Microsoft Edge (Latest Version)
Document any browser-specific issues identified.
Spend at least 1 hour performing exploratory testing on the application.
Submit:
- Areas Tested
- Findings
- Risks Identified
- Recommendations
Create a Test Scenario document containing:
- Scenario ID
- Scenario Description
Minimum: 15 Scenarios
Create detailed test cases containing:
- Test Case ID
- Test Scenario
- Preconditions
- Test Steps
- Test Data
- Expected Result
- Actual Result
- Status
Minimum: 20 Test Cases
Document all defects found.
Each defect should include:
- Defect ID
- Summary
- Description
- Steps to Reproduce
- Expected Result
- Actual Result
- Severity
- Priority
- Screenshot Evidence
Prepare a Test Summary Report containing:
- Scope of Testing
- Features Tested
- Test Execution Summary
- Defects Identified
- Risks
- Recommendations
- Overall Assessment
Use Postman to perform API Testing.
Perform testing for:
- GET Requests
- POST Requests
- PUT Requests
- DELETE Requests
Validate:
- HTTP Status Codes
- Response Body
- Response Structure
- Error Handling
- Response Time
Submit:
- Postman Collection
- API Test Report
- Screenshots of Executed Requests
Write SQL queries for the following scenarios:
- Find duplicate email records.
- Count active users.
- Retrieve the latest 10 records.
Submit:
- SQL Query Document
- Brief Explanation for Each Query
Automate the following workflows:
Login Functionality
Add Candidate Functionality
Search Candidate Functionality
Use:
- Selenium WebDriver
- Java
- TestNG
- Maven
Preferred:
- Page Object Model (POM)
- Reusable Utility Classes
- Assertions
- Proper Project Structure
Submit:
- Complete Source Code
- Execution Screenshots
- README Documentation
- Framework Structure Explanation
Provide brief answers for the following:
- Difference between Verification and Validation.
- Difference between Severity and Priority.
- Difference between Smoke Testing and Sanity Testing.
- What is Regression Testing?
- Explain the STLC Phases.
- What would you do if a developer rejects your bug?
Provide your approach for the following scenarios:
You report a bug to a developer, but the developer responds:
"I cannot reproduce this issue on my machine."
How would you proceed?
You discover a bug on the day of production release.
The bug:
- Does not cause data loss
- Does not crash the application
- Has a UI impact
Would you:
- Block the release?
- Release with a known issue?
- Escalate the issue?
Explain your decision.
You still have 20 test cases remaining to execute, but the release is scheduled in 2 hours.
How would you prioritize your testing efforts?
QA-Assessment
│
├── Manual-Testing
│ ├── Test-Scenarios
│ ├── Test-Cases
│ ├── Bug-Reports
│ └── Test-Summary-Report
│
├── API-Testing
│ ├── Postman-Collection
│ └── API-Test-Report
│
├── SQL
│ └── SQL-Queries
│
├── Automation
│ ├── Source-Code
│ ├── Screenshots
│ └── Documentation
│
└── README.md
Submit the following:
- Public GitHub Repository Link
- Test Scenario Document
- Test Case Document
- Bug Report Document
- Test Summary Report
- Postman Collection
- SQL Query Document
- Automation Framework
- Supporting Screenshots
Record a 5–10 minute screen-sharing video explaining:
- Your testing approach
- Key defects identified
- Automation framework structure
- API testing strategy
- Overall findings and recommendations
Candidates who provide a clear walkthrough demonstrating ownership of their work may receive additional consideration during evaluation.
| Area | Weightage |
|---|---|
| Manual Testing | 35% |
| Automation Testing | 25% |
| API Testing | 15% |
| SQL Testing | 5% |
| Compatibility Testing | 10% |
| QA Fundamentals | 5% |
| Communication & Decision Making | 5% |
Quality is more important than quantity.
Candidates will be evaluated based on:
- Critical Thinking
- Test Coverage
- Defect Identification
- Documentation Quality
- Automation Implementation
- Problem-Solving Approach
- Communication Skills
- Overall QA Mindset
The assessment will evaluate:
- Testing Knowledge
- Test Design Skills
- Defect Identification Ability
- Documentation Standards
- Automation Skills
- API Testing Knowledge
- SQL Fundamentals
- Communication and Reporting Skills
- Risk Assessment and Decision Making
Good Luck!