AI Automation Engineer (Web & API – Banking)
Banking automation is not a generic testing problem. Payments rails, KYC workflows, lending lifecycles, and compliance checks each carry regulatory weight and failure modes that only surface when the engineer understands the domain, not just the toolchain. This role exists because that combination — automation depth plus banking-domain fluency — is rare and consequential.
You will work across Web and API layers, own suite design from scratch, and integrate your work into live CI/CD pipelines. The systems you test move money and gate compliance decisions. Test design is therefore a domain problem first and a tooling problem second.
AI-native expectations
Every Qapitol engineer is expected to be AI-native. Here that means using AI tools to generate boundary and edge-case test data for regulated workflows, applying AI-assisted API contract testing and schema-drift detection, and bringing fraud and anomaly pattern awareness into scenario design for payments and transactions. These are working expectations, not aspirational ones.
Who thrives here
You have spent time inside banking or financial services and understand why a payments test suite looks different from a retail e-commerce one. You are precise about data, comfortable owning backend validation through SQL, and you treat OOP and design patterns as engineering hygiene rather than checkbox items. You want your work to matter — and in regulated systems, it does.
What you'll own
- Build and maintain Web and API automation suites using Java (Selenium, TestNG, Rest Assured) or Python (PyTest, Requests, Playwright).
- Perform UI validation and cross-browser testing across Web surfaces.
- Own API testing and automation end-to-end, including SQL-based backend and data validation.
- Integrate automation suites into CI/CD pipelines (Jenkins, Git, GitHub, GitLab).
- Design test scenarios around banking workflows — payments and transactions, account management, lending and loans, KYC and compliance.
- Apply OOP principles and design patterns (POM, BDD) within Agile/Scrum delivery cycles.
- Use AI tools to generate boundary and edge-case test data for regulated banking workflows.
- Apply AI-assisted API contract testing and schema-drift detection.
- Incorporate fraud and anomaly pattern awareness into test-scenario design for payments and transactions.
What it takes
- 3–5 years of hands-on Web and API automation testing experience.
- Proficiency in Java- or Python-based automation frameworks: Selenium/TestNG/Rest Assured or PyTest/Requests/Playwright.
- Strong SQL skills for backend and data validation.
- Working knowledge of CI/CD tooling: Jenkins, Git, GitHub, GitLab.
- Solid OOP fundamentals and design patterns including POM and BDD.
- Mandatory prior experience in Banking or Financial Services — payments, accounts, lending, KYC/compliance.
- Agile/Scrum delivery experience.
Nice to have
- BDD frameworks (Cucumber or Behave).
- Performance testing with JMeter.
- Familiarity with microservices architecture.
- Docker and/or Kubernetes.
- Test reporting tools such as Allure or Extent Reports.
We respond to every application within 2 business days.