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. Product and team context This role sits on the  Pepperstone Trading App  engineering thread within  Trading Experience (TREX) . Related capabilities in the wider group include Mobile Platform, integrations (connectors), and the trading platform (Centrum). Department shape includes Mobile Platform plus Trading Experience teams. The Trading App is a proprietary  iOS and Android  client for  CFD  trading and portfolio monitoring—charts, watchlists, execution, margin and P&L, funding, and multi-account types (e.g. Razor / Standard). It  complements  MetaTrader and cTrader; it does not replace them. The app connects to Centrum and other back-office systems via connectors, and integrates services such as SCA, Auth0, Segment, notifications, and others as the stack evolves. Delivery runs in  two-week Scrum  increments. A typical squad includes a tech lead or release captain, on the order of four developers and two manual QA engineers, with test automation as a parallel track. Engineering outcomes should reflect  CFD  realities: margin and leverage, contract-based P&L and financing, broker as counterparty, and region-specific regulation (e.g. FCA, ASIC, CySEC) affecting flows and copy. The Role The  Senior (Manual) QA Engineer  is an experienced individual contributor on the  Trading App . They own  test strategy  and  depth  for  manual  coverage,  support Middle (Manual) QA  on technique and in-sprint  prioritisation , and keep  two-week Scrum  work  release-ready . They work so  Trading App  features ship with  agreed  manual  coverage : critical paths,  regressions , and  exploratory findings are  documented ,  traceable , and  tied to risk . Test  artefacts  (cases,  charters , session  notes ) stay  maintainable and  reusable ;  Middle (Manual) QA  benefits from  clearer  scope, review of test  plans , and help on  complex  defects. Release and sprint decisions are backed by  explicit  quality  signals — pass / fail ,  known  issues,  residual  risk—rather than  informal  status alone. Key Responsibilities Lead  test planning  for assigned epics:  scope ,  environments ,  data ,  device/OS  matrix, and  integration  points (e.g.  auth ,  pricing ,  orders ). Drive  exploratory  testing on new  Trading App  capabilities; surface  edge  and  corner  cases to engineering with reproducible  evidence. Partner with  Product  and  Design  so  acceptance criteria  are  testable ; flag gaps where requirements omit  observable outcomes. Coordinate with  Senior Automation  on what should be  automated  vs. remains  manual ; avoid  duplicate  ownership and unclear hand-offs. Keep pace inside  two-week Scrum ; re-test fixes within the  sprint  boundary;  escalate  blockers early to  Tech Lead  and  EM  when testing or environments stall delivery. Refinement:  translate stories into test ideas and  risks ; flag  miss