Manual QA Tester
Posted:
31 August 2026 (2 days ago)
Application Deadline:
28 November 2026
Vacancies:
1 Vacancy
Job Summary
About the Role
Were looking for a detail-oriented Manual QA Tester to join a fast-growing automotive-tech startup. Youll work closely with developers and product owners to ensure the quality of a product built on C#/.NET microservices with a React front end. This is a hands-on manual testing role youll own test planning execution and defect management across the stack.
Key Responsibilities
- Analyze requirements/user stories and design detailed test cases and test plans
- Execute functional regression integration and UI testing across web (React) and backend (.NET microservices) components
- Log track and verify defects through resolution using a bug-tracking tool (e.g. Jira Azure DevOps)
- Validate API behavior across microservices (using tools like Postman) to catch integration issues early
- Collaborate with developers and product managers in an agile environment (sprint planning standups retros)
- Perform exploratory testing to uncover edge cases specific to automotive workflows/data
- Maintain and update test documentation checklists and QA sign-off reports
- Support UAT cycles and coordinate with stakeholders on release readiness
Requirements
- 35 years of hands-on manual testing experience in a software product environment
- Strong understanding of QA methodologies SDLC and STLC
- Experience testing web applications (React or similar SPA frameworks) and API-driven/microservices architectures
- Working knowledge of API testing tools (Postman or equivalent)
- Familiarity with bug-tracking and test management tools (Jira TestRail Azure DevOps etc.)
- Ability to write clear structured test cases and bug reports
- Comfortable working in a fast-paced startup environment with evolving requirements
- Good communication skills and ownership mindset
Nice to Have
- Prior exposure to automotive fleet or IoT-related products
- Basic SQL skills for backend data validation
- Exposure /C# environments (even from a QA perspective)
- Any scripting/automation exposure (not required but a plus for future growth)