QA Engineer (Contract)

This role is being created to bring dedicated quality assurance (QA) support Amptalk's core products. As the products grows, testing needs have grown with it: new features are shipped regularly, and each release needs to be checked carefully before it reaches customers.. In simple terms: this person's job is to make sure the amptalk product they are assigned to works correctly before customers ever see it. They will check new features, re-check old features after changes are made, and help catch problems early. Quality assurance is a full discipline that spans before, during, and after a feature is built. Below is a complete, detailed breakdown of the concrete tasks this role covers, organized by stage, with plain-language examples.

- Hands-on QA/testing experience — has actually tested software professionally, not just studied it - Experience writing test plans and test cases, not just executing tests someone else wrote - Comfortable with both manual testing (clicking through and checking things by hand) and automated testing (writing scripts that test things automatically) - Experience with a tool called "Playwright," or a similar automated testing tool — this is a common industry tool, so equivalent experience is fine - Able to work independently and figure out what needs to be tested without heavy guidance - Naturally curious and detail-oriented — good testers tend to think of unusual ways to try to "break" something, not just confirm it works normally - Comfortable working with AI-based products, or willing to learn — this is a newer skill area, so prior experience is a bonus, not a requirement - Basic understanding of testing across web, desktop, and mobile platforms - Clear written communication — this role involves writing up issues and test results clearly so other people can understand and act on them

■ What Success Looks Like Within the first few months, this person should have documented test plans and test cases for Coach's most important features, a working regression suite in active use, and be fully embedded in the release process — testing new features, re-testing existing ones, and tracking issues through to resolution. Over time, this role should build confidence across the team that releases are checked thoroughly and consistently, and that testing coverage keeps pace as the product grows.