Quality Assurance (QA) Engineer

Role Purpose

We are looking for a mid-level Quality Assurance (QA) Engineer to strengthen system quality, stability, and release confidence through structured testing and clear quality signals across the software development lifecycle. This role focuses on preventing regressions and surfacing risks early, rather than acting as a final safety net after development. The QA Engineer works closely with Product and Engineering teams to ensure changes are well-understood, well-tested, and release-ready. The QA Engineer is expected to raise quality and release-readiness risks early and clearly. While final release decisions are made by Product and Engineering leadership, QA input is considered a critical signal and should not be bypassed without explicit acknowledgment.

Key Responsibilities

1. Test Planning & Execution

● Design, maintain, and execute test cases based on requirements, user stories, and acceptance criteria.

● Perform functional, regression, and smoke testing across assigned systems and modules.

● Validate fixes and enhancements before UAT and production release.

● Ensure test coverage aligns with risk, impact, and change scope.

2. Defect Identification & Management

● Log defects clearly with reproducible steps, expected vs actual results, and supporting evidence.

● Classify defects by severity and priority using defined guidelines.

● Track defects through resolution and re-testing until closure.

● Identify recurring defects or patterns and flag systemic quality risks.

3. Quality Gates & Release Readiness

● Participate in pre-UAT and pre-release quality checks.

● Validate that required testing, documentation, and sign-offs are completed before release.

● Raise quality risks early and clearly when release readiness is compromised.

● Support go-live and post-release validation activities where required.

4. Collaboration with Product & Engineering

● Work closely with Product, BA, and Engineering teams to clarify requirements and acceptance criteria.

● Participate early in requirement and story discussions to identify testability gaps, assumptions, and risk areas.

● Provide early feedback on edge cases and high-impact scenarios.

● Support triage discussions by providing quality and impact perspectives (not solutioning).

5. Test Artefacts & Documentation

● Maintain test cases, test plans, and execution records in designated tools.

● Contribute to QA documentation, testing standards, and reusable test assets.

● Ensure testing activities are traceable to requirements and releases.

6. Continuous Improvement

● Identify gaps in test coverage, processes, or tooling.

● Propose pragmatic improvements to testing efficiency and reliability.

● Support gradual adoption of test automation where it adds clear value; strong test thinking and coverage design are prioritised over tooling expertise.

What This Role Is Not

This role focuses on practical testing, early risk detection, and release readiness.

● This is not a test automation-only role.

● This is not a final “gatekeeper after development” role.

● This is not a process policing position.

● This is not a senior QA strategy role.

Required Experience & Skills

Core

● 2–4 years experience in software QA, testing, or quality assurance roles.

● Strong understanding of SDLC and release processes.

● Ability to write clear, structured test cases and defect reports.

● Familiarity with issue tracking and test management tools.

● Detail-oriented, methodical, and risk-aware mindset.

● Strong written communication skills in English.

Preferred / Advantage

● Experience testing enterprise, SaaS, or workflow-driven systems.

● Exposure to medical, clinical, CRM, or regulated systems (advantage, not required).

● Experience supporting UAT coordination or release validation.

● Basic understanding of APIs, databases, or system integrations.

● Exposure to test automation tools or frameworks.

Reporting & Collaboration

● Reports to: Engineering Leadership

● Works closely with: Product, BA, Engineering, and Aftersales Support teams

● Receives: Clear priorities and release timelines