Calling all innovators – find your future at Fiserv.
We’re Fiserv, a global leader in Fintech and payments, and we move money and information in a way that moves the world. We connect financial institutions, corporations, merchants, and consumers to one another millions of times a day – quickly, reliably, and securely. Any time you swipe your credit card, pay through a mobile app, or withdraw money from the bank, we’re involved. If you want to make an impact on a global scale, come make a difference at Fiserv.
Job Title
QA Lead
About your role:
At Fiserv, we are modernising a high-volume global payment processing platform — moving from a monolithic, batch-driven architecture to an event-driven microservices platform on AWS. This is a ground-up build: Confluent Cloud for event streaming, Aurora PostgreSQL for persistence, Kubernetes for compute, and a modern Java/Kotlin stack throughout.
As a QA Lead, you will own the quality approach for a workstream or project within the modernisation programme. Your focus is the end-to-end flow — proving that systems integrate correctly across domain boundaries, external platforms, and legacy systems, not just that individual services work in isolation. You will define what needs to be tested, build the frameworks to prove it, and give the programme confidence that the integrated system works as expected.
This is a broader view than a single scrum team. You will work across multiple teams, following the transaction flow wherever it goes — across new services, into legacy systems, through external integrations — and own the test strategy for that full path.
This is not a manual testing role. You will be technically strong, comfortable with code, and capable of testing event-driven microservices at the contract, integration, and system level.
What you’ll do:
Own the end-to-end test strategy for your workstream — defining how to prove that the full integrated flow works correctly across multiple services, domains, and systems.
Test across system boundaries — verifying integration between new platform services, legacy systems, and external platforms (e.g. card schemes, partner systems, upstream channels).
Drive parity validation — proving that new platform flows produce the same outcomes as legacy for migrated functionality, defining what “equivalent” means, and building the comparison approach.
Define and manage cross-system test scenarios — the integration paths and edge cases that no single scrum team would own or think to test. Build shared test infrastructure — frameworks, test utilities, event assertion tools, and data comparison tooling that support end-to-end validation.
Create and curate test data — building representative datasets that exercise the full flow across system boundaries, institution configurations, and transaction scenarios.
Work across scrum teams — coaching developers on integration testing approaches, ensuring teams understand the upstream and downstream impact of their changes.
Contribute to CI/CD quality gates — ensuring automated integration tests provide fast, reliable feedback without becoming a deployment bottleneck.
Identify integration risks early — the failure modes that live at handoff points between systems, where most defects in distributed architectures actually occur.
Collaborate with the Quality Architect on programme-level standards and cross-workstream concerns.
Experience you’ll need to have:
Experience owning quality across system or service boundaries — not just within one team, but across the integration points between multiple systems.
Strong technical skills — comfortable with Java or Kotlin, test frameworks (JUnit, TestContainers, or similar), and building automation for distributed systems.
Experience testing event-driven or message-based systems — Kafka, async processing, eventual consistency, schema validation, or similar patterns.
Experience with migration or parity validation — proving a new system matches an existing one, managing expected…