12+ Regression Testing Jobs in Mumbai | Regression Testing Job openings in Mumbai

About the role 

Most QA teams test software. We want someone who builds a machine that gets better at testing software every time it encounters a bug. 

This is not a role for someone who "uses AI tools." This is a role for someone who thinks like an architect. You will design a QA system that is legible to machines — structured, documented, and self-improving — so that the knowledge of every bug ever found is permanently encoded, queryable, and feeds back into the next test cycle. The goal is simple: the longer you are here, the harder it should be for us to ship a bug. 

You will own quality for Cash, a digital lending app (short-term personal loans) on Android and web — and that ownership extends from the front end all the way through to the back end. 

You are the first QA hire. You will build this function from scratch. 

There is no existing QA process today. No tooling is chosen. No taxonomy exists. No team is in place. You are the founding hire for this function.

Your first 60 to 90 days will be spent laying the foundation: choosing the tools, defining the bug taxonomy, writing the first skills, and establishing what "done" means across the engineering org. Once that foundation is stable, you will define the team structure you need, propose it, and then lead the hiring yourself. The engineers who join QA after you will be hired because you decided you needed them. 

This is a founder-mode role inside an engineering team. It requires someone who is energised by a blank canvas, not someone who wants to inherit a mature process. 

If you have spent your career executing inside an established QA function and are looking for more of the same, this is not the right role. If you have wanted the mandate to build the system properly from day one and have never had it — this is that opportunity. 

What you will own 

The knowledge base 

Every bug you find — whether in QA or in production — gets documented in a structured, machine-readable format. Not just "what broke" but: what flow triggered it, what the borrower context was, what data state preceded it, what the expected behaviour was, what the actual behaviour was, and which class of error it belongs to. Over time, this becomes Cash's QA Wikipedia — a corpus that an LLM can read and use to generate new test cases, that a new engineer can query to understand failure patterns, and that you can analyse to find where the product keeps breaking. 

This is not documentation for its own sake. It is infrastructure. The test suite is only as good as the knowledge base behind it. 

Skills, not scripts 

For every recurring testing workflow — new feature regression, release smoke test, critical-path sanity check, payment flow validation — you will build a skill: a reusable,

prompt-able test protocol that is AI-executable. When a new engineer joins, they run the skill. When an AI agent is asked to help test a release, it reads the skill. The skill improves every time a bug gets through it. 

The feedback loop 

Every production issue must close the loop. When a bug is found in production, you trace back why the QA cycle did not catch it, update the relevant skill, and add the scenario to the knowledge base. No bug should be found in production twice for the same underlying reason. 

Coverage — front end and back end 

Front end (Android and web) 

● Onboarding and Know Your Customer — Aadhaar/PAN flows, video KYC, bureau pulls 

● Loan application and eligibility decisions — rule engine outcomes, edge cases across credit tiers 

● Disbursement — payment gateway integration, failure states, retry logic

● Repayment — in-app payments, auto-debit, partial payment handling

● Collections and dunning — overdue flows, notification logic, settlement scenarios

● Regulatory compliance — Reserve Bank of India guidelines on digital lending, fair practices code, key fact statement display 

● Cross-platform consistency — Android app and web admin panel 

Back end 

● API contract testing — request/response behaviour, error codes, edge-case inputs

● Rule engine validation — confirming that credit decisioning, eligibility, and pricing logic produces correct outputs for known borrower profiles, including boundary cases

● Data integrity checks — verifying that the right records are created, updated, or flagged after key events (disbursement, repayment, status transitions)

● Integration testing — bureau, KYC provider, payment gateway, and notification service behave correctly end-to-end 

● Regression on back-end changes — any service update, migration, or config change must pass a defined back-end test protocol before reaching production 

Failure-state and idempotency testing 

Disbursements and repayments involve real money. What happens if the payment gateway times out mid-disbursement? What happens if a repayment webhook is delivered twice? What happens when a bureau call fails mid-application? You will own failure-path and retry-logic testing explicitly — not as an edge case, but as a first-class part of every release cycle. 

Audit trail and logging validation 

Every significant event in the borrower lifecycle — application submitted, bureau pulled, decision made, loan disbursed, repayment received — must produce a correct, complete, and tamper-evident audit log. You will test that these logs are accurate. In a regulatory inquiry or a borrower dispute, the audit trail is the evidence. 

Security testing (functional) 

You will own a security testing checklist covering: whether borrower data is exposed in API responses or logs, whether sessions expire correctly, whether API responses are correctly scoped to the authenticated user, and whether error messages leak sensitive information. This is not a penetration testing mandate — that is a separate engagement — but functional security hygiene is part of every release. 

Notification and communication testing 

sends SMS, push notifications, and WhatsApp messages at specific borrower lifecycle triggers. You will test correct trigger conditions, correct content, correct recipient,

and correct timing — including the case where the same event should not produce duplicate messages. 

Performance and load testing 

You will own a baseline load test that runs before major releases — simulating concurrent loan applications, concurrent repayments, and peak traffic scenarios. A lending app that degrades under campaign load is a trust problem, not just a technical one. 

Feature flag and staged rollout validation 

Cash introduces features to specific segments (by tier, cohort, or geography), you will verify that flags work correctly — users outside the target segment do not see the feature, and partial rollouts do not produce inconsistent back-end states. 

What good looks like in 90 days 

● Tooling chosen and set up: test management, bug tracking, and at least basic CI/CD integration 

● A structured bug taxonomy with at least five top-level failure classes, each with sub-types and historical examples 

● A skills library covering the five highest-risk flows (loan application, disbursement, repayment, KYC, collections) 

● Every production bug from the past three months documented in the knowledge base with root cause and skill update 

● A release checklist — covering both front end and back end — that an AI agent can execute the first 80% of independently 

What good looks like in 12 months 

● The knowledge base has enough signal to answer: which part of the product produces the most bugs per sprint, which bug class most often escapes to

production, and whether the front end or back end is the higher source of production risk 

● New features ship with skills pre-written as part of acceptance criteria, not as an afterthought 

● Back-end engineers treat you as a partner in the definition of done, not a gatekeeper at the end of the cycle 

● You have hired at least one QA engineer and defined the roadmap for the rest of the team 

● A measurable reduction in production escape rate compared to the baseline when you joined 

What we are looking for 

Non-negotiable: 

● 3+ years in QA for a fintech or digital lending product — loan origination, payments, or collections 

● Experience testing both front-end and back-end services — API testing, database state validation, and integration testing must be in your toolkit, not stretch goals ● Comfort with failure-path and edge-case thinking — happy-path testers need not apply 

● Proven habit of writing documentation that others actually use — not as a compliance exercise but as a tool 

● Hands-on experience using LLMs (Claude, GPT-4, Gemini) to generate test cases, analyse logs, or review coverage gaps 

● Ability to write basic automation scripts in Python or JavaScript — you do not need to be a developer, but you need to be able to build and maintain simple automated checks 

Strong signal:

● You have built something like a bug knowledge base before — even informally — and can show us what it looks like 

● You have thought about the difference between documentation as a record and documentation as infrastructure 

● You have worked in an environment where a decision made by a system had a direct financial consequence for an end user, and you understood the stakes that came with that 

● You have hired or mentored QA engineers before 

Why this role is different 

Most QA roles are reactive. A bug is found, a ticket is filed, the developer fixes it, QA closes it. The institutional knowledge of why that bug happened lives in someone's head or in a comment nobody will read again. 

We want the opposite: a QA function that compounds. Every bug makes the next release safer. Every production incident makes the test suite smarter. The person who builds that system is not a tester. They are an engineer of quality infrastructure.

Why Join Us? 

● Work directly with Founders: Mikhil Innani, former co-founder of PharmEasy and ex-Product Head at Hotstar, and Diksha Nangia, a former banker and CFA Charterholder 

● Best of both worlds: startup speed + listed company stability 

● High ownership, strong learning curve, and direct business impact ● A fast-paced, collaborative culture that values innovation, ownership, and bold thinking

Learn More About Us 

● Annual Report 2024–25 

● Vision Video 

job Description:

We are looking for an experienced Salesforce & Workday QA Engineer with 6+ years of hands-on QA experience in testing Salesforce and Workday applications. The ideal candidate should have strong expertise in functional and integration testing, test planning, defect management, and Agile methodologies.

Required Skills:

• 6+ years of QA experience in Salesforce and Workday applications.
• Strong understanding of Software Testing Life Cycle (STLC) and Software Development Life Cycle (SDLC).
• Experience in Functional Testing, Regression Testing, Integration Testing, System Testing, Smoke Testing, and User Acceptance Testing (UAT).
• Hands-on experience testing Sales Cloud, Service Cloud, Experience Cloud, and custom Salesforce applications.
• Experience testing Workday HCM, Recruiting, Payroll, Benefits, Time Tracking, Compensation, and Financial modules.
• Strong knowledge of Salesforce objects, workflows, validation rules, profiles, permission sets, reports, and dashboards.
• Experience validating Workday business processes, security roles, integrations, and reports.
• Expertise in preparing Test Plans, Test Cases, Test Scenarios, Test Data, and Defect Reports.
• Hands-on experience with defect tracking tools such as JIRA or Azure DevOps.
• Experience in API Testing using Postman or similar tools.
• Good understanding of SQL for backend data validation.
• Experience testing integrations between Salesforce, Workday, and third-party systems.
• Hands-on experience working in Agile/Scrum environments.

Job Description: 

Job Title: QA/Test Management Engineer

Location: Bangalore/ Mumbai

Experience Level: 2-7 Years

Notice period: Immediate to serving notice period up to 45 days

You will:

. Part of a Global test management team working in the Regulatory reporting domain.

. Collaborate with a wide range of colleagues all over the technology and business domain.

Have a good knowledge about testing concepts- including but not limited to understanding

business requirement, defining test scope, ability to collaborate with business/automation

stakeholders and executing tests, bug/defect tracking and closure.

. Demonstrate a high level of subject matter expertise to bridge functional requirements and technical solution.

. Strong working knowledge of various test types including white-box, black-box,

positive/negative, edge cases, etc.

. Solid test design skills, test case writing, automation, and analysis.

. Strong working knowledge of various test phases including functional, integration and

Regression.

. Strong working experience in running the test suite, investigating the failures and can fix or get it fixed, raise bugs, etc.

. Work closely with Dev and Business Analyst team to understand the functional requirements.

. Actively participate in squad ceremonies Sprint Refinements, Planning, Retrospective and

daily standups.

. Ability to learn new things and exhibit innovative testing approach.

. Strong ability and problem-solving Skills.

You must have:

. Ability to test applications thoroughly before deployment to ensure that they are free of

errors.

. 2-7 years 'experience in test automation or feature development (programming experience)

. Should be able to work with geographically dispersed Dev & QA team in a very dynamic,

rapidly evolving, and high pressure, high visibility project setting.

. Experience of working in a fast-paced Agile framework.

. Ability to challenge status quo and think of out-of-the box solutions to existing problems.

. Excellent problem-solving skills.

. Knowledge of trade lifecycle. product types/asset class types.

. Willingness to guide fellow team members in learning new technologies.

You might also have:

. Understanding of DevOps for complex systems

. Knowledge of Transaction Reporting, OTC Derivatives, Post Trade processing activities.

. Experience with continuous deployment tools and practices

. Experience with automation tools such as Python/PowerBI

3-5 years of experience in manual and auto testing through Selenium

Write all automation scripts for Backend and Frontend

Document Test Cases.

• Develop and maintain automation suite throughout the product life cycle.
• Develop data driven test automation scripts and execute tests.
• Utilize innovative test technologies to develop application testing strategy.
• Analyse and debug the test data to identify the root cause of failures.
• Actively communicate test progress, results and other relevant information to project

stakeholders.

• Collaborate with other team members and stakeholders

Skills Required -

• No handholding
• Logical thinking (scenario)
• API testing (POSTMAN)
• Database SQL (think of null & able to write join query)
• Why & when regression and different types of testing
• Able to write test case
• Web testing

Requirements:

·  UIPath certification

·  Proficient in UI Path Platform, Test Manage, Test Suite, with 6+ years of Experience on Test Automation

·  Hands-on experience in building automated scripts using Low-Code No-Code Platform (UIpath)

·  Experience on Testing SOAP or REST API

·  Experience building data driven tests and frameworks for Web, Windows, and Micro services.

·  Understanding of test methodologies (regression, functional, unit, integration, code coverage, performance, etc.)

·  Experience building data driven tests and frameworks for Web, Windows, and Micro services.

·  Designing and developing test automation frameworks and understanding of test automation design patterns and software testing principles.

·  Familiarity with Relational Databases and SQL

·  Bachelor's degree in computer science, engineering or related field

·  Minimum of 7 years of experience in software testing and test automation

·  Minimum of 5 years of experience in UIPath test automation

·  Strong knowledge of test automation frameworks and tools

·  Experience with continuous integration and continuous delivery (CI/CD) pipelines

·  Ability to analyze and debug complex issues

·  Excellent problem-solving skills

·  Strong communication skills and ability to work collaboratively in a team environment

·  Knowledge of agile methodologies

 Flexibility

Need to be flexible with respect to working times, provide two hours overlap with IST (Central Time) and UK time on an ongoing basis.

If you are passionate about test automation and have experience with UIPath, we encourage you to apply for this exciting opportunity. We offer a competitive salary, excellent benefits, and opportunities for growth and development.

• Work very closely with development teams to ensure technical specifications and final product meet business requirements. 
• Responsible for setting up and implementing test automation strategy from a Functional and Non-functional perspective for one module or multiple modules who you work with.
• Understand User Experience, design thinking, and its importance to product features.
• Responsible for the addition of new capabilities and features in the automation framework which is used by the entire QA team for test automation.

• +3 years of exposure to manual testing on different methodologies.
• Experience in generating test cases.
• QA knowledge in test automation for products or systems.
• Exposure to agile methodology, cross-browser testing, functional testing, Regression testing, and Performance testing.
• Prepare and submit status reports for minimizing exposure and risks on the project or closure of escalations.
• Experience in generating Test Case documentation.
• Strong Knowledge of Test Automation, Software Testing, Selenium, TestNg, API Testing, Jmeter, Appium, and Cucumber 8. 8. Framework
• Good to have knowledge of Jenkins (CI)
• Extent Report generation in selenium
• Programming language - Java (preferred), Javascript, Database

We are looking for Senior Web QA Test Engineer (Manual + Automation)

When building software, you go through many stages. From initial requirements to product launch, it’s integral to ensure that everything works according to specification.

That’s why we’re looking for a quality assurance engineer to help us maintain our world-renowned level of quality and reliability.

By joining our team, you will take part in various projects, assessing software quality by designing and implementing software testing processes. You will take ownership of code quality through exploratory and automated tests. You will hunt bugs, identify issues, report them, and see that they’re dealt with.

There are no shortcuts in achieving greatness: It’s a lot of work. But once you’re at the top, you’ll enjoy the view.

• Review and analyze requirements, specifications, and technical design documents, providing timely feedback
• Develop detailed, comprehensive, and well-structured test plans and test cases
• Prioritize and plan testing activities
• Play the role of test engineer: Design, develop, and execute automated tests
• Identify and report issues found, then verify that issues are resolved
• Perform regression testing

• Proven work experience in software quality assurance
• Strong knowledge of software QA methodologies, tools, and processes
• Hands-on experience with automated testing tools
• A keen eye for detail and a commitment to excellence
• Be willing to help your teammates, share your knowledge with them, and learn from them
• Be open to receiving constructive feedback and turning it into process improvements

Designation: Associate - QA

Office Location: Goregaon Mumbai

Position description: 2+ years of hands on experience in testing.

Primary Responsibilities:

• To work closely with software developers and product planners to understand more about what the product is for, its key features and the intended audience
• Required to carry out a mix of key functional and non-functional tests such as Sanity, Regression, Load, Security and Deployment
• Required to plan test cases in consultation with the stake holders
• Required to document all bugs and findings of these tests and ensuring they are addressed

Required Skills:

Mandatory: Passionate about sports, Problem solving, Team player, Target & Result oriented.

Functional: Manual Functional Testing of Web and Mobile Applications, Writing Test Cases, Regression Testing, Data Verification, GIT & JIRA, Basic Automation Testing,
Testing feeds - Understanding of JSON and XML structures, Testing tools like Postman, Swagger & Charles Proxy, Browser Development Tools,GIT & JIRA.

Role/Title: Functional QA

Location: Mumbai/Bangalore 

Fulltime/Permanent role

Notice period should not exceed more than 60days

Job Responsibilities:

Test Analyst:

• Good Communicator, 4 to 7 years, BFSI domain exp.(Investment banking/Capital Market/Wealth Management) is a must.

Skills & tools needed:

• Agile exp. and knowledge, end to end testing, UAT, regression, automation test frameworks.

Testing tools: JIRA, ALM

• Hands-on experience on test planning/test strategy, defect validation, sending status reports