₹14L – ₹25L a year estimatetypical for IT Jobs in Bangalore, 267 posts
Posted 22 hr ago Last checked 50 min ago
Free · takes a minute · your resume fills your profile
CoreHRx never asks candidates for money. If anyone does, .
Role at a glance
You will
The candidate should have hands-on experience in both manual and automation testing, including functional, API, integration, regression…
Perform functional, integration, regression, and end-to-end testing of E-Commerce and OMS applications.
Validate the complete order lifecycle, including order creation, processing, fulfilment, shipment, cancellation, returns, and refunds.
Experience
5–7 years
Must-have skills
AgileAutomation TestingScrum
How well do your skills match this job?
Sign in to see your fit: the skills, experience and location this job asks for, checked against your profile.
Job description
Location: Bengaluru, India
Job Description – E-Commerce / OMS / Marketplace QA Engineer Experience: 5–7 Years Role: QA Engineer – Manual & Automation Testing Domain: E-Commerce, Order Management System (OMS), Marketplace Job Summary We are looking for a QA Engineer with 5–7 years of experience in E-Commerce, OMS, and Marketplace application testing. The candidate should have hands-on experience in both manual and automation testing, including functional, API, integration, regression, and end-to-end testing. Key Responsibilities
Perform functional, integration, regression, and end-to-end testing of E-Commerce and OMS applications.
Validate the complete order lifecycle, including order creation, processing, fulfilment, shipment, cancellation, returns, and refunds.
Test OMS integrations with e-commerce platforms, marketplaces, payment gateways, ERP, and third-party logistics (3PL) systems.
Perform marketplace testing covering product catalogs, listings, pricing, inventory synchronization, and order processing.
Develop and maintain automated test scripts for functional and regression testing.
Perform UI automation and API automation using relevant testing frameworks.
Identify automation opportunities and contribute to building and maintaining automation frameworks.
Perform API testing using Postman or similar tools.
Validate payment processing, refunds, promotions, discounts, and tax calculations.
Prepare test scenarios, test cases, automation scripts, test data, and execution reports.
Track defects, coordinate with development teams, and support defect resolution.
Participate in UAT, release validation, and production testing.
Required Technical Skills
5–7 years of experience in Software Testing.
Hands-on experience in Manual and Automation Testing.
Strong understanding of E-Commerce and OMS business processes.
Experience in Marketplace platforms such as Mirakl or similar.
Automation experience using Selenium / Playwright / Cypress.
Programming knowledge in Java / JavaScript / Python.
API automation and testing using Postman / REST Assured or similar.
Knowledge of REST APIs, JSON, and XML.
SQL queries and database validation.
Experience with Jira or similar defect management tools.
Most IT Jobs posts in Bangalore ask for 3–6 years of experience (41% of 4454 that say).
Hiring most for IT Jobs in Bangalore
Bosch Group175 open jobs
Trigent Software Private Limited129 open jobs
Brillio115 open jobs
Jobs asking for Agile in Bangalore also ask for
CI/CD30%
Scrum29%
Python26%
SQL26%
Java24%
From live job posts on CoreHRx, updated 13 Nov 2026. Skill figures count posts that list their skills; salary figures only posts that show a salary.
Questions about this job
What is the salary for this Senior QC Engineer job?
The post does not state the pay. As an estimate, comparable posts on CoreHRx advertise ₹14L – ₹25L a year (typical for IT Jobs in Bangalore, 267 posts).
Preparing for an IT or software developer interview in India? This guide covers the rounds companies run, the technical and HR interview questions asked most often for freshers and experienced developers, sample answers you can adapt, and a simple preparation plan.
Questions you may be asked
Tell me about yourself.
Explain the four pillars of object-oriented programming.
What is the difference between a process and a thread?