Quality Engineer

Role Overview

The QA / Release Engineer is responsible for quality assurance and release coordination across the full Paymorrow platform spanning backend services, both native mobile SDKs (iOS and Android), shared platform components, and integrations with external providers. This is a broad, multi-track role that operates across the Run, Build, and Mobile SDK release cycles simultaneously, and delivery planning must reflect that from the outset.

This role is not a dedicated Run resource. Time is shared across backend QA, mobile SDK release coordination, build track quality assurance, and integration testing against external providers. The release coordination scope alone covers two independent native mobile SDK distribution pipelines operating on different cadences to the backend release stream these cannot be collapsed into a single release process.

The role requires both manual and automated testing skills, strong release management discipline, and the technical depth to test against external provider integrations that have their own distinct failure modes and are not covered by standard backend or mobile testing alone.

Key Responsibilities

Quality Assurance — Backend and Shared Components

• Own QA across all backend tracks — Core Platform, Card Service (PCI scope), Payment Method Services, Merchant / Customer Domain Services, and the Business Rules / Risk Engine
• Design, build, and maintain automated test suites covering regression, integration, API, and contract testing for backend services across both the Java/Spring Core Platform and the Node.js/TypeScript Card Service environment
• Execute and maintain manual test cases for complex business logic scenarios that are not suitable for full automation — including credit decision flows, dunning workflows, SEPA mandate lifecycle, and rules engine policy scenarios
• Validate database-layer logic — including stored procedures and complex SQL — as part of end-to-end test coverage, ensuring payment method and transaction logic is tested at the layer where it executes, not only at the API surface
• Own regression test execution for all backend releases, including hotfixes, patches, and planned releases, producing test evidence in line with the change management and PCI DSS audit requirements
• Contribute to shift-left quality practices across the pod, embedding test design earlier in the delivery lifecycle and working with engineers during development rather than at the point of release

Quality Assurance — Mobile SDKs

• Own QA for both native mobile SDKs — iOS (Swift) and Android (Kotlin/Java) — across the full SDK release lifecycle, including functional testing, regression testing, integration testing with the Card Service backend, and merchant SDK integration validation
• Design and maintain automated test coverage for mobile SDK functionality, including tokenisation flows, 3-D Secure 2, hosted fields, and SDK-to-backend communication
• Test device-attestation flows and certificate-dependent communication between the mobile SDKs and the Card Service backend, covering both happy-path and failure-mode scenarios
• Validate SDK behaviour across a representative range of iOS and Android device and OS versions, identifying compatibility issues before release
• Coordinate with merchant integration teams to validate SDK integration scenarios and merchant-specific test cases

Integration Testing — External Providers

• Own integration testing against the external providers the platform depends on for authentication, device attestation, and credit and fraud risk decisions — these are separate technical surfaces with distinct failure modes and are not covered by generic backend or mobile testing
• Design and maintain integration test suites for each external provider dependency, covering both successful flows and provider-side failure scenarios (timeouts, degraded responses, partial failures, and fallback behaviour)
• Maintain a clear inventory of external provider integration points, their test environments, and their failure modes, ensuring this is documented and available to the team
• Coordinate with external provider contacts where test environment access, credential management, or provider-side test data is required
• Ensure integration test results are included in release sign-off evidence for any release that touches an external provider integration path

Release Coordination — Backend

• Own release coordination for all backend releases across Core Platform and Card Service, managing the end-to-end release process from test sign-off through to production deployment
• Maintain and execute the release checklist, ensuring all test evidence, approval gates, rollback plans, and change management documentation are in place before production deployment
• Coordinate the manual approval gate within the Card Service CI/CD pipeline (CodeCommit CodePipeline), ensuring the gate is exercised correctly and release evidence is retained for PCI DSS audit purposes

Release Coordination — Mobile SDKs

• Own release coordination for both native mobile SDK distribution pipelines — iOS App Store / TestFlight and Android Play Store / internal distribution — which operate on independent cadences to the backend release stream and to each other
• Manage the full SDK release lifecycle for both platforms: build verification, test sign-off, store submission, review management, and release confirmation
• Maintain SDK versioning, release tagging, and SDK changelog documentation
• Coordinate SDK releases with merchant integration teams where merchants require advance notice of SDK version changes or have integration certification requirements
• Manage SDK release scheduling to avoid conflicts between iOS and Android release cycles and backend releases that introduce breaking API changes

KPI and Reporting

• Define and maintain quality KPIs — defect escape rate, test coverage, automation coverage, release success rate — and report against them in the monthly service report
• Track and report test coverage trends across the build track, ensuring modernised components meet agreed coverage standards before production release
• Contribute to the annual productivity report with quality and release metrics

Required Skills and Experience

Essential

• 5–8 years of QA and release engineering experience spanning both manual and automated testing disciplines
• Proven experience with test automation frameworks for Java environments (JUnit 5, TestNG, RestAssured, TestContainers) and Node.js/TypeScript environments (Jest, Mocha, Supertest)
• Experience testing mobile applications on both iOS and Android platforms, including SDK-level testing and device compatibility testing
• Demonstrable experience with release management and release coordination in a multi-stream environment — candidates with experience managing independent release pipelines across backend and mobile will be strongly preferred
• Experience designing and executing integration tests against external provider APIs, with an understanding of external provider failure modes and how to test for them
• Experience with CI/CD pipeline integration for automated test execution, including build verification and automated regression triggering
• Strong understanding of PCI DSS testing and release evidence requirements
• Experience working in agile delivery teams with Jira-based backlog and release tracking
• Excellent documentation skills — test plans, release notes, test evidence, and runbook contributions

Desirable

• Experience with mobile SDK distribution pipelines for both iOS (App Store Connect, TestFlight) and Android (Google Play Console, internal distribution tracks)
• Familiarity with certificate management and certificate-dependent communication testing in mobile and backend environments
• Experience testing tokenisation flows, 3-D Secure 2, or PCI DSS-scoped card payment services
• Familiarity with SEPA payment processing flows, mandate lifecycle testing, or R-transaction scenario testing
• Experience testing business rules engines or credit decisioning logic, including boundary condition and policy rule validation
• Knowledge of performance and load testing for payment APIs under high-throughput conditions
• Experience with ELK/Kibana or equivalent observability tooling for test monitoring and defect investigation
• ISTQB Advanced Test Analyst or equivalent certification preferred

Skills

API Automation Testing, Manual Testing, Android Testing and Debugging, Release Management and Deployment, Agile Methodology, Communication Skills