SDET (L2) - Banking
OpenFX (company site, opens in a new tab)BengaluruOn-siteDirect career pageEst. 12–22 LPA
Posted on 17 Sept
Reach people at OpenFX
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at OpenFX you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Own backend quality engineering for the Banking team, focusing on automation frameworks that test APIs, services, databases, and end-to-end banking workflows.
- Ensure financial correctness and failure mode resilience across complex transaction systems including ledgers, payouts, reconciliation, and settlements.
- Drive continuous integration of automated tests into CI/CD pipelines and maintain test infrastructure such as Docker/Kubernetes environments and performance testing tools.
Minimum Requirements
- Experience building or significantly extending backend automation frameworks (SDET level).
- Strong skills testing REST APIs, backend services, databases; familiar with distributed system failure modes: retries, idempotency, concurrency, timeouts, duplicate processing.
- Proficient in complex SQL query writing for data validation.
- Work Experience Required: Not explicitly mentioned in the JD.
Ideal Candidate Profile
- Has domain experience testing payments, banking, fintech, or correctness-critical financial systems, especially ledgers and transaction flows.
- Skilled in production-quality coding (Java, TypeScript, JavaScript, or Python) and automation frameworks like Java/RestAssured or Maven/TestNG.
- Experienced with cloud (AWS), containerization (Docker/Kubernetes), event-driven architectures, performance/load testing (JMeter, k6), observability, and use of AI tools for test automation and debugging.