QA Engineer

Entry Level QA Engineer

Caava Group · Group Technology · Evolve Platform

Reports To

QA Lead

Works With

Software Engineers, QA Engineers and Product

Scope

Manual, exploratory and automated testing of assigned Evolve APIs and user workflows

Tech Stack

Postman, REST/JSON, OpenAPI/Swagger, Playwright, Git, CI and SQL

Growth Path

 Associate QA Engineer, based on performance and business need

Role Purpose

Evolve is Caava Group’s insurance management platform, built on Spring Boot services with Angular and Next.js frontends, and used by AIICO for its insurance operations.

Support the testing of Evolve’s APIs and user workflows through manual, exploratory and automated testing. Work with experienced engineers to find defects, verify fixes and build reliable test coverage.

Career Path

Progression to Associate QA Engineer depends on consistent delivery against these measures, growing independence on larger tasks, test and evidence quality, and business need.

Core Accountabilities

API testing and validation

• Translate requirements into test cases and test assigned REST APIs using Postman or similar tools.
• Check schemas, status codes, authentication, authorisation, error handling and edge cases. Maintain API collections and record results against agreed coverage.
• Check OpenAPI/Swagger documentation against API behaviour and work with engineers to close gaps.

Frontend quality assurance

• Perform manual, exploratory, cross-browser and responsive testing of Evolve workflows.
• Test forms, validation and user journeys; reproduce UI and usability issues.

Test automation

• Build and maintain foundational API and UI automation in the team’s framework, with review.
• Maintain safe test data and fixtures; help run tests in CI and investigate failures.

Defect reporting and release quality

• Write reproducible defect reports with steps, expected and actual results, and evidence.
• Verify fixes, run regression tests and escalate blockers or quality risks early.
• Summarise test coverage and open defects to support release decisions.

Key Performance Indicators

KPI

Measure

Target

Test delivery

Original sprint QA items Done by sprint end ÷ items committed at sprint start × 100.

≥85% each sprint.

API coverage

Assigned endpoints tested ÷ endpoints in agreed test scope × 100.

≥80%; results and documentation for every endpoint tested.

Defect evidence

Own reports rejected for missing or incorrect evidence ÷ own reports reviewed × 100.

<10%.

Retest quality

Own verified fixes reopened for missed verification ÷ own fixes verified × 100.

<5%; retest within 4 working hours of a ready build.

Automation quality

Reviewed, repeatable API/UI tests added or maintained per sprint.

3–5 meaningful tests per sprint when allocated.

Blocker escalation

Working time from identifying a testing blocker to informing the QA Lead.

<2 working hours.

Review weekly with your lead: sprint measures are scored per sprint and reopen rates over a rolling 4 weeks. Snapshot scope at sprint planning and record changes separately. Report N/A where no work is eligible. Proposed targets are confirmed after the first quarter of data.

Experience and Working Style

• A QA internship, coursework, personal projects or equivalent practical testing experience.
• Understanding of test cases, regression and exploratory testing, and the defect lifecycle.
• Basic scripting ability in Python, TypeScript or Java, with interest in test automation.
• Basic REST, HTTP and JSON knowledge, with exposure to Postman or a similar API tool.
• Ability to document test results clearly and use evidence to explain defects.

Working Style

• Attention to detail and curiosity about how user workflows and systems behave.
• Clear communication, follow-through on assigned work and willingness to ask for help when blocked.

Nice to Have

• Exposure to Playwright, Cypress, Selenium or Pytest through a project or internship.
• Familiarity with Git, CI/CD pipelines or OpenAPI/Swagger.
• Basic SQL for data validation and an interest in insurance workflows.