Back
Tier-1 brand, mid-level automation role, and common QA title increase candidate competition.
QA automation skills are transferable, but banking/payments domain knowledge increases background sensitivity.
Explicit 2–6 year requirement plus banking domain and mandatory automation tools raise shortlisting strictness.
Login to See Your Match Score
Create a free account or log in to unlock your CV match score across:
Develop and maintain automated and manual test cases for financial software products, focusing on Payments domain.
Execute test plans, track defects through resolution, and collaborate with developers and stakeholders to ensure product quality.
Set up and maintain testing environments, create SQL scripts for data validation, and support stakeholders before software GA release.
2-6 years of experience testing software applications, preferably in banking or financial domain.
Familiarity with Java, Selenium, Playwright automation tools; REST and SOAP APIs (Postman, SOAP UI).
Experience with build/CI tools such as Maven/Gradle and Jenkins; version control with Git; relational databases like Oracle.
Knowledge of Payment domain is mandatory; GPP knowledge is a plus.
Experienced QA engineer with a strong focus on Payment domain software testing within financial services.
Skilled in both manual and automated testing frameworks specializing in Java/Selenium ecosystem and API testing.
Comfortable working independently or in a team across multiple projects, with expertise in defect tracking and agile SDLC.