SaaS QA Automation Engineer Needed
Budget: $30 – $250 USD
Our engineering organization is doubling down on shift-left quality, and the next milestone is a fully automated test suite that lives alongside the codebase and runs on every commit. The work spans strategy, hands-on coding, and mentorship.
You will craft an automation framework in Selenium, writing suites in Python, Java, and JavaScript—whichever language best fits each micro-service. Functional coverage comes first, followed quickly by performance scenarios that exercise real-world concurrency and data volumes. Each suite must plug into our existing CI/CD pipeline so that failures block the build and generate actionable reports for developers inside their pull requests.
Key targets include:
• Converting current manual regression cases into reliable Selenium scripts.
• Building lightweight performance harnesses that reuse the same page objects and service stubs.
• Pairing with developers during story grooming to define test hooks and log points early.
• Coaching two junior QA engineers so they can extend and maintain the framework once the core is complete.
Acceptance will be measured by green pipeline integrations, coverage metrics agreed at sprint planning, and knowledge-transfer sessions recorded for future onboarding. Expect a fast-moving agile cadence, daily Slack touch-points, and code reviews through GitHub.
You will craft an automation framework in Selenium, writing suites in Python, Java, and JavaScript—whichever language best fits each micro-service. Functional coverage comes first, followed quickly by performance scenarios that exercise real-world concurrency and data volumes. Each suite must plug into our existing CI/CD pipeline so that failures block the build and generate actionable reports for developers inside their pull requests.
Key targets include:
• Converting current manual regression cases into reliable Selenium scripts.
• Building lightweight performance harnesses that reuse the same page objects and service stubs.
• Pairing with developers during story grooming to define test hooks and log points early.
• Coaching two junior QA engineers so they can extend and maintain the framework once the core is complete.
Acceptance will be measured by green pipeline integrations, coverage metrics agreed at sprint planning, and knowledge-transfer sessions recorded for future onboarding. Expect a fast-moving agile cadence, daily Slack touch-points, and code reviews through GitHub.