The role
We are interested in QA automation engineers who approach quality as a team activity rather than a final gate. You would understand how users complete important workflows, identify where failures would matter most and build tests that provide timely, trustworthy feedback. You would also explore behaviours automation can miss and help teams turn defects into better design and prevention. Your judgment about what to test matters as much as the code you write. This role-specific posting is for ongoing recruitment, subject to later opportunity details.
What you would work on
- Turn acceptance criteria and user journeys into a risk-based test approach spanning interface, API and integration behaviour.
- Write maintainable automated checks with reliable fixtures and clear assertions, keeping the test suite fast enough for regular delivery.
- Run exploratory sessions around edge cases, accessibility, data conditions and failure paths, then communicate findings with reproducible evidence.
- Investigate flaky tests and escaped defects, distinguish product issues from test-environment issues and recommend preventive changes.
- Integrate checks into CI, report meaningful quality signals and collaborate with developers and delivery leads on release readiness.
Essential experience
- Hands-on automation for web applications or APIs, with experience maintaining tests as features and interfaces change.
- Sound test design, defect analysis and exploratory testing; ability to choose useful coverage rather than maximize test count.
- Comfort reading application behaviour and collaborating with engineers, product partners and business testers.
Useful additional experience
- Accessibility testing, performance or security test collaboration, contract testing and test-data management.
- Helping teams introduce automation into an existing manual test process while preserving valuable human investigation.
What to include in your application
Send your résumé and describe a test strategy or automation suite you improved. Explain the risk it covered, how you kept tests trustworthy, a defect it helped uncover and what changed after release. Include an example of a test you chose not to automate and why exploratory or lower-level checking was more useful. A sanitized test example is welcome but optional. Please apply to the QA Automation Engineer posting so your résumé is tied to this role.