Front End Testing Engineer - Payments

Posted 8 days ago

ntt dataAtlanta (GA)

Software Quality Assurance Analysts and TestersSoftware Publishers

SENIORITY

Senior

About the role

Job Description: QA Front‐End Testing Engineer – Payments We are seeking a QA Front‐End Testing Engineer to join our Payments Engineering organization, with a focus on modern React‐based user interfaces that support critical payment flows, customer onboarding, transaction management, and reporting experiences. This role is responsible for ensuring our UIs are high quality, accessible, resilient, and compliant, while enabling rapid and safe delivery in an AI‐first, automation‐driven SDLC.This position partners closely with frontend engineers, backend services teams, product managers, and platform teams to embed quality deeply into design, development, and delivery.

About the Role: As a QA Front‐End Testing Engineer, you will own the quality strategy and automation for React‐based user interfaces supporting payment and transaction processing systems. You will focus on behavior‐driven UI testing, accessibility, API‐aware frontend validation, and CI‐integrated quality gates. You will help shape how UI quality scales across teams by promoting modern testing patterns, reducing flakiness, improving feedback loops, and ensuring frontend experiences

Essential Responsibilities: Front‐End Quality & React Testing Design and execute test strategies for React‐based user interfaces, focusing on user behavior rather than implementation details. Validate component behavior across state changes, asynchronous flows, and re‐render scenarios. Ensure frontend quality for payment‐critical user journeys, including submission, confirmation, error handling, and recovery paths. Partner with frontend engineers to improve testability, component design, and acceptance criteria. UI Automation & Test Architecture Build and maintain automated UI tests using modern frameworks (e.g., Playwright, Cypress, React Testing Library).Establish scalable test patterns that balance component, integration, and end‐to‐end coverage. Use network‐aware testing techniques to validate API interactions, payloads, and error scenarios. Ensure UI test suites are maintainable, high signal, and aligned with risk‐based priorities. Accessibility & User Experience Quality Incorporate accessibility (a 11y) testing into automated and manual test strategies. Validate semantic HTML, ARIA usage, keyboard navigation, and screen reader compatibility. Ensure UI changes meet accessibility expectations and support inclusive customer experiences. Detect and prevent accessibility regressions in CI pipelines. State, Error Handling & Edge‐Case Validation Test UI behavior across loading states, partial data, retries, and failure scenarios. Validate client‐side protections against duplicate submissions, race conditions, and inconsistent state. Ensure clear and consistent user feedback for errors, timeouts, and degraded backend conditions. Focus on frontend resilience for payment‐related workflows. Visual, Cross‐Browser & Responsive Testing Validate UI behavior across modern browsers and device form factors. Support visual regression testing for high‐risk and customer‐facing screens. Ensure responsive layouts, localization readiness, and consistent rendering across environments. Balance visual confidence with test stability and signal quality. CI/CD Integration & Quality Gates Integrate UI tests into CI/CD pipelines with fast, reliable feedback loops. Contribute to quality gates that ensure UI changes meet functional, accessibility, and reliability thresholds. Identify and reduce flaky tests through root cause analysis and test refactoring. Support progressive delivery strategies with frontend quality validation. Collaboration & Continuous Improvement Collaborate with developers, product, and design teams during refinement and planning. Review frontend changes with a quality and risk‐aware lens. Promote best practices in frontend testing and quality engineering. Contribute to shared tooling, documentation, and standards across teams.

Basic Qualifications: Bachelor's degree or equivalent work experience.3+ years of experience in QA, SDET, or Quality Engineering roles with a frontend focus. Hands‐on experience testing modern Java Script applications, preferably React. Experience working in agile and Dev Ops environments. Preferred

Skills & Experience: Strong experience with Playwright, Cypress, or similar UI automation frameworks. Hands‐on experience with React Testing Library and behavior‐driven testing approaches. Experience validating API interactions within UI tests (REST or GraphQL).Familiarity with accessibility testing tools (e.g., axe‐core).Experience running UI automation in CI/CD pipelines. Understanding of state management, async rendering, and frontend error handling.

Nice to Have: Experience testing payment or transaction‐based user interfaces. Exposure to visual regression testing tools. Familiarity with contract testing concepts or API mocking (e.g., MSW).Experience supporting AI‐assisted testing workflows or test generation. Knowledge of security‐aware frontend testing practices. Location Expectations The role offers a hybrid/flexible schedule, with an in‐office expectation of 3 or more days per week and flexibility to work remotely on other days Posting Date: Department: CONS: International Banking - 1460250021

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.