[Hiring] Sr. QA Engineer 2 - Mobile Apps @Numerator

Role Description

• Plan and perform functional testing from requirements, acceptance criteria, and product behavior.
• Explore new and changed features, edge cases, and end-to-end workflows; identify risks beyond the existing automated suite.
• Record reproducible defects with clear steps, expected and actual results, and supporting evidence.
• Retest fixes and run focused regression checks to support release decisions.

• Web test automation
• Turn stable, high-value scenarios into maintainable end-to-end tests using Playwright and TypeScript.
• Maintain shared fixtures, page objects, selectors, and test data so that tests remain readable and reusable.
• Automate critical public and signed-in journeys, including authentication, account and profile flows, surveys, transactions, and forms.
• Investigate failures, distinguish product defects from test or environment issues, and improve test reliability and diagnostics.

• Team quality practices
• Collaborate with engineering and product teams during refinement and delivery to clarify acceptance criteria and testability.
• Use Git and pull-request workflows to review and contribute automation changes.
• Contribute to agreed CI execution, test reporting, and continuous improvement of the team’s testing approach.
• Use findings from manual and exploratory testing to prioritize new automation coverage.

Qualifications

• Experience performing manual functional testing and exploratory testing for web applications.
• Ability to design test scenarios from requirements, investigate unexpected behavior, and report defects clearly.
• Practical experience with browser-based test automation; Playwright with TypeScript or JavaScript is the primary stack for this role.
• Understanding of maintainable automation design, assertions, test data, and debugging test failures.
• Working knowledge of Git and collaborative code review practices.
• Clear communication and effective collaboration across QA, engineering, and product teams.
• Experience integrating automated tests into CI pipelines and interpreting pipeline results.
• Experience with API testing, including validating responses, authentication, and test data.

Additional Experience

• Familiarity with other browser automation tools may be useful as the team’s needs evolve.

How Success is Measured

• Manual and exploratory testing finds and communicates meaningful risks before release.
• Critical agreed user journeys have reliable, maintainable automated coverage.
• Test results and defect reports are timely, reproducible, and useful for release decisions.
• Automation failures are triaged promptly and avoidable flakiness is reduced.
• Changes to product behavior are reflected in relevant test scenarios and automation.