qa engineer (manual) for payment infrastructure

Cross River builds infrastructure for financial products, powering payments, cards, lending, and digital asset capabilities for fintechs, enterprises, and other innovators.

• Design and implement layered quality sensors across the CI/CD pipeline, from static analysis to AI-driven code review passes;
• Improve and maintain E2E test suites for critical payment flows, including card authorisation, clearing and settlement, tokenisation, and 3D Secure;
• Review PRs for test intent alignment and ensure AI-authored and human-authored code meets the same quality bar;
• Identify test coverage gaps and prioritise them by customer impact and regulatory exposure;
• Build load testing and performance validation frameworks;
• Collaborate with the team on quality strategy and raise the quality bar;
• Explore chaos engineering approaches to validate system resilience;
• Contribute to audit-trail practices by ensuring generated diffs and suppressed checks are traceable and defensible.

• 5+ Years in software engineering with a strong focus on quality and testing, including equivalence partitioning, boundary analysis, and risk-based prioritisation;
• Proficiency in Go or strong willingness to learn;
• Daily use of AI assistants with the ability to identify incorrect outputs and determine when not to use them;
• Experience testing RESTful APIs and event-driven systems;
• Familiarity with CI/CD pipelines, containerisation, and infrastructure-as-code;
• Strong analytical thinking with the ability to trace bugs back to specifications;
• Experience with regulated environments and audit trails, blast radius, and data classification;
• Strong proficiency in English, written and verbal;
• Excellent communication skills and the ability to teach and mentor;
• Nice to have: Experience with observability platforms such as Datadog, New Relic, Elasticsearch, and Grafana; understanding of distributed-system failure modes, including event ordering, retries, idempotency, and eventual consistency; knowledge of Domain-Driven Design, including bounded contexts, ubiquitous language, and aggregate boundaries.

• Relocation support is not specified.