QA Lead

HCL Healthcare; Sector 10; On-site; INR 900,000 - 1,400,000; Full time

Job summary

HCL Healthcare is seeking an experienced QA Lead to architect test strategy and drive automation across microservices. You will design rigorous test conditions from requirements, prioritize risks, and prevent defects early by challenging acceptance criteria in design reviews.

You will implement an automation framework, integrate tests into Jenkins/Bitbucket Pipelines, and ensure API and event-flow test coverage. Coaching others and measuring defect metrics are integral to the role.

Qualifications

• Derive test conditions from requirements using partitioning and boundary analysis.
• Prioritize tests by risk while protecting patient-safety and critical paths.
• Identify ambiguities early by reviewing acceptance criteria in design reviews.
• Test REST services independently of UI with proper schemas and codes.
• Build a test framework with CI integration and data-driven tests.
• Document defects with root-cause classification and metrics.
• Coach junior testers and reuse data and utilities across tests.

Responsibilities

• Identify opportunities during requirements gathering and design testing plans.
• Define QA strategy: manual vs automated tests and upstream prevention.
• Participate in refinement, challenge acceptance criteria, surface data gaps.
• Shape test automation framework structure and data strategy.
• Cover API and event-flow tests across microservices, independent of UI.
• Make release-risk calls with defensible go/no-go decisions.
• Mentor senior and junior testers through code reviews and pairing.
• Track QA metrics like defect leakage and removal efficiency.

Skills

Test design rigour

Risk-based prioritization

Shift-left/defect prevention

API & integration testing

Automation framework & CI

Defect & metrics discipline

Coaching & leverage

Tools

Postman

REST Assured

Jenkins

Bitbucket Pipelines

Kafka

RabbitMQ

Job description

Key Responsibilities:

• Identify opportunities during requirements gathering phase of development and design testing plan.
• QA strategy for the product what gets tested manually, what gets automated, what gets prevented upstream, and the reasoning behind each choice.
• Requirement and design review. You sit in refinement, challenge acceptance criteria, and surface undefined error states and data assumptions before development starts.
• The test automation framework structure, standards, test data strategy, and its integration into the Jenkins / Bitbucket pipeline, including which tests are permitted to fail a build.
• API and event-flow test coverage across our Spring Boot microservices, independent of the user interface.
• Release risk calls. When time is short, you decide the test scope, write down the residual risk, and give a defensible go / no-go recommendation.
• Raising the capability of the Senior, Mid-senior and Junior QA through test-case review, automation code review, pairing and reusable framework components.
• QA metrics that drive decisions defect leakage to production, defect removal efficiency, requirement to test coverage, automation pass and flake rate.

Must Have Requirements:

• Test design rigour - Derives test conditions from a requirement using equivalence partitioning, boundary values, decision tables and pairwise and can state what was deliberately not tested and why. The skill that turns 200 cases into 20 without losing coverage.
• Risk-based prioritization - Given a fixed release date and insufficient time, decides what to test on impact likelihood, weights patient-safety and payment paths first, and states residual risk in writing rather than asking for more time.
• Shift-left / defect prevention - Works inside requirements and design review. Authors or challenges acceptance criteria, finds ambiguity and undefined error states before code exists, and has changed a process so that a class of defect stopped recurring.
• API & integration testing - Tests REST services independently of the UI (Postman / REST Assured): schema, status codes, authentication and roles, idempotency. Reasons about asynchronous flows Kafka or RabbitMQ events, retries, dead-letter queues, duplicate delivery.
• Automation framework & CI - Has built a framework from zero, not only written scripts inside one: layered structure, externalised test data, parallel execution, reporting. Suite runs in Jenkins or Bitbucket Pipelines on merge, and they can defend which tests are allowed to fail a build.
• Defect & metrics discipline - Writes reproducible defects, classifies root cause by origin (requirement / design / code / data / environment), and uses defect leakage and removal efficiency to change process. Distinguishes decision metrics from vanity counts.
• Coaching & leverage - Reviews other testers test cases and automation code against a written standard. Raises a juniors output rather than absorbing their work. Builds reusable data and utility layers so less-experienced QAs contribute without framework knowledge.