Remote job
QA Automation Engineer
Job details
About this role
Role overview Own the automated testing foundations that help engineering teams release production software with confidence. The role combines UI, API, and integration testing with CI quality gates and traceable evidence for audit-sensitive environments; test frameworks should remain useful and maintainable as products evolve.
Responsibilities - Build maintainable end-to-end UI automation for complex multi-tenant products using Playwright and Cypress. - Test Node.js and Python services at the API and integration layers, covering schemas, authentication, edge cases, and failure behavior. - Integrate appropriate automated checks into CI pipelines with fast feedback, parallel execution, and clear failure reports. - Set coverage, performance, and regression thresholds in partnership with engineering teams. - Investigate flaky tests, race conditions, and environment drift to make failures meaningful. - Produce traceable test artifacts and reports, and raise team standards through code review, mentoring, and shared documentation.
Requirements - Experience owning automation for production software with real users. - Strong Playwright and Cypress skills, including test structure, fixtures, and debugging. - API testing experience with REST and GraphQL, including authentication, mocks, and contract validation. - Experience integrating tests into CI systems such as GitHub Actions or GitLab CI, including Docker-based environments. - Solid JavaScript or TypeScript skills; Python is also useful. - A risk-focused approach to quality and the ability to communicate results clearly.
Nice to have - Performance or load testing experience with tools such as k6 or JMeter. - Familiarity with AWS, GCP, or Azure and Kubernetes test environments. - Experience in regulated domains, or building dependable test data pipelines. - Ability to use logs, traces, and metrics when investigating failures.
Benefits and work setup - Remote work from anywhere in Pakistan, with overlap across distributed teams. - Dedicated budget for learning and testing tools. - Growth paths toward senior QA, test architecture, or platform reliability.