Test Engineer

• *Test Engineer**
• ----------------

R\-0046373\-05

• MS \- Banking \& FS
• Mumbai
• Posted On 28 Oct 2026
• End Date 27 Dec 2026
• Required Experience1 \- 3 years

• *Basic Section**
• ----------------

No. Of Openings1

DesignationTest Engineer

Closing Date 27 Dec 2026

• *Organisational**
• -----------------

MainBUQuality Engineering

Sub BUMS \- Banking \& FS

ParentCCCOGS

CostCenterCOGS

Legal EntityQualityKiosk Technologies Private Limited

Legal Entity LocationNavi Mumbai

CountryIndia

RegionIndia

StateMaharashtra

CityMumbai

Working LocationWadala

Client LocationNA

• *Skills**
• ---------

#### **Skill**

Loan Origination System Loan Management System

#### **Highest Education**

No data available

#### **CERTIFICATION**

No data available

#### **Working Language**

No data available

• *JOB DESCRIPTION**
• ------------------

About the Role Own the test strategy and the hardest scenarios in the LAP lifecycle. You will shape how the team tests and mentor Junior testers. Key Responsibilities • Create the test strategy and plan per release; maintain BRD ? FSD ? test case traceability (RTM). • Design complex end\-to\-end scenarios: balance transfers, top\-ups, co\-applicants, multi\-property and cross\-collateralization. • Test EOD/BOD batches, IRR and APR calculations, interest accrual shifts, rate resets and moratorium impacts. • Review requirements early (shift\-left) and challenge gaps with Product Managers and Business Analysts. • Review Junior testers’ test cases, data and defects; coach on domain depth and quality. • Report coverage, risks and defect trends to the Team Lead and stakeholders. Must\-Haves • 2\-3 years testing LOS/LMS in Indian lending, with deep LAP domain knowledge • Hands\-on with Finone, Finnaxia, Nucleus, Pennant, Lentra or similar platforms • Experience with NACH/e\-Mandate and IMPS/RTGS payment flows • Working knowledge of RBI digital lending and LAP exposure norms Good\-to\-Haves SQL for ledger validation, Selenium/RestAssured/Playwright/Cypress, Jira/Confluence. Scope Boundary Does not own team capacity, release go/no\-go or regression automation strategy.