QA Automation Engineer - API Testing, Selenium, Java​/Wires

Responsible for all phases of testing for assigned projects or releases, including Smoke/Build Verification Testing, Sprint Testing, Integration Testing, End-to-End Testing, Business Testing Support, Deployment Order Testing, and PAT phase.

• Review system requirements, design documents, and technical user stories.
• Create, execute, and document detailed and accurate test cases.
• Develop and maintain automation test scripts for API, Services, and End-to-End (E2E) testing.
• Define test data and environment requirements.
• Participate in daily defect status calls to ensure defects are documented, tracked, retested, and reported in a timely manner.
• Assist Test Lead in delivery of test estimations and planning activities in adherence to system testing standards.
• Support technology peers in troubleshooting issues.
• Develop, debug, execute, and maintain performance testing scripts using various performance testing tools.
• Follow Technology Delivery practices, standards, and project management disciplines.
• Continuously enhance knowledge and expertise in technology and domain areas.

• Experience: 8–10 years in functional, manual, and automation testing.
• Strong experience in API Testing using SOA Test, SOAP UI, Ready API, POSTMAN, etc.
• Hands‑on experience with API Testing using Rest Assured
  .
• Working experience with test automation using Selenium
  .
• Knowledge of Maven for project builds.
• Basic knowledge of Java
  , Cucumber
  , JUnit
  , and TestNG
  .
• Excellent documentation, verbal communication, and problem‑solving skills.
• Engineering mindset with strong attention to quality and detail.
• Domain Knowledge: Payments / Wires

• API Testing
• Test Automation
• Framework Development
• Rest Assured
• Java

• Core Java
• Cucumber, JUnit, TestNG
• Performance testing tools (desirable)

• Inspire a positive work environment and champion quality, innovation, teamwork, and service to the business.
• Eager to learn, adapt, and stretch thinking continuously.
• Strong collaboration with cross‑functional teams.

• 8–10 years