Quality Architect OmniPay Modernisation

Quality Architect OmniPay Modernisation

About your role: We are looking for a Quality Architect to own the programme-level quality strategy across all five domains. Your focus is the quality of the end-to-end transaction chain, the integrity of contracts between domains, and proving that the new platform produces the same financial outcomes as the legacy system. This role is roughly 70% defining what needs to be tested and coaching teams, 30% hands-on building of shared tooling and frameworks that no single domain team would own.

About the Programme We are modernising a large-scale payment acquiring platform, replacing a monolithic batch processing system with event-driven microservices on AWS. The platform processes millions of transactions daily for institutions globally, covering the full acquiring lifecycle: transaction pricing, capture, clearing and settlement with card schemes, merchant funding, and disputes. The modernisation spans five independent processing domains, each with its own engineering team. The modernisation programme is scaling to 40-50 engineers. Migration is incremental, with legacy and new systems running in parallel during the transition.

What you’ll do

• Define testing standards for domain teams: required testing levels, where contract tests are mandatory, what gates deployments in CI. Own cross-domain test scenarios that exercise the full transaction lifecycle across multiple domains. Identify integration risks and edge cases that fall between teams — the failure modes no single domain would think to test. Lead the integration of quality tooling and best practices into CI pipelines, ArgoCD GitOps workflows, and Terraform-managed infrastructure. Own the programme-level approach to performance, resilience, and failover testing - particularly load validation at production-scale volumes before institution cutovers Define and validate back-pressure, retry, and degradation behaviour across the event-driven pipeline under stress conditions Design and own the approach for proving that the new platform produces the same financial results as the legacy system - same fees calculated, same merchant payouts, same clearing outputs, same settlement positions Build the comparison tooling and reporting that gives the programme confidence to cut institutions over from legacy to new Define the test environment strategy: topology, provisioning, and lifecycle management across the platform's infrastructure stack Own the synthetic data strategy and curate golden datasets for parity validation runs Ensure test data management practices support reproducible, reliable cross-domain testing without dependency on production data Define the acceptance criteria for migrating an institution to the new platform - covering functional parity, non-functional thresholds, and operational readiness Design the onboarding validation suite that proves all domains are correctly configured and processing end-to-end for a given institution Provide quality evidence that supports cutover decisions Define the metrics, logging, and tracing standards that domain teams must implement to make quality status measurable - not just in test environments but as production health indicators Give programme leadership clear visibility into quality status: domain boundary test coverage, parity validation progress, non-functional readiness, and institution go-live status Identify cross-domain quality risks early - before they block milestones

Experience you’ll need to have:

• Programme-level quality ownership across multiple engineering teams - defining strategy and standards
• Migration or platform replacement validation - proving a new system matches an old one at scale, including defining equivalence criteria, managing expected differences, and building comparison approaches
• Financial services domain - payments, acquiring, issuing, or banking.
• Technical literacy - able to read event schemas, understand data models and have informed conversations with engineers about testing approaches
• Non-functional testing - performance, resilience, failover, and back-pressure validation for high-throughput distributed systems
• CI/CD integration - embedding quality checks in pipelines, defining deployment gates, keeping test suites fast and maintainable
• Test environment and data management - provisioning strategies, synthetic data generation, golden dataset curation for cloud-native platforms (AWS or equivalent)

Experience that would be great to have:

• Card acquiring or issuing platform experience
• Event-driven architecture testing - Kafka, schema evolution, async processing challenges (ordering, idempotency, eventual consistency)