Job Opportunities API

The Pepperstone story started in 2010. We know what it’s like to trade the world’s markets. Our team describes us as a place for the curious and the driven, and we like to do things a little differently; as a transformative global fintech we’re digital, nimble, connected, and united in our vision to create a better way to trade. We thrive on progress – for our clients and for ourselves. Our organisational culture is ever-evolving, vibrant, diverse, global and results focused. You’ll find our  700+ team across 12 regions and 9 time zones. Job type and working arrangement Fixed-term, full-time — maternity cover for approximately five months (22 weeks). The Role The Senior Automation QA Engineer is an experienced individual contributor on Trading App and WebTrader Next . They own test automation architecture, CI integration, and maintainable suites using Playwright (web) and Maestro (mobile) so the squad gets fast, trustworthy feedback on every increment. They design automation for high-risk trading flows (auth, orders, pricing, critical calculations, upgrades), keep pipelines actionable when they fail, and partner with manual QA on clear scope boundaries. When automation cannot cover sprint risk in time, they contribute targeted manual testing on critical paths—without owning full manual regression (Lead QA / Manual QA). Release and sprint decisions are backed by explicit quality signals from automation—pass/fail, known gaps, flake rate, residual risk—not informal status alone. Key Responsibilities Own automation architecture and evolution for assigned epics : scope, environments, test data, device/browser matrix, and integration points (e.g. auth, pricing, orders) across web and mobile. Design, implement, and maintain Playwright suites for WebTrader Next and Maestro flows for the Trading App; keep tests structured for parallel execution and low flake. Integrate automation into PR and trunk workflows (GitHub Actions); work with engineers on testability (test IDs, hooks, build flavours). Partner with Product and Design so acceptance criteria are automation-friendly; flag gaps where requirements omit observable outcomes. Coordinate with Senior (Manual) QA on what should be automated vs. remains manual; avoid duplicate ownership and unclear hand-offs. When automation cannot cover sprint risk in time, contribute targeted manual testing on critical paths—without owning full manual regression (Lead QA / Manual QA). Keep pace inside two-week Scrum; fix or quarantine flaky tests within the sprint boundary; escalate blockers early to the Team Lead when pipelines or environments stall delivery. Refinement: flag automation debt and coverage gaps; propose tech tasks before sprint start. Sprint: keep CI signal trustworthy; react to breakages from app, web, or API changes. Pre-release: summarise automation coverage vs. scope, known gaps, and residual risk for release stakeholders. Post-release: drive flake reduction and concrete tooling improvements from retros. Support other QA engineers extending automation through templates, reviews, and guardrails. Formal mentoring is a separate programme; this is hands-on delivery support. Scope is WebTrader Next and Trading App automation quality and CI integration. Technology and architecture context Context : WebTrader Next ships as a web client; the Trading App ships on iOS and Android (React Native stack). The Senior Automation QA Engineer works across web and mobile environments, test data, and device/browser matrices for each increment. Automation stack: Playwright for web (webtrader-next); Maestro for mobile (mobile-e2e). Appium is not used. Work tools: Jira; Confluence; GitHub and GitHub Actions; Figma for design alignment where applicable. Slack / mail for coordination with dev and QA peers. Devices & labs: On-device and/or cloud device access (e.g. BrowserStack) as the team operates; know app-stor